FFmpeg 3.0 released

#1

Post by vivagn » Mon, Feb 15, 2016, 12:42 PM UTC

FFmpeg 3.0 released
ffmpeg.org

Re: FFmpeg 3.0 released

#2

Post by imaginenore » Mon, Feb 15, 2016, 12:53 PM UTC

Among new things:

- Common Encryption (CENC) MP4 encoding and decoding support.

- 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.

- New decoding: DXV, Screenpresso SPV1, ADPCM PSX, SDX2 DPCM, innoHeim/Rsupport Screen Capture Codec, ADPCM AICA, XMA1 & XMA2, and Cineform HD.

- New muxing: Chromaprint fingerprinting, WVE demuxer, Interplay ACM, and IVR demuxer.

- Dynamic volume control for ffplay.

- Native AAC encoder improvements.

- Zero-copy Intel QSV transcoding.

- Microsoft DXVA2-accelerated VP9 decoding on Windows.

- VA-API VP9 hardware acceleration.

- Automatic bitstream filtering.

Re: FFmpeg 3.0 released

#3

Post by Aissen » Mon, Feb 15, 2016, 12:53 PM UTC

This screams for proper release notes. The official ones are pretty light (http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;... ), and refer to the Changelog (http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;... ) which is quite terse. Phoronix did some reformatting of the changelog, it's a bit easier to read:

http://www.phoronix.com/scan.php?page=news_item&px=FFmpeg-3....

But honestly this type of stuff should be done by the project before any release.

Re: FFmpeg 3.0 released

#4

Post by danso » Mon, Feb 15, 2016, 12:59 PM UTC

I know this has been a constant question (in the lines of "Should I go Python 2.x or 3.x?")...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'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's changes...and I honestly don'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.

So, any reason for the casual graphics developer to install libav?

[1] https://lwn.net/Articles/650816/

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:

http://git.videolan.org/?p=vlc.git;a=blob;f=contrib/src/ffmp...

Re: FFmpeg 3.0 released

#5

Post by djm_ » Mon, Feb 15, 2016, 12:59 PM UTC

Thanks to all the FFmpeg contributors! Fantastic piece of software.

On a project I was recently on recently we started hitting the per-region concurrent transcode limits on Amazon's Elastic Transcoder. [1]

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).

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's also straight forward to split the process into steps and have multiple lambda jobs to make the flow more of a pipeline.

[1] http://docs.aws.amazon.com/elastictranscoder/latest/develope...

Re: FFmpeg 3.0 released

#6

Post by 0x0 » Mon, Feb 15, 2016, 1:02 PM UTC

danso wrote: post #4

I know this has been a constant question (in the lines of "Should I go Python 2.x or 3.x?")...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].…

It really does seem like the original ffmpeg is the way to go these days.

Re: FFmpeg 3.0 released

#7

Post by _kyran » Mon, Feb 15, 2016, 1:05 PM UTC

Thanks for all the work on FFmpeg!

Re: FFmpeg 3.0 released

#8

Post by douglasfshearer » Mon, Feb 15, 2016, 1:07 PM UTC

djm_ wrote: post #5

Thanks to all the FFmpeg contributors! Fantastic piece of software. On a project I was recently on recently we started hitting the per-region concurrent transcode limits on Amazon's Elastic Transcoder. [1] 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). It was incredibly simple to write the functions and has…

How did the costs compare with this setup?

I work on a project where ET isn't flexible enough (MPEG-DASH), and wondered whether Lambda would make for a good alternative to EC2 + SQS + Scaling Groups.

Re: FFmpeg 3.0 released

#9

Post by gerjomarty » Mon, Feb 15, 2016, 1:07 PM UTC

danso wrote: post #4

I know this has been a constant question (in the lines of "Should I go Python 2.x or 3.x?")...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].…

mpv has a nice (and opinionated, which is good) guide for the things that matter to them: https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav

Re: FFmpeg 3.0 released

#10

Post by bru » Mon, Feb 15, 2016, 1:09 PM UTC

danso wrote: post #4

I know this has been a constant question (in the lines of "Should I go Python 2.x or 3.x?")...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].…

> libav [...] promoted as a concerted effort to create a better API

True, but that was biased and unfair. Some developers leveraged their Debian influence to get Debian to switch from ffmpeg to libav, but the technical merits were debatable. In the end, they came back to ffmpeg.

This is mostly a political issue. Software-wise AFAIK ffmpeg has been integrating many changes from libav but the opposite is not true, making IMHO ffmpeg the right choice.

Good article (2012) with in-depth history: http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html

More recent (2015) short take on the matter, seems pretty biased though: https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav

Wikipedia entry: https://en.wikipedia.org/wiki/Libav#Fork_from_FFmpeg

The github link is on mpv wiki. mpv is a descendant of mplayer and mplayer2 (the latter being mostly dead). IMHO mpv is the best media player for any OS (lightweight, snappy, reads everything, better options and CLI than mplayer*, etc.).