FFmpeg 3.0 released

At Jumpshare, we use FFmpeg for screen recording. We noticed that the previous version of FFmpeg was not DPI aware. So we went ahead and fixed it. Now FFmpeg will show correct mouse location in hdpi screens. Unfortunately, it seems FFmpeg 3.0 does not ship with this fix. Nevertheless, we&#x27;re happy to contribute to this open source project.<p>Here&#x27;s the fix if anyone is interested: <a href="https:&#x2F;&#x2F;github.com&#x2F;FFmpeg&#x2F;FFmpeg&#x2F;commit&#x2F;00c73c475e3d2d7049eed73ea956f6798365b36a" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;FFmpeg&#x2F;FFmpeg&#x2F;commit&#x2F;00c73c475e3d2d7049ee...</a>

This screams for proper release notes. The official ones are pretty light (<a href="http:&#x2F;&#x2F;git.videolan.org&#x2F;gitweb.cgi&#x2F;ffmpeg.git&#x2F;?p=ffmpeg.git;a=blob;f=RELEASE_NOTES;h=861dc04a1316c8333cc49e9231fd4a6ffabe8282;hb=c40983a6f631d22fede713d535bb9c31d5c9740c" rel="nofollow">http:&#x2F;&#x2F;git.videolan.org&#x2F;gitweb.cgi&#x2F;ffmpeg.git&#x2F;?p=ffmpeg.git;...</a> ), and refer to the Changelog (<a href="http:&#x2F;&#x2F;git.videolan.org&#x2F;gitweb.cgi&#x2F;ffmpeg.git&#x2F;?p=ffmpeg.git;a=blob;f=Changelog;h=2e1cd36f5fe9cce3880697ddfe3079c0b1654473;hb=c40983a6f631d22fede713d535bb9c31d5c9740c" rel="nofollow">http:&#x2F;&#x2F;git.videolan.org&#x2F;gitweb.cgi&#x2F;ffmpeg.git&#x2F;?p=ffmpeg.git;...</a> ) which is quite terse. Phoronix did some reformatting of the changelog, it&#x27;s a bit easier to read:<p><a href="http:&#x2F;&#x2F;www.phoronix.com&#x2F;scan.php?page=news_item&amp;px=FFmpeg-3.0-Released" rel="nofollow">http:&#x2F;&#x2F;www.phoronix.com&#x2F;scan.php?page=news_item&amp;px=FFmpeg-3....</a><p>But honestly this type of stuff should be done by the project before any release.

Thanks to all the FFmpeg contributors! Fantastic piece of software.<p>On a project I was recently on recently we started hitting the per-region concurrent transcode limits on Amazon&#x27;s Elastic Transcoder. [1]<p>Instead of sharding over pipelines or accounts we set up a pipeline with FFMPEG + Lambda functions and it performed fantastically (within the free tier even).<p>It was incredibly simple to write the functions and has given that project a lot more freedom; with the caveat that the any single task you undertake should occur within the timeout window (currently 5 minutes). Having said that, it&#x27;s also straight forward to split the process into steps and have multiple lambda jobs to make the flow more of a pipeline.<p>[1] <a href="http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;elastictranscoder&#x2F;latest&#x2F;developerguide&#x2F;limits.html" rel="nofollow">http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;elastictranscoder&#x2F;latest&#x2F;develope...</a>

I know this has been a constant question (in the lines of &quot;Should I go Python 2.x or 3.x?&quot;)...but I feel the need to ask it again on the event of a major point release for ffmpeg...but how are things, pragmatically-speaking, in terms of libav vs ffmpeg? I had thought that libav was the new way a few years ago and have more or less been using it on OS X...but now I see that Debian recently switched back to ffmpeg [1]...What are the use-cases for sticking with libav these days? I&#x27;m almost sure I started using libav because it was promoted as a concerted effort to create a better API. But by some accounts, ffmpeg has been incorporating libav&#x27;s changes...and I honestly don&#x27;t use libav or ffmpeg enough, directly, to really benefit from a better API. And installing both, I believe, has led to a few subtle errors when using libraries that wrap around either.<p>So, any reason for the casual graphics developer to install libav?<p>[1] <a href="https:&#x2F;&#x2F;lwn.net&#x2F;Articles&#x2F;650816&#x2F;" rel="nofollow">https:&#x2F;&#x2F;lwn.net&#x2F;Articles&#x2F;650816&#x2F;</a><p>edit: Oh I see that VLC at some point switched to libav. That was likely a deciding factor when I last did my nominal research into ffmpeg vs libav:<p><a href="http:&#x2F;&#x2F;git.videolan.org&#x2F;?p=vlc.git;a=blob;f=contrib&#x2F;src&#x2F;ffmpeg&#x2F;rules.mak;h=85fea9c43e5b7e46ab9a2902e7279b9e0674acc0;hb=HEAD" rel="nofollow">http:&#x2F;&#x2F;git.videolan.org&#x2F;?p=vlc.git;a=blob;f=contrib&#x2F;src&#x2F;ffmp...</a>

Among new things:<p>- Common Encryption (CENC) MP4 encoding and decoding support.<p>- New filters: extrastereo, OCR, alimiter, stereowiden, stereotools, rubberband, tremolo, agate, chromakey, maskedmerge, displace, selectivecolor, zscale, shuffleframes, vibrato, realtime, compensationdelay, acompressor, apulsator, sidechaingate, aemphasis, virtual binaural acoustics, showspectrumpic, afftfilt, convolution, swaprect, and others.<p>- New decoding: DXV, Screenpresso SPV1, ADPCM PSX, SDX2 DPCM, innoHeim&#x2F;Rsupport Screen Capture Codec, ADPCM AICA, XMA1 &amp; XMA2, and Cineform HD.<p>- New muxing: Chromaprint fingerprinting, WVE demuxer, Interplay ACM, and IVR demuxer.<p>- Dynamic volume control for ffplay.<p>- Native AAC encoder improvements.<p>- Zero-copy Intel QSV transcoding.<p>- Microsoft DXVA2-accelerated VP9 decoding on Windows.<p>- VA-API VP9 hardware acceleration.<p>- Automatic bitstream filtering.

I use ffmpeg for housekeeping stuff like converting videos from one format to the other, and cutting clips - mostly from the command line. Can some advanced users share if there is anything to look forward to with this release? Better performance? Some convenience features? Thank you in advance

I love FFmpeg. I first used it to help with uploading 700 audio files to youtube years ago. Of course youtube is video only, so I used ffmpeg to reencode the audio with an image slideshow as video and then uploaded the &quot;videos&quot; using some web scrapping with perl.<p>More recently I have been downloading programming framework tutorials (android development, django, angular,ect) from youtube to my plex media server. I then go back with ffmpeg to reencode the vids to playback 50% faster. So now I can blast through tutorials on my TV while I eat lunch (I work from home mostly)<p>Edit: The release mentioned hardware acceleration improvements. I never knew ffmpeg even supported any HW accel: <a href="https:&#x2F;&#x2F;trac.ffmpeg.org&#x2F;wiki&#x2F;HWAccelIntro" rel="nofollow">https:&#x2F;&#x2F;trac.ffmpeg.org&#x2F;wiki&#x2F;HWAccelIntro</a>

If <i>ffplay</i> supported hardware decoding, it&#x27;d be the perfect player. You could not make a more minimal player. It does not, and it doesn&#x27;t seem to be high on the priority list, rather in last position perhaps.<p><a href="https:&#x2F;&#x2F;trac.ffmpeg.org&#x2F;ticket&#x2F;3359" rel="nofollow">https:&#x2F;&#x2F;trac.ffmpeg.org&#x2F;ticket&#x2F;3359</a>

Awesome! Hoping for quick updates to the OpenBSD and FreeBSD ports.

Thanks for all the work on FFmpeg!

Is the built-in aac encoder better or as good as fdk-aac? I&#x27;ve been using fdk-aac because it gives lower bitrates and better&#x2F;same sound.

Last version was named Feynman. This 3.0 is released on 15th feb - Death of Feynman.<p>Coincidence?

Why the heck do they make it so hard to figure out what&#x27;s in the release?