Live data from Hacker News

FFmpeg 4.4

ffmpeg.org

11–20 of 135 posts

Re: FFmpeg 4.4

#15
post #3

I am excited for AV1 stuff, included in the highlights: SVT-AV1 encoding and AV1 VAAPI decoding.

Sadly we are still incredibly lacking in encoding. It's been years since hevc encoding was included in consumer graphics cards and embeddable devices. For one reason or another vendors just haven't done av1 on the hardware level.

Re: FFmpeg 4.4

#17
post #3

I am excited for AV1 stuff, included in the highlights: SVT-AV1 encoding and AV1 VAAPI decoding.

For a typical 1080p "linux iso" what filesize difference will there be between x265 and av1?

I understand that you are probably trying to be funny, but just to be clear, linux iso's are not videos and therefore can't be compressed with a video codec.

Assuming that you actually meant video content, I think your question may be a bit misguided on the nuances and goals of video encoding. Video encoding can be both lossy and lossless. Lossless video encoding isn't particularly interesting in most cases, but I do believe that HEVC (H.265) will usually come out slightly smaller. However anything to do with encoding will always vary based on the actual source content. So partial answer to your question would probably be x265, but it depends. Based on the source you could construct theoretical content that could be better tuned to one or the other's encoding strengths.

Where it gets interesting is in lossy encoding. With lossy encoding you seek to retain visual acuity to a certain standard while minimizing size and/or processing requirements. Both codecs do an excellent job at removing the right amount of information to effectively fool the human observer. With lossy encoding there isn't really a filesize difference, as you tune your filesize to whatever you want to given your source and your desired output constraints. The big feature of av1 is that it is open and unencumbered by patents+royalties and will hopefully therefore make it THE industry standard in the coming years. It's openness also makes it more likely to eventually be ubiquitous as it should be implementable and playable on most new video platforms and hardware, and hopefully the mythical one format that just works everywhere.

Re: FFmpeg 4.4

#18
post #3

I am excited for AV1 stuff, included in the highlights: SVT-AV1 encoding and AV1 VAAPI decoding.

Sadly we are still incredibly lacking in encoding. It's been years since hevc encoding was included in consumer graphics cards and embeddable devices. For one reason or another vendors just haven't done av1 on the hardware level.

Silicon design cycles are slow. 2 years wouldn't be so surprising for most products.

Re: FFmpeg 4.4

#20

I think everyone was a txt file on their computer filled with FFmpeg commands. Care to share yours?

Here's one I wrote a blog post[0] about on how to merge two audio tracks of a video into one track without re-encoding the video:

    ffmpeg -i 'input.mkv' -filter_complex '[0:a:1]volume=0.1[l];[0:a:0][l]amerge=inputs=2[a]' -map '0:v:0' -map '[a]' -c:v copy -c:a libmp3lame -q:a 3 -ac 2 'output.mp4'
[0] https://blog.nytsoi.net/2017/12/31/ffmpeg-combining-audio-tr...
Post reply on HN