BrainModular

hi,

The probleme is :

when i make a patch with this plug and a preset module, values of the four tap frequences aren't always correctly restitued.

i think i found why, but don't know how to make it work, i'll try to explain :

each tap frequences sliders value is relative to the next one, representing a percentage off the next slider value. so, to found the value in frequence of the first slider, the plug begin by determining the fourth slider value, and the third, and the second, and finally the first, the plug work like this because these values can't overlap each other. for example :

the plug frequency is from 20 to 20000 Hz, sliders, from first to fourth have these values :
1:0.5
2:0.75
3:0.2
4:0.8

so, in frequence this is equivalent to :
1:0.5 * 2400 = 1200 Hz
2:0.75 * 3200 = 2400 Hz
3:0.2 * 16000 = 3200 Hz
4:0.8 * 20000 = 16000 Hz

the fact is, this is the internal way the plug work, and this is why, when a preset is recalled, depend of the order usine give the slider values, the result isn't the same.

senso, can you tell me if the preset module store and recall values in a certain order

the good thing is that i have the source of the plug, but the bad one is that i can't find a solution to have a predictable result.


the vst can be loaded here :
http://substance-night.it/4BPS/pitchshift.html

hope it's clear enough, don't hesitate to ask question

I don't know if this will work, but if you used Usine knobs or faders connected with WaitOne modules before the parameter inputs? None for the fourth parameter, one for the third, two for the second, and (yeah - you guessed it!) three for first parameter.

At least it's easy to try out... I can't do it now - too much to do at work.

yep,

tested, the result is better, but approximative, i have to click numerous time on the preset to refine the value to those intented... strange

The preset store & recall order is the order of the creation of the modules.
So you can try to delete and recreate faders to obtain the order you want.

thanks for the clarification, it's what i supposed.

Already tested , but i have to click 4 time to refine the internal plugin values to good position. Has i have the sources, i'll track the computation problem in the plugin. I can make all sliders absolute between 20 and 20000 Hz, but they'll always be interdependant (if slider 2 is on 2000 Hz, the first can't be superior). I'll try to find something and let you know.

PS : it's going off topic, has it's become a plugin coding problem, but i think it's an interesting algorythm problem.