←back to thread

FFmpeg 8.0

(ffmpeg.org)
985 points gyan | 2 comments | | HN request time: 0.453s | 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 #
jeanlucas ◴[] No.44985984[source]
nope, that would be handling tar balls

ffmpeg right after

replies(4): >>44986062 #>>44986260 #>>44986660 #>>44987094 #
porridgeraisin ◴[] No.44986062[source]
Personally I never understood the problem with tar balls.

The only options you ever need are tar -x, tar -c (x for extract and c for create). tar -l if you wanna list, l for list.

That's really it, -v for verbose just like every other tool if you wish.

Examples:

  tar -c project | gzip > backup.tar.gz
  cat backup.tar.gz | gunzip | tar -l
  cat backup.tar.gz | gunzip | tar -x
You never need anything else for the 99% case.
replies(7): >>44986123 #>>44986158 #>>44986160 #>>44986179 #>>44986359 #>>44986655 #>>44992428 #
tombert ◴[] No.44986179[source]
Yeah I never really understood why people complain about tar; 99% of what you need from it is just `tar -xvf blah.tar.gz`.
replies(2): >>44986239 #>>44986693 #
1. aidenn0 ◴[] No.44986239[source]
You for got the -z (or -a with a recent gnutar).
replies(1): >>44986300 #
2. adastra22 ◴[] No.44986300[source]
It’s no longer needed. You can leave it out and it auto-detects the file format.