11-04-2021, 11:35 PM
(This post was last modified: 11-04-2021, 11:36 PM by MikeyFresh.)
(11-04-2021, 07:22 PM)cereyanlimusiki Wrote:How about the TIDAL settings within the mconnect app? I think it has to be set for HiFi, but I'm going on memory from a trial of TIDAL 3 years ago. Ultimately I settled on Qobuz instead.(11-04-2021, 04:42 PM)cereyanlimusiki Wrote: @TheOldPresbyope TheOldPresbyope@cereyanlimusiki
The error you see is only an indirect indication since it occurs downstream of the upmpdcli renderer.
To get a more direct look, you'll need to enable the upmpdcli logging and examine its separate log. You'll have to work from the command line as user root and be familiar with operations like file manipulations and text editing using a tool such as nano or vi.
Yes I am comfortable with that
Quote:1. Are you running on a moOde player with no changes beyond those needed to enable your DAC and the UPnP renderer? No changes to esoteric audio parameters, right? It's difficult to diagnose problems remotely if the system is not in a known state.
Yes . It's Vanilla installation with only wifi , DAC and Spotify Renderer set up
Quote:I'm unclear what "does not play TIDAL track" means. Do you see the track appear in the queue in moOde's Playback screen? Does mconnect indicate the track is playing or is it paused/stopped?No, Nothing
See screenshot
[img][/img]