Hey Frank,
Are there any tutorials or documentation on how to make a rradical gop abstraction? I would like to integrate some of my existing GOPs (and design some new ones) with this system so they can have integrated parameter control, state saving + etc. Any info appreciated - I have read the paper already which gives the general idea but before I go digging around I was wondering if there was anything already.
Also I think loading presets hangs my pd at this point, but I will post again when I have time to isolate the problem more.
Thanks, Kevin
Sorry, I am not Frank but I think I know the answer to this issue:
- Open an existing rrad abstraction
- Replace GUI and non-rrad guts with your own. (leave [pd memento]
and boxes connected to it intact) 3. Set up appropriate send/receive in GUIs and whatnot. 4. Open [pd memento], find the communs sends and replace them with your own. 5. enjo.
On 9/16/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Hey Frank,
Are there any tutorials or documentation on how to make a rradical gop abstraction? I would like to integrate some of my existing GOPs (and design some new ones) with this system so they can have integrated parameter control, state saving + etc. Any info appreciated - I have read the paper already which gives the general idea but before I go digging around I was wondering if there was anything already.
Also I think loading presets hangs my pd at this point, but I will post again when I have time to isolate the problem more.
Thanks, Kevin _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Michal, thanks for the info - I will give that a shot. Hopefully using rradical will do good things for my work!
k
On 9/16/07, Michal Seta mis@artengine.ca wrote:
Sorry, I am not Frank but I think I know the answer to this issue:
- Open an existing rrad abstraction
- Replace GUI and non-rrad guts with your own. (leave [pd memento]
and boxes connected to it intact) 3. Set up appropriate send/receive in GUIs and whatnot. 4. Open [pd memento], find the communs sends and replace them with your own. 5. enjo.
On 9/16/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Hey Frank,
Are there any tutorials or documentation on how to make a rradical gop abstraction? I would like to integrate some of my existing GOPs (and
design
some new ones) with this system so they can have integrated parameter control, state saving + etc. Any info appreciated - I have read the
paper
already which gives the general idea but before I go digging around I
was
wondering if there was anything already.
Also I think loading presets hangs my pd at this point, but I will post again when I have time to isolate the problem more.
Thanks, Kevin _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hallo, Michal Seta hat gesagt: // Michal Seta wrote:
Sorry, I am not Frank but I think I know the answer to this issue:
- Open an existing rrad abstraction
- Replace GUI and non-rrad guts with your own. (leave [pd memento]
and boxes connected to it intact) 3. Set up appropriate send/receive in GUIs and whatnot. 4. Open [pd memento], find the communs sends and replace them with your own. 5. enjo.
Yep, that's basically it. The basic rules are this:
Put an object [originator $1 $0] into your abstraction.
connect the leftmost inlets and outlets of that originator to the leftmost inlets and outlets of your abstraction. (That's just a convention, though.)
For everthing you want to save, create a [commun /NAME $0] object and cross-connect its inlets and outlets to the thing you want to save, either a $0-local send/receive or directly. Replace "/NAME" with something useful.
By cross-connect I mean, that you should connect the outlets of an object whose state you want to save to the inlet of the commun and the inlets to the outlets of commun.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
Last question - what about persistent arrays in abstractions? Any advice about that? Some of my GOPs are table/array based, often for drawable control data.. I don't think I saw anything about this yet. I am willing to give a shot at developing something for it if it is not included yet.
Thanks again! Kevin
On 9/16/07, Frank Barknecht fbar@footils.org wrote:
Hallo, Michal Seta hat gesagt: // Michal Seta wrote:
Sorry, I am not Frank but I think I know the answer to this issue:
- Open an existing rrad abstraction
- Replace GUI and non-rrad guts with your own. (leave [pd memento]
and boxes connected to it intact) 3. Set up appropriate send/receive in GUIs and whatnot. 4. Open [pd memento], find the communs sends and replace them with your
own.
- enjo.
Yep, that's basically it. The basic rules are this:
Put an object [originator $1 $0] into your abstraction.
connect the leftmost inlets and outlets of that originator to the leftmost inlets and outlets of your abstraction. (That's just a convention, though.)
For everthing you want to save, create a [commun /NAME $0] object and cross-connect its inlets and outlets to the thing you want to save, either a $0-local send/receive or directly. Replace "/NAME" with something useful.
By cross-connect I mean, that you should connect the outlets of an object whose state you want to save to the inlet of the commun and the inlets to the outlets of commun.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi Kevin,For this in rradical/memento I added a "save-bang" to [careGUI], and had that dump the tables as lists into communs just before the data was written. On load i'd measure the list length, resize the table and dump it back in - it worked great. It's been a while since I've had time to even open Pd, but if you need me to show an example I'd be more than happy to use it as an excuse to do so : ).
Cheers Luke
On 9/16/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Last question - what about persistent arrays in abstractions? Any advice about that? Some of my GOPs are table/array based, often for drawable control data.. I don't think I saw anything about this yet. I am willing to give a shot at developing something for it if it is not included yet.
Thanks again! Kevin
On 9/16/07, Frank Barknecht fbar@footils.org wrote:
Hallo, Michal Seta hat gesagt: // Michal Seta wrote:
Sorry, I am not Frank but I think I know the answer to this issue:
- Open an existing rrad abstraction
- Replace GUI and non-rrad guts with your own. (leave [pd memento]
and boxes connected to it intact) 3. Set up appropriate send/receive in GUIs and whatnot. 4. Open [pd memento], find the communs sends and replace them with
your own.
- enjo.
Yep, that's basically it. The basic rules are this:
Put an object [originator $1 $0] into your abstraction.
connect the leftmost inlets and outlets of that originator to the leftmost inlets and outlets of your abstraction. (That's just a convention, though.)
For everthing you want to save, create a [commun /NAME $0] object and cross-connect its inlets and outlets to the thing you want to save, either a $0-local send/receive or directly. Replace "/NAME" with something useful.
By cross-connect I mean, that you should connect the outlets of an object whose state you want to save to the inlet of the commun and the inlets to the outlets of commun.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.infohttp://lists.puredata.info/listinfo/pd-list /listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.infohttp://lists.puredata.info/listinfo/pd-list /listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
Hey Luke, that would be great if you could show me some of that, I would really appreciate it.
Thanks, Kevin
On 9/17/07, Luke Iannini (pd) lukexipd@gmail.com wrote:
Hi Kevin,For this in rradical/memento I added a "save-bang" to [careGUI], and had that dump the tables as lists into communs just before the data was written. On load i'd measure the list length, resize the table and dump it back in - it worked great. It's been a while since I've had time to even open Pd, but if you need me to show an example I'd be more than happy to use it as an excuse to do so : ).
Cheers Luke
On 9/16/07, Kevin McCoy < km.takewithyou@gmail.com> wrote:
Last question - what about persistent arrays in abstractions? Any advice about that? Some of my GOPs are table/array based, often for drawable control data.. I don't think I saw anything about this yet. I am willing to give a shot at developing something for it if it is not included yet.
Thanks again! Kevin
On 9/16/07, Frank Barknecht <fbar@footils.org > wrote:
Hallo, Michal Seta hat gesagt: // Michal Seta wrote:
Sorry, I am not Frank but I think I know the answer to this issue:
- Open an existing rrad abstraction
- Replace GUI and non-rrad guts with your own. (leave [pd
memento]
and boxes connected to it intact) 3. Set up appropriate send/receive in GUIs and whatnot. 4. Open [pd memento], find the communs sends and replace them with
your own.
- enjo.
Yep, that's basically it. The basic rules are this:
Put an object [originator $1 $0] into your abstraction.
connect the leftmost inlets and outlets of that originator to the leftmost inlets and outlets of your abstraction. (That's just a convention, though.)
For everthing you want to save, create a [commun /NAME $0] object and cross-connect its inlets and outlets to the thing you want to save, either a $0-local send/receive or directly. Replace "/NAME" with something useful.
By cross-connect I mean, that you should connect the outlets of an object whose state you want to save to the inlet of the commun and the inlets to the outlets of commun.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.infohttp://lists.puredata.info/listinfo/pd-list /listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.infohttp://lists.puredata.info/listinfo/pd-list/listinfo/pd-listhttp://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 9/17/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Hey Luke, that would be great if you could show me some of that, I would really appreciate it.
OK, I dug up the code. I'm just including my full-blown careGUI replacement, but the only change necessary for this is the [t b b] split from the "save" button, with the right bang banging [s SAVE_PREP] before actually sending the save message to [caretaker].
The SAVE_PREP then bangs some zexy objects (I think they're zexy), which grab the size and contents of the array and put them into commun, so the when the left bang (from the t b b described above) fires, the data is in commun and waiting to be written. On load, I split off the table size parameter to resize the table (in case it's been resized since), then dump the data back in with [tabset] (again, I think from zexy).
You could definitely achieve this without any of those externals; I just figured they'd be faster. I'll leave that as an exercise : ).
Hope that helps! Luke
Um, mail clients should search for the words "I'm including" or "attached is" and yell at the user when they forget to do so : ). On 9/18/07, Luke Iannini (pd) lukexipd@gmail.com wrote:
On 9/17/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Hey Luke, that would be great if you could show me some of that, I would really appreciate it.
OK, I dug up the code. I'm just including my full-blown careGUI replacement, but the only change necessary for this is the [t b b] split from the "save" button, with the right bang banging [s SAVE_PREP] before actually sending the save message to [caretaker].
The SAVE_PREP then bangs some zexy objects (I think they're zexy), which grab the size and contents of the array and put them into commun, so the when the left bang (from the t b b described above) fires, the data is in commun and waiting to be written.
On load, I split off the table size parameter to resize the table (in case it's been resized since), then dump the data back in with [tabset] (again, I think from zexy).
You could definitely achieve this without any of those externals; I just figured they'd be faster. I'll leave that as an exercise : ).
Hope that helps! Luke
-
Frank Barknecht -
Kevin McCoy -
Luke Iannini (pd) -
Michal Seta