Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FFmpeg 8.0

ffmpeg.org

Post reply on HN
Print view View original

81–90 of 207 posts

Re: FFmpeg 8.0

#81

Post by fleabitdev »

Happy to hear that they've introduced video encoders and decoders based on compute shaders. The only video codecs widely supported in hardware are H.264, H.265 and AV1, so cross-platform acceleration for other codecs will be very nice to have, even if it's less efficient than fixed-function hardware. The new ProRes encoder already looks useful for a project I'm working on.

> Only codecs specifically designed for parallelised decoding can be implemented in such a way, with more mainstream codecs not being planned for support.

It makes sense that most video codecs aren't amenable to compute shader decoding. You need tens of thousands of threads to keep a GPU busy, and you'll struggle to get that much parallelism when you have data dependencies between frames and between tiles in the same frame.

I wonder whether encoders might have more flexibility than decoders. Using compute shaders to encode something like VP9 (https://blogs.gnome.org/rbultje/2016/12/13/overview-of-the-v...) would be an interesting challenge.

Re: FFmpeg 8.0

#82

Post by turnsout »

conradev wrote: post #51
Keyframe wrote: post #10

Earlier quoted context omitted.

with gemini-cli and claude-cli you can now prompt while it prompts ffmpeg, and it does work.

Yeah, you can give an LLM queries like “make this smaller with libx265 and add the hvc1 tag” or “concatenate these two videos” and it usually crushes it. They have a similar level of mastery over imagemagick, too!

Yeah, LLMs have honestly made ffmpeg usable for me, for the first time. The difficulty in constructing commands is not really ffmpeg's fault—it's just an artifact of the power of the tool and the difficulties in shoehorning that power into flags for a single CLI tool. It's just not the ideal human interface to access ffmpeg's functionality. But keeping it CLI makes it much more useful as part of a larger and often automated workflow.

Re: FFmpeg 8.0

#83

Post by bachittle »

0xbeefcab wrote: post #4

Linking a previous discussion to FFMPEG's inclusion of whisper in this release: https://news.ycombinator.com/item?id=44886647 This seemed to be interesting to users of this site. tl;dr they added support for whisper, an OpenAI model for speech-to-text, which should allow autogeneration of captions via ffmpeg

Heads up: Whisper support depends on how your FFmpeg was built. Some packages will not include it yet. Check with `ffmpeg -buildconf` or `ffmpeg -filters | grep whisper`. If you compile yourself, remember to pass `--enable-whisper` and give the filter a real model path.

Re: FFmpeg 8.0

#84

Post by mtillman »

fleabitdev wrote: post #81

Happy to hear that they've introduced video encoders and decoders based on compute shaders. The only video codecs widely supported in hardware are H.264, H.265 and AV1, so cross-platform acceleration for other codecs will be very nice to have, even if it's less efficient than fixed-function hardware. The new ProRes encoder already looks useful for a project I'm working on. > Only codecs specifically designed for para…

Exciting! I am consistently blown away by the talent of the ffmpeg maintainers. This is fairly hard stuff in my opinion and they do it for free.

Re: FFmpeg 8.0

#85

Post by profsummergig »

Keyframe wrote: post #10
Culonavirus wrote: post #6

Earlier quoted context omitted.

> incantation FFmpeg arguments, the original prompt engineering

with gemini-cli and claude-cli you can now prompt while it prompts ffmpeg, and it does work.

Just seeking a clarification on how this would be done:

One would use gemini-cli (or claude-cli),

- and give a natural language prompt to gemini (or claude) on what processing needs to be done,

- with the correct paths to FFmpeg and the media file,

- and g-cli (or c-cli) would take it from there.

Is this correct?

Re: FFmpeg 8.0

#87

Post by mrguyorama »

encom wrote: post #62
bigstrat2003 wrote: post #30

Earlier quoted context omitted.

The problem is it's very non-obvious and thus is unnecessarily hard to learn. Yes, once you learn the incantations they will serve you forever. But sit a newbie down in front of a shell and ask them to extract a file, and they struggle because the interface is unnecessarily hard to learn.

It's very similar to every other CLI program, I really don't understand what kind of usability issue you're implying is unique to tar?

As has been clearly demonstrated in this very thread, why is "Please list what files are in this archive" the option "-t"?

Principle of least surprise and all that.

Re: FFmpeg 8.0

#89

Post by mrguyorama »

Dwedit wrote: post #55

Has anyone made a good GUI frontend for accessing the various features of FFMPEG? Sometimes you just want to remux a video without doing any transcoding, or join several video and audio streams together (same codecs).

Shotcut is an open source Video production toolkit that is basically just a really nice interface for generating ffmpeg commands.

https://www.shotcut.org/

Re: FFmpeg 8.0

#90

Post by TiredOfLife »

Dwedit wrote: post #55

Has anyone made a good GUI frontend for accessing the various features of FFMPEG? Sometimes you just want to remux a video without doing any transcoding, or join several video and audio streams together (same codecs).

ChatGPT and other llms
Post reply on HN