Preset Manager with axocontrol


#21

...the interesting thing about a glide function is, that you can reproduce complex movements with very few controls.
here an example with the Axo control in mind: I use the three Buttons for load and safe and stepping thru 7 presets: using a binary display with the leds x00 0x0 xx0 00x etc. I could set the crossfade/ glide time and morph from one state to the other. A random function would make it even more interesting, because you could wildly change much more parameters than accessible as controls outside the box and save settings you like. Those parameters which cannot glide switch.

I used to have a similar system in my supercollider live setup and it was the hit for live performances, you can move forward with your music and glide back to a live saved preset


#22

Yes. Also just morphing(gliding) from one extreme preset to another is awesome. Very few synths got this feature. I think some of the Waldorf synth has got this feature...

@DrJustice I just read through the documentation for the PM again to make sure I set it right. I find in the global mode and the subpatch mode, that if I add an object to the patch, the previously made presets wont load..... If I remove the object again it works again. I guess its best to make sure a patch is very much done before starting to make presets.

In global and subpatch mode you should be able to move things around, right? But maybe adding stuff may not work?


#23

I agree. Even if it's possible to implement (and it is) I think it's outside the scope of the Preset Manager, at least for now.


#24

ok, fine.
where would you see a function like this within axolotl if not with a preset manager ?


#25

I made a change which should in theory eliminate all chances of clicks, except for the "Immediate" mode. The new Preset Manager is synced, and the image and test patch above is updated. I've included three different fade times (0.5s, 0.1s and 0.02s) as well as immediate switching.

I have now changed the PM so that it will allow loading of a preset in SubPatch and Global modes even if you have added, removed or renamed objects. You'll need to save the patch again if you want it to be refreshed with the changes of course. I did some quick test here, and it seems to work. I'd appreciate if you test this a bit.


#26

I will test it and let you know. But I have to wait a couple of weeks, my axolotl is doing some work in a sound installation in amsterdam


#27

Well... It does logically belong in the Preset Manager, and it is doable although there's quite a bit of work involved. Each parameter type must be handled separately, and that means quite a bit more code, and code space is precious.

I have to admit that I'm tempted by the challenge, but not today :wink:

Let's get the current PM updates verified and tested in the wild before the next round of features..


#28

I tested it now. I added object and presets still works. I removed objects and prestes still works. I moved objects around and preset still works.. Awesome!

Immediate function: Absolutely NO clicking even when using an lfo to switch preset and even at very high tempo! I had many clicks before.

Welll, from what I have testet now = 100% succes!

I need to test it on some more advanced patches to check how that reacts later on, but it seems like it works!

Humbly...... Great work!


#29

Curious about if the technique that you used to remove the clicks/bliips also can be used to remove the blib from tables?


#30

I absolutely understand !


#31

Are you thinking of the table/load object? If so, yes partly, a table/load clone with the fade method could be made.


#32

@jaffasplaffa

I've made an experimental general deglitcher module. It provides the service that is now built into the Preset Manager, i.e. to silence the audio while a blocking operation takes place. Getting a bit off topic here, but it's related.

This is what the drj/patch/deglitcher module does when it gets a rising edge on its trigger inlet::
- fade out
- silence the audio output buffer,
- generate a trigger for a blocking operation, which would normally result in glitching audio
- fade in

Note that when using the Immediate mode for deglitching, the deglitcher module must be place before the output module, as in to the left and/or above it, due to the iteration order.

Below is an example patch which can load one of two files into a table while repeatedly playing the same table.
The "--- Trigging a blocking operation ---" section is the deglitcher mechanism, supported by a volume control module as for the PM:

test_deglitcher.axp (5.1 KB)

test_deglitcher_embedded.axp (8.4 KB)


#33

Oh, looks great. will try it out tonight :slight_smile:

EDIT: Just opened the patch and the patch/deglitcher object is missing. Could you embedd the object and upload the patch again?

Thanks!


#34

It's in the GIT repository and working here. Did you sync your library? It would be better if you got the object in your library so you can reuse it for test cases of your choice. I have reuploaded the patch, just in case, and added one with the deglitcher embedded as well.

Edit: I think the deglitcher belongs in the "audio" object category , so I'm moving it there.

Edit 2: I reversed the order of the "volfade" attribute menu for the PM and the deglitcher, from fastest to slowest so "Immediate" becomes the default.

Edit 3: The Preset Manager or deglitcher module must be placed before the output module, as in to the left and/or above it, due to the iteration order. All attached patches and images has been updated to reflect this.


#35

I thought I synced library.. Maybe I didnt... It works now :slight_smile:

Will test it with a patch later tonight.

Thanks again!


#36

Did you get to testing it? If so, how did it fare?


#37

my axo is working a sound installation so i can't test it before end of the year..I'm very curious. I let you know as soon i have hands on my axe again

thank you, nicholas


#38

Hey @DrJustice

Sorry mate, I forgot to post my test here. I will test again and get back to you.

But as far as i remember, the de glitcher doesnt remove the bliiibs from loading tables. I think they are on a lower level than the output. If I remember correct the blib is there even if the master output is turned down.

Anyway, I will check again today.


#39

@jaffasplaffa:-If you test table load deglitching, I suggest using the deglitcher test patches above as a starting point for verification (you need to provide the two audio files yourself).

@Grandprixdamour: It works here - I tried the patches attached above, and one of them already have the deglitcher embedded. Did you sync your library? The deglitcher object got moved from patch to audio BTW, but that shouldn't make any difference.


#40

I synced the library, but can't test it without the Axoloti