Earlier quoted context omitted.
I recommend watching the Lex Fridman interview with Jean-Baptiste Kempf and Kieran Kunhya. Amazing work on and amazing project.
Link?
FFmpeg 9.0
41–50 of 107 posts
Re: FFmpeg 9.0
#42I still hope a future FFmpeg release will make Intel QSV encoding available on Windows laptops where the manufacturer disabled this capability from the ACPI tables. The only way to use it on these laptops is currently FFmpeg on Linux.
how common is this with laptop manufacturers, and why would they do this? what brands are doing this so I can know to avoid them in the future.
Re: FFmpeg 9.0
#43twitch.tv has new HLS streamers which break ffmpeg HLS.
Re: FFmpeg 9.0
#44Ffmpeg has patented codes and is GPLv3, what gives?
The patents for software don’t apply in their country
Re: FFmpeg 9.0
#45Earlier quoted context omitted.
I'm curious if they used LLMs to do the tedious work of porting the (de/en)coders to different architectures, and how useful they are here.
Seems like Yes. https://nitter.net/FFmpeg/status/2084084810813743614 "Thank you @ClaudeDevs and @AnthropicAI for supporting FFmpeg through the Claude for Open Source program! So far, Claude has helped find missing backports for the upcoming 9.0 release." Although i was under the impression that they ususally preferred hand optimized assembly. Not sure what their LLM/AI contribution policy looks like compared to other…
No domain knowledge at all here but "find missing backports" doesn't sound like writing/porting code.
Re: FFmpeg 9.0
#46Re: FFmpeg 9.0
#47Naive question... would it be possible to make a language that describes multimedia formats that could then be automatically converted into code.
Re: FFmpeg 9.0
#48Naive question... would it be possible to make a language that describes multimedia formats that could then be automatically converted into code.
Should take a look at some of the ISO specs for various MPEG standards for example.
The container formats are defined in a way that could potentially make this possible.
Re: FFmpeg 9.0
#49Changelog: - 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?
Some people might want to remove it, but onnx is one of the few ways you can run hw accelerated convolutions
Re: FFmpeg 9.0
#50I feel we’re blessed to have a project like FFmpeg. This open source tool is so important for everyone.
I recommend watching the Lex Fridman interview with Jean-Baptiste Kempf and Kieran Kunhya. Amazing work on and amazing project.
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 path is accessible to an attacker. If I upload a specially crafted .mkv with a little known codec on YouTube and they use ffmpeg to process it, and I compromise YouTube’s infrastructure that way, it’s a pretty big deal, no matter the popularity of that codec.