Hi,
I've looked at the sssad examples and searched the list (including a discussion this week on the topic) and I still have questions about using sssad to save settings of GUI objects in a particular abstraction or subpatch while ignoring sssad objects used in other subpatches or abstractions within the parent patch. I've looked through the sssad abstractions to try to figure out how arguments are passed along, and just kind of got lost without understanding what was doing what.
I've found the sssad implementation in McCormick's s-abstractions to be extremely useful, and I'd like to make a couple of tweaks to it so it will work for this specific purpose.
I'll try to be specific with my questions:
- do I need to add an argument or $0 variable to the sssad instance within
the abstraction that gets the special sssad treatment? 2. do i need to add arguments or variables to any of the sssad or SSSAD objects, sends & receives & such, within the sssad patches?
I hope this makes sense.
Joe
Hallo Joe, Joe Newlin hat gesagt: // Joe Newlin wrote:
I've looked at the sssad examples and searched the list (including a discussion this week on the topic) and I still have questions about using sssad to save settings of GUI objects in a particular abstraction or subpatch while ignoring sssad objects used in other subpatches or abstractions within the parent patch. I've looked through the sssad abstractions to try to figure out how arguments are passed along, and just kind of got lost without understanding what was doing what.
Yeah, the documentation of that part can be enhanced...
I put together a little example in the attachement: Basically what a local sssad created with $0 as second argument [sssad NAME $0] does is exchange the global receivers [r SSSAD] and [r SSSAD_ADMIN] with local ones calle [r $0-SSSAD] and [r $0-SSSAD_ADMIN]. Then you use these just like the global ones.
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
Thanks for that demonstration, Frank, and though I think the concept is pretty straightforward, I still can't get my particular implementation working right.
I can see in your example how the SSSAD messages are being sent and received locally. But I'm having trouble making the leap from there to saving and loading lists to textfiles.
I have Chris McCormick's global sssad implementation working perfectly in my parent patch. And I can get robotcowboy's rc-sssad collecting local data from my subpatch in a message object. But I can't seem to figure out how to combine the two concepts to that I can save local data to a text file (and load from a text file).
In the s-abstraction version, simply replacing all SSSAD with $0-SSSAD and SSSAD_ADMIN with $0-SSSAD_ADMIN doesn't do the trick (not sure whether SSSAD_SAVE should be $0-SSSAD_SAVE, but I've tried it both ways with no success). Ultimately I get an un-findable "write failed" error, I assume from the [textfile].
I've tried chasing the data from the "save as" down the line, and I get lost at the [s SSSAD-SAVE] because I can't figure out where it's sending to.
I notice that in the sssad objects in abs-number-local you don't add variables to the SSSAD objects, which also has me a little confused.
I'm approaching PD as an instrumentalist, not a programmer, so I appreciate your patience.
JN
On Sat, Dec 6, 2008 at 2:43 AM, Frank Barknecht fbar@footils.org wrote:
Hallo Joe, Joe Newlin hat gesagt: // Joe Newlin wrote:
I've looked at the sssad examples and searched the list (including a discussion this week on the topic) and I still have questions about using sssad to save settings of GUI objects in a particular abstraction or subpatch while ignoring sssad objects used in other subpatches or abstractions within the parent patch. I've looked through the sssad abstractions to try to figure out how arguments are passed along, and
just
kind of got lost without understanding what was doing what.
Yeah, the documentation of that part can be enhanced...
I put together a little example in the attachement: Basically what a local sssad created with $0 as second argument [sssad NAME $0] does is exchange the global receivers [r SSSAD] and [r SSSAD_ADMIN] with local ones calle [r $0-SSSAD] and [r $0-SSSAD_ADMIN]. Then you use these just like the global ones.
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Joe Newlin hat gesagt: // Joe Newlin wrote:
Thanks for that demonstration, Frank, and though I think the concept is pretty straightforward, I still can't get my particular implementation working right.
I can see in your example how the SSSAD messages are being sent and received locally. But I'm having trouble making the leap from there to saving and loading lists to textfiles.
I have Chris McCormick's global sssad implementation working perfectly in my parent patch. And I can get robotcowboy's rc-sssad collecting local data from my subpatch in a message object. But I can't seem to figure out how to combine the two concepts to that I can save local data to a text file (and load from a text file).
I attached a little variation to my previous patch. The only chang is in number-abs-local.pd, which now includes an object called [sssad-loader $0]. Take a close look at its internals to check out local saving. It accepts "save FILENAME" and "load FILENAME" messages and will restore rsp. store local settings from rsp. into that file.
You have to pass the parent patch's $0 to this sssad-loader abstraction as a creation argument, there it is used as $1 in the names of the SSSAD-receivers.
The three GUI bangs in number-abs-local.pd are used to demonstrate this. There is a settings.txt which you can load settings from (first select that file with the yellowish "file" bang once) or write settings into it.
You should be able to exchange the settings in both instances of number-abs-local.pd by selecting settings.txt in both of them and playing with the save/load bangs.
If anything isn't clear (which probably will happen) please ask more! ;)
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
Hi, Frank-
This still isn't working for me. I bang the File to set the textfile to a new file in the same directory as the MAIN patch. But when I bang Save I get this in the pd window:
error: D:/+Audio_Sync/pd/sssad-ex-2/tester.txt: write failed
The only modification I made to your patches is changing [sssad number $0] to [sssad/sssad number $0] & respectively with number2.
Thanks,
JN
On Sun, Dec 7, 2008 at 11:49 AM, Frank Barknecht fbar@footils.org wrote:
Hallo, Joe Newlin hat gesagt: // Joe Newlin wrote:
Thanks for that demonstration, Frank, and though I think the concept is pretty straightforward, I still can't get my particular implementation working right.
I can see in your example how the SSSAD messages are being sent and
received
locally. But I'm having trouble making the leap from there to saving and loading lists to textfiles.
I have Chris McCormick's global sssad implementation working perfectly in
my
parent patch. And I can get robotcowboy's rc-sssad collecting local data from my subpatch in a message object. But I can't seem to figure out how
to
combine the two concepts to that I can save local data to a text file
(and
load from a text file).
I attached a little variation to my previous patch. The only chang is in number-abs-local.pd, which now includes an object called [sssad-loader $0]. Take a close look at its internals to check out local saving. It accepts "save FILENAME" and "load FILENAME" messages and will restore rsp. store local settings from rsp. into that file.
You have to pass the parent patch's $0 to this sssad-loader abstraction as a creation argument, there it is used as $1 in the names of the SSSAD-receivers.
The three GUI bangs in number-abs-local.pd are used to demonstrate this. There is a settings.txt which you can load settings from (first select that file with the yellowish "file" bang once) or write settings into it.
You should be able to exchange the settings in both instances of number-abs-local.pd by selecting settings.txt in both of them and playing with the save/load bangs.
If anything isn't clear (which probably will happen) please ask more! ;)
Ciao
Frank Barknecht Do You RjDj.me? _ ______footils.org__
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Joe Newlin hat gesagt: // Joe Newlin wrote:
This still isn't working for me. I bang the File to set the textfile to a new file in the same directory as the MAIN patch. But when I bang Save I get this in the pd window:
error: D:/+Audio_Sync/pd/sssad-ex-2/tester.txt: write failed
Can you use the "print" message in sssad-loader to see, if something is in the [textfile]? [textfile] won't save empty files, so you maybe have to change some numberboxes first.
The only modification I made to your patches is changing [sssad number $0] to [sssad/sssad number $0] & respectively with number2.
As long as your sssad/sssad.pd supports local saving (i.e. is new enough) this should work as well. (I'm not such a big fan of using a prefix for a single-object library but that's another story. [import sssad] or so on pd-extended should work as well.)
Ciao
Frank
I downloaded & reinstalled pd 0.40.3-extended, cleaned up the search paths so that sssad objects load without prefixes, changed the values in the number boxes, set the textfile, tried to save, and got the same write failed error.
Thanks,
JN
On Sun, Dec 7, 2008 at 4:14 PM, Frank Barknecht fbar@footils.org wrote:
Hallo, Joe Newlin hat gesagt: // Joe Newlin wrote:
This still isn't working for me. I bang the File to set the textfile to a new file in the same directory as the MAIN patch. But when I bang Save I
get
this in the pd window:
error: D:/+Audio_Sync/pd/sssad-ex-2/tester.txt: write failed
Can you use the "print" message in sssad-loader to see, if something is in the [textfile]? [textfile] won't save empty files, so you maybe have to change some numberboxes first.
The only modification I made to your patches is changing [sssad number
$0]
to [sssad/sssad number $0] & respectively with number2.
As long as your sssad/sssad.pd supports local saving (i.e. is new enough) this should work as well. (I'm not such a big fan of using a prefix for a single-object library but that's another story. [import sssad] or so on pd-extended should work as well.)
Ciao
Frank
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Joe Newlin hat gesagt: // Joe Newlin wrote:
I downloaded & reinstalled pd 0.40.3-extended, cleaned up the search paths so that sssad objects load without prefixes, changed the values in the number boxes, set the textfile, tried to save, and got the same write failed error.
sssad in pd-extended is out of date.
You can check out the latest version from the Subverson repository here: http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/abstractions/foo...
Ciao
Frank
I seem to remember reading that recently. Anyway, that did the trick.
Thanks. Now I can finally arrange songs by sequencing sssad preset loading.
JN
On Mon, Dec 8, 2008 at 12:38 AM, Frank Barknecht fbar@footils.org wrote:
Hallo, Joe Newlin hat gesagt: // Joe Newlin wrote:
I downloaded & reinstalled pd 0.40.3-extended, cleaned up the search
paths
so that sssad objects load without prefixes, changed the values in the number boxes, set the textfile, tried to save, and got the same write
failed
error.
sssad in pd-extended is out of date.
You can check out the latest version from the Subverson repository here:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/abstractions/foo...
Ciao
Frank
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Frank Barknecht -
Joe Newlin