I've been trying to figure out a way to open and load a PD patch as a subpatch. I've been experimenting with [openpanel] and [openpatch], however it just opens the patch and doesn't create a subpatch.

I thought about putting a loadbang in the patches that would then copy all the information in the patch and paste it into a subpatch. But I figured it would have to use shell commands and I'm not too savy with those.

Any help would be greatly appreciated

Save a patch to file (ie 'my-patch.pd') and then create an object of the same name (ie. [my-patch] ). Inlets and outlets work as in sub-patches, and you also have the added feature of creation arguments.

Then you should be able to do this:

[obj 0 0 my-abstraction(
|
[iemguts/sendcanvas]

where 0 0 is the x-y coordinate where you want the object to appear.

If you don't want to use an external, you can use [namecanvas] instead of [sendcanvas], or even [send pd-my_canvas_name].

You can also use [openpanel] to choose the abstraction if you want, but you'll have to split the .pd off the end of the symbol.

[bng]
|
[openpanel]
|
[symbol2list /]
|
[unpack s s s]
           /
[symbol2list .]
|
[unpack s s]
         /
[obj 0 0 $1(
|
[iemguts/sendcanvas]

Now the tricky part is to get the abstraction to automatically send and recieve information from the parent patch. I'm currently using [s~] / [r~] however the [r~] in the abstraction doesn't seem to be working. If I connect information into the inlet of the abstraction it'll work, but ideally I would like information to be sent to and from the abstraction automatically upon creation.

However, I'm encountering a new issue now. I'm running the aforementioned patch as an abstraction with the [bang] and [inlets]/[outlets] in the parent window using parent-to-graph. However, information isn't sent to the loaded abstraction until it is saved

My question is; does an external exist that saves an abstraction/patch. A simple ctrl+S in the abstraction resolves this issue, so I'm looking to streamline the process.

THANKS

Or....... if you bury the abstraction 2 levels down (in another empty abstraction....... gui's will show through more than one gop window) then you can send the [clear( message to clear that window....... so removing your "put" abstraction before you load another one, or before you finally resave the empty parent.
David.

Note that in L2Ork and Purr data, loadbang *does work with dynamic patch creation, so if you're using those platforms then this isn't the problem.

THANKS AGAIN FOR ALL THE HELP

I tried changing all of the sends and receives to [s~ $2Lin], [s~ $2Rin] etc... But the Pd terminal is saying there's no matching sends
I switched over to [throw~] / [catch~] and got a nice signal flow, however I'm planning on having multiple instances of the same abstraction.

I'm really stumped with this one

Thanks again for all the help!! This is proving to be a much bigger undertaking than I planned, but I'm liking the challenge

Because the effects are abstractions $0 will not work.
The effect can be given it's identifier here.......

It needs to be initiated at the creation of the loader, so it would be good if it were $1.

I have built you a system that will work, using an extra blank abstraction "[rack]" to hold the effects.
The effects inherit $1 from each [effectloader] so that the audio is kept separate.
You will need to check your parameter saving as I have stolen $1 for the new numbering system.
Please BACK UP your current folder before playing with this!
effect_loader_test_1.zip

Hmm..... I can never leave it alone......
The delete (old effect) is not working as I expected. I think the effects in the rack will need "place-holders" (sub-patches) so that a [clear( message can be sent instead of using [iemguts/canvasdelete]
Otherwise it is not possible to keep track of the order in which effects are created...........
I will post a new version of the test soon.
David.

I substituted [initbang] for just a [bang] and I was able to see how the 'rack' system works, but I feel like I'm gonna need [initbang] or some sort of workaround to get this working.

Looking ahead, the final step that would make this an effect tool would be an 'open' button in the graph-to-parent, one that would just 'open' the window/abstraction that the effect was in so you can edit parameters

Thanks again for all the help
-Sean

And this gets you part way to opening the effect..... effect_loader_test_3.zip
There is an edit button in the [effectloader] gop window.
If you give your effect abstractions a gop window then the parameters will appear when the edit button is clicked (and close when clicked again).......
You might have to resize the gop's in the rack.......... big enough for all your sliders.
David.