Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 949765" data-attributes="member: 18896">In all previous cases where I've helped somebody solve this, it turned out to be a corrupted file that stalled the importer as it crashed MediaInfo trying to read the info.&nbsp;The easiest way to find the offending files in those cases was to rename movingpictures.db3 (for backup purpose), rename your old import folder and create empty new one. For example D:\Movies becomes D:\Movies.old and create an empty D:\Movies folder. Then recreate the movingpictures.db3 by by launching MovPic config and redo all your settings. Backup your movingpictures.db3 again at this point to make it easy to go back to this &quot;clean slate&quot; if needed later on during testing.&nbsp;Now move first movie out of 79 over and wait for it to import, rinse and repeat until you stumble upon the file in question that hangs it.&nbsp;You can use the standalone MediaInfo GUI to get more crash information, and the MediaInfo developers are happy to give you FTP access to upload the file, so they can fix the issue (which would benefit all of us as users).&nbsp;As final test, restore the clean movpic database and let it import all files that imported correct and see if it will do a bulk import without any issues.&nbsp;PS: In one rare case it turned out that the users system (mainly internet connection) wasn't good enough to keep up with an asynchrone 5 thread import process. That is the default value, but you can change this in advanced settings. In that specific case a setting of 3 threads made everything import flawless. Setting it to 1 thread makes importing go slower, but is also a perfect way to find out what the offending file is via movingpictures.log, as it can be read in synchrone order.</blockquote>

[QUOTE="RoChess, post: 949765, member: 18896"] In all previous cases where I've helped somebody solve this, it turned out to be a corrupted file that stalled the importer as it crashed MediaInfo trying to read the info. The easiest way to find the offending files in those cases was to rename movingpictures.db3 (for backup purpose), rename your old import folder and create empty new one. For example D:\Movies becomes D:\Movies.old and create an empty D:\Movies folder. Then recreate the movingpictures.db3 by by launching MovPic config and redo all your settings. Backup your movingpictures.db3 again at this point to make it easy to go back to this "clean slate" if needed later on during testing. Now move first movie out of 79 over and wait for it to import, rinse and repeat until you stumble upon the file in question that hangs it. You can use the standalone MediaInfo GUI to get more crash information, and the MediaInfo developers are happy to give you FTP access to upload the file, so they can fix the issue (which would benefit all of us as users). As final test, restore the clean movpic database and let it import all files that imported correct and see if it will do a bulk import without any issues. PS: In one rare case it turned out that the users system (mainly internet connection) wasn't good enough to keep up with an asynchrone 5 thread import process. That is the default value, but you can change this in advanced settings. In that specific case a setting of 3 threads made everything import flawless. Setting it to 1 thread makes importing go slower, but is also a perfect way to find out what the offending file is via movingpictures.log, as it can be read in synchrone order. [/QUOTE]

Verification