Bug: Tracks imported into Library have date of 1 January 1

The scenario is that a friend brings round a USB stick containing a selection of audio tracks that s/he would like to hear on your Roon system. I did the following, which gave unexpected results:

  1. I get a USB stick with a variety of files culled from different albums. For example:

  1. I plug the USB stick into a PC or Mac that is running a Roon Remote (in my case, Roon Core is running on a ROCK NUC), and I drag and drop the DATAUSB icon from the Windows File Explorer into Roon. The following screen pops up:

  1. So far so good. I say I want to copy the files (because it is not possible to add a USB stick as a shared folder in Windows). I expect to see the files grouped into albums (whether identified or not) that will appear in the “recently added” display on the Overview screen. Instead, nothing apparently happens; the display remains as it was:

  1. So I go to the Tracks browser, display the Path, and filter on the word “Imported”. I discover the files have been imported, but with a date added of “1 January 1”:

  1. Sure enough, if I go to the Albums browser, sort by Date added, the contents of the USB stick are there as my oldest albums:

This must be a bug, surely? The last time I used drag and drop (last year), the date added was correct, so this must have crept in in a later build…


I’m seeing the same. Remote on MacOS and the core(s) are all linux / Rock / Nucleus.

Thanks for the feedback @Geoff_Coupe and @AMP! I am going to have the team bang on this a bit to see what we can come up with. I will be sure to update with findings once testing has completed.


1 Like

@Geoff_Coupe and @AMP ---- Thank you both for your patience and understanding here. We’ve been quite busy getting this release out the door so it is very appreciated!

Myself, along with @dylan and @noris have been working to try and re-create the behavior that you have both reported in this thread in a variety of testing environments to see what we could come up with. All of our testing was conducted with the previous build (i.e 339) and with the most recent build (i.e 354).

In all test runs we were unable to get Roon to produce the same results mentioned in your posts. I did see a remote crash happen once during the drag/drop/import process but this was resolved by a simple reboot of one of my test cores and the behavior did not repeat despite how much stress I tried to put on the system.

Are you both still seeing this with B354 and if you are, are there any other details you can provide me with to make this happen on our end? If there is a bug here we would definitely like to get it in front of the DEV team but as you both know we must make it reproducible first.

Many thanks!

1 Like

@eric - I’m afraid that this is still happening here. I’m using Roon build 354 running on Windows 10 on my desktop PC, and Roon Server build 354 running on ROCK on an Intel i5 NUC (NUC7I5BNH), which has been transposed into an Akasa fanless housing. Dragged and dropped a folder using Windows File Explorer onto the Roon Overview screen.

Edit: I should add that my music library is being housed on an internal 1TB HDD (formatted via ROCK) in the Intel NUC

I’m seeing the same… inconsistently.

All cores are at the most current revisions and either Nucleus+, ROCK, or Ubuntu. I can’t get the ROCK or Nucleus cores to reproduce the issue, but I’m also having a lot of trouble finding music files that aren’t already in the library on those cores. All are using local storage as the target for the drag-and-drop.

On the Ubuntu core (running 354) I’m getting pretty consistent results with the albums showing a 1/1/1 import date. The files are being written to a local disk formatted ext4. After several import / delete / import cycles using the same tracks it got the date right on 1 out of 4 tries. I’ve also tried different permutations of dragging individual files vs the entire album folder vs the album folder contained within an artist folder and the results are the same. Also doesn’t seem to matter if Roon can or can’t identify the album.

I could send you an album which is failing, but it’s only failing on this one core. You’re welcome to grab logs if you like (core name roonvm1). Did these tests immediately after doing the 354 update so all of the action should be in the most recent log file.

@Geoff_Coupe and @AMP ----- Thank you both for the update and additional insight. Very appreciated!

I am going to schedule some more testing to see if can get this to happen in house and if we cannot we will look into enabling diagnostics and check logs. I will be sure to touch base again when the next round of testing has completed. Again, many thanks to you both!


