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
General Development (no feature request here!)
MDAPI: Pros and Cons
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="draktheas" data-source="post: 61629" data-attributes="member: 17330"><p>Agarwal, I was not implying that we should do any decoding or plugin directly in MP and thus C#. I understand very well the performance implications. And I was not implying that we should write the MDAPI plugin wrapper for MP in C# either. There are ways to make generic MDAPI plugin support possible without using C# but still hooking into MP directly. One way is the way you have done it. Make a directshow filter that generically supports all MDAPI plugins. And if that is how you have implemented it then kudos to you. </p><p></p><p>I still, however, stand by my original statement that I am not for making it closed source. Again the main reason for that is because if it is closed source and you are the only one that is able to build it or fix bugs then everyone that uses MP is dependant solely on you. This is not a stab at you personally. It just defeats the purpose of having an opensource project when there are certain features that are only supported if the author of a closed source project releases updates and fixes bugs. I am not trying to get you to disclose your source. If you feel you have a viable reason for keeping it closed source, then that is your choice. I am, however, recommending that someone else (whether it's me or not) create and release MDAPI support that is open source so that MP and all of it's features can remain open source and maintainable by the MP devs.</p><p></p><p>Drak</p></blockquote><p></p>
[QUOTE="draktheas, post: 61629, member: 17330"] Agarwal, I was not implying that we should do any decoding or plugin directly in MP and thus C#. I understand very well the performance implications. And I was not implying that we should write the MDAPI plugin wrapper for MP in C# either. There are ways to make generic MDAPI plugin support possible without using C# but still hooking into MP directly. One way is the way you have done it. Make a directshow filter that generically supports all MDAPI plugins. And if that is how you have implemented it then kudos to you. I still, however, stand by my original statement that I am not for making it closed source. Again the main reason for that is because if it is closed source and you are the only one that is able to build it or fix bugs then everyone that uses MP is dependant solely on you. This is not a stab at you personally. It just defeats the purpose of having an opensource project when there are certain features that are only supported if the author of a closed source project releases updates and fixes bugs. I am not trying to get you to disclose your source. If you feel you have a viable reason for keeping it closed source, then that is your choice. I am, however, recommending that someone else (whether it's me or not) create and release MDAPI support that is open source so that MP and all of it's features can remain open source and maintainable by the MP devs. Drak [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MDAPI: Pros and Cons
Contact us
RSS
Top
Bottom