←back to thread

FFmpeg 8.0

(ffmpeg.org)
985 points gyan | 3 comments | | HN request time: 0s | source
Show context
pmarreck ◴[] No.44985875[source]
Impressed anytime I have to use it (even if I have to study its man page again or use an LLM to construct the right incantation or use a GUI that just builds the incantation based on visual options). Becoming an indispensable transcoding multitool.

I think building some processing off of Vulkan 1.3 was the right move. (Aside, I also just noticed yesterday that Asahi Linux on Mac supports that standard as well.)

replies(3): >>44985906 #>>44986225 #>>44986323 #
Culonavirus ◴[] No.44985906[source]
> incantation

FFmpeg arguments, the original prompt engineering

replies(4): >>44985969 #>>44985984 #>>44986587 #>>44987357 #
Keyframe ◴[] No.44985969[source]
with gemini-cli and claude-cli you can now prompt while it prompts ffmpeg, and it does work.
replies(3): >>44986076 #>>44986346 #>>44986872 #
1. conradev ◴[] No.44986346[source]
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!
replies(2): >>44986808 #>>44998506 #
2. turnsout ◴[] No.44986808[source]
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.
3. lukeschlather ◴[] No.44998506[source]
It's funny because GPU stuff like what this article is about is where the LLMs totally fall apart. I can make any LLM produce volumes hallucinations at the drop of a hat by asking it how to construct ffmpeg commands that use hardware acceleration.