Re:JSMpeg – Decode It Like It's 1999
by ryanmjacobs on Tuesday May 07, 2019 @07:13AM
(#19848341)
Of course. FFMpeg was used consistently on our backend; we cycled through various codecs to find the best one for our purpose and changed the frontend library accordingly.
And I think you're right on the encoding latency. I believe that H.264 buffers a little bit before it makes a decision on how to compress the frames, where as MPEG1 doesn't? I could be completely wrong but my gut is telling me that MPEG1 is basically independent, slightly-modified JPEG frames.
> I could be completely wrong but my gut is telling me that MPEG1 is basically independent, slightly-modified JPEG frames.
Not that simple, but not that far off.
Basically MPEG1 has key-frames (“JPEG” frames) and (forward) delta-frames (diffs).
From my understanding H264 has many improvements, including reverse delta-frames.
My guess is that disabling those in the encoder will improve real-time capabilities.
Re:JSMpeg – Decode It Like It's 1999
by ryanmjacobs on Tuesday May 07, 2019 @10:47AM
(#19849938)
Ah gotcha, I think I was mixing up MPEG1 and MJPEG in my head.
I didn't realize that you could disable those features in the encoder. I'll have to look into x264 tunables that lower latency. Might be interesting.
Bingo, that's one of the tuning you can use for real-time communication.
There's a lot of ways to tune an encoder, and getting optimal setting for each use case is always tricky.
Curious what exactly you tried - H.264 is a codec, and there's a bunch of ways of delivering it to the client (HLS, WebRTC, some have build WebSocket-based streaming, ...), and I'd expect that the main latency is hidden there, not in the decoding?