←back to thread

FFmpeg 8.0

(ffmpeg.org)
985 points gyan | 1 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 #
jeanlucas ◴[] No.44985984[source]
nope, that would be handling tar balls

ffmpeg right after

replies(4): >>44986062 #>>44986260 #>>44986660 #>>44987094 #
fullstop ◴[] No.44987094{3}[source]
I have so much of tar memorized. cpio is super funky to me, though.
replies(1): >>44998366 #
fuzztester ◴[] No.44998366{4}[source]
cpio is not that hard.

A common use case is:

  $ cpio -pdumv args 
See:

  $ man cpio 
and here is an example from its Wikipedia page, under the "Operation and archive format" section, under the Copy subsection:

Copy

Cpio supports a third type of operation which copies files. It is initiated with the pass-through option flag (p). This mode combines the copy-out and copy-in steps without actually creating any file archive. In this mode, cpio reads path names on standard input like the copy-out operation, but instead of creating an archive, it recreates the directories and files at a different location in the file system, as specified by the path given as a command line argument.

This example copies the directory tree starting at the current directory to another path new-path in the file system, preserving files modification times (flag m), creating directories as needed (d), replacing any existing files unconditionally (u), while producing a progress listing on standard output (v):

$ find . -depth -print | cpio -p -dumv new-path

replies(1): >>45000344 #
1. fullstop ◴[] No.45000344{5}[source]
I think that it's the fact that it requires a pipe to work and that you add files by feeding stdin that throw me for a loop.

I also use it very infrequently compared to tar -- mostly in conjunction with swupdate. I've also run into file size limits, but that's not really a function of the command line interface to the tool.