More > JRiver Media Center 31 for Mac
Cover Art location - per Library
MrBiff:
Can you make the Cover Art location use an MC field rather than the current single global value. Currently it is defined in User Settings as:
File Location - Image File Location="\[App Data Path\]Cover Art/"
and this means one library's Cover Art pollutes another library's Cover Art. I have several test libraries, and I don't want their Cover Art polluting my Main library's art.
I'd like to be able to use an MC field in the setting File Location > Cover Art > Folder so that I can have the library define where Cover Art is located, as in:
File Location - Image File Location="\[LibraryCoverArtLocation\]/"
HaWi:
--- Quote from: MrBiff on July 16, 2023, 01:25:11 pm ---Can you make the Cover Art location use an MC field rather than the current single global value. Currently it is defined in User Settings as:
File Location - Image File Location="\[App Data Path\]Cover Art/"
and this means one library's Cover Art pollutes another library's Cover Art. I have several test libraries, and I don't want their Cover Art polluting my Main library's art.
I'd like to be able to use an MC field in the setting File Location > Cover Art > Folder so that I can have the library define where Cover Art is located, as in:
File Location - Image File Location="\[LibraryCoverArtLocation\]/"
--- End quote ---
If possible, I'd love that, too.
blgentry:
This is not a direct answer to your question. Rather it's my opinion on this subject in general.
Centralized cover art directories are a bad idea. It separates the metadata (cover art) from the actual file (the song file, MP3, FLAC, etc). They should be tied together.
For me this means placing cover art in the same directory as the song files. Better yet, embedding the cover art INSIDE those files when the file supports it. That way they are never separated. This is the most straight forward and easy to maintain approach. Anything else adds additional maintenance steps and more things to keep track of.
MC supports both of these things: Keeping cover art in the same directory as the music files and embedding the cover art inside the files.
Brian.
MrBiff:
--- Quote from: blgentry on July 17, 2023, 08:35:54 am ---Centralized cover art directories are a bad idea. It separates the metadata (cover art) from the actual file (the song file, MP3, FLAC, etc). They should be tied together.
For me this means placing cover art in the same directory as the song files. Better yet, embedding the cover art INSIDE those files when the file supports it. That way they are never separated. This is the most straight forward and easy to maintain approach. Anything else adds additional maintenance steps and more things to keep track of.
MC supports both of these things: Keeping cover art in the same directory as the music files and embedding the cover art inside the files.
--- End quote ---
This doesn't address the issue of Series and Actor images for video files. These must live at a higher level since they are connected to many files within many directories. The higher level avoids large duplication, and that's the only thing MC supports for certain image types.
The issue is that these files should be library-related, not global to all libraries.
lepa:
I agree on the library level point. On attach issue my 2 cents is that hires scanned artwork might be very very big to be attached to your files and not sure if MC supports anything else than cover image attach. Also for videos I keep ALL the artwork (thumbs/covers/other) on local SSD otherwise MC is hanging all the time when NAS (or any drive on it) is sleeping. So there are valid use cases for centralized parts in the collection
Navigation
[0] Message Index
[#] Next page
Go to full version