INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: lise on April 24, 2013, 09:23:38 pm
-
I save my films as ISO files in a folder, one ISO per folder.
Example:
Sanjuro
Sanjuro.iso
Sanjuro.jpg
I manually add the jpg file myself.
MC keeps replacing my jpg, presumably from the default movie lookup.
I can't figure out why it would do that, though, when there is already a jpg in the folder with the correct name.
-
Anyone? It is getting really irritating that MC is overwriting all of my jpgs. I take the time to add the cover of the film that is the actual edition of my dvd or blu-ray, and then for some reason MC finds the cover art it prefers and actually overwrites mine. I wouldn't care so much if it added it, but to overwrite is unacceptable.
Please, how can I change this? So much of my work is being undone.
-
Do you add it via Media Center (Tools > Cover Art > Add From File…) or replace the file in Explorer?
-
I use Vice Versa and it syncs an external drive with my internal drive. The iso and jpg get synced.
I think I may have found the issue: under Import options I just unchecked "get cover art". That would be a pain if I was importing both music and films (I would want it for music but not for films) but since this machine is the movie machine I was able to uncheck that.
Hopefully this fixes the issue. I still find it strange that MC would actually overwrite an exising jpg rather than add it by adding a 1 to the name or something. Very odd.
-
Are you sure it's MC? I've never seen this reported.
-
Jim, yeah, MC is the only thing running on that computer.
I have my auto-import settings to automatically get tv and movie info as well as cover art.
When I copy a movie ISO file onto that computer, MC imports it, gets the info and an image. No problem.
But if there is already an image in the folder named the same as the ISO, an image I put there, MC replaces it. Not sure it should do that.
I've disabled "get cover art" in my auto-import settings and that seems to have fixed the problem.
-
Auto-import will download metadata and images for movies if it doesn't already have that information.
It won't overwrite either.
But the wrinkle is that MC doesn't know the ISO file has cover art since the 'Image File' field is blank.
How are you importing? I mean, how does MC even decide the ISO is a movie in the first place?
-
Auto import rules, in order:
For each of my drives, apply to folders and child folders, import Video and Data (iso) (One drive was also set to import images, if that matters. I just removed that just in case it was causing the issue).
Field: Media Type: If(IsEqual([File Type],iso,8),Video,[Media Type])
Field: Media SubType: Movie
ignore special files (folder.jpg)
-
Let me think about this one for a few days.
I wonder if it'd work around the issue if you created one more import rule:
Image File: [Name].jpg
This way, the program would have a link to the existing image and not download a new image.
-
Ok, I'll try that.
One thing though, is the [Name] the name of the ISO or the title it gets within MC?
I know, stupid question, but I name the ISO "Leopard.ISO" whereas in the database I change the title to The Leopard.
oh, and of course I would have to set my imports to include images rather than just video and data, right?
-
I must be out of it. I can't seem to add a rule saying: Image File. Doesn't seem to be a field for that.
-
Let me think about this one for a few days.
I wonder if it'd work around the issue if you created one more import rule:
Image File: [Name].jpg
This way, the program would have a link to the existing image and not download a new image.
Matt is probably busy with the new v19. Any gurus out there know what he meant by "image file" and how I could add what he suggested to my list of import rules? When I create an import rule I can't find a field that just says "image" in the fly-out (or any image related field for that matter).
-
It isn't there, so you can't select it. Just an oversight I'm sure.
-
Sorry, I gave bad advice. You can't sent the 'Image File' field because it's special.
So I'm still trying to figure out how to handle this. It'd be a lot better if we could know what an ISO is at import time instead of forcing rules to categorize it as a movie, etc.
We might be able to look for sidecar image files for ISO files, even if we think they're data. This way, MC would correctly link to the artwork instead of thinking it should download new artwork.
-
How about building a cheap file-guesser which uses simple heuristics like the *nix File(1) utility. For ISO of type DVD, you could search the header material for obvious DVDisms:
hexdump -C Vision_Quest.iso | grep VIDEO_TS
00080820 01 00 56 49 44 45 4f 5f 54 53 00 00 00 00 00 00 |..VIDEO_TS......|
00081020 00 01 56 49 44 45 4f 5f 54 53 00 00 00 00 00 00 |..VIDEO_TS......|
000818a0 08 56 49 44 45 4f 5f 54 53 00 00 00 00 00 00 00 |.VIDEO_TS.......|
00082870 0e 56 49 44 45 4f 5f 54 53 2e 42 55 50 3b 31 00 |.VIDEO_TS.BUP;1.|
000828a0 00 00 01 00 00 01 0e 56 49 44 45 4f 5f 54 53 2e |.......VIDEO_TS.|
00086880 00 00 08 56 49 44 45 4f 5f 54 53 2e 49 46 4f 00 |...VIDEO_TS.IFO.|
-
MrC, gee, I hope that wasn't meant for me ?
-
Nope, for Matt. He was hoping to be able to (cheaply) determine what type of content is in an ISO file, so that he could automatically tag it as Media Type=Video. Then, the [Image File] field would be valid and could be stored.
Another option might be to just open up Image File to assignment via auto-import. This would also allow users to use names such as coverart.jpg (currently, they have to use Cover Art > Get From File).
-
How about building a cheap file-guesser which uses simple heuristics like the *nix File(1) utility. For ISO of type DVD, you could search the header material for obvious DVDisms:
hexdump -C Vision_Quest.iso | grep VIDEO_TS
00080820 01 00 56 49 44 45 4f 5f 54 53 00 00 00 00 00 00 |..VIDEO_TS......|
00081020 00 01 56 49 44 45 4f 5f 54 53 00 00 00 00 00 00 |..VIDEO_TS......|
000818a0 08 56 49 44 45 4f 5f 54 53 00 00 00 00 00 00 00 |.VIDEO_TS.......|
00082870 0e 56 49 44 45 4f 5f 54 53 2e 42 55 50 3b 31 00 |.VIDEO_TS.BUP;1.|
000828a0 00 00 01 00 00 01 0e 56 49 44 45 4f 5f 54 53 2e |.......VIDEO_TS.|
00086880 00 00 08 56 49 44 45 4f 5f 54 53 2e 49 46 4f 00 |...VIDEO_TS.IFO.|
It's a good idea.
We actually have ISO parsing and building code for burning, so we might be able to do one better.
We even talked about allowing native playback from ISO files until we realized the DRM baked into Blu-ray ISO files made it a dead end.
-
http://yabb.jriver.com/interact/index.php?topic=82033.0