Live data from Hacker News

FFmpeg 9.0

github.com

91–100 of 107 posts

Re: FFmpeg 9.0

#91
post #47

Naive question... would it be possible to make a language that describes multimedia formats that could then be automatically converted into code.

You could, but there's two big reasons why this isn't useful:

1. The translation system would still have to implement the underlying ideas. For example, your spec might explain "key frames are made by doing a wavelet transform ABC, dropping frequency XYZ, applying Heuristic Alpha and then doing LZ encoding on the result" or something like that. You still need implementations of those specific operations. Having to explain all that stuff in the spec would mean each english language doc would be book length tretsie on encoding. As a result, you don't really gain much by doing this kind of meta-explaination.

2. Video encoding/decoding is something where optimization is extremely important. Writing code that is specific to a single purpose is generally going to be faster than generic code that could be applied to any theoretical format. For example, by knowing the exact size of a transformation matrix, you can decide whether to build a lookup table or calculate on the fly - you can use hardware level features that require knowing exact sizes at build-time etc.

Re: FFmpeg 9.0

#92
post #2

Changelog: - Extend AMF Color Converter (vf_vpp_amf) HDR capabilities - LCEVC track muxing support in MP4 muxer - Playdate video encoder and muxer - Add v360_vulkan filter - HE-AAC 960 decoding (DAB+) - transpose_cuda filter - Add AMF Frame Rate Converter (vf_frc_amf) filter - SMPTE 2094-50 metadata support and passthrough - ProRes RAW VideoToolbox hwaccel - APV Vulkan hwaccel - Animated WebP decoder - Animated WebP…

> Animated Webp

Hah! Useful for me today, to get rid of some hacks. Good stuff FFmpeg. It truly continues to be a pillar supporting the world in so many ways.

Re: FFmpeg 9.0

#93
post #76

Earlier quoted context omitted.

> - Animated WebP decoder Nice. browsers have supported this for a long time, and it was annoying ffmpeg did not, because that meant a lot of non-browser desktop apps couldn't view them either.

I thought it already supported webp via libwebp. Is this different?

[deleted]

Re: FFmpeg 9.0

#94
post #52
post #50

Earlier quoted context omitted.

Though there is one part I didn’t understand in that interview. They were complaining of being overwhelmed by AI submitted bug reports (fair), including for obscure codecs that must have been used by a couple of users at most. And therefore implying that securing those codecs is low priority/important. I don’t understand that. To me the severity has nothing to do with how popular is a code path, but whether that code…

That sounds nice in theory, but it seems obvious to me there is a major discrepancy between who is burdened with this responsibility, and who benefits from the result. Given many of these contributors are unpaid volunteers, maybe the infrastructure provider needs to secure FFmpeg in another way, for example by restricting codecs or by running it in a container?

AppArmor profile is probably what you are looking for to run ffmpeg on untrusted input

Re: FFmpeg 9.0

#95
post #50

Earlier quoted context omitted.

Though there is one part I didn’t understand in that interview. They were complaining of being overwhelmed by AI submitted bug reports (fair), including for obscure codecs that must have been used by a couple of users at most. And therefore implying that securing those codecs is low priority/important. I don’t understand that. To me the severity has nothing to do with how popular is a code path, but whether that code…

> To me the severity has nothing to do with how popular is a code path, but whether that code path is accessible to an attacker. That's true for targeted attacks. For untargeted attacks, attackers have little incentive to do the exploit.

Targeted to what? ffmpeg? Ffmpeg is the OpenSSL of video transcoding, it is used absolutely everywhere. If there is a vulnerability in ffmpeg, any website that processes user supplied videos is vulnerable

Re: FFmpeg 9.0

#97
post #75

Earlier quoted context omitted.

Wouldn't be impossible. I'm old enough to remember the original B+W game boy, and my B+W e-reader refreshes faster.

I've seen some very recent niche tech demoing fast-refresh e-ink screens but pretty much everything until now has required a noticeable flash to clear the entire screen on update. Which is fine for reading books but not for quick animating in an action game. Most e-ink displays do not refresh faster than the original GameBoy which was 60fps.

60fps is the speed the PPU pushes pixels to the LCD, not the speed the LCD physically refreshes itself. That part was slow enough you could toggle pixels at 30Hz to simulate more than 4 levels of gray.

I have a Boox e-reader. You can run Firefox on it, you can drag-to-scroll like a phone, there's a lot of ghosting (like the game boy) but it works fine. Now I wish I still had a game boy to compare it to.

Re: FFmpeg 9.0

#98
post #2

Changelog: - Extend AMF Color Converter (vf_vpp_amf) HDR capabilities - LCEVC track muxing support in MP4 muxer - Playdate video encoder and muxer - Add v360_vulkan filter - HE-AAC 960 decoding (DAB+) - transpose_cuda filter - Add AMF Frame Rate Converter (vf_frc_amf) filter - SMPTE 2094-50 metadata support and passthrough - ProRes RAW VideoToolbox hwaccel - APV Vulkan hwaccel - Animated WebP decoder - Animated WebP…

> - ONNX Runtime DNN backend with GPU execution provider support Oh, wonder what fancy new things this will enable. Any examples in the wild already perhaps?

When I was a vision engineer at a previous role back in 2022-ish, laptop-class Intel chips used in their SFF NUCs were powerful enough to run small finetuned convolutional nets by dancing across the different on the package: first decode using QSV, and then downsize using the CPU, run the images through an OpenVINO model running on the iGPU, and aggregate results and append metadata using the CPU core. You could have 50% of the hardware in today's high-end security cameras for 10% of the cost.

I have to assume that hardware advancements in the past four years have only pushed the efficiency envelope further.

Re: FFmpeg 9.0

#99
post #2

Changelog: - Extend AMF Color Converter (vf_vpp_amf) HDR capabilities - LCEVC track muxing support in MP4 muxer - Playdate video encoder and muxer - Add v360_vulkan filter - HE-AAC 960 decoding (DAB+) - transpose_cuda filter - Add AMF Frame Rate Converter (vf_frc_amf) filter - SMPTE 2094-50 metadata support and passthrough - ProRes RAW VideoToolbox hwaccel - APV Vulkan hwaccel - Animated WebP decoder - Animated WebP…

>- LCEVC track muxing support in MP4 muxer

I guess I am the only one excited to see this.

Re: FFmpeg 9.0

#100

Earlier quoted context omitted.

They used Claude for this release, as stated yesterday in their twitter page.

Yes, to find missing backports. The hand rolled aspects are still there and haven't been replaced by slop.

It's frustrating that vibecoding has gotten so pervasive that it's impossible to tell when someone uses LLMs as an awareness-increaser and research assistant, rather than an unreviewable code vomiter. I still appreciate the design of code done via the former strategy, whereas I simply will not rely on the latter.
Post reply on HN