I was scrolling through my Metallica albums when I found out that …And Justice For All was missing. I was quite surprised because that album appears just fine in JRiver.
After some investigation, it seems that Roon does not import folders beginning with “.”
Anyone can reproduce this ?
Thanks !
Setup : Music files on Synology DS413j NAS -> ethernet -> Roon 1.3 on Windows 10 desktop PC (using mapped drives for NAS files)
Roon 1.3 made it possible to stop ignoring folders starting with a “.”, although we do ignore them by default. To change this on your system, go to settings -> storage -> 3 dots menu for the folder you want to change. That will bring up a screen that looks like this:
Do you happen to have ZZTop’s “Recycler” album as well? Not sure whether this one’s still covered by Roon not scraping folders with Recycle in the folder name.
Hi @ben,
I assume that the leading slash refers to the configured ‘Folder’ path. Would this then mean that ‘/.’ only ignores top level directories that start with a ‘.’?
This isn’t quite right. The ignore patterns are just use a with a simple string contains test. This means that a slash of the appropriate direction (’/’ on Mac/Linux cores, ‘’ on Windows cores) at the start of the pattern means “match directory names beginning with this”, and at the end means “match directory names ending with this”. The ‘;’ is just a seperator between patterns.
In other news, while looking at a related bug I just found a line in our code that ignored all directory or file names starting with a ‘.’ regardless of all the normal ignoring mechanisms. The fact that removing the “/.;” from the ignore patterns didn’t work was just a bug, which should be fixed for the next build.
Correct, at this time we don’t support any kind of wildcard characters. I don’t think we really want to either, those patterns are hard enough to explain as it is.
By default, all watched folders in Roon come with a pattern like “/.” or “.” in the ignore patterns to ignore files and folders starting with a “.” on all systems. We’ve just made it so that in 1.3 you can turn that off if you want to for whatever reason.