Whenever I add a new FLAC album to my library, Roon is detecting the album and importing all tracks apart from the last one which it always says is corrupt with zero bytes in length (you can see this information from viewing the 'Go to folder...' option for the album). In order to get Roon to import all of the tracks and therefore recognise the album is by renaming the folder containing the tracks and then renaming in back to what it was originally. This seems to force Roon to re-analyse the folder and it imports the missing track. I am guessing that the issue might be because Roon is analysing the FLAC files as they are being copied across to the monitored library folder before they have all been copied fully. This has only been a problem for the past release or two though and I have imported new albums in the same way for many years without any issues so something seems to have changed.
Describe your network setup
Mac mini M4 Roon server with library files on a USB HDD
I have just imported another album which had the same problem apart it was track 1 that was marked as corrupt and not the last track on the album as before.
This could indeed be the issue here. Perhaps you could stop Roon Server before adding albums to the watched folder, and restart Roon Server after all files are copied.
this has been my solution as well. I’ve experienced the same issue since the last update or so, and quitting Roon Server before I import has “solved” the corrupted file issue.
Can you reproduce this issue, note the exact local time + date + track that had the zero bytes in length and let us know here? We will activate diagnostics and check logs for clues to see if there’s anything interesting noted there, thanks!
I can share it but all I did was rename the album folder within macOS by adding a character, waited a few seconds and then renamed it back and Roon automatically updated the album with the missing track that was no longer listed as corrupt. The track also plays fine.
I assume that Roon is scanning the file before it has been fully copied across and is therefore corrupt at that point in time.
Hi @Daniel - I had a couple of albums with a corrupted file when I added them an hour or so ago so tried running the Force Rescan as suggested.
This didn’t fix the albums which both still showed a corrupted file after the process had finished. I then renamed the two folders containing the album tracks by just adding another character and then renamed them back to the original name which triggered a rescan of the files and this fixed both albums.
Oddly enough, we haven’t made any changes to our analysis mechanism. What is your background audio analysis speed set to? If you change this setting at all, does it affect your importing?
With that, are you by chance importing your files from a different location? What happens if you test out importing from a few different locations?
We’re seeing some errors around the file tags as well, have you incorporated any additional file tagging prior to importing into your storage location?
