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
Development
Improvement Suggestions
New system for importing music/video/weather... data
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="auralsix" data-source="post: 66418" data-attributes="member: 21232"><p>Several of us are transitioning from Meedio to MediaPortal, with a bit of difficulty. I'd say the biggest issue is definitely the video importing capabilities. When it's not crashing on certain titles, it's mismatching results, and is generally a pain to work with.</p><p></p><p>Meedio movie imports worked off of standalone text property (.my) files which would be placed in a corresponding movie's directory. These .my files contained information regarding which files were associated with that movie entry, standard IMDB values, along with any extended info you wished to store. The importer would scan through movie directories, looking for these files, and adding their entries to the Meedio database as necessary. A full import of 400 or so movies, from scratch, would take a matter of minutes, and required no user interaction.</p><p></p><p>I know that a lot of work has been put into IMDB importing, and it's certainly appreciated. However, many of us are looking for a more portable solution for our content, so that we can add or drop media into our collections quickly. Additionally, any person who's taken pride in their HTPC project, probably wants to retain control over the details displayed on that info screen, and leaving final control up to IMDB is sort of a crapshoot.</p><p></p><p>A new video import methodology, one based off a portable text format, such as XML, might be more viable for MediaPortal in the long-term. Perhaps the IMDB import code could even be used for initial creation of these XML files, for users who don't necessarily micromanage their collections, or are just initially lacking that detailed metadata. No use letting that code go to waste.</p><p></p><p>Thoughts?</p><p></p><p>In the meantime, I guess I'll be looking into writing a .my file importer =]</p></blockquote><p></p>
[QUOTE="auralsix, post: 66418, member: 21232"] Several of us are transitioning from Meedio to MediaPortal, with a bit of difficulty. I'd say the biggest issue is definitely the video importing capabilities. When it's not crashing on certain titles, it's mismatching results, and is generally a pain to work with. Meedio movie imports worked off of standalone text property (.my) files which would be placed in a corresponding movie's directory. These .my files contained information regarding which files were associated with that movie entry, standard IMDB values, along with any extended info you wished to store. The importer would scan through movie directories, looking for these files, and adding their entries to the Meedio database as necessary. A full import of 400 or so movies, from scratch, would take a matter of minutes, and required no user interaction. I know that a lot of work has been put into IMDB importing, and it's certainly appreciated. However, many of us are looking for a more portable solution for our content, so that we can add or drop media into our collections quickly. Additionally, any person who's taken pride in their HTPC project, probably wants to retain control over the details displayed on that info screen, and leaving final control up to IMDB is sort of a crapshoot. A new video import methodology, one based off a portable text format, such as XML, might be more viable for MediaPortal in the long-term. Perhaps the IMDB import code could even be used for initial creation of these XML files, for users who don't necessarily micromanage their collections, or are just initially lacking that detailed metadata. No use letting that code go to waste. Thoughts? In the meantime, I guess I'll be looking into writing a .my file importer =] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
New system for importing music/video/weather... data
Contact us
RSS
Top
Bottom