2x PCs , 2 x MM5, one drive common, Artwork doesn't update.

[GiantRay]

I have two PCs networked locally. Each has MM5 installed. All my music is stored on a separate internal SSD on my first PC. Both PCs access this to play the music.

When I update track info (artist, album, genre etc) on MM5 on my first PC, I can watch it update automatically on MM5 on my second PC. Almost instantly. However, when I update the artwork, which is tagged to the MP3 file, my first PC's MM5 updates the artwork, but my second PC's never updates the artwork, even if I close down and restart both PCs. Yet if I add a new track, and add new info and artwork, the artwork appears on both PCs. Why?

[Lowlander]

Does the Artwork appear after manual rescanning?

[GiantRay]

If I do a manual re-scanning, the MM5 on the second computer does not show the new nor updated Artwork.

[Lowlander]

Disable Only for files with changed timestamp or size and try again.

What File Type(s) did you add Artwork to?

[GiantRay]

All my music files are saved as MP3s. My artwork is optioned to save to TAG first if not then to a folder. No artwork goes to the folder, all gets added as TAGs, the artwork folder is empty.

The only problem with "Disable Only for files with changed timestamp or size and try again." is I have over 70,000 files and it takes ages to scan all those files.

I would have thought adding artwork as a TAG would change the size of the file and a new timestamp created, hence it should spot the changed file.

[Lowlander]

You can try scanning on a sub-folder where you've edited the Artwork and it wasn't seen. Just to test if that does the trick.

[GiantRay]

Just tried that and it did not update artwork, yet artwork is okay on my other PC using the exact same file.

[GiantRay]

It has done it. After second attempt! But I cannot do that each time I want to edit a files artwork.

[Lowlander]

Are you saying 2 scans gets Artwork in?

Can you try with the latest MediaMonkey 2024?

[GiantRay]

It took two scans yes.

I do not have MM2024 whatever that is. I have had a Gold license for many years now and only recently started using MM5 because I do not like the way some things work different compared to MM4. I still am considering going back to MM4 as it was much better to use. I am not even going to migrate to whatever MM2024 is unless there is something that is better with it. I will have to check it out.

[Rob_S]

As a user, I would say MM2024 is beginning to be what MM5 only hoped to be..

Many bugs fixed, and a number of improvements over a very long Beta cycle where I used a large number of the recent builds at some time or other.

Latest almost ready to release build can be found here. You can install regular build as portable so it does not mess with your existing.

viewtopic.php?p=523357#p523357

Only thing to confirm if you bought Gold Lifetime, it will give you gold 2024. If you have regular gold, you will have to inquire about update cost, as it will be considered a new version.

[GiantRay]

Okay so I capitulated and downloaded MM2024 on my second computer, using the music files stored on the SSD on my first computer, the same files MM5 uses on that computer.

I updated the artwork on a track on my first computer. Again the artwork didn't update on the second PC on MM2024, but other info did. I then did the same as before, "Disable Only for files with changed timestamp or size and try again." Re-scanned and the artwork updated.

Tried again. This time having scanning set at continuously & disabled "Only for files with changed timestamp or size" And it automatically updated the artwork as I watched it.

This is good because it means I can have the same music file storage drive, but maintain separate databases on each computer, each personal to the user.

[CrashMonkey]

"Only for files with changed timestamp or size and try again."

I have noticed, that it does not always update all files even if timestamp was changed. Then rescanning the next day it would detect it.
Is there a certain limit in age for the timestamp, before it gets updated?

[Rob_S]

I think this issue has a lot to do with the caching of artwork, which nobody seems to understand or be able to explain how it works and what to do when it doesnt.

Deleting all the cached artwork is one possible solution when it fails. I dont know why but the appdata folder has one cache called artistimages, and another called thumbs at 200*200 size.