Maximum number of sliders in SliderPack

[Oli Ullmann]

Hello everyone! :-)

Does anyone know if there is an upper limit for sliders in a SliderPack? I have 1452 and have noticed that it has reverted to an older, smaller value. I don't know if this is due to a crash though, so I thought I'd ask again here.

All the best from cold Germany
Oli

[Oli Ullmann]

I have found the error! The slider pack is “safeInPreset” and I had saved a preset with fewer sliders.

[bendurso]

@Oli-Ullmann Nice, just wondering, why 1452 sliders in the sliderpack?

[Oli Ullmann]

@bendurso
I'm building a synthesizer with 4 layers and lots of modulation options. Sometimes 7 modulation sources per parameter. I don't want to add a separate slider to the project for each modulation intensity, but I still need to save the setting in the preset. That's why I use a slider pack. And that's why this slider pack needs so many sliders.

I also tried to save the status of the modulators in the preset via Engine.addModuleStateToUserPreset(). But with so many modulators, the preset became 0.5 MB in size and it took forever to load it. That's why I use a slider pack.

[bendurso]

@Oli-Ullmann Nice, makes sense. Thanks :) I thought it was crazy to have so many sliders at first hehe.

[Oli Ullmann]

@bendurso
Yes... If there was a way to add modulators dynamically in the compiled plug-in, I wouldn't have to do that. But at the moment there is no such possibility...

[d.healey]

@Oli-Ullmann Are you using 1 sliderpack per layer, or one big sliderpack for everything?

[Chazrox]

@Oli-Ullmann @d-healey is this technique of using hidden slider packs just for the purpose of setting hidden 'default' settings? Just curious.

[d.healey]

@Chazrox It's for saving data that you want to be recalled with a preset that you don't have a dedicated control for.

Imagine you have an attack knob and a release knob on your interface, but you have two envelopes in your module tree, so you add a switch on your UI to choose which envelope the two knobs control.

If you want to save the state of both envelopes you can use a sliderpack with 4 sliders, with the attack and release values for both envelopes. Then when a preset is loaded you can set the knob on the UI to the values stored in the sliderpack, depending on the state of the button.

[Chazrox]

@d-healey Sick. I can actually use this now. Thanks.

[Oli Ullmann]

@Chazrox
Yes, as David described, you can use it to store additional data without a dedicated UI element.

[Oli Ullmann]

@d-healey
Good morning David,

I use a large slider pack.

One reason is that I have two “general envelopes” that can be used as a modulation source for different parameters. These are basically created as global modulators in a global modulation container. However, as envelopes are not always reliable as global modulators (for example with pitch modulation), I had to create dedicated envelopes for many parameters and could not use the global ones. However, the user should have the feeling that there are only two global envelopes. That's why the parameters of all envelopes are controlled via the same UI elements. Since the parameters of the envelopes (attack, decay, etc.) can also be modulated, this results in a large number of modules, which is why I use a slider pack.

I have now packed all the modules to be processed into a large array (in a specific value range). I have arranged them so that, for example, every fifth entry in the array is an LFO 1 modulation:

150 Attack LFO 1
151...
152...
153...
154 Decay LFO 1
155...
156...

So with the help of a little math I can access all parameters via the same UI elements (the slider number in the slider pack matches the array entry of the module). Therefore, using a large slider pack was easier than using a dedicated one for each layer.

Did I make that clear? :-)

Why do you ask?

[d.healey]

@Oli-Ullmann said in Maximum number of sliders in SliderPack:

Why do you ask?

Just curious