I was given the following formula perhaps a couple years ago by someone...
video bitrate = 0.00022458 * width * height * framerate
Anyone else found this useful?
Results 1 to 6 of 6
-
I've never seen that formula, but its functional dependencies seem not quite right -- it scales linearly with width*height, rather than, say, logarithmically with the product. But for some range of parameters, I'm sure that it can do ok, given that quality is a moderately weak function of bitrate beyond some minimum threshold.
-
The value 0.00022458 seems to be what ffmpegX 0.0.9x r2 (*) uses for [Best]:
207 = 206.972928 = 0.00022458 * 320 * 240 * 12
703 = 703.0042472448 = 0.00022458 * 480 * 272 * 23.976
2328 = 2328.44544 = 0.00022458 * 720 * 576 * 25
(*) 0.0.9x has a working [Best] button for the ffmpeg engine, where 0.0.9y shows the iframeflag error (on my system).
-
What about ffmpegx 0.0.9y?
What would be the difference? This has really been a useful resource; but I obviously didn't understand the underlying math!
Thanks!
-
I think what Case is saying is that version y should be using the same math, but it has a bug. No need to understand the underlying math more than this: higher framerates and larger resolutions should require higher bitrates. The approximate formulas used by ffmpegx assume that the bitrate is proportional to the simple product of these factors. The magic proportionality constant just fixes up the numbers to give you an absolute bitrate. I'm sure that it was chosen somewhat by eye, guided by some science.
DSP experts would point out that the assumption of simple proportionality is a bit dubious, but for a practical range of parameters, it yields a useful rough guide.
-
Originally Posted by stembridge
Originally Posted by stembridge
So, one could get the multiplier by experimentation (testing various bitrates) and reversing the equation:
video bitrate = multiplier * width * height * framerate
multiplier = video bitrate / ( width * height * framerate )
One could keep it all mathematical and use "Peak signal-to-noise ratio" (psnr) as quality measurement, even across codecs, and avoid subjective human quality perception, although the threshold would still be subjective.
But if you think 207 kbps at 320x240 @ 12 fps still looks crap, then you're free to use a higher bitrate. The 'standard' used for FLV bitrates is pretty low, after all...
Similar Threads
-
Can you JOIN two FLVs?
By r2997790 in forum Video ConversionReplies: 1Last Post: 22nd Jun 2010, 03:04 -
FLVs and 15fps?
By CursedLemon in forum Video ConversionReplies: 4Last Post: 10th Oct 2009, 17:30 -
Problems with my FLVs!!!
By durgamata57 in forum Video ConversionReplies: 2Last Post: 8th Oct 2008, 10:17 -
A/V Sync on only some FLVs
By RedPenguin in forum Video ConversionReplies: 13Last Post: 23rd Jun 2008, 18:37 -
FLVs not looking too good...
By stembridge in forum ffmpegX general discussionReplies: 4Last Post: 26th Aug 2007, 10:40