| ▲ | kccqzy 9 hours ago | |||||||||||||
There are so many things that I would have done differently. > We added a keyframes_only flag. We modified the video decoder to check FrameType::Idr. We set GOP to 60 (one keyframe per second at 60fps). We tested. Why muck around with P-frames and keyframes? Just make your video 1fps. > Now it’s 10Mbps of blocky garbage that’s still 30 seconds behind. 10 Mbps is way too much. I occasionally watch YouTube videos where someone writes code. I set my quality to 1080p to be comparable with the article and YouTube serves me the video at way less than 1Mbps. I did a quick napkin math for a random coding video and it was 0.6Mbps. It’s not blocky garbage at all. | ||||||||||||||
| ▲ | taberiand 8 hours ago | parent | next [-] | |||||||||||||
This blog post smells of LLM, both in the language style and the muddled explanations / bad technical justifications. I wouldn't be surprised if their code is also vibe coded slop. | ||||||||||||||
| ||||||||||||||
| ▲ | mdavid626 9 hours ago | parent | prev | next [-] | |||||||||||||
Setting to 1 FPS might not be enough. GOP or P frame setting needs to be adjusted to make every frame keyframe. | ||||||||||||||
| ||||||||||||||
| ▲ | jcelerier 7 hours ago | parent | prev [-] | |||||||||||||
One man's not-blocky-garbage is another's insufferable hell. Even at 4k I find YouTube quality to be just awful with artefacts everywhere. | ||||||||||||||