Live data from Hacker News

Ffmprovisr – Making FFmpeg Easier

amiaopensource.github.io

101–106 of 106 posts

Re: Ffmprovisr – Making FFmpeg Easier

#101

Earlier quoted context omitted.

Perhaps it's a form of hipster irony, since by and large all GIF sites and social media sites now convert source GIFs to mp4.

There are still plenty of contexts where you can embed images but not videos (or at least not with automatic looping playback) - forums, github README.md, other markdown-based comment/post systems. Gif compression limitations also encourage you to cut down to the essential parts - too many videos waste the viewers time with delays and irrelevant bits.

> irrelevant bits

Hmm.

Re: Ffmprovisr – Making FFmpeg Easier

#102

This is a great idea! Trying to get FFmpeg to do what I want it to do is always daunting. ChatGPT has been helpful, but not perfect. Thanks for this :)

Chatgpt made lot of CLI tool args/options easy to use. I always had a hard time remembering OpenSSL options and arguments. Now I just use gpt

Re: Ffmprovisr – Making FFmpeg Easier

#103

A bit off topic, IMO ffmpeg is one of the best software ever written. Fabian Fabrice (ff) is one talented engineer and people such as him are a gift to the FOSS community. I used to work in a ~2 bil unicorn in which a big part of the products we worked on relied on ffmpeg.

>Fabian Fabrice *Fabrice Bellard. Also creator of QEMU, TCC, QuickJS, and others.

Yeah, the etymology suggested by the top-level comment is completely wrong. Wikipedia says

> The name of the project is inspired by the MPEG video standards group, together with "FF" for "fast forward"

Corresponding source (Fabrice Bellard himself): https://ffmpeg.org/pipermail/ffmpeg-devel/2006-February/0103...

Re: Ffmprovisr – Making FFmpeg Easier

#104
post #79

I was looking for a ffmpeg UI recently and came across Shutter Encoder. It's open source, mac/windows, very good software. I've finally started compressing my 15 year, 300GB personal video collection.. https://www.shutterencoder.com/ I'm compressing everything using, H.265 and videos are shrinking to sometimes 1/10th the size.. Is there who would give me reasons why I would not want to do this? I've read that it take…

One reason for me to still pick h.264 is many aging (or budget?) hardware doesn't have hardware decoding for h.265.

Also it's just easier on my homelab to use Plex without having to transcode

Re: Ffmprovisr – Making FFmpeg Easier

#105

Earlier quoted context omitted.

The second link's clipping command is not ideal in my experience. For some god known reason, ffmpeg behaves differently depending on whether you put the -ss and -t/-to flags before or after the -i flag. And for me, before worked better. It's also an issue in the original post.

Effectively, placing ss before the input filename seeks the file (the container?) without decoding it. Placing it after will decode the streams while skipping to the point you specify. Seeking the container is usually much faster than decoding and then throwing away what you don't need, but it has fatal flaw: most videos use p-frames and thus require you to decode the frames before it. So, say you want to skip to 60…

That trick (-ss -i -ss) should not be necessary by default (unless you use -noaccurate_seek) according to current documentation. But I haven't verified it.

https://ffmpeg.org/ffmpeg-all.html#toc-Main-options

  -ss position (input/output)

     When used as an input option (before -i), seeks in this input file to 
 position. Note that in most formats it is not possible to seek exactly, so 
 ffmpeg will seek to the closest seek point before position. When transcoding 
 and -accurate_seek is enabled (the default), this extra segment between the 
 seek point and position will be decoded and discarded. When doing stream copy 
 or when -noaccurate_seek is used, it will be preserved.
 
    When used as an output option (before an output url), decodes but discards 
 input until the timestamps reach position.

Re: Ffmprovisr – Making FFmpeg Easier

#106

A bit off topic, IMO ffmpeg is one of the best software ever written. Fabian Fabrice (ff) is one talented engineer and people such as him are a gift to the FOSS community. I used to work in a ~2 bil unicorn in which a big part of the products we worked on relied on ffmpeg.

I love ffmpeg, but its performance has got to improve on ARM!
Post reply on HN