It goes to show that I could use a good read of that tutorial as well.

[wrap~] behaves sorta like a [mod] in that a steadily increasing input signal will result in an output signal that repeatedly slides from zero to one, and then jumps back to zero. It even takes of negative number correctly. However, unlike [mod], [wrap~] doesn't have any creation arguments so you're stuck between zero and one with just the [wrap~] object alone. So then I guess you would be stuck with trying to scale your input and outputs correctly just to make it behave.

Given that Maelstorm's idea is virtually the "[mod~]", and that you don't need floating points to index a table, you (and I) will probably find his idea way more intuitive.

[wrap~] maybe?

Exactly. I really just have a bunch of tape flying around in my head when I think of this stuff.

At least now I know a bit more about how a software buffer actually works.

Yeah that seems right. I find it pretty interesting that you think of the write pointer as something that travels along with and in front of the read pointer. . . while I have a much easier time thinking of the write pointer as something that's fixed while read pointer moves in front of it.

Different thinking, same idea I suppose.