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
General Forums
OffTopic
A Dream: MediaPortal & XBMC combining forces together...
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="phunqe" data-source="post: 282282" data-attributes="member: 50050"><p>The only thing that REALLY bothers me is the IMDB scan in MP at the moment. It bothers me that much that I think it should either be fixed or removed all together.</p><p>It is beyond broken. Scanning 500 movies in MP resulted in about 10% tagged correctly. Scanning the same with XBMC yielded the OPPOSITE result, i.e 10% NOT tagged correctly.</p><p></p><p>Another thing is the general beta state of things. For example I want to install Skin X right. Ok then I need this and that SVN version. Oh wait, something broke in that SVN version so I have to download a separate SVN version for some module. But uh oh, that version broke something in the skin so then I have to downgrade the skin, but now the skin insn't working at all since I upgraded other stuff.</p><p></p><p>It's basically the story of MP if you want to use anything newer than the official releases (which are usually very old, or has been very old before the latest RC1). There is too much breakage of stuff. I know about SVN and development, I am a developer myself, but it seems there are issues in settling for certain APIs and such which leads to a lot of frustration. </p><p>Some would say "Well beta is beta, run the release version". Yes, I would, but even the release version ends up being unusable after a while since you cannot even find plugins for it that works anylonger (or you have a seriously hard time finding them, you might even need to get a specific tag from SVN and compile it yourself).</p><p></p><p>I sincerely hope this will change with MPII and that certain things are really thought through from the beginning. In my opinion, internal APIs etc shold not even be changed within a version cycle. If they are in such bad state the branch should just be declared EOL as soon as possible.</p><p></p><p>With that said I, personally, think that MPI should have reached End of Life a long time ago. What is (seemingly) happening now is trying to repair something that was a quilt even before. MPI should have been left and the development on MPII should have been started asap. Many said "well it will be a while before we will see anyhing". Yeah ok, but that was like what.. over 6 months ago? MPII would have been lightyears more mature now than it is, in some areas probably much better than MPI is now. Even if MPI has reacher greater stability I'm having a hard time weighing the value in what has been done on MPI as opposed to what we would have had with MPII if that development started seriously when it could have.</p></blockquote><p></p>
[QUOTE="phunqe, post: 282282, member: 50050"] The only thing that REALLY bothers me is the IMDB scan in MP at the moment. It bothers me that much that I think it should either be fixed or removed all together. It is beyond broken. Scanning 500 movies in MP resulted in about 10% tagged correctly. Scanning the same with XBMC yielded the OPPOSITE result, i.e 10% NOT tagged correctly. Another thing is the general beta state of things. For example I want to install Skin X right. Ok then I need this and that SVN version. Oh wait, something broke in that SVN version so I have to download a separate SVN version for some module. But uh oh, that version broke something in the skin so then I have to downgrade the skin, but now the skin insn't working at all since I upgraded other stuff. It's basically the story of MP if you want to use anything newer than the official releases (which are usually very old, or has been very old before the latest RC1). There is too much breakage of stuff. I know about SVN and development, I am a developer myself, but it seems there are issues in settling for certain APIs and such which leads to a lot of frustration. Some would say "Well beta is beta, run the release version". Yes, I would, but even the release version ends up being unusable after a while since you cannot even find plugins for it that works anylonger (or you have a seriously hard time finding them, you might even need to get a specific tag from SVN and compile it yourself). I sincerely hope this will change with MPII and that certain things are really thought through from the beginning. In my opinion, internal APIs etc shold not even be changed within a version cycle. If they are in such bad state the branch should just be declared EOL as soon as possible. With that said I, personally, think that MPI should have reached End of Life a long time ago. What is (seemingly) happening now is trying to repair something that was a quilt even before. MPI should have been left and the development on MPII should have been started asap. Many said "well it will be a while before we will see anyhing". Yeah ok, but that was like what.. over 6 months ago? MPII would have been lightyears more mature now than it is, in some areas probably much better than MPI is now. Even if MPI has reacher greater stability I'm having a hard time weighing the value in what has been done on MPI as opposed to what we would have had with MPII if that development started seriously when it could have. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
OffTopic
A Dream: MediaPortal & XBMC combining forces together...
Contact us
RSS
Top
Bottom