THANK YOU FOR THE REPLY!!!!
Tuukka Jääskeläinen
1

Hi, and thank you for coming back to Glitch!

Glitch is now much more than a bytebeat synthesizer and we had to change the syntax a bit. Now the primary range of the output signal is [-1..+1], because it’s much easier to control it with math (e.g. modulate or mix together). Also, there is no automatic wrapping if the signal reaches the upper limit.

It was not an easy decision, because it broke backwards compatibility. But we tried to make the migration as easy as possible — there is a special function byte() that converts bytebeat range [0..255] to a more common glitch range [-1..+1] and performs the overflow if needed. Simply wrap your bytebeat formula into byte() function and it should work.

You formula most likely can be rewritten like this: q=t*10.08, byte(q*(4&q>>8)|q/8)

It’s worth mentioning that since byte() operates in a normal signal range — you can now use filters, sequencers, delay and all other niceties of glitch with your bytebeat tunes, for example:

bb=byte(t*(42&t>>10))
bpm = 117.1875
mix(
 0.2*lpf(delay(bb, 60/bpm/4, 0.4, 0.4), 2000)
 tr808(BD, seq(bpm*2, 0.5, (0.5, 0.2, 0.2)))
 tr808(SD, seq(bpm*2, 0, 1))
 tr808(HH, seq(bpm*4, r()))
)

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.