Maybe someone here can help to find that problem. The juce vst demo application has this problem too.
FL 9 includes a new dynamic input output routing that leads to the problem. FL9 assigns 2 inputs and 2 outputs instead of 1 input and 1 output to the juce plugins (the demo vst included in juce and mine). My older plugins, made with the raw VST 2.4 SDK, havent that issue.
I would expect that this means one stereo input and one stereo output. The juce VST wrapper code looks right at a first sight…
This all works pretty well with other hosts. Maybe its a FL9 problem, or have i to set channels to 1 for stereo?
Downloaded the latest tip of juce with git. I had version 1.46. The change list goes now up to version 1.5- hope i got the newest one. The problem persists. Tried both setSpeakerArrangement code snippets of the other post too. Still the same problem.
This is very strange. FL9 sends the audio input twice to the plugin, because FL9 believe the plugin has 2 stereo inputs. I’m not a fruity loop user by myself, but someone reported the bug and i could easy reproduce it with the fruity loops 9 demo version.
Some additional info:
I found out, that FL9 shows only one input/output channel if i set the configuration to:
I don’t know that much about FL but I checked one of my Plugins which has 10 Ins / 2 Outs with the FL9 Demo and the CHannels were detected correctly by FL (5 Stereo Ins and 1 Stereo Out, even the names I specified with juce::getInputChannelName were shown correctly). I’m using the latest juce tip with the modifications to vst_wrapper of my post (Jules already mentioned it).
Maybe you should check your juce::isInputChannelStereoPair and perhaps you should make use of the juce::getInputChannelName / juce::getOutputChannelName, to make it easier to find out what was detected by FL.
[quote=“friscokid”]I don’t know that much about FL but I checked one of my Plugins which has 10 Ins / 2 Outs with the FL9 Demo and the CHannels were detected correctly by FL (5 Stereo Ins and 1 Stereo Out, even the names I specified with juce::getInputChannelName were shown correctly). I’m using the latest juce tip with the modifications to vst_wrapper of my post (Jules already mentioned it).
Maybe you should check your juce::isInputChannelStereoPair and perhaps you should make use of the juce::getInputChannelName / juce::getOutputChannelName, to make it easier to find out what was detected by FL.[/quote]
Thanks a lot for this comment. Its good to know that this isnt a juce problem. I’ll try giving names to the channels and will check isInputChannelStereoPair.