newtfish

Ive got a vst~ with massive vst instrument loaded, then routing/prepending the parameter ID with a live.dial inbetween.

However, there is huge feedback with some VST's, clearly because when the parameter receives input it outputs the values as well.

Is there any way around this feedback? Ive tried gates all over the place, but it seems there is no way to avoid it.

This seems to be a problem with massive vst, ive tried on others and it seems to be working on some.

Ive got a vst~  with massive vst instrument loaded, then routing/prepending the parameter ID with a live.dial inbetween.

This seems to be a problem with massive vst, ive tried on others and it seems to be working on some.


avoid-vst-parameter-feedback-2

yep I can confirm Im getting back feedback problems from other vst's such as MS20 korg.

Isn't it possible to get the VST object to spit out a different list depending on whether the vst is being controlled by the mouse or max?

im afraid it doesnt work - still loads of feedback :/ I think because the feedback problem doesnt happen when the live.slider is being set by the vst. It happens when moving the live.slider (and then the feedback comes into the slider (through the set message))

It would be good if the vst object behaved like a live.slider does, so that you can set the values without output, but I dont think its possible :/

yeah, ive had a go at that. I think its impossible because the values are going in from the live.slider and then coming out of vst object, going straight into the set message.

They really need to allow the "set" message for the VST object. It seems the only way to control parameters properly outside of the object itself.

Ive contacted support about it. I do hope they get back with some suggestions... Its a huge oversight, particularly when using touchscreen applications where bidirectional support is important

I tweaked your patch a bit. Increased the [delay] time and stuck a [change] object in there.

I tweaked your patch a bit. Increased the [delay] time and stuck a [change] object in there.
See if this smooths things out for you.


I tried the following patch wit Korg's MS-20 and it seems to work for me.

Could [zl change] help here?
I tried the following patch wit Korg's MS-20 and it seems to work for me.


Which versions of Live are you guys seeing this in?

The set message should not cause any output from live.* objects at all.

It's not the set message/live.slider that's causing the problem.

It is when you move the live.slider the changes are sent to the vst object, and then sent straight back out of the vst object, straight into the set message again (which causes the live.slider to jump around)

It is when you move the live.slider the changes are sent to the vst object, and then sent straight back out of the   vst object, straight into the set message again (which causes the live.slider to jump around)


Hi Rick, thanks your solution works perfectly. This has been driving me round the bend for ages so thanks so much for your help :)

Hi LSKA, you might try with some different VSTs? if you move the slider around fast you can see some jumpiness. This is probably worst with Massive vst, but you can also see it happens on most other VSTs if moved around fast.

Some VSTs seem to handle it better than others

avoid vst parameter feedback