patch change problems

[amiga909]

have a very basic problem: its so obvious, prolly it has been discussed b4, or I am doing something wrong

- hook up a fader to a vst parameter input pin, say, to cutoff, and the fader is set to 0.5
- change preset on vst. new preset would have a cutoff value of 1
-> usine changes the preset immediately: value of 1 gets lost, replaced with 0.5?
I did a workaround with a logical = and a separator (comparing the vst param out pin with the controller value), does work but I dont want to do that for every param??

[martignasse]

hello amiga909,

if i understand correctly, you connected a fader to a vst parameter connection, and when you change the internal vst preset, the fader isn't updated, and more than that, the fader value over right the vst internal value of the preset. Is that right ?

In this case, it's totally normal, the fact you change the internal preset of you're vst doesn't affect the fader, in other words, the fader isn't informed of the change, and continue to provide his internal value to the vst parameter connexion.

I assume you're connexion look like this :

You can, see that if you change something internally in the vst, the fader isn't informed. It's a one way communication.

with this kind of schema :

You let the fader know what going on and he can update his value.

the bad news is that you have to do like this for every param you want to be controlled internally and by slider.

Hope it help.
I can explain more if needed.

[amiga909]

great advice. tkx a lot!
yet I dont understand why this works.

A)
the first thing I tried was connecting the fader_IN to the vstParam_OUT pin, without the passOnlyIfChange module. as a result u can then only change the internal vst_param slider (if you click on the vst). on vst preset change the value will be set correctly.

B)
with ur method its the opposite: the internal param fader does not respond. the external fader (and the hardware remote control fader) can change the value.
here to the preset value does not get lost.

why?
passOnlyIfChange: only if a value changes the output becomes active. but this does happen on the vstParam_OUT all the time? why does the external fader module do not get freezed (as in case A)?


- if vst_GUI is changed:

[martignasse]

B) with ur method its the opposite: the internal param fader does not respond.

In this case, you should add another 'passOnlyIfChange' module beetwen the fader OUT and the VST IN.

passOnlyIfChange: only if a value changes the output becomes active. but this does happen on the vstParam_OUT all the time? why does the external fader module do not get freezed (as in case A)?

just because the vstParam_OUT isn't changing all the time.

Let say you fader and the internal param are set 1 at init, it's a stable state, the 'passOnlyIfChange' module block the feedback to the fader.
Now, you manually change the value of the internal param, the out connector value change, say from 1 to 0.5, so the 'passOnlyIfChange' module pass the value (just one time) to the fader who is updated to 0.5. Now, the sate is stable again, internal value is always 0.5, the 'passOnlyIfChange' module pass block the feedback again.

[amiga909]

guess I should remind me more often usine connections are mostly bidirectional.

I like usine is different than synthedit here: feedback connections (or networks) are a principle not the exception - very analogue design concept I find

..usine still does play tricks on me all the time coz its a hell of complexity pushed in a very easy UI... have to understand it better and practice more..