do.while

im getting my head ever the Gen . I knew it will be quite hard *stuff* but i didnt know that it will really made me wondering about certain implementations so much for so long .

I dont know C lang but im friends with the javascript (i mean, i like him quite much but im not sure what that language thinks about me actually ), so i thought that it will somehow help me in thinking there . Not really .

Im trying to figure out how to construct the sample playback engine like a groove object .

I started from driving "peek" via "history" and "wrap" etc . (hacked from examples)

As a next step i would love to know how to implement the "retrigger" part , where provided value by the user or lets say boolean (trigger) would do two operations .

At first it will reset the "history" ,next it will push incrementing to run again .

As for now i can STOP or START as a separate process ,which is not what im trying to do at the moment . While resetting "history" i cant force it to increment again . I think i dont understand how the order works in Gen , nor assignments and conditions .

im getting my head ever the Gen . I knew it will be quite hard *stuff* but i didnt know that it will really made me wondering about certain implementations so much for so long .
I dont know C lang but im friends with the javascript (i mean, i like him quite much but im not sure what that language thinks about me actually ), so i thought that it will somehow help me in thinking there . Not really .
Im trying to figure out how to construct the sample playback engine like a groove object .
I started from driving "peek" via "history" and "wrap" etc . (hacked from examples)
As a next step i would love to know how to implement the "retrigger" part , where provided value by the user or lets say boolean (trigger) would do two operations .
At first it will reset the "history" ,next it will push incrementing to run again .
As for now i can STOP or START as a separate process ,which is not what im trying to do at the moment . While resetting "history" i cant force it to increment again . I think i dont understand how the order works in Gen , nor assignments and conditions . 

gen-sample-playback-retrigger

I added some sah goodness for the start and stop times since this has come up a number of times on the forum. If you don't want it, feel free to clear it out. I only implemented the looping portion of groove~. It's possible to

add the other, but I'll leave that out for now.

Feel free to tweak away. It has a minimum duration and a fade value that works with trapezoid~ so you can specify a fixed(ish) fade duration. Not production tested, but should be fun...

I added some sah goodness for the start and stop times since this has come up a number of times on the forum.  If you don't want it, feel free to clear it out.  I only implemented the looping portion of groove~.  It's possible to
add the other, but I'll leave that out for now.

Feel free to tweak away.  It has a minimum duration and a fade value that works with trapezoid~ so you can specify a fixed(ish) fade duration.  Not production tested, but should be fun...


Peter ! its a huge gift from ya . This makes a lot of sense to me . It also has appropriate use of "sah" which leads to other possible aspects that could be done , its powerful . youve opened my mind Peter . i see things now !

Also thanks for the click trigger , i wouldnt be able to figure that out , because triggering "bang => trigger 1 0 => sig~ => gen" wasnt working (even defferlow'ed).

Okay , so ... i will go with it ... within a week i will post some results .

ps: your click detection is suitable for "waveform" sync detection ? thats why you did not used "!=" ?

Peter ! its a huge gift from ya . This makes a lot of sense to me . It also has appropriate use of "sah" which leads to other possible aspects that could be done , its powerful . youve opened my mind Peter . i see things now !
Also thanks for the click trigger , i wouldnt be able to figure that out , because triggering "bang => trigger 1 0 => sig~ => gen"  wasnt working (even defferlow'ed).
Okay , so ... i will go with it ... within a week i will post some results .

ps: your click detection is suitable for "waveform" sync detection ? thats why you did not used "!=" ?


Exactly. That way it's not continually resyncing if you use an oscillator for triggering (or a comparator)

Exactly.  That way it's not continually resyncing if you use an oscillator for triggering (or a comparator)


GEN . Sample Playback (retrigger)