Although I hate having discrepancies in my db, this is one problem that I have given up ever having fixed but I hope you can find an answer for everyone else.

Nyn
I'm not sure how to load an image of the debug page but the final three lines of debug on one of the tracks show:Bex wrote:DasKraut,
I've updated the Debug-Helper Script so it displays AlbumArt Info.
It displays what MM has stored in its DB as well as what exists as an albumart object. This means that you can compare this two ways and see if there are any differences.
http://www.mediamonkey.com/forum/viewtopic.php?t=25935
Let me know what you find.
Code: Select all
ArtObj: Image 1: : (In Tag) Cover (front),
This means that MM's DataBase only knows about one image but it actually exists two images in the file itself. Did you really rescan this file?In DB: Image 1: (In Tag) Cover (front),
ArtObj: Image 1: : (In Tag) Cover (front),
ArtObj: Image 2: : (In Tag) Not Specified,
No, the DB-thing is SQL but the Object thing is VBScript. The only way to find these is to write a script which I'm sure MoDementia will do very soon. (It should be pretty easy.nynaevelan wrote:Hey Bex:
My problem tracks don't have the line below, is there a sql statement that I can run in SQL Viewer or maybe a custom node that would identify any tracks with the In DB statement not the ArtObj statement?
NynCode: Select all
ArtObj: Image 1: : (In Tag) Cover (front),
I deleted the file from the library, closed MM, restarted MM, MM picked up the file from the monitored directory.Bex wrote:The debug-helper script is just an info page which let you see hard to get data.
This means that MM's DataBase only knows about one image but it actually exists two images in the file itself. Did you really rescan this file?In DB: Image 1: (In Tag) Cover (front),
ArtObj: Image 1: : (In Tag) Cover (front),
ArtObj: Image 2: : (In Tag) Not Specified,
Oh, and I selected maintain library before closing and restarting MM.DasKraut wrote:I deleted the file from the library, closed MM, restarted MM, MM picked up the file from the monitored directory.Bex wrote:The debug-helper script is just an info page which let you see hard to get data.
This means that MM's DataBase only knows about one image but it actually exists two images in the file itself. Did you really rescan this file?In DB: Image 1: (In Tag) Cover (front),
ArtObj: Image 1: : (In Tag) Cover (front),
ArtObj: Image 2: : (In Tag) Not Specified,
Do all the files in the album look the same?DasKraut wrote:I deleted the file from the library, closed MM, restarted MM, MM picked up the file from the monitored directory.Bex wrote:The debug-helper script is just an info page which let you see hard to get data.
This means that MM's DataBase only knows about one image but it actually exists two images in the file itself. Did you really rescan this file?In DB: Image 1: (In Tag) Cover (front),
ArtObj: Image 1: : (In Tag) Cover (front),
ArtObj: Image 2: : (In Tag) Not Specified,
Some of the tracks in that album have both images and some have only the Cover (front) image. All of them display the "In DB" line the same way.Bex wrote:Do all the files in the album look the same?DasKraut wrote:I deleted the file from the library, closed MM, restarted MM, MM picked up the file from the monitored directory.Bex wrote:The debug-helper script is just an info page which let you see hard to get data.
This means that MM's DataBase only knows about one image but it actually exists two images in the file itself. Did you really rescan this file?
When I select the Album Art tab, I see all of the images. Deleting the unspecified ones and leaving the good one, ensuring that the "apply to all selected tracks" is checked, and then saying okay does clean up the files. But I have a fairly large library. I was hoping for a way to avoid going through every single track.Bex wrote:And all tracks have the same AlbumID?
If so select all tracks and go into the properties -> Album Art tab, check "Apply to all tracks" and hit OK. Does it work then?