I was doing some music library testing on 12.2 and 13A4 (Win 7). In my test I was adding a folder within an existing music source folder tree. The folder contains mp3 files in which only APEv2 tags were written (no ID3 V1 or v2 tags). On a music library update, the new folders were found by MusicInfoScanner, but none of the files added to the library. Log shows
DEBUG: MUSIC_INFO::CMusicInfoScanner::ScanTags - No tag found for: F:\testmusic\やなぎなぎ\ユキトキ\01. ユキトキ.mp3
So I removed the folder and did an update to clear the path data in the musicdb. This time I inserted the
directive in advancedsettings and repeated the test. This time all mp3 files were found and the APEv2 tags read except for
DEBUG: unrecognized APE tag: COVER ART (FRONT)
which I don't consider a problem as there probably isn't a spec for this.
So what seems to be the case is that for mp3 files with APEv2 tags and no ID3 tags, it doesn't appear that they will scan without having the prioitiseapetags set. I would have expected that the APEv2 tags would have been read regardless in this case.
scott s.
.
DEBUG: MUSIC_INFO::CMusicInfoScanner::ScanTags - No tag found for: F:\testmusic\やなぎなぎ\ユキトキ\01. ユキトキ.mp3
So I removed the folder and did an update to clear the path data in the musicdb. This time I inserted the
Code:
<musiclibrary>
<prioritiseapetags>true</prioritiseapetags>
</musiclibrary>DEBUG: unrecognized APE tag: COVER ART (FRONT)
which I don't consider a problem as there probably isn't a spec for this.
So what seems to be the case is that for mp3 files with APEv2 tags and no ID3 tags, it doesn't appear that they will scan without having the prioitiseapetags set. I would have expected that the APEv2 tags would have been read regardless in this case.
scott s.
.