Preset Manager help

[BrianA]

I've been trying to use the Dr Justice's Preset Manager in my latest preset and I'm having some trouble. Axoloti 1.0.12. Windows 7 64 bit.

I've tried the drj preset_manager_demo and is mostly working (except, surprisingly, saving, then loading the same patch alters the settings!) I tried to copy it's layout in my patch.

So, in my patch, it's 'sort of working' - top level parameters are getting saved and loaded, except:
1) No matter what I do, I can't get it to load (or save?) parameters in an embedded sub patch. My patch has 4 embedded sub patches.Each has number of controls exposed in the parent. While trying to troubleshoot this, I'm only trying to save parms from one sub patch (not sure if this messes things up or not). I set a different string for the preset manager in the sub patch instance and I see separate files for each preset manager instance being saved and loaded in the console. So, it appears to be going through the motions, bu t not actually, loading (or saving) parameters.
2) When I use the 'sub patch' setting for the preset manager in the subpatch (top level is 'Global') I get a message in the console stating:
3 non registered parms were skipped
What does that message mean and which setting - Global or Sub Patch - should be used in what circumstance?
3) I sometimes get a pair of console messages:
preset_maAxoA
Ping: WaitSync Timeout, disconnecting now
followed by a disconnect request, and I lose my GUI session connection to the Axoloti.
Sometimes, it just disconnects without any messages. Has never happened with no Preset Manager running. Is there an incompatibility with this release of Axoloti s/w?
4) Is there an execution order component to the preset manager? I seem to get some different behaviour depending on where the manager is positioned in Axoloti. Is there a preferred topology for success?
5) What's the threaded vs non threaded Preset Manager?

So any help would be appreciated. This is functionality some of us really need in Axoloti.

Thanks in advance!

[lokki]

the preset manager is not the most stable module i am afraid. it also uses mechanisms that are likely to change in a later release.

i tried it quite extensively and could also not get it to work reliably, seeing basically the same behavior as you:

-sometimes the axo would simply reboot
-parameters in subpatches are not always loaded.

as i would need this for live stage work i had to ditch this system altogether. i now simply use a controller object to switch patches via program change. this works reliably but has the disadvantage of a disruption in audio (half a second or so)

[BrianA]

Thank you for the prompt reply! Disappointing that this patch doesn't work reliably. I take it that Dr Justice is no longer active?

I haven't tried to do any 'live' patch loading yet. Can you point me at a thread or example on now to do this?

[lokki]

here is one way (read the last post):

Help with program change and patch/load

Hi! First I have to say that English is not my language, maybe the reason why I didn't find the answer. So for the moment, to change patch I use a controller object like this: [image] It's working but each time I change a patch I have to switch to Card reader an rename the patch.bin to copy it at root of SD card. Maybe now there is a better way. It would be great to load patches in their respective directory. Is it possible?

though you will have to name your patches in a format like:

patch01 patch02 patch03 etc... otherwise this solution will not work.

the better solution is to use controller objects and to upload a patch bank (file, new patch bank) then upload it...

How to use controller object?

Hey :smile: Yesterday I was trying to set up a controller object to pass audio through Axoloti. I want to connect output of one Axoloti to input of another and just pass the audio through. I tried putting the subpatch on the sd-card, in the root and name it "InOut.axs". And then I entered this into the controller object preferences to call it up: "cardname/InOut.axs". But no luck. I tried with a regular .axp patch too, but that didnt work either. I also tried just entering "/InOut.axs" in t…

sorry, i don't have more time a.t.m. but this should get you started.

[BrianA]

I've been out of town but back at it today and thought I'd follow up with you on this topic...

I was able to use the first method to load off the SD Card. Clumsy to setup, but does work nicely. Thanks for your help!

I have to admit I did not totally grok the whole controller object concept. I'm not sure I understand the general problem you're solving with this. I'll have to revisit that another time.

[lokki]

I have to admit I did not totally grok the whole controller object concept. I'm not sure I understand the general problem you're solving with this. I'll have to revisit that another time.

the approach is similar but since you upload a patch bank the filenames don't have to follow a pattern like patch01 02 03 etc...

[BrianA]

Okay... got it now. Created a patch bank using the Axoloti patcher and the controllers/pgmchange object. Working!

I found this thread very helpful:

Patch loading in 1.0.12

with 1.0.12 you should not need to do this manually there are 2 parts to this: a) patch change there is a controller object in the factory library called controllers/pgmchange use this as a controller object b) patches to switch these are now stored in a 'patch bank' file -> new patch bank add patches then click 'upload patch bank' fyi upload table, just uploads this table, upload - uploads the selected patch, upload patch bank, uploads all the patches and the patch bank table