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 2
Plugin Development
How To Install a MPE1 Plugin File in MediaPortal2
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="Lehmden" data-source="post: 1171799" data-attributes="member: 109222"><p>Hi.</p><p></p><p>This may be your personal experience, but mine is the opposite. With every new release of MP1 more and more unneeded breaking changes are introduced, the system was getting more complex and it was far away from being stable at all. Here even the old Alpha Builds of MP2 were working much more stable... And the TV Server never was reliable as it depends on a full blown SQL server to be up and running before TV server can start at all. On 99% of all system starts this did not work here (no matter if I use MySQL or SQL Express) so the TV server never did start with Windows as it should be... Need to start TV server manually with a batch to get schedules working at all... </p><p>I can remember I was developing a skin for MP1 and needed to start three times from scratch because there are changes that breaks the skin compatibility in every new version. This was my last attempt to work on MP1...<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite4" alt=":mad:" title="Mad :mad:" loading="lazy" data-shortname=":mad:" /></p><p></p><p></p><p>This is something I definitely can not agree. SMP is so huge, it's so slow and it is really not even half as good looking as e.g. PureVision or even DefaultWide... But I always would prefer SMP over Titan. This "candy store" skin I never liked and never will be. The most beautiful skin I've seen is dead since years<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite16" alt=":cry:" title="Crying :cry:" loading="lazy" data-shortname=":cry:" />, it was Backdrop.</p><p></p><p></p><p>Yes. This is a fact. Client plugins needs to be ported over to MP2 if you want to use them (as example, OnlineVideos was ported from MP1 to MP2)...</p><p></p><p></p><p>This never was possible at all. You always need the MP2-Server as it is the core of any MP2- architecture. Long time ago you could select if you want to use the new TV Engine 3.5 (only available for MP2 up to now) or the MP1-TV server with MPExtended as TV source. The MPExtended solution has limited features and as MPE development is dead since ages we could not get a nice TV solution based on any of those TV sources. A year ago we decided to not wait any longer for TVE 3.5 hitting at least Alpha state (here you have your beloved <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> Alpha, Beta or whatever) so we use the TV Engine 3.0 (not the TV server from MP1!) as primary TV source. Ever since then the TVE 3.0 is part of the MP2 Server installation. As TV only is a simple plugin inside the MP2- server you still can use the old (depend on your POV) TVE3.5 or MPExtended plugins like before. But every average user of MP2 has a full blown TV solution installed with MP2 automatically... And as the TV engine is nearly identical to the Engine used in MP1- TV server you can use (most of the) MP1 TV server plugins in MP2 too... This definitely is true for the schedules direct plugin that was the start of this topic...</p><p></p><p></p><p>This you understand completely wrong. As told before the MP2-Server is the core part of every MP2 installation. TV only is a single plugin inside the MP2-Server. And this single plugin is exchanged a year ago from TVE 3.5 "pre Alpha" to TVE3.0 "Stable"...</p><p></p><p></p><p>This did not work, as you still need the MP2-Server and aside this the MPEI will install the plugins to the wrong place when using MP2...</p><p></p><p></p><p>And here you have missed another step. We have decided to not use Alpha or Beta any longer as this did not match the real status of the MP2 development at all. If you really need to add such a label then MP2 is "Stable" since a year now! Means all parts are reliable and working (imho much more reliable than MP1 ever was) But as MP2 still is not feature complete (at the end of this year we probably are close to be feature complete) we also do not like to use the term "Stable" that much... That's why there is no such label any more and probably never will be back again...</p><p></p><p></p><p>Because I can not see MP1 is the present. Eating up so much resources, the need for full set of metadata on every client, no future support for mobile devices (MPExtended is a) proprietary and b) dead since years) all this is something for the first decade of the 21st century, not for the second... </p><p>Don't get me wrong, this did not mean it is not working as you may like it. My Vespa (my main transport vehicle) is from the 20th Century, and it is still working like a charm. I never will exchange it with a modern Chinese or Japanese scooter, never ever... But I know I have to live without ABS and with a high fuel consumption (twice as much as a modern e.g. Honda) if I want to drive Vespa. If I have to suggest a scooter for a newbie I definitely would not suggest to buy an old Vespa as a modern "Chinese" is cheaper a lot and easier to maintain. Modern Vespas (yes they are build up to today) are really expensive so not that good choice for a beginner... Later if the driver is more experienced he can decide on his own what he wants...</p><p></p><p></p><p>Also old fashioned vs modern attempt... A version numbering is an completely abstract thing that didn't say nothing about the real status. In a few years you will not remember which version of MP1 was recent today. But if it is called "Summer 15" you always will know it is from the year 2015...</p><p></p><p></p><p>Ok, thanks. That is indeed a new one to me. As I have used MP1 (it's long ago) this was definitely not the case and, even worse it was called "impossible" as MPEi would need too much parts of an MP1 Client to work... Looks as if it was not that impossible at all...<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p></p><p>By the way, I did not know where you get that screenshot from. I can't reach this page at all...</p></blockquote><p></p>
[QUOTE="Lehmden, post: 1171799, member: 109222"] Hi. This may be your personal experience, but mine is the opposite. With every new release of MP1 more and more unneeded breaking changes are introduced, the system was getting more complex and it was far away from being stable at all. Here even the old Alpha Builds of MP2 were working much more stable... And the TV Server never was reliable as it depends on a full blown SQL server to be up and running before TV server can start at all. On 99% of all system starts this did not work here (no matter if I use MySQL or SQL Express) so the TV server never did start with Windows as it should be... Need to start TV server manually with a batch to get schedules working at all... I can remember I was developing a skin for MP1 and needed to start three times from scratch because there are changes that breaks the skin compatibility in every new version. This was my last attempt to work on MP1...:mad: This is something I definitely can not agree. SMP is so huge, it's so slow and it is really not even half as good looking as e.g. PureVision or even DefaultWide... But I always would prefer SMP over Titan. This "candy store" skin I never liked and never will be. The most beautiful skin I've seen is dead since years:cry:, it was Backdrop. Yes. This is a fact. Client plugins needs to be ported over to MP2 if you want to use them (as example, OnlineVideos was ported from MP1 to MP2)... This never was possible at all. You always need the MP2-Server as it is the core of any MP2- architecture. Long time ago you could select if you want to use the new TV Engine 3.5 (only available for MP2 up to now) or the MP1-TV server with MPExtended as TV source. The MPExtended solution has limited features and as MPE development is dead since ages we could not get a nice TV solution based on any of those TV sources. A year ago we decided to not wait any longer for TVE 3.5 hitting at least Alpha state (here you have your beloved ;) Alpha, Beta or whatever) so we use the TV Engine 3.0 (not the TV server from MP1!) as primary TV source. Ever since then the TVE 3.0 is part of the MP2 Server installation. As TV only is a simple plugin inside the MP2- server you still can use the old (depend on your POV) TVE3.5 or MPExtended plugins like before. But every average user of MP2 has a full blown TV solution installed with MP2 automatically... And as the TV engine is nearly identical to the Engine used in MP1- TV server you can use (most of the) MP1 TV server plugins in MP2 too... This definitely is true for the schedules direct plugin that was the start of this topic... This you understand completely wrong. As told before the MP2-Server is the core part of every MP2 installation. TV only is a single plugin inside the MP2-Server. And this single plugin is exchanged a year ago from TVE 3.5 "pre Alpha" to TVE3.0 "Stable"... This did not work, as you still need the MP2-Server and aside this the MPEI will install the plugins to the wrong place when using MP2... And here you have missed another step. We have decided to not use Alpha or Beta any longer as this did not match the real status of the MP2 development at all. If you really need to add such a label then MP2 is "Stable" since a year now! Means all parts are reliable and working (imho much more reliable than MP1 ever was) But as MP2 still is not feature complete (at the end of this year we probably are close to be feature complete) we also do not like to use the term "Stable" that much... That's why there is no such label any more and probably never will be back again... Because I can not see MP1 is the present. Eating up so much resources, the need for full set of metadata on every client, no future support for mobile devices (MPExtended is a) proprietary and b) dead since years) all this is something for the first decade of the 21st century, not for the second... Don't get me wrong, this did not mean it is not working as you may like it. My Vespa (my main transport vehicle) is from the 20th Century, and it is still working like a charm. I never will exchange it with a modern Chinese or Japanese scooter, never ever... But I know I have to live without ABS and with a high fuel consumption (twice as much as a modern e.g. Honda) if I want to drive Vespa. If I have to suggest a scooter for a newbie I definitely would not suggest to buy an old Vespa as a modern "Chinese" is cheaper a lot and easier to maintain. Modern Vespas (yes they are build up to today) are really expensive so not that good choice for a beginner... Later if the driver is more experienced he can decide on his own what he wants... Also old fashioned vs modern attempt... A version numbering is an completely abstract thing that didn't say nothing about the real status. In a few years you will not remember which version of MP1 was recent today. But if it is called "Summer 15" you always will know it is from the year 2015... Ok, thanks. That is indeed a new one to me. As I have used MP1 (it's long ago) this was definitely not the case and, even worse it was called "impossible" as MPEi would need too much parts of an MP1 Client to work... Looks as if it was not that impossible at all...;) By the way, I did not know where you get that screenshot from. I can't reach this page at all... [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
Plugin Development
How To Install a MPE1 Plugin File in MediaPortal2
Contact us
RSS
Top
Bottom