(12-Sep-2023, 04:21 PM)agent_kith Wrote:I used loopback, mainly because it was easier to understand and install than web sockets. Web sockets appeared more elegant but if SQ could potentially be affected, then go loopback.(10-Sep-2023, 04:08 PM)Snoopy8 Wrote: And use web sockets rather than loopback?Thanks for the offer. Will ask for your help once I get the installer ready. You mean for the WebApp? Probably not going to use web sockets as RestAPI is more CPU cycle friendly.
Technically the library (cpprestsdk) I'm using for the implementation do have a WS interface, but don't see any need for introducing that for now. In truth I did thought of introducing WS when doing app installs and firmware upgrades, but just don't like the idea of introducing something that could potentially affect SQ.
When you ready, we can continue discussing CamillaDSP in my feature request thread. And V2 is in Alpha, with a GUI to make it easier, but I have yet to try.
(12-Sep-2023, 05:31 PM)uglymusic Wrote: The thing that tweaked my worry module was your expressed commitment to CM4 - I'd be interested in your hardware setup for the CM4 as I've been starting to think if a CM4 might be better for my server (there's probably a whole new thread on this one, I guess).Your comment prompted me to look up the differences between CM4 (have Pi2 Design Mercury V2) and Pi4
https://www.makeuseof.com/raspberry-pi-4...fferences/
Given you are using Pi3's, I think it will be logical to go Pi4 ?