-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message type MB #45
Comments
According to here #13 (comment) Considering So MB is probably "Meter Byte" That said, I haven't made any time to dissect the |
It's really weird that they're using the term "meter" for faders and mutes.
Hopefully that should give us enough to work with... |
Okay, experiment complete. Under each setting, I muted/unmuted main channel1, then muted/unmuted aux1 channel2. The UC side of things is quite simple:
Note that UC never sends the MB messages - although it does receive them. From the subscribing client side, we see (only showing the muting; the unmuting is equivalent): UnlinkedThe client just sees the PV messages, both for main and aux. Main Mutes AuxesMute main ch1:
(The data here is everything after the "C-bytes".) Mute aux1 ch2: The client just sees the PV messages (e.g. Key=line/ch2/assign_aux1; Group=0; Value=0) All aux mute linkMute main ch1: PV, MB, MB (I believe the messages are basically as above) Mute aux1 ch2: No MB, but a separate PV message for each aux (so line/ch2/assign_aux2, line/ch2/assign_aux3 etc) Global mute linkMute main ch1: PV, MB, MB Mute aux1 ch2: No MB, but a separate PV message for each aux and line/ch2/mute and the FX outputs (e.g. line/ch2/assign_fx4) Hope that's useful! |
In my experimentation, I've found that the MB message type is used when the mute button is pressed on the "main" output for a channel, when mutes are linked. (I personally use globally linked mutes, which is how I discovered this.)
I'm guessing MB might be "Mute Button"?
I haven't looked into the details of the body though, other than to note that two messages are sent each time.
The text was updated successfully, but these errors were encountered: