"8-12 seconds End-to-End Latency" for community edition.
Actually a commercial product is not necessarily a problem, but the monthly fees are. If there was a one time fee version (perhaps with limited number of clients or something), then this might work.
I also poked a round with making a real time remote desktop client that could be access via a web browser for linux. It to -- at least on local lans got very low latency video. The link for that is below too.
- https://www.youtube.com/watch?v=7kSbm-IQjK0
- https://www.youtube.com/watch?v=JJ_srz7Ti8Y
Edit: I should mention latency were measured in ms, not seconds, even for many clients. I am sure to scale out to 1000's of users I would have to add a bit, of latency but not by much.
That being said, the ffmpeg solution is not using the hardware accelerator either, even though it does support MJPEG. But I think with work we can get a gstreamer based solution: the missing part is an equivalent of ffserver that works with gstreamer. The hardware vendors like to provide gstreamer plug-ins for their accelerators.
Also, it's weird to me that this needs a giant javascript client library. What about the HTML5 built-in video support?
My code is geared to robots -- and has not been updated recently but there is at least a example of the simpler multiplexing in go.