-
Apple & x264 cap data rates
While outputting a commercial for a TV station that requested a specific data rate, I came across something I don’t understand and can’t find much of anything about online.
If I use Quicktime Pro or Handbrake to encode a 720×486 uncompressed AVI file to H264 (same pixel size), both cap the data rate at 32768kb/sec (no matter what data rate that I input). If I use Carbon Coder and export to H264 using it’s native codec (MainConcept), it allows me to plug-in literally any data rate I want and reflects it in the resulting file.
A TV station asked for an H264 file at 35000kb/sec. Most ask for around 25000kbs so that’s why we’ve never discovered this issue.
If I plug in 35000 in the data rate field of Quicktime Pro (Windows), it shows 35000 in the settings summary window, but as soon as you click back into the main settings tab, the number drops to 32768. You can change to anything below that and it shows and encodes correctly. But no matter what number above 32768 you input, the resulting file always ends up at the 32768kb/sec data rate. Roughly the same thing happens in Handbrake, although I believe its settings still show whatever you input into the data rate field.
I know that it’s capping the data rate because no matter what number you plug in above 32768, the file size stays the same on each encode. Conversely, using Carbon Coder, the resulting file sizes correctly reflect the various data rates that are input above 32768.
Anybody know why Apple’s H264 and x264 both seem to do this??
Chris Blair
Magnetic Image, Inc.
Evansville, IN
http://www.videomi.com
Read our blog http://www.videomi.com/blog