Hi @Geoff_Coupe and @AMP —— Thanks for your patience here!

I have had our QA team trying to reproduce this behavior and they have been getting some mixed results. In light of this the team has asked me to gather some core and remote logs from @Geoff_Coupe so they can have a closer look into this behavior being experienced.

Geoff, with this in mind may very kindly ask you to please perform the following:

  1. Please reproduce the issue and note the time when it occurs.

    1. So I go to the Tracks browser, display the Path, and filter on the word “Imported”. I discover the files have been imported, but with a date added of “1 January 1”

    2. Sure enough, if I go to the Albums browser, sort by Date added, the contents of the USB stick are there as my oldest albums

  2. After the issue has been reproduced please use the support ID found just below in conjunction with the instructions found here to send us over a set of your logs

    support ID: e99e7dd6-a5f0-4ca6-834e-fcf8ddc41572

Note: The support ID should be entered in on the Win10 remote where the issue was reproduced. This procedure will provide us with logs not only from the Win10 remote but also from your core machine as well :sunglasses:

Many thanks!

I’ve reproduced the issue (at 17:23 CET) and tried to send the logs - but am getting a “We couldn’t connect to our server” error message. I’ve saved the support package - what do I do with it? Thanks.

Thanks @Geoff_Coupe! I am going to contact you with revised instructions via PM in a few minutes so you can get your logs over to us.


@Geoff_Coupe and @AMP — Again, thank you both for your continued patience and understanding while our team has been trying to run down this behavior in house.

As you both are aware, our tech team have been having difficulties reproducing this behavior in house and as such we met today to discuss the tickets I opened for both of your reports. Our techs have asked if you both would kindly provide the following:

Andrew, you mentioned here that the files are “being written to a local disk formatted ext4”. My understanding is that this type of formatting will not work on MAC and would like to confirm what was used when you tested on OSX? Thanks!

Geoff, the team would like a new set of logs from your system and as such may I kindly ask you to perform the same procedure listed above. If you run into the same error message please proceed with the work flow discussed in our PM chain.

Many thanks to you both!

Hi @eric

That is correct, but I think something got lost in communication.

The core is running Linux and mounts most of its content via NAS. So as to remove the NAS from the equation (and keep from making a bunch of changes to the NAS library) I setup a new storage location on the root partition of the core’s boot drive. It’s formatted ext4.

All of my experience with this issue has been using a MacOS 10.13.6 remote connected to a linux core.

As an aside, I was at a customer’s home and dropped a file onto his core (one of our firmware updates, which is a WAV file). That file came up with the same 1-JAN-1 import date.

His core is Ubuntu 16.04 on a NUC. Music storage is on a synology NAS. Remote running on MacOS. In my case, at least, the common element seems to be linux / ext4.

@AMP ----- Thank you for reaching out and clarifying things for information for me! Very appreciated Andrew.

I am going to update your ticket right now. Thanks again!


Hi @eric - logs uploaded, see my PM. Thanks.

1 Like

Hi @Geoff_Coupe,

We’ve recently released Roon 1.7 (Build 521) which includes changes that should improve this behavior. Please give it this a try and let us know how it goes!

You can read the full release notes here:

The Team at Roon Labs

Hi @dylan - it is now working properly. One thing to watch out for is how the files are organised.

  • If they are a bunch of individual files, each with different date and timestamps for the file creation/modified dates, then both albums and files in the Roon Library will be marked with the date/time of Import.
  • If, however, the files are in a folder, and the folder is dragged and dropped into Roon, then Roon sets the date added of the album to be whatever the folder has as the folder creation date.

Here’s an example. I dragged and dropped a bunch of individual files created several years ago, and a folder containing a couple of Yo-Yo Ma tracks. The latter had been created on the 7th January 2020. In the Album browser, the individual files have been clumped into four albums, with a “Date Added” set to today. The Yo-Yo- Ma album has been created, but the “Date Added” has been set to the 7th January 2020 - the timestamp of the folder.