thnx i go bananas, the idea is to not use SSSAD or mmb's state saving abstractions
On Fri, Nov 15, 2013 at 11:12 PM, i go bananas <hard....@gmail.com> wrote: > and here's the same patch expanded a bit to include your $0 sends to > oscillators > > the only step that i haven't added here, is state saving. But now that > all your values are stored in the table, it is not too difficult to > read/write them using SSSAD or mmb's state saving abstractions, or whatever > system you choose. > > > > > On Sat, Nov 16, 2013 at 12:46 PM, i go bananas <hard....@gmail.com> wrote: > >> hi Billy, do you know that the gui's have a 'set' function. So, if you >> send [set 0.4( to a slider, for example, it will be set at that value, but >> the value is not actually passed on. >> >> If you store all your values for osc1, env1, lfo1 and osc2, env2, lfo2 in >> separate tables or float objects, then you can switch between different >> settings on your GUI objects, by using the set object to input the desired >> controls. >> >> anyway, i have a hangover, and this is harder to explain than i >> imagined... but i am attaching a patch to demonstrate >> >> >> >
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list