Then, the issue I found is that if you try to change the outputs of MAIN, it does not replace the outputs in the card sound but add in parallel… it means that for example, I start with MAIN = Stéréo 1/2. Then I change to Stéréo 3/4. In my sound card, I have signal from Live Vst in Stéréo 1/2 + Stéréo 3-4… If I change 10 times, I will have 10 times the signal to the 10 configured stéréo outputs.
I have noticed a similar problem. I am new to working with VST Live (VST instrument) on macos in conjunction with a Dante Virtual Soundcard (with 48x48 in/outs).
Have set the MAIN output in Live to ‘DVS stereo output 35+36’. However, a parallel signal from VST Live also comes to the mixer on DVS output channel 1+2.
Further outputs are set in VST Live only for metronome (Output 7+8). No other plugins or further outputs…
Ok, we need to narrow this.
So with my UR22 created a 2nd port Stereo 3+4 and out channel “second” routed to that. Then 2 audio tracks, one sent to stereo and the other to second. Moving either fader will have no influence on the other, and that comes to no surprise.
We also had a similar test set up with an x32 setup, as there used to be a bug quite some time ago.
We see no way yet how this could go wrong. This is a complex setup so you may want to narrow it to 2 tracks or so as well. You may send your .vlprj file so we can possibly emulate the problem here, thanks.
So here is the link to my project file. I hope this works
Can’t upload here because its bigger than 4 MB.
Tomorrow I can do some more testing about the issue.
Its not this complex setup. The Dante Channels 1-32 are for use with another app that isn’t runing at all for the moment. And the System Outs in the macos Midi-Audio-Settings is set for Dante Channels 33+34. But I will have another try…
MAIN has been assigned to several outputs when saving the project. It was assigned to 1+2, 33+34, “Stereo” (could be a different device), and the last and current 35+36.
Will check for Dante specifics, but it is supposed to be a black box for apps.
By console you mean the VST Live Mixer? What do its meters show?
If you have 2 out channels in VST Live, and you route a signal to out 1, then you say signal also appears on out 2 which it should not. But if VST Live shows meter and signal reacting only on one channel when lowering volume, the problem is most probably outside of VST Live.
I will try to describe the phenomenon again step by step.
In VST Live, I want to use one or two VST instruments per song part. Their outputs are routed to the StereoOut in VST Live by default. This in turn is routed to the MAIN output, which is assigned to outputs 35+36 of the DVS.
I’ve been playing with this exact setup for two years via MainStage without this problem on the same machine. This only occurs now with VST Live.
The outputs of my Dante Virtual Soundcard are patched 1:1 to our WING mixer using “Dante Controller” (channels 1 to 36 on channel 1 to 36). There was no parallel routing done in the controller software there either. As I said, with MainStage I don’t have the problem currently either.
The problem is that the audio signal from VST Live is not only sent through channel 35+36 of the DVS, but is also sent to the mixer in parallel on channel 1+2 of the DVS. Although in VST Live the outputs 1+2 are not addressed at all. (that was the screenshot in the earlier post; you can see the input signal on 1+2 and 35+36)
The hint with the pulling down of the fader I referred to the “StereoOut” fader in VST Live. When I pull it down, the audio signal from VST Live becomes quieter at the receiver (WING) both on channel 1+2 and on 35+36.
It’s as if both pairs of outputs are running in true parallel mode, feed from the same source in VST Live, even though output 1+2 has no signal assigned to it by me at all…
MAIN was assigned to 1+2 at some point (earlier project save) as I can see in your project. Maybe you could delete MAIN from connections, re-create it, and assign 35+36, will that make a difference? Also try to save the project under a different name (“Save As”) thereafter, and send it again, should that not resolve the issue, thanks.
Would you also have the possibility to check if the problem also occurs with channels lower than 32? With the x-32 it might be possible to reproduce it.