Asset Initial Track Count Higher than Final Track Count

[Chip]

Hi all,
I have installed Asset v3 and run the scan of my music database three times with the same results.
My music database is stored in flac format on a ReadyNAS NV+. The files have either been ripped using dBpoweramp Reference or downloaded.
When Asset first starts it does a track count and finds 20524 tracks. This is the same number of music tracks that TreeSize Professional identifies for the same folder structure on the ReadyNAS.
Asset then starts adding the tracks showing 'track number' of 20524 tracks.
When the scan has finished Asset shows 20521 tracks and 1704 albums.

The initial count is 20524 and final count is 20521.
What happened to the other 3 tracks?

How can I tell which tracks are missing?

Why would some tracks not be included?

Any ideas?

Thanks,
Chip

[Spoon]

Re: Asset Initial Track Count Higher than Final Track Count

They might be corrupted and cannot be read. You might be able to switch on the debug mode and it might show which files they are.

[Chip]

Re: Asset Initial Track Count Higher than Final Track Count

Hello,
I switched on debugging and ran the rescan to pick up differences and the log shows three files with the following error:
Error cannot read track meta, file must be in use.

The file should not be in use since Asset is the only process I have running against the NAS during this time.

If I select the file and right click I cannot see the option for Properties. This seems to be a dead giveaway that something is wrong with these three tracks.

I noticed these three files all have very long file names.
Is there a maximum number of positions in a file name?
Including the path?

I would like to know before I re-rip the tracks.

Thanks for your help,
Chip

[Spoon]

Re: Asset Initial Track Count Higher than Final Track Count

Windows and Asset does not, but the readynas possibly does.

[Chip]

Re: Asset Initial Track Count Higher than Final Track Count

Hi all,
I changed the track file names of the three missing tracks and now they appear in Asset.
I do not remember if I was able to play them using Kinsky Desktop and Twonky but adding the longer names seemed to be the problem with Asset. I was probably not able to play them since I could see the tracks in Windows Explorer but could not see the metadata.
Anyway when I originally ripped the tracks using dBpoweramp I was over zealous with the naming. I have since gained some sense and the tracks names are now more manageable.
Now I will continue my testing. So far so good.
Thanks for your help,
Chip