Vdx – An intuitive CLI for processing video, powered by FFmpeg

Re:Vdx – An intuitive CLI for processing video, powered by F... by technoplato on Saturday October 24, 2020 @08:29PM (#24882945)

I anticipate some much more savvy than myself saying this wrapper is unnecessary as you can do all of this “easily” with ffmpeg. I welcome tools like this that have a more common user in mind, evidenced immediately in the beginning of the README with common use cases.

Ffmpegs documentation on the other hand forces me to feel as though it’s normal to assume knowledge about a point in a video and what it means if my encoders are different from input to output.

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by timc3 on Sunday October 25, 2020 @12:47AM (#24883903)

Even if what the abstraction is doing is not really the best way of doing things?

For example not the best - re-encoding video or audio tracks when it could just copy them, picking the defaults when their is a better quality option?

Video and audio processing is one of things that if you want good results with wide flexibility you have to learn it and also try things out.

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by jahlove on Saturday October 24, 2020 @08:52PM (#24883039)

I consider myself pretty savvy and have used ffmpeg many times over the years. I struggle through it like hell every time. I'd gladly use something like this.

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by handol on Sunday October 25, 2020 @12:06AM (#24883758)

> Ffmpegs documentation

    ffplay --help

8826 lines

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by mkl on Sunday October 25, 2020 @07:19AM (#24885433)

That's ffplay.

  $ man ffmpeg-all 2> /dev/null | wc -l
  33160

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by luckman212 on Sunday October 25, 2020 @09:21PM (#24891896)

why are you redirecting stderr? does `man ffmpeg` produce error output on your system?

anyway, on my system (macOS, ffmpeg 4.3.1 from Homebrew) the situation is even more dire:

    $ man ffmpeg-all | wc -l
    38738

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by mkl on Monday October 26, 2020 @03:56AM (#24893767)

On my system (Kubuntu 20.04) man/troff produces errors when its output is redirected:

  $ man ffmpeg-all | wc -l
  troff: <standard input>:6148: warning [p 42, 3.5i, div 'an-div', 0.0i]: can't break line
  troff: <standard input>:6150: warning [p 42, 3.7i, div 'an-div', 0.0i]: can't break line
  troff: <standard input>:11396: warning [p 68, 8.7i]: can't break line
  troff: <standard input>:11398: warning [p 68, 9.2i]: can't break line
  troff: <standard input>:13562: warning [p 79, 6.0i]: can't break line
  troff: <standard input>:13564: warning [p 79, 6.5i]: can't break line
  troff: <standard input>:26366: warning [p 132, 17.2i]: can't break line
  troff: <standard input>:38313: warning [p 174, 27.5i]: can't break line
  33160

No idea what it means.

[ Parent | on HN ]

Re:Vdx – An intuitive CLI for processing video, powered by F... by rezonant on Sunday October 25, 2020 @04:01AM (#24884613)

oh sweet summer child

[ Parent | on HN ]