Alias Patches

[woodslanding]

I'm not sure if I've brought this up before, but one feature that would save me a huge amount of time in putting together wkps. LaTaneille's post reminded me of it:

To have the idea of an 'alias' patch, which is a copy of a source patch, such that when the source patch is modified, the alias is automatically modified the same way.

You would want all the cabling to be identical, but would want to allow for different positions in the GUI. Not sure how that would work, but since GUI positioning is not affected by undo-redo, I assume that info is stored differently already.

Since I use a lot of identical subpatches, which I am constantly improving, I spend a huge amount of time deleting many identical objects, and replacing them all with the new version of that object. Then I have to reposition the new versions in the GUI, if they have a visual component.

I know I asked about better alt-drag functionality for subpatches, but this feature would be much more useful for my purposes.

I'm told Max/MSP has this feature.....

Perhaps there is a way to do this already, with IML, but I haven't figured it out. Have the patches construct themselves by reading IML from a common source file or something.... But you would still lose the layout placement.

thanks,
-e

[bsork]

What about "Reload sub-patch"? . Reload patch is already available.

[gurulogic]

This is something that would save me a ton of time too...

The problem in both cases as I see it, is how to maintain positions of containers, or other ib items? within each patch while mirroring or reloading all other content?

[gurulogic]

I see a possible solution for this in correlation with my suggestion for movable XY inlets for the container module.
If there were a "get current line module" (or method) in conjunction with the current track module, these could be used to name receive busses according to which line or track the patch was on.
Then the position values for each container could be stored in a master patch with a data send bus for each patch that might get reloaded so that the containers would receive a default XY position depending on which track and line they were reloaded to.

I am pretty sure I could make an example with image panels, but afaik only for one line...

Senso, kill two birds with one stone?

[gurulogic]

Here's an example of what I am getting at (just replace image panel with container in your mind)
http://www.sensomusic.com/forums/upload ... reload.wkp

The panel X and Y outputs are not behaving for me at all right now (not working)(edit:, Ok I think it works now...) so I am not using feedback from the panel to set the coordinates in the XY pad, rather you have to set the initial placement of the panel with the XY balls.
Regardless, reloading the same patch across multiple tracks sets the panel position fine.

I think this would work well with either the original "Alias patches" suggestion, or patch reload...

[23fx23]

Yup, finding a way to make 'alias', or in 3D softwares that's called "Instances".

what i love in 3D using instances is you can ie make an object with some design on it.
when copy paste the object there is an option asking you "1_copy 2_instance 3_reference" i mostly use copy and instance:

if make a simple copy then can change both objects indepandantely./normal
if making instances any change on one of the objects will be reflected on all other objects, but you can still pick one object and say it's no more instancied if it needs a special tweak, all other keeping being instancied together.
Where it goes very deep is that a subpart can be disinstancied ie just change the color of object or it's position,
while all other parameter keeping being instancied, so if changing one shape, booth will update, keeping color indepandant.

that's different from a second option called "XRef".
Xref mean an object is pointing from another file. Any changes on the initial file will be reflected when reopening/reupdating
other files that are using the Xref object, and one must admit it comes naturally to mind especially with a 3d soft or a Patch oriented software, many patches are intended to be reused X times, maintenance might be easier.

As an example If we make a complex movie using 3D peoples spit over several shots/scenes(=wkps), if the client comes and say
"well i find the guy too fat can you make it slim", one modeler can make changes on modeling in a single file, all animators opening their shot/scenes will have it updated in, whithout loosing their animation (=wiring), and without having anything more to do. without the option it would be awful/impossible to match those often silly last minute requests.

so im also saying +1 for one of those features (or booth of course), and while i could understand it's not easy to implement, maybe a simpler "reload subpatch" or any other idea that could allow an easier maintenance of heavy clonedsubpatched parts would be cool.

[La Tenaille]

Hi,
That makes me think about css when creating web pages.
I also remember an audio soft (but not its name) that uses a "pool" with all the original wave files, and ghosts of these files that are used in multitrack.
...Usine with a "pool" of patches to drag wherever we want ?
My present trouble is same patches in different conductor banks are not dynamicaly updated, that "instance" approach would also solve that.