(03-24-2021, 06:45 PM)Tim Curtis Wrote: The approach is somewhat similar to what was done several years ago to support Airplay metadata. It proved to be overly complex, unreliable and impossible to maintain.Understood. Yes I can imagine many things that can go wrong mixing both... It was a shortcut to get a quick working demo.
Core components like engine-mpd.php and the rest of the MPD idle timeout pipeline are not on the table to be modified since they provide the underlying reliability for moOde. The renderer management framework is designed to be separate from core MPD framework to ensure its own reliability. If the two were to become intertwined the overall system would become unreliable.
Renderer metadata would need an approach that keeps it in its own pipeline, separate from core MPD components and it would need to prevent UI access to any MPD functions.
Would it be possible to automatically redirect the user to a separate renderer page (separated from MPD core components) once it is identified that Spotify is active, instead of showing a cover over the MPD user interface? In the future this could be reused for Airplay/Sonos or whatever.
This renderer status page would show song title/author/album cover along with some minimal user interaction controls (play/pause) using the same visual style as for MPD (but without sharing any code).
Would one of the configuration pages (like spo-config.php + html template) be a good model from an application architecture point of view to use for a new hypothetical “renderer-status.php + .html”?
