I’ve been noticing that fairly often when I copy music to my NAS drive where ROON accessing it there are skipped files. This happens with music ripped from CD as well as digital downloads. I usually keep my music in ALAC format. I found that if I converted the skipped files to FLAC then ROON would see them.
Eventually, I would see two versions of the songs show up, both FLAC and ALAC. I was confused by this at first then realized that when the ROON server was restarted it was then reading the original ALAC files. Since then, when I see skipped files I always restart the ROON server and so far that has always fixed the problem for me.
We wanted to split this report into a dedicated thread so we could investigate this behavior more deeply.
Can you please provide an example of an album you imported that caused this duplicate FLAC/ALAC behavior to occur? Ideally, this would be an album you’d imported in the last week, so we could capture it in the diagnostic log period for closer inspection.
Please also upload an album here, just in case we’re able to reproduce it immediately with the media in question: Media Uploader
I just downloaded a couple of albums from HDTracks. One of them (Just Like That - Bonnie Raitt) had one song that was skipped. Here’s a couple of screenshots:
Thanks for sending over the files @Tony_Fardella! We were able to reproduce this in-house and will be discussing potential next steps with our development team tomorrow.
I should have more information to share after that - thank you for your patience in the meantime!
Thanks for your patience! If possible, could you share your exact process, step by step, so I can share it with the team?
With that, if you temporarily disable your turn Roon/Storage, move the new files into your watched folder, and then turn Roon/Storage back on, do you experience the same issue?
What I usually do is to rip a CD to my laptop using DBPowerAmp or sometimes (more often these days) it’s a digital download from HDTracks, Qobuz, or BandCamp. I then copy the folders containing the new albums to my NAS drive over the network. That’s pretty much it. Of course now I check that the files were recognized and, if not, I restart the ROON server.
Next time I get some new albums I will try disabling the ROON storage and see what that does. Doesn’t seem too much different from restarting the server though.
What happens if you force a re-scan of this album from the album editor window?
Navigate to an affected album you’ve attempted to import. Click on three dots and find the Your Files section. Re-scan, re-analyze, and re-identify the album. Does this have any effect?
I’ve tried forcing a rescan many times and it doesn’t seem to fix the problem. Only restarting fixes the problem for me.
Also, I just downloaded a new album this morning from Qobuz. I disabled the storage on the ROON server like you mentioned, then copied the album over, and re-enabled. The album imported fine. Since not all albums have this problem I’m not sure that tells us much.
Thanks for sharing the above info @Tony_Fardella - we’ll forward it to our development team for further analysis.
In the meantime, while I realize it’s less than ideal, let me know if you end up running into the same issue when continuing to disable your watched folder prior to adding new content.
Following up on the issue here, our development team has pushed a fix that should be included in one of the upcoming releases. I can’t speak on specific timelines, but a fix is in the pipeline that should get you sorted out for future imports!
I’ll go ahead and close this thread for now, but definitely keep your eyes on our Software Release notes over the next update or two for additional details!
