Ive been having some hardware issues with my Seed Oopsy Patches where sometimes the unit will power up in an confused state with some options being inactive.
I would like to create a start up cycle within my gen patch whereby on power up I
I force the seed into a known state (perhaps using the @default parameters) for say 1000 ms and then revert to the settings as set by the knobs and switches.
Could the “hang up/lock up” have something to do with having oopsy.ctrl.smooth3 directly after the input of all my hardware Pots? Ive noticed if I change something in the Max Patch that has oopsy.ctrl.smooth3 in the pots patch cord path that I have to wake up the program parameter by adjusting the pots value. ?
The oopsy.ctrl.smooth3 function hasnt been an issue before but this effect has quite complex switching and as such i’m trying to work out what is causing the SW “hangups”.
I can’t find the page number right now, but in the new gen~ book (Generating Sound & Organizing Time) some patches use an [elapsed == 0] object that seems to function similar to loadmess… I had never used that object before, so seeing it in the book stuck with me…