You might have noticed that when you're using your Wing console with RemoteMix, you can't control the group fader for a virtual group if it's assigned to the Main 1-4 outputs. This isn't a mistake – it's just how the software currently works.
Here's the simplified explanation:
Think of your mixer's Main outputs as having a special setup. RemoteMix needs a specific way to "talk" to those Main outputs to control things like virtual group faders. Right now, that communication link isn't available for the Main 1-4 outputs on Wing consoles. So, RemoteMix can't control the group fader in that situation.
What does this mean for me?
This means if you rely on virtual groups and need to send them to the Main 1-4 outputs (which is common for streaming setups), you won't be able to use the virtual group fader in RemoteMix.
What's being done about it?
We know this is an issue and we're looking into ways to fix it in a future update. We appreciate you letting us know how this affects your workflow so we can prioritize the fix.
What is the work around for this?
There are a few ways you can work around this for now:
Set a different mix target instead of a Main.
Adjust levels & mutes in the group individually instead of by the group fader.
We're always working to make RemoteMix better, and we appreciate your patience! If you need additional help, reach out to the community in our Discord server (invite link here).