data outs on vst don't reflect changes via midi

[woodslanding]

I have a nice little display of faders for my hammond module, so I can see the drawbars for a patch. If I change programs, the graphic shows me the positions of all the drawbars on the screen for that program. They're just for display--they're too small to edit.

Unfortunately, if I change the drawbar settings via midi CCs, this is not reflected in the VSTs parameter outputs, although the drawbar positions are changing on the vst's graphic. If I drag drawbars on the vst graphic with the mouse, it DOES reflect in the parameter outs!

This actually strikes me as a bug, but maybe it's more of an unimplemented feature.

I guess to get this to work, I need a bunch of midi filters to control my faders, and cable them to the midi out--or would that even work???

Anyway, it sure would be cleaner to use the parameter outs.

cheers!
-e

[bsork]

If I understand you correctly, you've created a set of faders connected to the VTS's output, and you've also assigned CCs directly to the same parameters on the VST.

I'm not sure where the fault lies with the missing update of output parameters when using CCs - Usine, VST or just a "mismatch" between the two - but here's another way of doing it the I'm pretty sure will work no matter where you change the parameters:

Connect the VST's outputs through a PassOnlyIfHasChanged to the faders, and the faders back into the VST. Use MIDI learn on the faders to assign the CCs, and there you go. You may have to remove the CCs assignments on the VST to avoid hiccups.

[woodslanding]

well, I don't want to use midi learn on these faders, as I want to do some processing on these cc's before they get to the vst. Specifically, I want to be able to use a cc button to switch the faders on my controller from affecting the Hammond to mixing the audio outs.

I assume if I use midi learn, the connection from cc to fader is going to be active all the time, right?

[bsork]

Yes, you're right. Hm...have to think about this one...