Mairlist–Oxygen Mixer Integration Fix
Budget: €6 – €12 EUR
I need help finishing the link-up between my Oxygen 3000PLUS digital broadcast mixer (AxelTech) and mAirList v6. I have already enabled the mixer’s remote interface and begun writing both TCP and REST commands, but the Start and Stop buttons still won’t trigger play/stop of the tracks inside mAirList.
What’s working so far
• The mixer is visible on the network, responds to pings, and accepts manual TCP commands from a terminal.
• mAirList’s Control Panel is set to listen on the same IP/port.
Where I’m stuck
Mapping the physical Start/Stop buttons to the correct commands. Either I’m missing a handshake parameter or the JSON syntax isn’t what mAirList expects. I’ve tried the documentation examples as well as forum snippets with no success.
What I need from you
• Inspect and correct my existing TCP/REST command set.
• Configure any additional mixer settings (or mAirList remote-control options) required to make the buttons fire reliably.
• Provide a concise rundown of what you changed so I can replicate it later or apply it to other channels.
You’ll have remote access to both the mixer’s web interface and the mAirList machine via AnyDesk or similar; scheduling can be flexible but I’d like this wrapped up quickly. If you’ve previously integrated mAirList with broadcast consoles—or specifically with an AxelTech desk—this should be a straightforward task.
What’s working so far
• The mixer is visible on the network, responds to pings, and accepts manual TCP commands from a terminal.
• mAirList’s Control Panel is set to listen on the same IP/port.
Where I’m stuck
Mapping the physical Start/Stop buttons to the correct commands. Either I’m missing a handshake parameter or the JSON syntax isn’t what mAirList expects. I’ve tried the documentation examples as well as forum snippets with no success.
What I need from you
• Inspect and correct my existing TCP/REST command set.
• Configure any additional mixer settings (or mAirList remote-control options) required to make the buttons fire reliably.
• Provide a concise rundown of what you changed so I can replicate it later or apply it to other channels.
You’ll have remote access to both the mixer’s web interface and the mAirList machine via AnyDesk or similar; scheduling can be flexible but I’d like this wrapped up quickly. If you’ve previously integrated mAirList with broadcast consoles—or specifically with an AxelTech desk—this should be a straightforward task.
Related categories:
Technical Support
Broadcast Engineering
Network Administration
JSON
Audio Engineering
REST API