Tim 'mithro' Ansell
Tim 'mithro' Ansell
Maybe use a database or something rather than the data.py file.
http://mindlinux.wordpress.com/2013/10/22/latest-gstreamer-streaming-server-features-video-on-demand-smooth-streaming-and-drm-david-schleef-rdio-inc/ http://superuser.com/questions/443411/http-streaming-with-gst-launch-gstreamer if you want stream via net, start you web server and correct pipe: gst-launch-1.0 videotestsrc is-live=true ! x264enc ! mpegtsmux ! hlssink max-files=5 playlist-root=http://server.com location=/var/www/hlssink playlist-location=/var/www/hlssink https://coaxion.net/blog/2014/05/http-adaptive-streaming-with-gstreamer/ http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/tree/ext/hls
Related to the idea of moving the configuration to a database.
- Crazy module import system. - Crazy module download system. - All the admin stuff - replace with JSON endpoints. - Merge the many repositories. - Rename the project.
I was unable to get flumotion working with hls. This module might be a way around it.
We currently use jwplayer 5.0 which is the previous version of the player. The new version includes a lot of new features such as; - Extended device support, including mobile...
We should be collecting video quality and performance stats on the client side and then report on them. Maybe through Google Analytics? # Firefox - mozParsedFrames - number of frames...
The system has a nice stat tracking feature. Make the frontend record everything possible about the client experiences.
WebRTC is awesome, lets see if we can use it?