I believe the question of saving automation data has come up before, but this is a different question, I think.
I want to write and read the objects in a subpatch to and from textfiles; not the state of the objects, nor scalars, but the patch itself. Is there a way? I have 8 voices in my sequencer, and 8 subpatches for creating control values to send to csoundapi~. But each Csound orchestra I work with will have different parameters for different instruments, and so the 8 will be different from each other, as well as being different depending on what score I open in my Pd sequencer. So I gave up on using abstractions with arguments, because whenever I change one they all change. But AFAIK subpatches can't be read and written by sending messages to them. Any ideas? Is there a 'menusaveas' message or something? -Chuckk
Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
I believe the question of saving automation data has come up before, but this is a different question, I think.
I want to write and read the objects in a subpatch to and from textfiles; not the state of the objects, nor scalars, but the patch itself. Is there a way? I have 8 voices in my sequencer, and 8 subpatches for creating control values to send to csoundapi~. But each Csound orchestra I work with will have different parameters for different instruments, and so the 8 will be different from each other, as well as being different depending on what score I open in my Pd sequencer. So I gave up on using abstractions with arguments, because whenever I change one they all change. But AFAIK subpatches can't be read and written by sending messages to them. Any ideas? Is there a 'menusaveas' message or something?
Maybe you can script something with "select all" "copy and paste", but did you try to use one of the saving systems like [sssad] to save parameters? I don't know what exactly is in your subpatches, but I'm pretty sure [sssad] can be made to save it. (taking my mouth quite full here ;)
Ciao
Frank Barknecht _ ______footils.org__
On Nov 19, 2007 5:51 PM, Frank Barknecht fbar@footils.org wrote:
Hallo, Maybe you can script something with "select all" "copy and paste", but did you try to use one of the saving systems like [sssad] to save parameters? I don't know what exactly is in your subpatches, but I'm pretty sure [sssad] can be made to save it. (taking my mouth quite full here ;)
Thanks again, I'll check it out. I discovered that the message [; pd-abstraction.pd menuclose 1( closes abstraction.pd with no warning message, btw. I'm curious what other hidden messages I can discover peeking through code. Quite likely half the workarounds I cobbled together when first learning Pd were unnecessary.
-Chuckk
hey, I posted a pddp template some time ago which (I think) makes use of automated scripting. it loads the pd patch as a textfile into [textfile] and then scripts this into a subpatch. I am a little short of time right now, so explanation has to follow at a later point, sorry. get it at http://puredata.info/dev/pddp/pddp-drafts/template_ms1/view marius.
Chuckk Hubbard wrote:
I believe the question of saving automation data has come up before, but this is a different question, I think.
I want to write and read the objects in a subpatch to and from textfiles; not the state of the objects, nor scalars, but the patch itself. Is there a way? I have 8 voices in my sequencer, and 8 subpatches for creating control values to send to csoundapi~. But each Csound orchestra I work with will have different parameters for different instruments, and so the 8 will be different from each other, as well as being different depending on what score I open in my Pd sequencer. So I gave up on using abstractions with arguments, because whenever I change one they all change. But AFAIK subpatches can't be read and written by sending messages to them. Any ideas? Is there a 'menusaveas' message or something? -Chuckk
-
Chuckk Hubbard -
Frank Barknecht -
marius schebella