charliesjc
commented
2 years ago I have made some headway with this and I think it's exactly how the communication is supposed to happen. Combing the log files in level 6 (TRACE) there is a process called "tisoc" controlling everything. I found a unix socket at /tmp/tisoc-controller and connected to it with socat. It shows all the inbound/outbound JSON comms that I assume you're supposed to read for metadata info and send commands to for control.
I haven't been able to get much further than see what's happening because once you connect via socat, the file basically gets locked and my phone can't connect to Tidal-Connect and/or the speaker controller can't connect either. So I have to restart the Tidal-connect service. BUT, if you connect with your phone first, then use socat, you can see all the progress, pause/play/next/previous from the phone and the notifications for metadata changes with all the track/playlist details. This is obviously the same info as in the detailed logs but it means you can interface with it this way.
There is also a debugging port that you can turn on and it creates a FIFO socket at /tmp/scdport but after opening it with socat I haven't got a clue what to do with it.
I've been trying to work out how to "view" the tisoc-controller without blocking it so you can see which commands are sent from the speaker controller/other apps. I have confirmed that this seems to be the way to interface with it because if you do the same socat on the tisoc-controller on the other raspberry music integration that you have to pay for, for Tidal-connect, it breaks in exactly the same way and the interface becomes useless without a restart of TC.
MoM-Raider
TonyTromp
nasawyer7
For some odd reason running audiocontrol2 in foreground works fine, but when running as daemon/service (systemctl start audiocontrol2) it doesnt pick up any changes.