Reply to thread

Message

<blockquote data-quote="johanj" data-source="post: 1173961" data-attributes="member: 88055">I meant MP2Ext is work in progress in my post above.I really believe that your posts make people leave MediaPortal instead of attract them. MPExt for MP1 were developed during several years and we developed MediaPortal iViewer during those years. A lot of effort has been put in the service and it's stable although the version numbering state that it's not. And yes, it's not actively developed but it's used by several clients with little issues. I know that MP2 usage of the tv part of MPExt were not reliable. The most common usage(if you ask me) is to use MPExtended together with WifiRemote with a client (like aMPDroid or MediaPortal iViewer). Then the WifiRemote part as important as MPExtended. Other usage is Emby where only the tv-server part of MPExt is used. A lot happened during a short period of time with WifiRemote and MP2Ext for MP2 and I actively supported this by testing with our client MPiV. But WifiRemote part for MP2 is not completely developed and has issues. MP2Ext has issues. This is fully normal since it's currently in development. It will be better in the end than the MP1 versions. But today it's not and I can't recommend anyone to test it if you are not developing a client for the APIs. We will officially support MPiV together with MP2 and release a new version when everything is working. Until then I, sure, please help out testing your client and give the developers feedback of what's not working. But don't expect that you can connect existing clients and get most of the features working. Things can be different with aMPDroid and much more of the features can work there compared to MPiV. But MPiV uses much larger part of the MPExt api compared to aMPDroid...</blockquote>

[QUOTE="johanj, post: 1173961, member: 88055"] I meant MP2Ext is work in progress in my post above. I really believe that your posts make people leave MediaPortal instead of attract them. MPExt for MP1 were developed during several years and we developed MediaPortal iViewer during those years. A lot of effort has been put in the service and it's stable although the version numbering state that it's not. And yes, it's not actively developed but it's used by several clients with little issues. I know that MP2 usage of the tv part of MPExt were not reliable. The most common usage(if you ask me) is to use MPExtended together with WifiRemote with a client (like aMPDroid or MediaPortal iViewer). Then the WifiRemote part as important as MPExtended. Other usage is Emby where only the tv-server part of MPExt is used. A lot happened during a short period of time with WifiRemote and MP2Ext for MP2 and I actively supported this by testing with our client MPiV. But WifiRemote part for MP2 is not completely developed and has issues. MP2Ext has issues. This is fully normal since it's currently in development. It will be better in the end than the MP1 versions. But today it's not and I can't recommend anyone to test it if you are not developing a client for the APIs. We will officially support MPiV together with MP2 and release a new version when everything is working. Until then I, sure, please help out testing your client and give the developers feedback of what's not working. But don't expect that you can connect existing clients and get most of the features working. Things can be different with aMPDroid and much more of the features can work there compared to MPiV. But MPiV uses much larger part of the MPExt api compared to aMPDroid... [/QUOTE]

Verification