Hi all.
Is there a way identify how may and who may be connected to the M32 remotely via M32-Edit, Mixing Station or M32-Q?
Ours is a multi-M32 installation and sometimes musicians inadvertently connect to the wrong M32 when trying to control their IEM mixes. Ideally our sound techs would be able to identify the incorrect connection before the musicians get frustrated or accidentally change a mix bus on the wrong M32. We do rename the mix-bus to the assigned musician and this has helped in 'if don't see your name you are in the wrong place' kind of way. But sometimes this doesn't work, and on a rare occasion, a sound tech has connected to the wrong M32.
So, is there a way at the actual M32, or in M32-Edit, or in Mixing Station, or some other un-named tool, to view active connections into a given M32?
Thx in advance for your help.
Dwayne A
Identify remote connections to M32
Re: Identify remote connections to M32
I'm not aware of anything that can provide that info. But one thing you can do is to rename all your M32 consoles to something more obvious (eg. M32 FOH, M32 Broadcast, etc.). This can be done using the M32 Edit (Connection screen, bottom left) or use the /-prefs/name OSC command.
Paul Vannatto
Global Moderator
Global Moderator
Re: Identify remote connections to M32
@DwayneA, another option to consider is to use DP48s instead of relying on mixbuses and apps.
Paul Vannatto
Global Moderator
Global Moderator
Re: Identify remote connections to M32
Give a name to your consoles using the /prefs/style OSC command; You can then query the data to know which console you're talking to.
Each console have their own IP, you could use that data too, which is returned by the /info or /xinfo queries.
There are plenty of other ways to name and later identify the consoles.
And if people do not check where they connect to... You can set a small middleman app that will clarify/filter that for them and prevent them to connect if they shouldn't.
-Patrick
Each console have their own IP, you could use that data too, which is returned by the /info or /xinfo queries.
There are plenty of other ways to name and later identify the consoles.
And if people do not check where they connect to... You can set a small middleman app that will clarify/filter that for them and prevent them to connect if they shouldn't.
-Patrick
Re: Identify remote connections to M32
Considered. Thx Paul.
Ah, ah, ah.... let me play with this.
Thx Patrick