Here's my new logs. I tried viewing some MP3 file info this time. How exactly does the logic work that looks for the album art associated with an MP3? I have ID3 v1 tags only, does that matter?
OK, just tried something... if I remove all ID3 tag info from a file, then re-scan the library, when I select the MP3 in ML2, it shows the album art as expected. It looks like it's having trouble associating the ID3 tag info with the file?
That's really strange. I can see verbose messages in there, but there's pretty much nothing from ML2. I can see the start and end of the scan, but no messages.
For each MP3 file that that tags are read on, it then goes and checks for album art folder.jpg, default.jpg and cover.jpg (new one not released yet). It also checks for albumname.jpg and trackname.jpg just incase you've got music in one big directory.
Tag 1 shouldn't make any difference,the only thing I can think of is that it's getting an error in reading the tag, so doesn't get up to the point where it checks for art.
I'm expecting a log of similar size as the attached from you. It should show me reading all of the mp3 files during a scan...
I deleted my collection, deleted the .db3 file and made a new collection from scratch. It now works OK. When I originally started using ML2, I didn't have album covers in my folders, so it seems to have something to do with the initial scanning of the folder to whether the album cover shows up or not.
I am having a problem though. I think that MusicLibrary2 does not support m3u files with entries like: "\\htpc\media1\MUSIC\Christian\Michael Card\Joy in the Journey\Michael Card - Jubilee.mp3"
Is that correct? It seems that it will work ok if I replace "\\htpc\media1" with "D:" (local directory name). I would like to use the mount-form, however, so that other machines can use the playlist as well.
I have a large music collection (>10,000 tracks) and the way that ML2 organises the display suits my needs well.
However there appears to be a problem with displaying the contents correctly. (using 98.8) I have just done a fresh zap and reload and have taken a peek at the database with SQLite. It seems OK. I have done this twice now and:
1. The first time several artists did not have all their albums displayed, and also not all the tracks within the album.
2. After the second zap and reload, those artists now display OK, but the Genre list only displays genres beginning with "A".
My Tags are all properly formed (they made the database after all!)
This behaviour is constant in that if I stop and restart GBPVR, I get the same.
Is there any inherent limitation in ML2 which would cause these symptoms?
I don't know of any reasons or have had any reports from anyone else of this happening.... But also I've never had anyone mention a collection that large!!
Ok, so you're telling me the DB contains all the information if should, and it's just the display that's a bit suspect??
Basically ML2 would be trying to store all of those tracks in memory to display (the disadvantage of being DB based) I wonder if it's maxxing out the memory?? Have you had a look in the logs, can you see any errors from ML2??
That's correct. And I couldn't find anything to indicate aproblem in the gbpvr and native logs. Should I look anywhere else.
I wondered about memory, but the odd thing is the consistency. Both straight away and even after several days without a restart, I still only get all the genres beginning with "A" shown. And my system isn't short of memory, but I suppose the gbpvr task might have limits (?).
MusicLibrary2
