To be fair, they are going through a company acquisition and a healthy stack of devices trying to get roon ready certs. And its the holiday season at this point. Im sure the devs have families.
A few months back, I downgraded my TIDAL subscription from HiFi Plus to HiFi. In the mobile and desktop apps, the change was reflected accurately with only conventional 16/44 content.
Today, in the BluOS controller, I noticed MQA content is streaming even though a few weeks ago, this album was “CD.”
I am obviously out-of-the-loop on recent changes.
HiFi includes 16/44.1 MQA CD. MQA will be recognized by MQA DAC even if you truncate a 24/44.1 delivery of MQA source (HiFi Plus) to 16/44.1 (HiFi). This is by design - not a flaw.
I was under the impression Tidal was going to replace these with true flac CD files. Does only the Max setting bypass MQA? Was looking to go back to Tidal once roon implemented Max setting but not if still a lot of MQA files out there.
Again, MAX = Hi-Res FLAC (higher priority) and MQA
If an album is available as high res FLAC then that will be played with Tidal Max. If there isn’t a high res FLAC version available then you will get the MQA version.
So what happens on the lower setting when there is 16 bit MQA file and a 16 bit CD file? I assume the Max setting would always choose non MQA version. And once roon is updated we’d actually be able to see all versions and choose. Roon has essentially confirm Tidal update won’t becoming this year.
not in roon, they continue to come out in MQA for me, the same albums that through the streamer are Max flac in Roon are still in MQA, and they sound worse, I imagine we have to wait as I have already read several times here
I was answering the questions related to how Tidal treats Tidal MAX and why there is MQA CD even with HiFi subscription, not referring to Roon which does not support MAX yet. (There is a widespread belief that by downgrading to HiFi you avoid MQA but I’m convinced it is not true at this point, and another misunderstanding that with MAX most MQA albums are to be replaced by Hi-Res FLAC, which is obviously false. Those who really want to avoid MQA will have to use Qobuz instead, if available in their countries.)
I recently changed my dac to one that doesn’t decode MQA files. I use a TIDAL MAX subscription. I can’t get hi res quality in Flack even though Tidal offers it. In the Roon settings I checked “everything except MQA” and in the streamer “no MQA support”. Roon Rock is only connected to the LAN, I have not connected it to the DAC via USB. Should I change something to make the endpoint send the hi res signal to the DAC?
Welcome to the Roon community, @Jacek_Gut.
I merged your post with this thread. Here’s a recent update from Roon.
https://community.roonlabs.com/t/roon-compatibility-with-new-tidal-hires-flac/246363/181
OK thanks. It’s a pity that there is no access to Qobuz in Poland, because the waiting time for integration with Tidal is very long.
Actually, it is too long already. I understand that the merger with Harman Kardon keeps the management busy, but managers usually don’t code. So, what are the techies doing? We are customers to the Roon platform and pay quite some money without any timely response to new technology. Very disappointing I have to say.
This is good to know. At one point I was kind of excited to try Tidal again but all of this sounds like a headache to me to get a handful of albums that are not Qobuz at the moment. Also Tidal has 10,000 max album favorites that I’ve hit and can’t add new favorites. Don’t believe Qobuz has this limit or they just have more albums missing than I thought and below the limit.
So for Tidal never said they’re completely moving away from MQA and MQA were recently bought out so they live to see another day. So possible Tidal will continue to offer MQA for unseen future.
In case you missed it, a respond from Roon …
https://community.roonlabs.com/t/roon-compatibility-with-new-tidal-hires-flac/246363/326?u=carl
Hi Carl,
I have read and understood all the posts on this topic. The core message from Roon is: We know our customers want this Tidal HiRes Flac, but we are busy doing something else. By the way, we’re not going to tell you what we’re doing, and we’re not going to tell you when we’re going to find the time to do the HighRes FLAC Tidal integration. Every other software company I work with has a release policy. Roon doesn’t and that’s disappointing and leaves us customers in the dark.
That’s a glass half full interpretation but that’s your call.
I’m more positive and pleased that Roon has confirmed they are working on this together with Tidal.
You are in Vienna, nobody forced you to use Tidal since 2014 when Qobuz launched in Austria. So it was good enough with MQA until fall 2023 but now 2 months more is a disaster?
And very few consumer software companies have public roadmaps that make promises. For good reasons as well
Hey @Franz_Stibitzhofer, actually, it looks like you’ve read and then misinterpreted what was said. Let me help - our core message is: This is something we’re all excited about and work is in progress on this currently. We’re not working on other stuff instead, we do happen to have a lot of concurrent work underway on new features. In addition means we’re doing these things also.
Our work is extremely fluid and in this case even more so because we’re coordinating with a partner. Roon doesn’t disclose features that are in development. We’ve always been consistent with that policy. We’re focused on quality, not shipping dates.
Additionally, please refrain from adding to misinformation about our acquisition and suggesting that our techs are sitting around on their thumbs. Our developers are talented, creative, hard-working people. We do a lot with a small team of dedicated staff. You aren’t privy to our internal processes, with that, kindly don’t insult the team or the work they do.
Thanks for the explanations. I understand you do not want to provide exact timelines to not overcommit and to not disappoint other users. For me it would be ok to provide estimate timeliness and if something goes wrong give an explanation why a given functionality is postponed.
Best Regards.