Multimedia Powerhouse FFmpeg Hits 3.0
An anonymous reader writes: The milestone release FFmpeg 3.0 "Einstein" has been unleashed. For those who need a reminder, FFmpeg comprises several libraries and command-line tools (the main command-line tool being "ffmpeg") that encode, decode, transcode, and stream audio/visual data, etc. FFmpeg supports a multitude of codecs, filters, and container formats too numerous to mention here. FFmpeg is used by MPlayer, VLC, HandBrake, Chrome, and many other projects. Changes from 2.x to 3.0 include: a much better native AAC encoder, better hardware acceleration, and some API/ABI breakage. See this, this, this, this, and the changelog for much better descriptions of the improvements.
It's not in the default repos on Mint, I learned this was replaced by libav. I used it to crop some videos for use in OpenShot* by commandline and the parameters seem compatible with FFmpeg. Any reason for the fork? I'm currently reading this to suss it out, hopefully it's good in the long run, and at least I can do what I need to do in the meantime.
*(love it for editing home videos but lacking soundtrack support, added that by commandline too w/libav)
Twinstiq, game news
I wonder how much sooner we would have gotten this release if not for all of the HEVC patent/licensing fee shenanigans of late?
My initial reaction:
That's nice, but does it have a stable ABI yet?
Welp.
How fast can ffmpeg do encoding on modern hardware? Is there functional GPU support to get high compression rates in real time?
You're not right :)
I added a link to the news at the ffmpeg.org site re: the actual release, might have fixed some punctuation or some other trivial stuff, but the submission that became this post came in pretty much as-is.
Apologies for not noting this release a few days sooner, too; the things that FFmpeg make possible are deeply appreciated by naive end-users like me.
timothy
jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
Like stealing from a Girl Scout
https://trac.ffmpeg.org/query?...
On a lot of motherboards you can get around it by enabling both PCI-E and iGPU in BIOS or EFI/UEFI, and then in your OS you add another, virtual, display that is linked to the Intel GPU. Even works with some of the cheaper Sandy Bridge era mobos(and pretty much all the expensive ones from the time) running Windows 7.