Since last Roon-Updates, it shows MQA in the signal path. This must be wrong, as Qobuz does not supply MQA. I do not use any other sources than Qobuz. There was no update of the Lyngdorf in the meantime, so it must be a bug in Roon…
However I am not sure if this is truly a matter of the Lyngdorf firmware. Before recent Roon updates it did show a correct signal path and there has been no update to the TDAI since october 2022…
Just out of curiosity, have you checked the “device setup” for the Lyngdorf in Roon to see if “MQA Capabilities” is set to “No MQA support”? Don’t know if it will make a difference but worth a look?
Eh, Qobuz absolutely does have MQA FLACs (MQA and FLAC are completely orthogonal anyway). If that’s what the label gives them (e.g. 2L), that’s what you will get. Of course if the track in question definitely is NOT an MQA one then there’s problem somewhere, but just because it is Qobuz does not mean that you can not get an MQA track from them.
This is indeed bizarre. I would like to ask you to duplicate this for us so we can get logs. It’s also possible we can source the hardware to try and duplicate the issue and compare notes.
Will you please do the following?
Play a track to duplicate the issue.
Respond with the date, time (and zone), and the artist/track played.
We can use this information to look at the logs and then attempt to duplicate things on our side.
It would be helpful if you could share a screenshot of the signal path and also say what track/album you are playing and what the source is (local file/Qobuz/Tidal). Thanks.
Roon cannot “activate” MQA. See pic. below. Roon is sending the file without any processing or DSP to the Lyngdorf. Everything else happens afterwards:
Once Roon has handed the file off to the Lyngdorf, anything below that line is just Roon reporting what the Lyngdorf is doing. For some reason, the Lyngdorf is seeing it as an MQA file. Have you tried asking Lyngdorf support? It looks like an error in their process reporting.
Sure, but, that is a different reporting mechanism. The Lyngdorf is reporting this step back to Roon:
Just like the Lyngdorf is reporting back it’s RoomPerfect process and the Limiter.
So, it is probably, as I mentioned in the previous post, an error in Lyngdorf’s process reporting to Roon. The fix will probably have to come from Lyngdorf since it is reporting this information back to the RoonServer.