YES !!
It’s a solution.
After the change to import date by “file creation time” (before, it was “file modification time”) there was a lot of exchanges with your central servers. And gradually the Album view sorted by Date added became correct (because the date added of each album was the right one).
Of course I will keep this setting with this new value.
I changed the machine for my Roon server some months ago, and I suppose the setting for import date was effectively by “file creation time” on the old machine, because I explicitly manage this attribute on my flac files. So, the new setting is really what I want, for local albums.
On the new machine I forgot to duplicate the old value for this setting, and it seemed without importance because I very rarely add local albums nowadays.
However, the behavior with import date by “file modification time” gave a correct result with Roon v2.64 and previous.
As there is really no files imported for Qobuz albums, your change of interpretation for this setting in v2.65 is comprehensible, but the side effect was stressing.
Happy to have a prompt solution, easy, and which doesn’t need a new software version (I will add new Qobuz albums this week-end !)
Thank you !
It is my habit to sort albums by “last added.” However, after updating to Roon version 2.65, the “date added” for all Tidal albums has been set to April 29, 2026—the date I performed the update. Fortunately, albums on my file share still have the correct “date added.”
Very, very annoying! Can this be fixed, and if so, how?
Development is finalizing a fix for this issue and it will soon be in the pipeline for release. This should resolve these “Date Added” discrepancies across all streaming services in Roon. We don’t yet have a confirmed timeline to release but will share that information here as soon as it becomes available.
As a reminder, a workaround for those affected in the meantime:
Navigate to Roon Settings > Library > Import Settings
Scroll down to “Import date defaults to” and select “File Creation time” (temporarily)
Thanks for reaching out. We had some changes in this area with our most recent release from yesterday. Can you please update and let us know how it’s looking on your end?