MQA/Local track preference/duplicate bug?

Support
1

Core Machine (Operating system/System info/Roon build number)

ROCK/Intel NUC8I3BEH3, 8GB RAM, 256GB M.2 SSD, 500GB SSD storage/Roon v.1.7 (build 528)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Plusnet (Technicolor) router, Netgear and Zyxel switches, all hardwired (ethernet) apart from iphone/ipad remotes which are wifi.

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Meridian 818v3 (ID41, ethernet)

Description Of Issue

Been having a weird problem recently.

For a while, I’ve kept local copies of recordings I already owned on the ROCK internal drive, alongside MQA versions of the same file streamed from Tidal.

This used to work in that I’d add the Tidal album to the library, then set the MQA version as the primary version. Fine.

The other day, I noticed for the first time, that the local file was playing instead of the MQA file and that I couldn’t add the MQA version to the library from the iPhone app, nor remove the local album from duplicates from there. On the Mac OS version of Roon, I could add the MQA file to the library which then set it as the primary version, but back on the iPhone I usually use as a remote, the local file still persisted as the one playing, and the one set as primary.

In the end I had to resort to deleting the local file, in which case the MQA from Tidal stayed as the primary version, and played OK.

Today, searching for a different album with the same setup, I can see both albums in the search results. The local file sets itself as the primary, despite my having previously set the Tidal MQA as primary, in this case, if I select the MQA version, the local file disappears completely as an option under the ‘versions’ tab, but still appears as a separate album under search results.

This seems odd/buggy behaviour all round. I don’t really want to have to physically delete/remove local files to de-dup, or prefer the Tidal MQA - for one thing, it’s useful to demo MQA to friends, etc.

3

As part of troubleshooting have you rebooted everything?

4

Hi @ScreenMachine,

Can you share some screenshots of what you’re seeing?

5

Yes, everything has been rebooted.

6

Hi Dylan,

Here are some screenshots corresponding to the above, hope they make sense out of context, let me know if you need anything further -

IMG_9979.PNG
IMG_9979.PNG1242×2208 385 KB
IMG_9984.PNG
IMG_9984.PNG1242×2208 378 KB
IMG_9980.PNG
IMG_9980.PNG1242×2208 369 KB
IMG_9981.PNG
IMG_9981.PNG1242×2208 366 KB
IMG_9982.PNG
IMG_9982.PNG1242×2208 480 KB
IMG_9983.PNG
IMG_9983.PNG1242×2208 511 KB
image
image1242×2208 449 KB

It’s difficult to represent what’s going on because, as I mentioned above, the albums which show, and which are in the library/primary version, or not, change according to which I have selected at the time. To me, this is not correct behaviour -

  1. once I have added a version to the library, it should stay there, and not keep ‘dropping off’
  2. once I have made a library version the primary version, this should stick and not keep making another version the primary.
  3. duplicate versions should show at all times, and not disappear from the list when I have another version set as primary (unless I’ve actually removed a version from duplicates).
  4. Add to library should work, even on the remote, and not do nothing.
  5. Make primary and remove from duplicates should work and not be greyed out.

Many thanks for your help,

James

7

Thanks, @ScreenMachine. I’ll pass this along to the team for further investigation.

8

Thanks Dylan,

Just for a bit of extra info, I noticed today that this odd behaviour does not occur if both tracks in question originate on Tidal - I am able to manipulate those in ways I would consider normal in terms of the above. So it seems specific to local files/Tidal/Tidal MQA in some way.

9

Just some new behaviour to report - now I can’t add a new MQA album from Tidal to my library at all using Roon on my iPhone.

10

And even more weird new behaviour with Tidal/MQA tonight. Tried to play André Previn / Pittsburgh Symphony Orchestra / Gershwin: Rhapsody in Blue / An American in Paris / Piano Concerto in F / Phillips label, which was showing up as MQA on Tidal.

Then noticed that when I hit play on An American In Paris, Roon was actually playing a different version - a Classic FM branded non-MQA version.

I made several attempts to play the MQA version, but Roon persisted in playing the non-MQA album.

This was resolved only by adding the MQA, Phillips album to my library and it played the MQA version correctly.

And yes in this case my iPhone remote could add the MQA album.

Guys, what’s going on? I never had any of these issues until recently, something feels very broken here.

11

Any progress on this, please? Still persisting here…

12

Tidal user in the US, just pulled up the album ( no local copy ) and am playing it via Roon now. It’s playing the correct tracks from the album in MQA.

Not sure this helps you but it appears that now Roon is playing the selected album and not another version.

Using Roon on Windows 10 laptop to search and control core.

Tim

13

I’m afraid not, I have the same random behaviour persisting, as described in the posts above. Sometimes I can get Roon to play the MQA version, sometimes it decides it will play the red-book version, whether I have the album locally or whether there are just two Tidal versions. Sometimes it will allow me to add an MQA album to my library if no existing copy is there locally or on Tidal. Still different behaviour on the iPhone remote to the Mac OS remote. Very strange indeed.

14

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.