All fixed, all good. Thank you!!!
Well, you can (and as far as I remeber, this has always be possible)
Select all tracks in the album
Edit - Edit tracks
Correct date - Save
and there you are
Yes, for local albums. However, streaming albums in your library do not have the Import Date field to be edited. I put up a Feature Request for it.
I am able to edit Qobuz input dates, even the time stamp. Maybe this is a recent release?
You can edit some dates as shown in the screen pic below. None of which is the Import Date when added the album to your local Roon Library.
I can’t see what editor you are in. You need to go to the track editor. I can change the import date of any Qobuz album. Not sure why I would want to do it, but the option is there for those that want it:
I’m in the Album Editor as the topic and issue is talking about the Import Date for the Album which dictates how it sorts in the album screen.
Yes, you can change the individual track import dates, but, that does not change the actual Album import date. The import date for tracks is stored by Roon separately, but, even if you change all the tracks to a new Import Date, that does not change the Album Import Date.
For example, I added an album on 4-2-2026. You can see that date as the original date in the Track Editor. You can also see that I edited that track (and every other track on album) to a new date of 3-30-2026 and it is active.
However, if you go to the Album Information section, you will see that the Album Import Date is still the original 4-2-2026 date.
Yes, but Roon will sort on the edited date.
We seem to be talking at cross purposes. If I want to change the Qobuz album import date I go to the track editor. That’s all. There is no rhyme or reason. Roon is riddled with these sorts of inconsistencies as it evolved. So sticking with my original example. The import date for this Qobuz album was 21 November 2025:
If I edit in the track editor to todays date, then that sticks on the album view and album date imported sort order:
I don’t know how long this functionality has been there as it is not something I have done in the past but it did come up when all my Qobuz unavailable import dates were reset. I soon gave up though as it was all too much.
Yes, you are right. I had been selecting all and then using the Edit button on the track line which doesn’t change every track even when all are selected. In editing track by track, if even 1 track is mis-matched in terms of Import Date, then it stays with the original Album Import Date.
I will leave the changed date to see if the maintenance process switches the changed date back, which is part of the problem.
Glad to see a possible fix Is imminent. Had this for a while now which sort of makes the “Sort by Date Added” pointless. Just had a stack of old albums showing as newly added… as in, somewhere between 70-100 albums. Got bored counting them
so yeah, looking forward to this fix!
So, is that statement: “The main cause was a synchronisation issue on the Qobuz side”, which in a sense suggests that Qobuz might be to blame, really justified?
Given your belief that it is unclear who is actually responsible for the correctness of the code…
So I’m understanding that for the abum import date to be changed and stick for the whole album, you have to manually and individually change the date on each track of the album?
This is a technically correct solution to what I requested, but not an actual working solution that is useful.
No, you can multi-select tracks just like you can multi-select nearly anything in Roon (and apply edits to the multi-selection)
Still waiting for the fix to land. Obviously, my account isn’t amongst the first groups to be processed.
Is it known, how long the rollout will take in total? One week? One month? Even Longer? What’s to expect?
I was just coming on here to post the exact same thing….I’m in same boat as you.
Yes, confirmed by the fact that the error is now resolving (as corrected Qobuz data roles out) without any changes to the Roon implementation.
I did not say that, my belief (based on observations) is that the root cause of this issue squarely falls with Qobuz.
There’s nothing more I can add, if you wish to add further comment for Roon I suggest you open a topic in Feedback in the meantime enjoy the music.
Hey everyone,
Quick update on where things stand, since I know some of you are still waiting for the fix to reach your library.
This appears to affect a sizable number of Qobuz users within Roon, so the resynchronisation effort on Qobuz’s side is substantial. They’re working through it in batches, and at the current pace it could still take a couple of weeks to reach everyone affected. We’re actively working with the Qobuz team to see whether the daily throughput can be increased and the rollout completed sooner.
As I stated before, we will revisit this thread and notify once process is completed.










