Midi plugins (vst) problem
Posted: Mon Nov 04, 2019 7:42 pm
Hi!
Originally I thought this was a BitWig issue, but seems none had the same problem over there at answers.bitwig.com so I thought I'd try here..
I'm running BitWig on linux and use linvst for converting windows vst .dll files to .so files. This works perfectly with audio vst instruments and effects, no problems what so ever!
However, when I try vst midi plugins (example Chordz https://www.codefn42.com/chordz/index.html), there is no midi signal out of the plugin. In the device chain (panel) the native midi plugins indicate a light on input and output, but when using vst midi plugins only the input lights up, the signal is not passing through the chain.
Is there some setting I'm missing here? Why won't the midi signal pass into/through the midi plugin?
Here's a screenshot when the plugin is activated (only input lighted)
Here's a screenshot when the plugin is deactivated (output + input lighted)
Thanks for any hint suggested!
Originally I thought this was a BitWig issue, but seems none had the same problem over there at answers.bitwig.com so I thought I'd try here..
I'm running BitWig on linux and use linvst for converting windows vst .dll files to .so files. This works perfectly with audio vst instruments and effects, no problems what so ever!
However, when I try vst midi plugins (example Chordz https://www.codefn42.com/chordz/index.html), there is no midi signal out of the plugin. In the device chain (panel) the native midi plugins indicate a light on input and output, but when using vst midi plugins only the input lights up, the signal is not passing through the chain.
Is there some setting I'm missing here? Why won't the midi signal pass into/through the midi plugin?
Here's a screenshot when the plugin is activated (only input lighted)
Here's a screenshot when the plugin is deactivated (output + input lighted)
Thanks for any hint suggested!