Roon is taking file modification time instead of IMPORTDATE. I’m pretty sure this was working properly a few months ago, but I have started over with a new database.
Am I missing something, or is this a regression?
I did a couple of tests by modifying IMPORTDATE and it seems to work as usual
Maybe it’s the date/time format?
1 Like
Thanks for confirming this. I note that the format isn’t mentioned here:
But, it is here, and uses YYYY-MM-DD.
Sigh … DD/MM/YYYY or MM/DD/YYYY (?) is not the standard approach. I guess I’ll have to write a script to transform the dates, and preserve the original value. I may try dropping the time value first.
Date formats are a pain , I have for many years only formatted dates as text month
01 Mar 25 ,
the DD/MM or MM/DD has no standard it depends on what nationality you are if even then
Okay, I’ve had a closer look, and the issue isn’t formatting, but rather the date itself. Roon only uses IMPORTDATE if all the dates are the same.
In each case I checked, so far, they were multi-disk, and each disk had a different time stamp.
So, to summarize:
DD/MM/YYYYworks (I’m not sure howMM/DD/YYYYis handled, unless Roon checks locale)YYYY-MM-DDworksYYYY-MM-DD HH:MM:SSworks- All dates must be the same
At least I can keep IMPORTDATE as-is; I’ll write a script to check for differences in albums, just to be safe.
Thanks for the input … bouncing ideas around often helps to find a solution.
1 Like
PS: I usually set the time to noon (12:00) because last I checked, Roon still thought that a user provided date is in UTC and not local time – which of course is usually not the case. With the time set to noon the import date should stay the same day even after Roon’s UTC to local time translation.