I'm using the preset manager on a patch; I've never used it before. In general, the preset manager is intuitive, I can clear & save presets and it all makes sense.
This patch has a LOT of settings, 100+. A mix of knobs, switches & combo boxes.
However, I have some controls whose settings:
(a) are not saved with the patch, &
(b) seem to be getting confused with each other.
I.e., I update control A, save the preset, and when I recall the preset, control A is not restored, but control B seems to reflect its value... The problem is with switches. All of my knobs and comboboxes appear to behave perfectly.
Any known limitations with preset manager?
Can presets SAVE more than 100 settings?
Anything I can do to address?
Any workarounds for switches, do they need unique names? The switches that are getting confused have identical names but are used in different subpatches...
Thanks,
Shawn
Preset settings getting a little confused - am I missing something?
Found a fix.
Well, I tried deleting & re-adding the preset manager, that didn't fix it.
I tried renaming controls & captions, that didn't fix it.
I deleted & re-added the offending controls, that fixed it.
Bottom line: If the preset manager starts acting flaky, delete & rebuild the specific control whose presets are not being saved properly.
Well, I tried deleting & re-adding the preset manager, that didn't fix it.
I tried renaming controls & captions, that didn't fix it.
I deleted & re-added the offending controls, that fixed it.
Bottom line: If the preset manager starts acting flaky, delete & rebuild the specific control whose presets are not being saved properly.
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Yes, this can happen in specific cases and when you copy paste modules with same names
before deleting and recreate the modules, you can try to use the repair id's command in the remote tab of your sub patches or patch
before deleting and recreate the modules, you can try to use the repair id's command in the remote tab of your sub patches or patch
Hmmm... Never encountered the 'repair IDs' command. I'll take a peek.
Though this patch is straightforward, it has a LOT of simple subpatches (enabled me to copy & tweak a high # of similar controls). It takes an extremely long time to load.
I created a control surface for a very cool & unique instrument! Will likely share after testing it for a while.
Any pointers on VERY long loading patches would be welcome. It works beautifully once loaded.
Thanks,
Though this patch is straightforward, it has a LOT of simple subpatches (enabled me to copy & tweak a high # of similar controls). It takes an extremely long time to load.
I created a control surface for a very cool & unique instrument! Will likely share after testing it for a while.
Any pointers on VERY long loading patches would be welcome. It works beautifully once loaded.
Thanks,
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Thank you - Repair IDs straightened everything out.
After I "fixed" it last night, I hadn't noticed that deleting & re-adding the problem controls merely moved the problem to a different set of controls... It just moved the problem.
I ran Repair IDs on the problem controls - no change. I ran Repair IDs on the whole patch & NOW everything seems OK.
Thanks, hadn't found/used that function before. Straightened me right up.
I still have a LONG load time problem. Any pointers welcome...
After I "fixed" it last night, I hadn't noticed that deleting & re-adding the problem controls merely moved the problem to a different set of controls... It just moved the problem.
I ran Repair IDs on the problem controls - no change. I ran Repair IDs on the whole patch & NOW everything seems OK.
Thanks, hadn't found/used that function before. Straightened me right up.
I still have a LONG load time problem. Any pointers welcome...
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
OK... This problem came back with a vengeance. Preset manager refuses to work at all.
First, it behaved oddly - specifically, a 2nd preset manager icon showed up in the control panel, where it was supposed to be in the interface builder. Then, the 2nd one somehow morphed into 32-presets, not the 16 configured. I deleted & re-added the preset manger, thinking this would tidy things up. But now, it's royally broken. Repair IDs won't help.
I think the patch is corrupted somehow.
Is there a routine or process to 'clean' corrupted patches? I really can't start over, it took me a couple weeks to get this far...
First, it behaved oddly - specifically, a 2nd preset manager icon showed up in the control panel, where it was supposed to be in the interface builder. Then, the 2nd one somehow morphed into 32-presets, not the 16 configured. I deleted & re-added the preset manger, thinking this would tidy things up. But now, it's royally broken. Repair IDs won't help.
I think the patch is corrupted somehow.
Is there a routine or process to 'clean' corrupted patches? I really can't start over, it took me a couple weeks to get this far...
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Unfortunately I don't have any advice or help, but wanted to mention that I am watching this thread with great interest. I have *never* had a preset manager patch behave the way I expect. I've tried to rewrite Sequins to use a preset manager many times, and I've never gotten past the first step successfully -- and that step is just to save a the state of a sequenced switch in a preset manager!
I think I remember nay mentioning some updates and improvements to the preset system. I hope they work out.
I think I remember nay mentioning some updates and improvements to the preset system. I hope they work out.
Well my patch is fully functional again. I had disabled the patch-level 'saved in preset' setting trying to get rid of a 2nd preset manager that had appeared. Re-enabling 'saved in preset' at the patch level enabled the patch manager itself to work.
So... My lessons thus far:
- Repair IDs at the patch level definitely tidied things up when presets were acting flaky
- Make sure 'saved in preset' is set at the patch level as well as on the controls you want saved in the preset.
(I'm still confused where the 2nd preset manager came from, but I have a working patch, so I'm good for now. I'll likely find that I enabled something else while putzing/learning.)
Thanks to senso for excellent support.
So... My lessons thus far:
- Repair IDs at the patch level definitely tidied things up when presets were acting flaky
- Make sure 'saved in preset' is set at the patch level as well as on the controls you want saved in the preset.
(I'm still confused where the 2nd preset manager came from, but I have a working patch, so I'm good for now. I'll likely find that I enabled something else while putzing/learning.)
Thanks to senso for excellent support.
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Learned a bit more...
That "2nd" preset manager comes from clicking on the camera icon visible on the patch in the rack.
My understanding is that each patch comes with 32 presets by default, managed here. I don't know how to change its location, e.g., move it to the interface builder. I also don't know how to access its inlets & outlets.
I believe that if you want (a) more than 32 presets, or (b) to access the inlets & outlets of a preset manger, then you need to add a preset manager module in your patch.
That "2nd" preset manager comes from clicking on the camera icon visible on the patch in the rack.
My understanding is that each patch comes with 32 presets by default, managed here. I don't know how to change its location, e.g., move it to the interface builder. I also don't know how to access its inlets & outlets.
I believe that if you want (a) more than 32 presets, or (b) to access the inlets & outlets of a preset manger, then you need to add a preset manager module in your patch.
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
I'm now reworking the patch to use poly functions wherever I had repetitive similar controls. I'm hoping this will address my long load time issue mentioned above (senso's suggestion).
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Who is online
Users browsing this forum: No registered users and 11 guests