09-09-2018, 12:30 PM
(09-04-2018, 01:45 PM)TheOldPresbyope Wrote:(09-04-2018, 08:24 AM)gza123 Wrote: Thanks Kent,
I enabled upmpdcli logging exactly as you advised. Then I tried to play one of my Tidal playlists and see what has been written into /var/log/moodeupnp.log . Surprisingly the logfile was not been created at all.
Then I had a look at Audio info -> Input Processing -> Source from moOde menu. In most cases there is statement: File Not Found.
However, sometimes it shows moOde local adderes instead of Tidal's url:
I'm wondering what was happened?
Regards,
It's been a while since I explored the innards of upmpdcli. I probably left something out of my instructions.
However, the source info you reported is correct. upmpdcli is acting as a proxy server for the Tidal stream so you see the IP address of the local host rather than a Tidal server.
[EDIT] Do you see anything interesting in /var/log/mpd/log?
Here's what my log contains after successfully playing first a radio station and then a track from Tidal:
Code:Sep 04 09:34 : player: played "http://stream.radioactive.fm:8000/ractive"
Sep 04 09:37 : player: played "http://192.168.1.184:49149/tidal/track?version=1&trackId=89621546"
I'll report back after revisiting my notes on upmpdcli.
Regards,
Kent
For your Notes Kent:
I am no longer on the version UPMPDCLI that is default with Moode but I think the log entries actually end up in syslog, perhaps a bug. I think think this is fixed in the latest source code but it is not available as a package.
From what I understand from the developer UPMPDCLI serves up a url (as above) but this url actually does a redirect to the tidal url which is why the Tidal URL errors appear in the MPD logs I think.