USB streaming stops on muting the channels

Hi,
I have an issue with our CQ18 (newest firmware and newest driver on windows laptop). setting up all connections (usb-B multitrack to laptop) shows the channels and I cna select them in OBS. But muting the channels and unmute them afterwards stops completely the streaming. first with changing multitrack to stereo and back enables the streaming again. Is it a bug or feature?
We unmute the channels with the CQ app on a tablet.

Thanks
Dietmar

This doesn’t sound right.

Obviously muting a channel will mute it “everywhere”. So when you mute a channel, it will not be heard on the USB/stream output.

However, changing the mute status should not “stop” any software or hardware you might be utilizing to host your stream. If this is occuring, you might want to double check to see if you have implemented MIDI commands. It could be that the console’s MIDI command for mute/unmute is being interpreted as a “stop” command by the streaming software/hardware.

Sorry, I was not clear.
We use OBS Studio for streaming on a windows computer. The CQ audio driver is installed and switching to Multitrack I can select all channels set up on the CQ tablet app. If I mute on of these channels assigned to the multitrack output, the channel is muted. But all unmuted channels didn’t get signals too. And unmute the first channel again didn’t bring the signals back. first after changing mutlitrack to stereo in the configuration and back to multitrack allows me to set the audio source again in OBS. so the following took place:

  1. start computer and OBS
  2. assign in OBS signal source to CQ audio device
  3. mute one channel on the CQ18 tablet app
  4. audio source in OBS did not getting signals anymore but is connected
  5. unmute the channel → again no signal from CQ18
  6. change USB config on CQ18 (mutlitrack → stereo → multitrack)
  7. reassign audio source in OBS with CQ audio device
  8. signal is back

Hope this makes it more clear

I think it must be a bug. I would recommend that you reach out to the “official” A&H support team via the A&H website. They hopefully can be of better help and if it is truly a bug, they need to be made aware of it so they can log and fix it.