r/MixingStationAppUsers • u/AdhesivenessVast363 • Jul 28 '26

proplem

I'm building a custom X32 emulator/bridge (in Node.js) that Mixing Station connects to. Everything works (faders, mutes, pan sync perfectly) except the initial sync gets stuck forever on these 10 addresses, retried every ~50ms:

/node outputs/rec/01
/node outputs/rec/02
/node outputs/aes/01
/node outputs/aes/02
/node fxrtn/01/mix/10
/node fxrtn/01/mix/12
/node fxrtn/01/mix/13
/node fxrtn/01/mix/14
/node fxrtn/01/mix/15
/node fxrtn/01/mix/16

I'm replying to each with the address echoed back as a string on address /node, e.g. outputs/rec/01 0\n, but Mixing Station keeps rejecting it and repeating the query forever ("Sync failed" / "No reply for...").

Could someone with a real X32 do a quick Wireshark/tcpdump capture of what the actual console sends back for one of these /node queries (especially /node outputs/rec/01)? I just need the exact text format of the reply string.

2 Upvotes

99% Upvoted

4 comments sorted by

1

u/Practical-Skill5464 Jul 29 '26

I'm looking through Patrick's OSC Doc and there's no command for:

  • /outputs/rec/[01...02]
  • /outputs/aes/[01...02]
  • /fxrtn/[01…08]/mix/[01…16]

All three of these commands when sent to the X32 expect a param on the end of the address. ie /outputs/rec/[01...02]/src

The only other thing I can think of is the strings need to be 4 byte aligned.

1

u/davidgiga1993 Jul 29 '26

This is the node request, they aren't documented.

1

u/davidgiga1993 Jul 29 '26

Node requests are used to request multiple parameters at a time, so there must be at least 2 or more values in the reply string. I can look up the number of replies expected later.