Store VST data locally but recall globally?

[woodslanding]

My patch has an instance of Kontakt. There is a subpatch inside with a PM set to 'parent patch'. Which kontakt setting is to be recalled is controlled by a list elsewhere, connected via a buss.

The problem is that if I have a bunch of these in a wkp, and want to store everything in a global PM, the kontakt data gets recalled twice. Once by the global PM which stores the local PM number, and again by the list, which sends out its stored value.

I want the list to be updated, otherwise the GUI will not reflect what's going on in the patch. What I'd like is for the value of the local PM NOT to be recalled by the global PM. But if I disable 'stored in patch' for the kontakt patch, then PM recall stops working at all.

Is there any way to tell the PM to recall patches via it's numerical input, without having it also recalled via a global PM?? It's counter-intuitive to me that deselecting 'saved in preset' for a patch would make that patch's internal PM stop working. I would think it would just prevent it being recalled externally via a larger scope PM (rack or wkp), rather than disabling its own internal PM.

When you get a bunch of VSTs running, doubling the time to change settings is unfortunate.....

[gurulogic]

Hmm, a couple of my methods that might help..

To have a sub patch with a preset manager that operates independently of a global preset manager, I nest the sub patch inside another that has saved in preset turned off. Then you can have a sub patch within a sub patch that has its own preset manager functions.

Not sure if this is applicable to your situation, but a method I use to to have a sub patch selectively stored in a global preset is to have a not saved in preset sub patch with array get/set with values 0 or 1 with a get array element value linked to my preset selection and connected to saved in preset inlet on desired sub patch. With this you can choose which preset is save/recalled in sub patch or not. You may need to put a wait data flow so that the array element is recalled before the preset saves/loads.

And yes, I agree that it would be better if a sub patched that had saved in preset disabled could still be controlled by its own preset manager. This would save having extra wiring and nesting sub patches as a work around. Definitely worth making a feature request I think.

[woodslanding]

Hmmm. I already have the PM in a subpatch, but haven't found a combination of saved and not saved that gives the desired result yet...Maybe I need to nest further....

[woodslanding]

Double-hmmm. It seems like subpatches don't have a 'recalling preset' pin... so my tidy mechanism for updating gui elements after a preset has loaded breaks when I bury the patch in a subpatch. grrr.....

[gurulogic]

Having one sub patch "buffer" with saved in preset disabled works here for me..

Top parent patch w/ preset manager, target = workspace> sub patch w/saved in preset = no> sub patch w/saved in preset = yes w/preset manager, target = current patch