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 able to be edited and saved without changeing the $$4 to a $$4 once reloaded after a save.
this is what the patch looks like from the .pd file after a save.
#X msg 188 -194 ; $1-o$2-waveform-rx receive $$4-o$3-waveform-rx ; $1-o$2-dt-rx receive-rx $$4-o$3-dt-rx ; $1-env$2-o$2-dt-rx receive $$4-env$3-o$3-dt-rx ; $1-lfo$2-o$2-dt-rx receive $$4-lfo$3-o$3-dt-rx ; $1-o$2-pw receive-rx $$4-o$3-pw-rx ; $1-env$2-o$2-pw-rx receive $$4-env$3-o$3-pw-rx ; $1-lfo$2-o$2-pw-rx receive $$4-lfo$3-o$3-pw-rx ; $1-env$2-o$2-rx receive $$4-env$3-o$3-rx ; $1-lfo$2-o$2-rx receive $$4-lfo$3-o$3-rx; #X msg -109 -193 ; $1-o$2-waveform-rx send $$4-o$3-waveform ; $1-o$2-dt-rx send $$4-o$3-dt ; $1-env$2-o$2-dt-rx send $$4-env$3-o$3-dt ; $1-lfo$2-o$2-dt-rx send $$4-lfo$3-o$3-dt ; $1-o$2-pw-rx send $$4-o$3-pw ; $1-env$2-o$2-pw-rx send $$4-env$3-o$3-pw ; $1-lfo$2-o$2-pw-rx send $$4-lfo$3-o$3-pw ; $1-env$2-o$2-rx send $$4-env$3-o$3 ; $1-lfo$2-o$2-rx send $$4-lfo$3-o$3;
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 gets messed up after saving and reloading.
I might have a found a way that doesn't mess up the patch after saving, but I still consider it somewhat hack-ish.
I'm not clear of the purpose of what you want to achieve, though. You can only convert the receivenames to use $0 once, so it seems easier to use a text editor to edit the pd file. Or if you set the receive names dynamically whenever you fire up the patch, you could instead use the real number instead of the variable $0.
Roman
somehow the patch does need to be able to be edited and saved without changeing the $$4 to a $$4 once reloaded after a save.
this is what the patch looks like from the .pd file after a save.
#X msg 188 -194 ; $1-o$2-waveform-rx receive $$4-o$3-waveform-rx ; $1-o$2-dt-rx receive-rx $$4-o$3-dt-rx ; $1-env$2-o$2-dt-rx receive $$4-env$3-o$3-dt-rx ; $1-lfo$2-o$2-dt-rx receive
$$4-lfo$3-o$3-dt-rx ; $1-o$2-pw receive-rx $$4-o$3-pw-rx ; $1-env$2-o$2-pw-rx receive $$4-env$3-o$3-pw-rx ; $1-lfo$2-o$2-pw-rx receive
$$4-lfo$3-o$3-pw-rx ; $1-env$2-o$2-rx receive $$4-env$3-o$3-rx ; $1-lfo$2-o
$2-rx receive $$4-lfo$3-o$3-rx; #X msg -109 -193 ; $1-o$2-waveform-rx send $$4-o$3-waveform ; $1-o$2-dt-rx send $$4-o$3-dt ; $1-env$2-o$2-dt-rx send
$$4-env$3-o$3-dt ; $1-lfo$2-o$2-dt-rx send $$4-lfo$3-o$3-dt ; $1-o$2-pw-rx send $$4-o$3-pw ; $1-env$2-o$2-pw-rx send $$4-env$3-o$3-pw ; $1-lfo$2-o$2-pw-rx send $$4-lfo$3-o$3-pw ; $1-env$2-o
$2-rx send $$4-env$3-o$3 ; $1-lfo$2-o$2-rx send $$4-lfo$3-o$3; ______________________________________________________________________
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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 I can reduce the controls so that there are only 3 sets then the screen area took up by 1 synth will almost be reduced to 1/2. so like the osc guis can control either osc1 or osc2 instead of having a set of controls each for osc1 and osc2. during all of my realtime performance adjustments to patches and even my patch building I never adjust more than one parameter at a time. I guess a better Idea would be to make numberbox controls for everything instead of the gui controls but the gui controls are much cooler.
On Fri, Nov 15, 2013 at 12:02 PM, Roman Haefeli reduzent@gmail.com wrote:
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 gets messed up after saving and reloading.
I might have a found a way that doesn't mess up the patch after saving, but I still consider it somewhat hack-ish.
I'm not clear of the purpose of what you want to achieve, though. You can only convert the receivenames to use $0 once, so it seems easier to use a text editor to edit the pd file. Or if you set the receive names dynamically whenever you fire up the patch, you could instead use the real number instead of the variable $0.
Roman
somehow the patch does need to be able to be edited and saved without changeing the $$4 to a $$4 once reloaded after a save.
this is what the patch looks like from the .pd file after a save.
#X msg 188 -194 ; $1-o$2-waveform-rx receive $$4-o$3-waveform-rx ; $1-o$2-dt-rx receive-rx $$4-o$3-dt-rx ; $1-env$2-o$2-dt-rx receive $$4-env$3-o$3-dt-rx ; $1-lfo$2-o$2-dt-rx receive
$$4-lfo$3-o$3-dt-rx ; $1-o$2-pw receive-rx $$4-o$3-pw-rx ; $1-env$2-o$2-pw-rx receive $$4-env$3-o$3-pw-rx ; $1-lfo$2-o$2-pw-rx receive
$$4-lfo$3-o$3-pw-rx ; $1-env$2-o$2-rx receive $$4-env$3-o$3-rx ; $1-lfo$2-o
$2-rx receive $$4-lfo$3-o$3-rx; #X msg -109 -193 ; $1-o$2-waveform-rx send $$4-o$3-waveform ; $1-o$2-dt-rx send $$4-o$3-dt ; $1-env$2-o$2-dt-rx send
$$4-env$3-o$3-dt ; $1-lfo$2-o$2-dt-rx send $$4-lfo$3-o$3-dt ; $1-o$2-pw-rx send $$4-o$3-pw ; $1-env$2-o$2-pw-rx send $$4-env$3-o$3-pw ; $1-lfo$2-o$2-pw-rx send $$4-lfo$3-o$3-pw ; $1-env$2-o
$2-rx send $$4-env$3-o$3 ; $1-lfo$2-o$2-rx send $$4-lfo$3-o$3; ______________________________________________________________________
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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
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.off@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
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.off@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.off@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
http://puredata.hurleur.com/sujet-6417-dollar-signs-objects-messages
On Sun, Nov 17, 2013 at 1:32 PM, Billy Stiltner billy.stiltner@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 hard.off@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.off@gmail.comwrote:
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
-
Billy Stiltner -
i go bananas -
Roman Haefeli