I have a question about a use case. I am a life long end user and not in IT so there is a good chance I am asking the wrong question.
I have been directed to mopidy from the Jellyfin crowd, after asking a question about a 3 part client server model, which I am told is better known as ‘casting’. Say I have a Jellyfin server at home. It has music on it. I want to stream it to a client. I have a repurposed hifi from the 90s, now driven by (something like) an rpi. I want to use a phone to browse the music on the server, then when you press play it comes over the repurposed hifi.
To make this work I think I would have the mopidy-jellyfin back end and then two mopidy clients, one a phone like M.A.L.P. or browse a web page client like Mopidy-http, and have it play out another headless (?rpi?) client (what would that be?). Is this within scope of Mopidy or am I just getting over-imaginative?
By doing this I don’t have to put a whole head on the rpi/other, and my wife can stop walking round with her favourite music pouring out of the rubbish mobile phone speakers in her pocket; streaming what we have from our server, not what she can search off YouTube with all the ads.
Is what I am suggesting achievable/ beyond scope for mopidy?