Closed kench closed 8 years ago
I can't get behind Flowplayer and their licensing tactics. Not truly open source if you ask me. On Nov 8, 2014 7:26 PM, "Kenley Cheung" notifications@github.com wrote:
Add support for RTMP URLs. We might need to pull in something like Flowplayer to handle this one.
Source: https://groups.google.com/forum/#!topic/concerto-digital-signage/CXJDjNTONjE
— Reply to this email directly or view it on GitHub https://github.com/concerto/concerto-remote-video/issues/23.
Key term is "something like Flowplayer"
A quick Google search for alternatives include:
https://github.com/gokercebeci/f4player https://github.com/mikkun/rtmpPlayer
All of which are some variant of the GPL, which may not be completely desirable since Concerto 2 and plugins are Apache licensed. Perhaps writing our own player in AS3 would be the best solution.
From casual observation of the above projects, the logic can be implemented in less than 1000 lines of code if anyone was inclined to write their own RTMP playback solution.
I don't think we've seen enough demand for RTMP for it to warrant direct integration into the remote-video element yet, lets keep this open to track interest.
Agreed. My sense is that adding video URL support (backed by HTML5 and Flash) was the key use case for this plugin and has addressed most people's video needs (and with additional browser support will solve yet more).
Add support for RTMP URLs. We might need to pull in something like Flowplayer to handle this one.
Source: https://groups.google.com/forum/#!topic/concerto-digital-signage/CXJDjNTONjE