http://puredata.hurleur.com/sujet-6417-dollar-signs-objects-messages
On Sun, Nov 17, 2013 at 1:32 PM, Billy Stiltner billy.stilt...@gmail.comwrote:
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
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
hey,
I have been trying to rename sends and receives of dials at runtime
they need actual literal $0 in their name.
so I tried this with sending a 0 to $$4 in a message
it worked for the literal renaming but the patch gets messed up after
saving and reloading.
somehow the patch does need to be
On Fri, 2013-11-15 at 09:06 -0500, Billy Stiltner wrote:
hey,
I have been trying to rename sends and receives of dials at runtime
they need actual literal $0 in their name.
so I tried this with sending a 0 to $$4 in a message
it worked for the literal renaming but the patch
hell yeah Roman,
thanks that works great.
Your solution is brilliant.
I'm using it to switch a set of controls so that I can load more
synthesizers up and not have that TCL screen redrawing processor hog
activity.
for instance a synth currently consists of osc, osc2,
env1,env2,lfo1,lfo2. If
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
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
