I have two copies of my music files, one on a home library (Synology NAS) and another on a MacBook Pro (work). There is one album that Roon refuses to import on the home library, even though the identical set of files is correctly imported on the work library. Note, this is not an issue of album identification, Roon simply does not see the files at all on the NAS library.
I have re-copied the files twice from my laptop to the NAS, but RoonServer on the NAS will not detect them with a Force Rescan. Any ideas?
How are the music files set up on both of your devices? (Local folders on both devices?)
What happens if you restart the app via package center or restart the whole synology NAS?
Before you do: can you check the synology activity panel? How much Ram is currently in use/free?
Yes, the files are in local folders on both devices. I had already tried restarting the Roon package on Synology, but no change in behavior.
The album that will not import was my only set of mp3 files, the rest being flac or dsf. I tried converting a few flac to mp3, and those are successfully imported by Roon, so there is not a general issue with mp3 handling on the NAS.
Before rebooting, the DS1515+ is using 15% of 6GB. RoonAppliance is only using 258 MB, probably because I restarted RoonServer fairly recently.
Rebooting the NAS just now had no further effect on this behavior. The album remains undetectable by Roon on the NAS.
There are no duplicates in this case. There are two roon databases running on two different computers with different file systems. Just to be certain, I turned on âShow hidden albumsâ on the synology library, but the album in question is still missing from that library.
One thing that proved helpful when I had a similar âmissing albumâ issue: go to âall tracksâ, export that to a spreadsheet, and look for the path to the album to see what itâs actually matching, if itâs there.
Also, you might want to check to see if the files are being found as âcorruptâ by the NASâs ROON implementation. I had that happen with a number of tracks that were fine on other ROON implementations, with shared files.
The files are also missing from the exported excel library (with âShow hidden tracksâ enabled). As another test, if I add other music files to the same directory folder as the non-importable album, Roon finds the additional files. Therefore, the folder path is not broken.
I am unsure how to determine if Roon thinks the tracks are corrupt if they do not show up in the Synology library. In the MacBook library, the Track Info windows doesnât indicate any corruption issues with the tracks. Is that the right place to look?
Can you try if anything changes if you edit the id3 tag of one of the non importing tracks?
I use the software Tag on my mac.
I experienced before that some tracks were not imported due to bad id3 tags. I just made a small change in any id3 tag field and could change it back afterwards. These files were then correctly imported.
If you look at the Roon server logs you can see if the files are being flagged as invalid (your logs may have rolled over, or not, but thatâs how I discovered them).
I had already tried editing some tags with JRiver, but the files still did not import. I will try wiping all tags just in case there is something in an odd tag field that Iâm not normally displaying.
Yep - thatâs what I saw too. The tracks were fine with the native Synology servers, and with OS X and Windows Roon⌠maybe some library thatâs incorrectly flagging them as corrupt (or is pickier than most)âŚ
Roon uses native codecs for MP3 and AAC, and ffmpeg on Linux is clearly hating your file. Chances are the file is corrupt, but the OSX decoder can deal with it anyway.
Running it through mp3check or another validation/fixer tool might fix it enough to let ffmpeg see it just fine.
I tested the album on QNAP and the files are also not recognized there.
I also tried to tinker with the files using ffmepg (command line).
You can rebuild the mp3 files without another encoding process by entering the folder that contains the bad mp3 files and enter
ls *.mp3 | while read f; do ffmpeg -i "$f" -c:a copy -c:v copy $(basename "${f/.mp3}")_new.mp3 & done
The track-title and coverart has to be inserted manually afterwards. The other meta information seem to be in the new mp3.
The files are then correctly recognized by RoonServer.
I forgot to mention that ffmpeg is not preinstalled on the mac.
I downloaded it here and copied all 3 binaries to the /usr/local/bin directory to make it globally executable.
