This is not really an issue, but since Roon added the functionality that an album could have multiple album covers embedded in the metadata (which you could view in the playback window I guess - because I don’t have many albums that actually have multiple album covers, and I can’t think of one right now) I have been looking for a way to add extra album covers with my Yate tag editor so that they actually show up in Roon.
Again, this is not a big deal, but it would be nice to be able to do this for albums that got a new cover when they were remastered, like the Holger Czukay & David Sylvian albums Plight & Premonition and Flux + Mutability (where I tried and failed).
My experience has been that extra art needs to be in separate files within the music folder. I think YATE has a way of doing that. Maybe Save Artwork to Folder.
A map of an album can only have one cover art, naming cover.jpg or folder.jpg unless you are tagging different covers into several music files (flac or other music files)
Be careful of what you wish for. While storage is cheap, having one set of art per album is usually more efficient. But it can be done already; just don’t know how Roon treats embedded art.
I know, and I try to keep the embedded art as small as possible (though large enough for decent resolution, typically around 250-300kb).
A few years ago I read an article about this in an online American hifi-magazine (but can’t remember which one) where the author actually listened to the optimum size of embedded artwork. I thought it was way too farfetched, but he said that embedded artwork should not be bigger than 800x800px. That’s right, pixels, not kilobytes. Hence the farfetchiness. But still, somehow, I have always tried to keep my metadata as clean as possible.
Adding a small’ish’ extra img-file to the album folder doesn’t realy make it too bulky, and I only need this for a small number of albums.
Original booklet img-files (if that ever becomes an option in Roon) should be stored in the local Roon library, instead of being embedded in the audio file. That will inevitably make your library bigger, but that would be an acceptable trade-off afaIc…