home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Moving Pictures Crash
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="RoChess" data-source="post: 1190110" data-attributes="member: 18896"><p>[USER=76888]@kiwijunglist[/USER] did you add any new movies as well? I've had those crashes myself when it would freak out over a new movie, either on the filename, or the MediaInfo import would fail. The problem is that the crash sometimes prevents the log files from getting updated so they make it impossible to find out what movie is causing the crash.</p><p></p><p>The only solution I found was to remove all movies, and add them at n/2 times, so at 400 movies you would add 200 first, if it doesn't crash on first half, you add 100 of the next half, then 50, 25, etc. If it does crash you eliminate it more by re-importing just half of that batch, until eventually you find the culprit that is causing the crash.</p><p></p><p>In some cases updating the MediaInfo.DLL binary in the MediaPortal root folder also solves the trick (keep in mind that this is the 32-bit version), and you can find direct download to that @ <a href="https://mediaarea.net/download/binary/libmediainfo0/0.7.87/MediaInfo_DLL_0.7.87_Windows_i386_WithoutInstaller.7z" target="_blank">https://mediaarea.net/download/binary/libmediainfo0/0.7.87/MediaInfo_DLL_0.7.87_Windows_i386_WithoutInstaller.7z</a></p><p></p><p>Hope you can find it easy.</p><p></p><p>PS: If your system stores the last added/modified dates correct, then you might be able to speed things up by looking for the files you added since the last time you knew everything was working. Another solution is to rely on a MovPic backup when everything was still working, and look at the log files of all the new files it "detects" during import, and temporary move them outside of the import folder and add them one at a time until they finish importing. That way at one at a time you'll immediately locate the bad one. In most cases it is easy to fix them as it is usually a corrupted header that can be fixed with their respective encoder toolkit.</p></blockquote><p></p>
[QUOTE="RoChess, post: 1190110, member: 18896"] [USER=76888]@kiwijunglist[/USER] did you add any new movies as well? I've had those crashes myself when it would freak out over a new movie, either on the filename, or the MediaInfo import would fail. The problem is that the crash sometimes prevents the log files from getting updated so they make it impossible to find out what movie is causing the crash. The only solution I found was to remove all movies, and add them at n/2 times, so at 400 movies you would add 200 first, if it doesn't crash on first half, you add 100 of the next half, then 50, 25, etc. If it does crash you eliminate it more by re-importing just half of that batch, until eventually you find the culprit that is causing the crash. In some cases updating the MediaInfo.DLL binary in the MediaPortal root folder also solves the trick (keep in mind that this is the 32-bit version), and you can find direct download to that @ [URL]https://mediaarea.net/download/binary/libmediainfo0/0.7.87/MediaInfo_DLL_0.7.87_Windows_i386_WithoutInstaller.7z[/URL] Hope you can find it easy. PS: If your system stores the last added/modified dates correct, then you might be able to speed things up by looking for the files you added since the last time you knew everything was working. Another solution is to rely on a MovPic backup when everything was still working, and look at the log files of all the new files it "detects" during import, and temporary move them outside of the import folder and add them one at a time until they finish importing. That way at one at a time you'll immediately locate the bad one. In most cases it is easy to fix them as it is usually a corrupted header that can be fixed with their respective encoder toolkit. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Moving Pictures Crash
Contact us
RSS
Top
Bottom