Need routing table ...
 
Notifications
Clear all

Need routing table features

0 Posts
1 Users
0 Reactions
2 Views
0
Topic starter

Hello! Recently, I purchased a 200XLR for my live streaming setup, but during actual use, I noticed several functional limitations that have affected operational convenience. I sincerely hope these can be promptly improved.

The primary issue lies in the lack of routing table functionality. For example, when connecting an XLR microphone to headphones, there's no way to disable the microphone monitoring function in the headphone jack. You might suggest muting the creator's microphone on the console, but this would silence my voice entirely. Alternatively, connecting headphones to the LINE OUT jack to adjust audience output not only defeats the purpose of using audience as OBS output, but also risks accidental unmuting in LINK mode, causing microphone audio to reappear in audience. Moreover, using third-party DAWs to adjust audio output would only route it through aux channels, which would also mix the sound into both creator and audience outputs. I urgently hope for routing table implementation to enable free control over channel-specific audio distribution.

Secondly, regarding the global mute button: Its practical utility seems limited, as it's hard to imagine scenarios requiring full device muting. If this button could be customized to mute specific channels, it would eliminate the need for redundant XLR microphone monitoring items across two interface pages or occupying extra buttons for quick muting. This would enable instant microphone muting at any time.

Lastly, I hope the panel design can expand its application scope. Currently, it only supports monitoring built-in audio channels. Could future updates enhance compatibility to allow monitoring of system-level audio and display of OBS audio chains?