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
Large import not working
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: 1261094" data-attributes="member: 18896"><p>[USER=108314]@fredco[/USER], I've never had to do a fresh import, as I've always just migrated everything over (still on 1.22 though as I'm holding off until that one bug is fixed).</p><p></p><p>Do your logs indicate at all where it is failing?</p><p></p><p>In my experience it tends to often be your thread count is too high (so lower it in advanced settings), or MediaInfo freaks out (be sure to manually update DLL).</p><p></p><p>What I also noticed is that often users will have corrupted media file headers and not realize it. To that extend when I had to rely on a partly successful parity recovery I ended up writing a batch script that relies on ffmpeg to play each file at maximum speed (most modern computers can handle 600fps+, especially if you activate hardware acceleration) to ensure that each media file is not corrupt. The script is available on forum somewhere, but I can locate it if you cannot find it.</p><p></p><p>Logs should reveal this to you, but if you have thread count higher than 1, then logs in asynchronous state can be difficult to read.</p><p></p><p>Of course importing at 1 thread will take a lot longer, but when I do an IMDb+ refresh (to get updated vote/cert/info) I always run it when I sleep, so I wake up to a fresh collection.</p></blockquote><p></p>
[QUOTE="RoChess, post: 1261094, member: 18896"] [USER=108314]@fredco[/USER], I've never had to do a fresh import, as I've always just migrated everything over (still on 1.22 though as I'm holding off until that one bug is fixed). Do your logs indicate at all where it is failing? In my experience it tends to often be your thread count is too high (so lower it in advanced settings), or MediaInfo freaks out (be sure to manually update DLL). What I also noticed is that often users will have corrupted media file headers and not realize it. To that extend when I had to rely on a partly successful parity recovery I ended up writing a batch script that relies on ffmpeg to play each file at maximum speed (most modern computers can handle 600fps+, especially if you activate hardware acceleration) to ensure that each media file is not corrupt. The script is available on forum somewhere, but I can locate it if you cannot find it. Logs should reveal this to you, but if you have thread count higher than 1, then logs in asynchronous state can be difficult to read. Of course importing at 1 thread will take a lot longer, but when I do an IMDb+ refresh (to get updated vote/cert/info) I always run it when I sleep, so I wake up to a fresh collection. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Large import not working
Contact us
RSS
Top
Bottom