Hi We had the same problem, and we solved it by creating cbr ts files stuffed with NULL packets. The following thread shows the ffmpeg command parameters to create h.264 cbr files: http://stackoverflow.com/questions/7125446/encoding-h-264-cbr-videos-with-ffmpeg
Mojtaba Nouri Soroush HighTech Ltd. On Tue, Sep 11, 2012 at 9:41 PM, Warren Young <war...@etr-usa.com> wrote: > On 9/10/2012 5:51 PM, Warren Young wrote: > >> >> If you take >> a guess at the GOP length, you can infer frame rate. >> > > I meant bit rate, obviously. > > We've tried to get a CBR stream out of ffmpeg, just to prove to ourselves > that stream variability is the problem. We haven't succeeded. Apparently > ffmpeg is incapable of CBR with H.264, even when you set min = avg = max. > > That said, those settings did greatly reduce the variability. Here's the > new stream: > > > http://etr-usa.com/live555/**h264-test-cbr.ts<http://etr-usa.com/live555/h264-test-cbr.ts> > > It shows the same stuttery playback with the stock build of the RTSP > server. The bit rate range is now 5-10 Mbit/s over the majority of the > play time, averaging 7.5 Mbit/s. (It was 2-16 Mbit/s!) > > We'll try to get a less variable file out of other encoders next. > > ______________________________**_________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/**mailman/listinfo/live-devel<http://lists.live555.com/mailman/listinfo/live-devel> >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
