Open MeowPerth opened 3 years ago
@MeowPerth please provide sample of faulty cbr output.
No sample provided, I close the issue -which can be reopened on demand.
I've once found this issue, and have been searching around solutions for it. Until I've made it through FFMPEG, there's still no other solutions including this tsMuxer to get proper "fixed"-CBR-muxed output, as I get, in result from tsMuxer, a VBR-muxed file with a bit rate much larger than I supposed it to have, no matter how I set the VBV buffer size.
@jcdr428 I was trying to figure out whereelse available for posting attachments that may seem so "large", but finally done it for I just figured it out to really have filesize limitation. failedcbr2.zip
Now posting a request to reopen this issue with many thanks in advance!
Maybe there's another issue with relation to this CBR muxing issue. No matter which muxing-rate mode I used in the most recent nightly build (git-f4fa419), including VBR, VBR (max bitrate restricted) and CBR mentioned above, I always get files result in a "maximum overall bitrate" of "35.5Mbps", which I'm so confused in as I can see playback realtime statistics showing bitrates peaking above some 30-ish Mbps nearly to 35Mbps and dropped drastically.
What makes it worse is for CBR muxing mode, I get files recently that result not only in nearly twice the desired bitrate, but in twice the desired size as well, with the "maximum overall bitrate" at 35.5Mbps and never changed all the way.
It seems there's gotta be solutions to take great advantage of FFmpeg's muxing method, for it can give, at least, bitrate results most approximate to desired values, and lowest muxing rate it is able give.
Why did I tick Mux CBR after, But the TS generated is still VBR?