Discussion to integrate X264 support
Posted: Thu Nov 11, 2010 3:07 am
There are a few threads on-going talking about x264 support, so I thought I would start something to condense information regarding some possible (not too far) future development...
Today, ZMS supports MJPEG and MPEG output such that basically the "watch" view creates an appropriate HTML wrapper and then ZMS just sends the output to stdout when called in a CGI application.
I think a good extension of this would be to support the creation of HTML-5 Video element to wrap x264 since that is what browsers are moving towards. What do you guys think?
I have this working in my XML plugin as it is today by using Pada's zstreamer piped to ffmpeg which is then piped to a HTML-5 segmenter. This approach is working, but I would like to integrate it all into ZMS so that we can all benefit from it by using it out of the XML plugin context, and use it in 'classic' ZM view.
What do you guys think about this path... any problems/points of contention? I will be contributing a lot in this arena in the coming few weeks, but would obviously benefit from the involvement from others.
Note: In the interest of full disclosure, I am doing this work as part of integrating H264 streaming into my eyeZm iPhone app as a feature, however, I'm contributing the code back to ZM of course and think it can benefit everyone the faster it gets done.
Today, ZMS supports MJPEG and MPEG output such that basically the "watch" view creates an appropriate HTML wrapper and then ZMS just sends the output to stdout when called in a CGI application.
I think a good extension of this would be to support the creation of HTML-5 Video element to wrap x264 since that is what browsers are moving towards. What do you guys think?
I have this working in my XML plugin as it is today by using Pada's zstreamer piped to ffmpeg which is then piped to a HTML-5 segmenter. This approach is working, but I would like to integrate it all into ZMS so that we can all benefit from it by using it out of the XML plugin context, and use it in 'classic' ZM view.
What do you guys think about this path... any problems/points of contention? I will be contributing a lot in this arena in the coming few weeks, but would obviously benefit from the involvement from others.
Note: In the interest of full disclosure, I am doing this work as part of integrating H264 streaming into my eyeZm iPhone app as a feature, however, I'm contributing the code back to ZM of course and think it can benefit everyone the faster it gets done.