Video resolution vs bit-rate
Ask iLounge offers readers the opportunity to get answers to their iPod-, iPhone-, iPad-, iTunes-, or Apple TV-related questions from a member of the iLounge editorial team. We'll answer several questions here each week, and of course, you can always get help with more immediate concerns from the iLounge Discussion Forums. Submit your questions for consideration using our Ask iLounge Submit Form. We reserve the right to edit questions for grammar, spelling, and length.
Q: I have a new iPod classic 160 GB that I’m loading with videos. I’ve read that a 640x480 file is the same MB size as a 320x176 file if encoded at the same kbps (bit-rate). Is this correct? Is there an advantage to the bigger size? Is there a “definitive” guide you can point me to that explains the relation between resolution and kbps clearly. Thanks in advance, and keep up the great work.
A: As odd as it may sound, it is actually correct that a given video file’s size is based on the bit-rate of that file, expressed in kbps or kilobits per second, rather than on the resolution.
Much like audio files, the bit-rate defines how much data is stored for each second of playback. This means that a 1500 kbps video file has 1,500,000 bits of data stored for each second of playback time. In that sense, basic math will let you determine the size of a file relative to the bit-rate.
This may seem counterintuitive, since you expect a higher resolution file to occupy more space, in the same way that a higher resolution picture occupies more space. While this may be true in the case of an uncompressed video, the reality is that modern video compression algorithms are “lossy” by nature, and do not actually store a full image for each frame of video—instead, “reference” frames are stored, and then additional data is used to represent the changes between reference frames. These are interpreted during playback to produce relatively smooth motion video.
The catch is that there actually is a direct relationship between the bit-rate of a video and the resolution—or perhaps more accurately, between the resolution and an acceptable bit-rate. The larger the image, the more data is going to be required to accurately represent the motion within that image. For instance, although you may technically be able to encode a 640x480 and a 320x172 video file at the same bit-rate, you will either be creating an unnecessarily large 320x172 video (if the bit-rate is too high), or creating a very poor quality 640x480 video (if the bit-rate is too low). Generally, the bit-rate needs to be appropriate for the video resolution in order to produce an acceptable playback experience with reasonable quality. Too low of a bit-rate will produce a movie file that with visual problems such as “artifacting” and “macroblocking” and possibly even choppy playback (skipped frames).
As a rule, for acceptable playback when encoding video for the iPod using the H.264 codec, a 320x240 video file (encoded for the iPod screen), can generally be done with a bit-rate of approximately 750kbps, whereas a 640x480 file should use a bit-rate of approximately 1500kbps. On the other hand, videos encoded into standard MPEG-4 require slightly higher bit-rates, as the standard MPEG-4 codec is not as efficient.
You can find a much more detailed discussion about this, as well the suggested formats and display resolutions in our iPod 101 tutorial The Complete Guide to iPod, Apple TV and iPhone Video Formats
- Will removing a credit card from Safari also remove it from Apple Pay?
- Can I mute Handoff calls coming into my Mac from my iPhone?
- How do I keep my iPhone calls from ringing on my Mac?
- Why doesn’t Traffic show up on my Today Notifications Screen?
- Why doesn’t my iPhone reconnect to Wi-Fi after I turn it on?
- Why can’t I see the iPad-style landscape view on my iPhone 6 Plus?
- More details emerge on Apple Music overhaul
- iPhone tops Time’s list of most influential gadgets
- Kohl’s integrates rewards system with Apple Pay
- Apple hires ex-Nest exec to aid in health initiatives
- Apple loses exclusive ‘iPhone’ trademark in China
- Apple to reveal ‘sweeping changes’ to Apple Music interface at WWDC
- Apple releases fourth developer betas for iOS 9.3.2, tvOS 9.2.1
- Bowers & Wilkins acquired by EVA Automation
- India rejects Apple’s plan to sell used iPhones
- Rumor: Purported iPhone 7 component photo shows headphone jack intact
- August Doorbell Cam
- August Smart Lock HomeKit enabled + Smart Keypad
- ecobee3 HomeKit-enabled smart Wi-Fi thermostat
- Zagg Now Cam
- Yantouch EyE Portable Wireless Speaker
- Netatmo Wind Gauge
- Incipio Stashback for iPhone 6/6s
- Schlage Sense Smart Deadbolt with HomeKit support
- ClamCase ClamCase Pro for iPad mini 4
- Brydge BrydgeMini II Keyboard for iPad mini 4
- Filling the Gap: A look at third-party HomeKit apps
- Instant Expert: Secrets & Features of tvOS 9.2
- Instant Expert: Secrets & Features of iOS 9.3
- Opinion: Why Apple needs a dedicated HomeKit app
- Inside the betas: What’s new in iOS 9.3 and tvOS 9.2 (Updated)
- Life with HomeKit: Our experiences with Apple’s home automation system
- Under the Radar: 10 ‘hidden’ details about the new Apple TV
- Instant Expert: Secrets & Features of iOS 9.0
- Under the Radar: A closer look at smaller iPhone 6s and iPhone 6s Plus changes
- A First Look at iOS 9’s Transit in Apple Maps (Updated for watchOS 2)