(08-Mar-2019, 09:03 AM)agent_kith Wrote: 1) Are you saying, after adding in the Tidal configuration, MPD 0.21.5 is now broken for you? If yes, can you generate a diagnostic file and send it to me? Thanks.
2) Looking at how you're describing the workflow, the BubbleUPNP is the ideal configuration to go for Tidal <-> MPD integration. Bubble will create the Tidal URL and upmpdcli will send it to MPD. I'd double check upmpdcli later this weekend and see if I need to do anything extra to get this to work.
1) Ok, problem solved, it was the fuc... internet box, i have no possibility to control the router and this one block some streams without any logic. I insert a real router on my network and now it is much better and predictable... In this configuration i can use MPD 0.21+UPMPDCLI like a charm with snakeoil 1.1.3 ;-)
I'll try to play a tidal track (http://192.xxx.x.xx:xxxxx/tidal/94587741.flac) with MPD 0.21 alone and modified mpd.conf as described below without any success. I supect the modification described have a typo error or token extracted is not efficient for MPD 0.21.
2) In opposite, if i install UPMPDCLI and select it as player, i am able to use mconnect to choose a tidal song and stream it to my snakeoil device (it appear as "UPMPD" in players in mconnect). Funny thing: if i open M.A.L.P. i can see the URL of the tidal stream and stop/play it directly with M.A.L.P. This is because tidal upmpdcli module decrypt the stream i suppose.
It is the same with Bubbleupnp, the only added value to share a tidal stream with share function to MPD is to avoid UPMPDCLI use and maybe obtain a better SQ. But for the moment i cannot make MPD 0.21 compatible with tidal streams.