Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 807861" data-attributes="member: 18896">Yes, for some reason the ImdbBuilder log line is not present for you.
07-Nov-2011 20:42:04 Debug [ DBImportPath]: New File: Batman III Batman Forever (1995) [tt0112462].avi 
07-Nov-2011 20:42:09 Debug [VideoFormatExtension]: Identifier: Path='F:\Media\Movies\Batman III Batman Forever (1995)\Batman III Batman Forever (1995) [tt0112462].avi', Format='File', Hash='b2d937333b2dd8a3' 
07-Nov-2011 20:42:12 Debug [ DataProviderManager]: SEARCH: Title='Batman III Batman Forever', Provider='IMDb+', Version=3.3.7, Number of Results=18 
Above are the relevant log lines from your test, and it is missing the very important:07-Nov-2011 20:42:xx Debug [ ImdbBuilder]: Lookup Imdbid=tt0112462: Title='Batman Forever', Year=1995 This is however done by the MovingPictures plugin.You only provided a small part of the log file, or sometimes the other stuff ends up in movingpictures.old.log, either way I can not find the exact version of MovingPictures that you are running. So please verify it is at least: &quot;Info [&nbsp; MovingPicturesCore]: Moving Pictures (1.2.3:1329)&quot;What I could do however is modify the IMDb+ scraper-script and see if any tt\d{7} number is still present inside the filename and use that as IMDb tt-ID if the ImdbBuilder failed. But I'm more curious (and I'm sure so is the MovingPictures developer) in the 'why' on the failure, because it is supposed to just work.Is that (F) drive a share, or anything else out of the ordinary? There are some issues with network shares are drive letters, if you adjust MovPic to use \\UNC share-name, that should eliminate a lot of weird side effects.</blockquote>

[QUOTE="RoChess, post: 807861, member: 18896"] Yes, for some reason the ImdbBuilder log line is not present for you. [INDENT] 07-Nov-2011 20:42:04 Debug [ DBImportPath]: New File: Batman III Batman Forever (1995) [tt0112462].avi 07-Nov-2011 20:42:09 Debug [VideoFormatExtension]: Identifier: Path='F:\Media\Movies\Batman III Batman Forever (1995)\Batman III Batman Forever (1995) [tt0112462].avi', Format='File', Hash='b2d937333b2dd8a3' 07-Nov-2011 20:42:12 Debug [ DataProviderManager]: SEARCH: Title='Batman III Batman Forever', Provider='IMDb+', Version=3.3.7, Number of Results=18 [/INDENT] Above are the relevant log lines from your test, and it is missing the very important: [INDENT]07-Nov-2011 20:42:xx Debug [ ImdbBuilder]: Lookup Imdbid=tt0112462: Title='Batman Forever', Year=1995 [/INDENT] This is however done by the MovingPictures plugin. You only provided a small part of the log file, or sometimes the other stuff ends up in movingpictures.old.log, either way I can not find the exact version of MovingPictures that you are running. So please verify it is at least: "Info [ MovingPicturesCore]: Moving Pictures (1.2.3:1329)" What I could do however is modify the IMDb+ scraper-script and see if any tt\d{7} number is still present inside the filename and use that as IMDb tt-ID if the ImdbBuilder failed. But I'm more curious (and I'm sure so is the MovingPictures developer) in the 'why' on the failure, because it is supposed to just work. Is that (F) drive a share, or anything else out of the ordinary? There are some issues with network shares are drive letters, if you adjust MovPic to use \\UNC share-name, that should eliminate a lot of weird side effects. [/QUOTE]

Verification