Peru 8K HDR 60FPS (FUHD)

Jacob + Katie Schwarz · 63.8M views · 2017 · 5:38

Open on YouTube

Audio & video engineeringVisual arts, photography & architectureotherdated

Why Hacker News recommends it

HN doesn't recommend it for its content but uses it as a handy example of file size and bitrate for high-resolution video.

What it is

A travel video of Peru shot natively in 8K HDR at 60fps on a Red Helium sensor. It covers Lima, the Amazon, Cusco and other places.

Recommended by 0 HN commenters across 0 different months, 2019 to 2025.

What Hacker News said

Cites darkpuma · 2019-06 · on “NYC Mesh Begins Broadband Expansion in Brooklyn”

No way, 100Mbps is fast today for most people. This 8K youtube video is 5m38s long and 850MiB large: [this video] Do the math on that and you need 21Mbps to stream that video without buffering, assuming a uniform bitrate: [LINK] 100Mbps down is fast for most people. What do you think the average user is doing that needs more than 100Mbps down?

Cites exikyut · 2020-07 · on “Western Digital's 16TB and 18TB drives: EAMR HDDs enter the retail channel”

> YT alone adds 500hrs of video per min . That is at minimum 9000 TB / day (500 18TB disks/day ...) ... assuming SD quality 220 mb per hour single format and one copy. Nitpick: Each bigger resolution stacks on top of the previous one, so 8K60fps means storing 8K60 (webm+av1), alongside 4K60 HDR (webm), 4K60 (webm+av1), 4K (webm), 1440p60 HDR (webm), 1440p60 (webm+av1), 1440p (webm), 1080p60 HDR (webm), 1080p60 (webm+h264+av1), 1080p (webm+h264), 720p60 HDR (webm), 720p60 (webm+h264+av1), 720p (webm+h264), 480p60 HDR (webm), 480p (webm+h264+av1), 360p60 HDR (webm), 360p (webm+h264+av1), 240p60 HDR (webm), 240p (webm+h264+av1), 144p60 HDR (webm), and 144p (webm+h264+av1). And as noted, a given

Cites nemothekid · 2025-12 · on “We replaced H.264 streaming with JPEG screenshots (and it worked better)”

Video Streaming has surprising little overlap with Video Codecs . Once you choose input/output options, then there's little to change about the codec. The vast majority of options available to ffmpeg aren't supported in the browser. Streamers don't have options for precisely the same reason OP doesn't have options - you are limited entirely into what the browser supports. I've built the exact pipeline OP has done - Video, over TCP, over Websockets, precisely because I had to deliver video to through a corporate firewall. Wolf, Moonlight and maybe even gstreamer just shows they didn't even try to understand what they were doing, and just threw every buzzword into an LLM. To give you some pers