There was a firmware update that made the faders faster/more responsive.
The newer m32 had this update from the start so the faders were perceived to be faster than the older m32.
If the older m32 is updated with the latest firmware then the faders should move at the same speed as the newer m32.
Looking at the buttons, some cosmetic changes were made. There should be no sonic or operational difference between the older and newer m32.
I don’t think that it is related, but your serial suggests an old console (2014?) with a depleted battery since the clock is stuck.
Was this console actually shipped with an x-usb and not an x-uf card?
Your best approach would be to use a ’virtual patchbay’ that you can find in the OUT and P16 routing. Then you assign your Card output to be either P16 or OUT depending on your routing.
I am a webcaster not an audio engineer, so I appreciate any help.
Here is a link to a google drive folder containing an audio diagram and the scene off my X32
I want to be able to bring in my commentator mic (AVIO in CH-1) into the X32, (this is already working) I need to apply the gate, eq, dyn and FX Compressor/Limiter... before it gets send back out the Dante Channel to VMix running DVS.
Also, the only way I have figured out how to get a MixBus on a Dante channel is a physical loop from Aux out 1 into CH16 (for example)
Is it possible to assign a MixBus to a Dante channel (virtually) without the need for a physical loop?
If the fader returns to zero in mc-mode, this indicates that studio1 for some reason isn’t sending back control data to the controller. Verify in studio1 that the mcu midi ports are correctly setup. If you are using regular midi cables, verify that they are connected to their correct in/out ports and that the midi cables aren’t bad for some reason. You should be able to utilize the studio1 midi monitor logger to verify midi communication. to/from the motör.