Hi!
We’re having some problems getting our plug to work. The Plex crew seems pretty busy att the moment, so it’s kind of hard to get
answers to questions. This is of course completely understandable. To be able to move forward however it would be sweet if one
could access the source code for the media server to try and figure out what’s going on behind the scenes.
I looked at http://github.com/elan/plex/tree/v0.7, but was unable to locate anything resembling the media server.
Can someone point me in the right direction on where to find it?
Cheers!
Sorry, the media server isn’t open source, so the code isn’t available publicly.
Let us know if you have specific questions, we’d be happy to answer then 
If you’ve already asked them in a forum post, feel free to send me an email (elan at plexapp dot com) with the link.
Why is the Media Server closed-source? Are you planning to make us pay? No offence, but if so I’d better start looking for an alternative to Plex.
Greets
No, there are no plans at all to begin charging for Plex or the media server. Closed source does not equal having to pay, just like open source doesn't equal cost-free.
Were I a more cynical man, I'd say you ducked half the question there Jam :)
Out of curiosity, what are the ideological, commercial or other reasons that the decision was made to keep PMS closed source?
It is entirely reasonable that you may see it as something that could be profit making in the future - and that doesn't mean that you have to charge people for using it, there are other mechanisms (paid plugins for example).
I would be really sorry if the main (future) differentiator of plex vs. XBMC would end up closed-source. I can fully understand that it is kept closed while it is not finished, to keep off too eager people (me included) from fiddling around with it and get on jams nerves with too much “change/improvement requests”.
Isn't it probable that they keep it closed source just to keep it a differentiator between Plex and the XBMC branch??
Yes that could be - but what for ? Why should they give a damn if the xbmc team would pull their code in ?
If they are planning to use this to generate some revenue by selling it as IP to other commercial media-software players (mostly receiver boxes) then this would be a rather clever move. "We" would also benefit from being able to manage and use the dream-box or other receivers to be integrated into plex. From a "strategical" view that would make a lot of sense because most (or all) of those boxes are crap in terms of management of their content.
As long as most of the new mediamgr has open APIs for us to enhance and use it - i can live with it (that at least jam told me answering my inquiry of participation in that area).
Lets wait and see....
I can't speak for anyone. I don't know the reasoning. But if your assumption is correct, then I really hope they change their minds. Plex clearly benefits from being able to pull desired features (in fact, a LARGE part of the code) from XBMC. Turning around and then saying "your code was nice, thank you, now we're gonna do our own thing and not let you have it" is both petty and may lead to similar decisions by the xbmc developers. If everyone starts closed-sourcing, but making freely available.... well, we all lose.
I in fact removed boxee and switched to plex after learning that boxee was not intending to share their hulu code (I didn't care that much for hulu, but I *did* care that the Boxee developers were deciding to be selfish with their code). I'm rather disappointed to learn that the Plex streaming server code is closed source. I'm hoping this is just a temporary thing while the developers get it stabilized. If the streaming server code gets added to xbmc (with polite acknowledgements), odds are we will see more modules available for both.
For the most part I agree, and I humbly admit that my reasoning is most likely completely wrong.
I came here, because OSXBMCs source is available. If the guys want to make money with it, okay. Charge. I don’t care. But I want to be able to tinker with the source code to get it to do, what I want. Simple as that. If access to the source costs 100$, thats fine with me.
On the other hand, if this was to become commerical software, so will the free support from the community be gone, /me thinks.
Greets
trust me, that will NEVER happen.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
