The test is behind you. Today has two jobs: turn your test back into learning, and answer one question that sounds simple and isn’t — how big is a minute of video?
No reading. Bring your returned test and something to write with. Everything else is on this page.
The last time you’ll stand in Bits as home base. One foot is already in Programs — but before you go, today’s estimate reaches all the way forward to Big Data, because “how big is a minute of video” is where you first feel how much bits add up.
Most people guess “a few megabytes.” You now know enough to work out the real answer, and it is going to be much bigger than that. Everything you learned this unit — pixels, RGB, bits per pixel, and why compression has to exist — is about to land in one number.
A returned test is a dataset about you, and the point is not the grade at the top — it’s the pattern in what you missed. Sort your wrong answers into these three buckets. The bucket tells you what to do differently, which is far more useful than “study harder.”
| Bucket | What it looked like | The fix |
|---|---|---|
| Careless | You knew it; you misread the question or slipped on arithmetic. | Slow down and re-read the last line. Free points. |
| Confused pair | Overflow vs round-off, 2n vs 2n−1, lossless vs lossy, values vs largest value. | Re-learn the difference, not each term alone. |
| Never learned | You had no idea. The concept didn’t stick the first time. | Reopen that one lesson. Just that one. |
Here is the whole calculation, and every step is something you learned this unit:
Take a normal 1080p video: that’s 1920×1080 = about 2.07 million pixels per frame, at 30 frames per second. Multiply it out and one uncompressed minute is roughly 11 gigabytes — more than a whole phone’s worth of photos, for sixty seconds of footage. Yet the version you actually stream is around 50 MB. That gap, more than 200 to 1, is compression (1.8–1.9) doing the single most important job on the internet. Work it out yourself below.
Pick a resolution and frame rate, set how long the clip is, and watch the raw bits pile up. The “uncompressed” number is the honest pixel math; the “streamed” number is what a typical compressed version actually costs.
Everything above is multiplication you could do on paper — and Python does it in three lines. This is the arithmetic, not a new idea:
# A 1080p frame, uncompressed pixels = 1920 * 1080 → 2073600 bits = pixels * 24 → 49766400 # per frame per_min = bits * 30 * 60 / 8 → 11197440000 # bytes ≈ 11.2 GB
Notice the / 8 at the end: that converts bits to bytes, because
storage is measured in bytes. Miss it and your answer is 8× too big — exactly the
bit-vs-byte trap from the test.
No new terms today. The estimate above is built entirely from words you already own — and if any of these felt shaky while you worked, that is your signal to reopen the lesson in brackets:
/ 8 step is the difference, and forgetting it is the
classic mistake.Four questions on the estimate you just built. Pick an answer for instant feedback.
If raw video is 11 GB a minute and streamed video is 50 MB a minute, compression looks like a pure win — and mostly it is. But the streamed number isn’t one number. When a network is busy or a data plan is small, the video quality drops automatically: the bitrate falls, the picture softens, detail disappears. The student watching the same lecture on a capped phone plan gets a blurrier, choppier version than the one on home fiber — same video, different bits delivered.
That is the digital divide showing up in the arithmetic you just did, and it is a preview of Unit 8. Compression made streaming possible for everyone; the tradeoffs inside it still land unevenly on whoever has the least bandwidth. Both things are true at once.