#222 New albums not found when scanned, but new tracks in existing ones are

[Steve Insley]

Hi

Weird behaviour on 6.1.3 of late. When I add new music to an existing album (e.g. one that I'm creating and adding new tracks for mix testing) they show up immediately. However, if I add a new artist/album, they do not, even after using "scan media folders now".

The only way I can get new music to add now is by disabling then deleting the music folder entry in "settings" -> "media folders", scanning, then re-adding the folder and scanning again. Nothing else seems to work.

I have restored an old version of my DB from a time when I know everything worked, but the problem persists.

Please help! This is driving me mad!

Thanks,
Steve.

[Steve Insley]

Extra info:
- Running 6.1.3
- Premium licence
- Windows Server 2012R2 - up to date with all updates

To elaborate after some additional testing, another use case is:

• I have a new album for a new artist for which I have no other albums
• I add a new folder at the root of my music folder for the artist and a sub-folder for the album that contains the tracks. Scanning does not update the library with the new album
• I add a new folder for the new artist's album into an EXISTING folder for a different artist. Scanning correctly picks up the new album and correct artist name, despite it being in the wrong folder. Yay tagging.
• I move the folder after it has been detected into a new artist folder, rescan, the album disappears.

I think with multiple tests in different scenarios I have proved conclusively that Subsonic no longer detects new folders sitting at the root of the music library folder. No amount of "touching" to update create/update/accesssed dates forces SS to detect it.

I have found over a dozen other posts in various forums with people having the exact same problem on both Windows and Linux. Given that Sindre has chosen to go closed-source, but now seemingly doesn't ever pick up any support tickets, perhaps it's time to abandon Subsonic in favour of something else?

[Steve Insley]

FURTHER UPDATE:

If I manually add an entry into the MEDIA_FILE table in the database through the db.view page using (my specific case example):

insert into media_file values (46015, 'R:\Media\Music\Perturbator', 'R:\Media\Music', 'DIRECTORY', null, null, null, 'Perturbator', null, null, null, null, null, null, false, null, null, null, null, null, 'R:\Media\Music', 0, null, null, 0,0,0,0, true, 5)

...and then re-scan the library, the album that exists in that folder now shows up!!

I think the (potential) bug here is simply that new folders in root music folder are not detected in the scan.

[Sindre Mehus]

Unfortunately I'm not able to reproduce this error. Normally, this behavior would suggest that the last-modified timestamp of the parent (root) directory hasn't been updated, but you have checked that.

Does anything happen if you click the "Refresh" link on the "Index" page?

Are there any errors in c:\subsonic\subsonic.log?

Regards, Sindre

[Steve Insley]

Based on your comments above, I decided try the following:
1) stop subsonic service
2) create a new folder to contain all my music
3) move all folders from my old music folder to the new one
4) delete the old music folder
5) rename the new folder with the same name as the old one
6) restart Subsonic

This seems to have helped the situation in that new artist folders (and albums within) are now detected by Subsonic when I run a scan! However, there seems to be a few minutes of lag between the scan completing and the new albums showing up, even if I refresh the web interface. I guess there's an on-going background task that is running that doesn't add the new alubm to the database until some other processing completes? Just a theory.

btw: I don't have the "fast access mode" setting checked. A few months back (prior to upgrade to 6.1.3 from 5.3) when I added new artists/albums, they would show up in my subsonic library after a few seconds automatically without having to trigger a scan. This still doesn't seem to happen even after I updated.

[Steve Insley]

UPDATE:

After a LOT of investigation, it turns out that the issue is with StableBit Drivepool. I have a pooled drive on which I keep all my music. Unfortunately, unless all files are all under one folder that exists on one drive (in the pool) only, the timestamps of the folders are not reported properly and Subsonic cannot "see" the changes when it scans.

So either:
a) StableBit need to fix this (what I believe to be) bug and Subsonic should work ok, or/and
b) Subsonic needs to be updated to be a bit more agressive in how it checks for new/changed files. I can only asusme at the moment that folder timestamps are used to determine changes and if this is reported incorrectly, then the folder's contents are not scanned and the files not found.

For (b) - I guess that could be a configurable option?

[Anonymous]

[Anonymous]

[Anonymous]

[Sebastian Mangelsen]

I can cofirm the bug even in version 6.1.6 running in a Docker container. One has to copy a single file into the music folder in order to make subsonic scan the music folder successfully.

[Ju Zi]

Stop Subsonic service. Delete the entire content of the /subsonic/db library (preferably move it to a backup folder, in case). Restart Subsonic service or restart PC. Perform a new "Setup Media Folders"/"Scan Media Folders Now" scan. The process will take longer since is rebuilding the whole library but will end succesfully covering all the library files. At least it worked for me.

[Steve Insley]

This isn't a solution to the problem. In fact, I said that I did that in my original post, but the problem would recur again straight away. Did you read my post?!

To say again - this turned out NOT to be a Subsonic bug, but rather a problem caused by StableBit Drivepool.

[Anonymous]

[Anonymous]

[Anonymous]

[Anonymous]

[Anonymous]