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: 1261146" data-attributes="member: 18896"><p>Yeah I saw from your logs that you have mainly BR rips, so that complicates things for my script (no idea if ffmpeg can verify integrity on those).</p><p></p><p>Moving-Pictures is pretty stand-alone during the import, but the one thing it relies on for MediaPortal during import is the MediaInfo scanning to get resolution/etc.</p><p></p><p>MediaPortal by default also likes to generate thumbnails (disable that myself always to avoid issues).</p><p></p><p>Seeing as it works under MediaPortal 1.16, but then fails when you do the same step under 1.17+ there is clearly something different about the way MediaPortal handles the MediaInfoWrapper requests that Moving-Pictures makes during the import process.</p><p></p><p>The main factor on that is the mediainfo.dll file within the MediaPortal folder, and if you install 1.17+ that is obviously a different version than the one v1.16 installs.</p><p></p><p>I've worked with the MediaInfo developers when I had serious issues on a WiFi share with some AVI files, and they constantly fix things, but they also adjust the way things work that might break software that relies on that. Manually replacing the DLL in the MePo root folder would then solve my issues.</p><p></p><p><a href="https://mediaarea.net/en/MediaInfo/Download/Windows" target="_blank">MediaInfo - Download MediaInfo for Microsoft Windows</a></p><p></p><p>Latest version is v19.07 now, and you'll need to use the 32-bit DLL download for MediaPortal, but it would be wise to first check what version is bundled with MePo 1.16 and what is included with 1.17+.</p><p></p><p>Downloaded v1.16 ZIP real quick, and it comes with: Mediainfo.dll v0.7.69.0</p><p>MediaPortal v1.17 comes with MediaInfo.dll v0.7.95.0</p><p></p><p>So, you can try downgrading MediaPortal v1.17 to Mediainfo.dll v0.7.69, and if collection imports fine then clearly issue is centered around MediaInfo.</p><p></p><p>You can also try MediaInfo v19.07 to see if that solves it again (might be a bug they fixed).</p><p></p><p>Otherwise it is a new bug that MediaInfo developers need to solve, but perhaps that is what MediaPortal v1.23 is about, which requires a fix to Moving-Pictures.</p><p></p><p>Fun stuff <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" /></p></blockquote><p></p>
[QUOTE="RoChess, post: 1261146, member: 18896"] Yeah I saw from your logs that you have mainly BR rips, so that complicates things for my script (no idea if ffmpeg can verify integrity on those). Moving-Pictures is pretty stand-alone during the import, but the one thing it relies on for MediaPortal during import is the MediaInfo scanning to get resolution/etc. MediaPortal by default also likes to generate thumbnails (disable that myself always to avoid issues). Seeing as it works under MediaPortal 1.16, but then fails when you do the same step under 1.17+ there is clearly something different about the way MediaPortal handles the MediaInfoWrapper requests that Moving-Pictures makes during the import process. The main factor on that is the mediainfo.dll file within the MediaPortal folder, and if you install 1.17+ that is obviously a different version than the one v1.16 installs. I've worked with the MediaInfo developers when I had serious issues on a WiFi share with some AVI files, and they constantly fix things, but they also adjust the way things work that might break software that relies on that. Manually replacing the DLL in the MePo root folder would then solve my issues. [URL="https://mediaarea.net/en/MediaInfo/Download/Windows"]MediaInfo - Download MediaInfo for Microsoft Windows[/URL] Latest version is v19.07 now, and you'll need to use the 32-bit DLL download for MediaPortal, but it would be wise to first check what version is bundled with MePo 1.16 and what is included with 1.17+. Downloaded v1.16 ZIP real quick, and it comes with: Mediainfo.dll v0.7.69.0 MediaPortal v1.17 comes with MediaInfo.dll v0.7.95.0 So, you can try downgrading MediaPortal v1.17 to Mediainfo.dll v0.7.69, and if collection imports fine then clearly issue is centered around MediaInfo. You can also try MediaInfo v19.07 to see if that solves it again (might be a bug they fixed). Otherwise it is a new bug that MediaInfo developers need to solve, but perhaps that is what MediaPortal v1.23 is about, which requires a fix to Moving-Pictures. Fun stuff :confused: [/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