Hi Jez,
Been meaning to ask about this for a while....
I quite often move album folders around or sometimes rename folders - for instance when I get an new album I often place its folder in a "new rip" directory until I decide what genre I'm going to file it as. When I rescan my library after doing any file management like this I end up with two references to the album in Muso which I then need trim by removing tracks in the database.
The highlighting of songs that are "file not accessible" definitely helps in this - but it would be made a lot easier if there was a filter or other function which found all such files.
Is this possible?
Thanks
BTW - I'm enjoying the the 2.5 beta very much will post some comments on it soon.
Finding all files that re no longer valid
Re: Finding all files that re no longer valid
If you move the album's containing folder but don't change that folder's name, then scan the new folder location, Muso will recognise that the album has moved location and will simply point it at the new location, so this will retain any album data that is specific to Muso.
If however you do change the album folder's name, then import the new folder, Muso won't automatically know it's the same album as before, so then you'll get dead tracks as you've mentioned. A filter on the db view would take a LONG time to run, as evaluating network locations for file existence is a slow process, so it's probably quicker to handle dead album removal manually.
If however you do change the album folder's name, then import the new folder, Muso won't automatically know it's the same album as before, so then you'll get dead tracks as you've mentioned. A filter on the db view would take a LONG time to run, as evaluating network locations for file existence is a slow process, so it's probably quicker to handle dead album removal manually.
Re: Finding all files that re no longer valid
If you move the album's containing folder but don't change that folder's name, then scan the new folder location, Muso will recognise that the album has moved location and will simply point it at the new location, so this will retain any album data that is specific to Muso.
That doesn't appear to be the case. I move albums without changing the directory name only the location and end up with duplicates in Muso.
I did wonder if these changes should be picked-up - I'll do some tests to make sure I'm seeing this correctly.
A filter on the db view would take a LONG time to run, as evaluating network locations for file existence is a slow process, so it's probably quicker to handle dead album removal manually.
I feared this might be a slow process, especially with big libraries.
Re: Finding all files that re no longer valid
I've run a quick test moving one folder without changing any names or anything else. Re-scanned in LMS and then did a 'full import from LMS' in Muso.
The album concerned is showing as twice:
I'm pretty sure if I make any data/tag changes within Muso and then move the albums folder, the new Muso entry takes the old data with it ?!? A bit odd.
The album concerned is showing as twice:
I'm pretty sure if I make any data/tag changes within Muso and then move the albums folder, the new Muso entry takes the old data with it ?!? A bit odd.
Re: Finding all files that re no longer valid
The log shows the album being 'added':
Re: Finding all files that re no longer valid
Ah now you mention it I've unwittingly included a change to the album keys in 2.5 Beta that means this folder migration no longer works. I'll try to address this tonight.
Re: Finding all files that re no longer valid
Great - thanks.
Re: Finding all files that re no longer valid
Should be there now. So just running the app should pick it up (I've found that it normally picks up the fact that an upgrade is required after a couple of startups).
Re: Finding all files that re no longer valid
Yeah - all seems good now. That's a big help, thanks.