Reply to thread

Message: <blockquote data-quote="RoChess" data-source="post: 1244706" data-attributes="member: 18896">Glad it works again for you as well. It is a constant battle to keep up with IMDb.com changes, but until AI works, it is a never ending cat-and-mouse game.<ol> <li data-xf-list-type="ol">MediaPortal -- in debug mode (under General somewhere)</li> <li data-xf-list-type="ol">Moving-Pictures -- in scraper-debug mode (shows little green bug icon inside scraper-script section)</li> <li data-xf-list-type="ol">IMDb+ -- turn on hidden XML option to include HTML sources</li> </ol>I think you did 1+3, but forgot/overlooked #2, no biggie, just remember it for the future, and be sure to change it back once done as creating those extreme log files has a serious impact on performance.That depends on their settings, so you should allow one movie to import using them and verify why they are acting up. Localized detection is a pain in the ass for this, which is the main reason why I need to completely rewrite IMDb+, but trouble with finding the time to do so.Default time is 24 hours to not overload the GitHub server, but simply adjust the IMDb+ XML settings file to force a check upon launch.Yes, even at 3 seconds per movie, that is a full hour, but you want to be sure that all the debug stuff is disabled so it doesn't take 12 seconds per movie and you are stuck waiting for 4 hours <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />Of course I usually launch it, go to bed, and enjoy results when I wake up.That I'm not sure about, but the key about solving any problem is the ability to consistently reproduce an issue, because then whatever developer needs to fix it (be it MediaPortal, Moving-Pictures, or IMDb+) can step through their code until they hit the offending code-section and examine/fix the issue.The problem with these random or hard to define issues is that this becomes a painstaking process, but keep in mind if it is difficult for you to reproduce, it is practically impossible for a developer to fix it. Good logs are a lifesaver though, and you might be lucky enough that somebody encountered the same thing.One suggestion I have is that you might have an anti-virus solution interfering, which I had myself, and was forced to exclude the MediaPortal process, MediaPortal program folder, and my import folders from the default Windows Defender AV solution that ships with Windows.Weird thing on that was that I was hitting 100% CPU usage, but the AV solution wasn't showing in task manager. Third party tools such as ProcMonitor from SysInternals revealed what was really going on. Microsoft system resource tool probably would have worked as well, but you get the idea.</blockquote>

Verification