MOTU Monitor Section Remote Project

[Col. Panic]

I have my MOTU 828ES in a rack out of arm's reach and I wanted comfortable control of basic monitor functions including: volume, speaker select, mono, and mute/unmute my noisy phono preamp. I didn't want an external monitor controller with all the extra interconnects and points of failure since my interface had everything I needed. It's just a little out of reach. I wasn't able to find anything commercially available, so made my own leveraging MOTU's API. So that it would be robust, I opted to base it on a micro-controller rather a general purpose CPU. So far, it's been very reliable, so I'll share what I did here in case anyone finds it useful.

 

[sarieri]

Does this support the new 828 and ultralite mk5 which uses Cuemix5?

 

[somebodyelse]

Does this support the new 828 and ultralite mk5 which uses Cuemix5?

I doubt it. Cuemix5 uses a different protocol that's been discussed in the Ultralite mk5 thread. Something similar could be done for that protocol though.

 

[Col. Panic]

Does this support the new 828 and ultralite mk5 which uses Cuemix5?

I don't have access to the latest generation, so can't say...somebodyelse may be right. But a super simple way to check is to just type in you browser:

http://xxx.xxx.xx.xx/000xxxxxxxxxxxxx/datastore

Where the first string of number is the IP address of your device and the second string is your device's UID. The leading zero are necessary for my situation. It should return something like this:

which you can then use to control any parameter you want. MOTU's API is extensive.

 

[somebodyelse]

See for example https://www.audiosciencereview.com/...mk5-review-audio-interface.24777/post-1299420 - CueMix5 is an embedded web app with its code accessible. You can open it in another browser, or examine it to see how it works. It uses websockets instead of the more conventional API used by the AVB series. https://www.audiosciencereview.com/...mk5-review-audio-interface.24777/post-1524606 introduces using node.js on a Pi to host the app and forward the connection to the local network so you can control it via the browser from any machine on the local network. You would need the forwarding part, but would need to use the websocket protocol directly from the remote instead of via a browser. I've not looked into whether you can do that with an ESP, Pico-W or similar - my guess is probably. If nnot there's always something like a Pi Zero-W.

 

[Col. Panic]

See for example https://www.audiosciencereview.com/...mk5-review-audio-interface.24777/post-1299420 - CueMix5 is an embedded web app with its code accessible. You can open it in another browser, or examine it to see how it works. It uses websockets instead of the more conventional API used by the AVB series. https://www.audiosciencereview.com/...mk5-review-audio-interface.24777/post-1524606 introduces using node.js on a Pi to host the app and forward the connection to the local network so you can control it via the browser from any machine on the local network. You would need the forwarding part, but would need to use the websocket protocol directly from the remote instead of via a browser. I've not looked into whether you can do that with an ESP, Pico-W or similar - my guess is probably. If nnot there's always something like a Pi Zero-W.

Thanks for the links and pointing out the switch from http POST to Websocket! I'll download Cue Mix 5 on another machine sometime this week (I'm a little worried about conflicts on this one) and check it out. But I agree that my code will need a good tear up to function with Cue Mix 5 compatible devices due to the underlying communication protocol changing. I'm unfamiliar with Websockets, but my 5 minutes of Googling have me concerned that there would be additional complexity handling multiple clients to ensure that the remote doesn't interfere with other connections to the interface.

Thanks again for all the great info! I'm new to this community but am excited by wealth of knowledge and willingness to take a few minutes to share it.