10 ms·

FFmpeg 3.0 released

454 points by vivagn 11y ago

imaginenore 11y ago
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.
- JimDabell 11y ago
  Chromakey was introduced in 2.8.x.
  - ericmo 11y ago
    It's in the official changelog as a new feature: http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;a=blob;f=Changelog;h=2e1cd36f5fe9cce3880697ddfe3079c0b1654473;hb=c40983a6f631d22fede713d535bb9c31d5c9740c http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;...
    - JimDabell 11y ago
      Apologies, you're correct. I was thinking of the colorkey filter: https://ffmpeg.org/ffmpeg-filters.html#colorkey https://ffmpeg.org/ffmpeg-filters.html#colorkey This was introduced in 2.8 and does the same thing as chromakey, except in RGB rather than YUV.
- Veratyr 11y ago
  Is Intel QSV available on Mac/Linux yet by any chance?
  - tmm1 11y ago
    There's a patchset for this feature being discussed on the mailing list: http://ffmpeg.org/pipermail/ffmpeg-devel/2016-February/189533.html http://ffmpeg.org/pipermail/ffmpeg-devel/2016-February/18953...
  - willkelleher 11y ago
    FFmpeg on Linux supports QSV either through the h264_qsv encoder or through some soon-to-be-merged va-api changes. On Mac I think you need to use the VideoToolbox API to access the GPU codec, and there is support for this in FFmpeg as well, but I haven't used it myself.
Aissen 11y ago
This screams for proper release notes. The official ones are pretty light (http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;a=blob;f=RELEASE_NOTES;h=861dc04a1316c8333cc49e9231fd4a6ffabe8282;hb=c40983a6f631d22fede713d535bb9c31d5c9740c 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;a=blob;f=Changelog;h=2e1cd36f5fe9cce3880697ddfe3079c0b1654473;hb=c40983a6f631d22fede713d535bb9c31d5c9740c 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.0-Released 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.
- ux 11y ago
  Yeah, sorry about that. It was indeed done in a hurry. I think the main highlights are: - The API/ABI break (implied by the major bump) - The many improvements in the native AAC encoder making it the recommended one (libaacplus and libvo-aacenc are removed) - A ton of filters were added - Many ASM optimizations that weren't mentioned in the Changelog (it will take a while to make highlights on those, I don't remember them) Hopefully a proper news will be posted soon. Sorry again.
  - cm2187 11y ago
    Any plan to support QuickSync?
    - JoshTriplett 11y ago
      Looking at the release notes, I see several mentions of QSV support.
      - cm2187 11y ago
        I think earlier versions had an x264 module supporting QSV but which was never included in the official windows build. I wonder if that changed.
danso 11y ago
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/ 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/ffmpeg/rules.mak;h=85fea9c43e5b7e46ab9a2902e7279b9e0674acc0;hb=HEAD http://git.videolan.org/?p=vlc.git;a=blob;f=contrib/src/ffmp...
- 0x0 11y ago
  It really does seem like the original ffmpeg is the way to go these days.
- gerjomarty 11y ago
  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 https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav
  - diimdeep 11y ago
    Thats nice one: - Libav - Pretends FFmpeg doesn't exist, though sometimes merges individual patches. - FFmpeg - Pretends Libav doesn't exist, but merges absolutely everything it does. Sometimes with consequences; for example there are now 2 prores decoders, and 3 prores encoders.
- 11y ago
djm_ 11y ago
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/developerguide/limits.html http://docs.aws.amazon.com/elastictranscoder/latest/develope...
- douglasfshearer 11y ago
  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.
  - bagels 11y ago
    EC2 + SQS + ffmpeg is 1/5 the cost of elastic transcoding for me, and that's not even using all the ec2 capacity.
- Exuma 11y ago
  Wow... I would truly appreciate if you could share a bit more about your specific setup. I found myself working on a new project yesterday that I was really really excited about, until I saw the costs to transcode video. How does doing all this in-house compare price wise (say, per minute), compared to using elastic transcoder? Edit: The ultimate lowest cost I can find is $0.0125-0.015
  - djm_ 11y ago
    I wish I could edit my parent comment but alas. The key point was missed: we were dealing with very short, small videos. If you are dealing with longer or large videos, it's simply not feasible on Lambda. As for costings, unfortunately I cannot retrieve them as this project was mid last year and I've since moved on to other clients. They can be calculated though with a few short tests I'm sure.
_kyran 11y ago
Thanks for all the work on FFmpeg!
hiphopyo 11y ago
Awesome! Hoping for quick updates to the OpenBSD and FreeBSD ports.
nakodari 11y ago
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're happy to contribute to this open source project. Here's the fix if anyone is interested: https://github.com/FFmpeg/FFmpeg/commit/00c73c475e3d2d7049eed73ea956f6798365b36a https://github.com/FFmpeg/FFmpeg/commit/00c73c475e3d2d7049ee...
- ux 11y ago
  You can backport it easily, and it will be present in 3.0.1. Ask on IRC or the dev ML.
- exadeci 11y ago
  First time that I hear about your service and it seems like a copy of Dropbox but with way more features. (the interface) Just a suggestion: Jumpshare Plus link should either be at the top or renamed "Pricing" because you don't see it directly and the usual ctrl+f of pricing gives nothing. Plus your pricing is nothing to be ashamed of :)
  - nakodari 11y ago
    Hi, thank you for the feedback and suggestions. We will make sure to include the pricing in the new homepage we're working on. :) By the way, we're more about quick sharing than syncing. We will be overhauling our homepage to make that clearer. Here's the app if you're using a Mac (Windows app is coming soon): https://itunes.apple.com/us/app/jumpshare/id889922906 https://itunes.apple.com/us/app/jumpshare/id889922906
    - alphapapa 11y ago
      Syncing (and its related attributes of backup and redundancy) are more useful, and Dropbox facilitates both that and sharing. So what's your angle? :)
fareesh 11y ago
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
- krullie 11y ago
  From the list given by @imaginenore the major one for me is CineformHD support. We work on a lot of VR stuff and there are quite some GoPro users out there that generate material in this codec. Not having to transcode to an intermediate is nice. Also hardware acceleration is always good to have.
  - theoh 11y ago
    FYI, the phrase "quite some users" is not uncommon among (continental european?) non-native speakers of English, but it's not correct. "In the British National Corpus, for example, most examples of quite some are "quite some time", others are "quite some distance". If you replace "quite some" with "a considerable", the meaning should be clear. If the sentence does not make sense when you do that, it's likely that "quite some" is not being used properly." From http://forum.wordreference.com/threads/quite-some.1011589/ http://forum.wordreference.com/threads/quite-some.1011589/
    - krullie 11y ago
      Thanks theoh. Dutchie here. Always nice to learn something new about a foreign language.
obiefernandez 11y ago
Why the heck do they make it so hard to figure out what's in the release?
- slhck 11y ago
  There will be a proper news release on the homepage soon, I suppose.
esaym 11y ago
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 "videos" using some web scrapping with perl. 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) Edit: The release mentioned hardware acceleration improvements. I never knew ffmpeg even supported any HW accel: https://trac.ffmpeg.org/wiki/HWAccelIntro https://trac.ffmpeg.org/wiki/HWAccelIntro
- GhotiFish 11y ago
  mplayer and mpv and vlc and most native players can speed videos up on the fly, tempo-shifting or pitch shifting the audio based on preferences. Usually the [ and ] keys.
  - esaym 11y ago
    Yes, those are players. But I don't want to sit in front of my computer or cell phone while on lunch break, I want to sit on the couch in front of a TV. Natively, neither plex or roku allows videos to be speed up, so they have to be reencoded at a different speed.
pdknsk 11y ago
If ffplay supported hardware decoding, it'd be the perfect player. You could not make a more minimal player. It does not, and it doesn't seem to be high on the priority list, rather in last position perhaps. https://trac.ffmpeg.org/ticket/3359 https://trac.ffmpeg.org/ticket/3359
- cm3 11y ago
  Have you tried mpv?
- deleted 11y ago
  [deleted]
mkagenius 11y ago
Last version was named Feynman. This 3.0 is released on 15th feb - Death of Feynman. Coincidence?
cm3 11y ago
Is the built-in aac encoder better or as good as fdk-aac? I've been using fdk-aac because it gives lower bitrates and better/same sound.
- slhck 11y ago
  libfdk historically always was a bit better and supports VBR properly. See also: https://trac.ffmpeg.org/wiki/Encode/AAC https://trac.ffmpeg.org/wiki/Encode/AAC
  - cm3 11y ago
    That's why I've been using it. Is the improved built-in encoder on par now?
    - slhck 11y ago
      I haven't done or seen any tests, but I suppose if you require VBR and/or HE-AAC support, go for libfdk, otherwise for bitrates ~128k or higher, use the internal AAC encoder.
- lozf 11y ago
  Official docs say that it's competitive at 128kbps, but these[0] listening test from Kamendo2 (who's very experienced in ABX listening tests of lossy codecs) suggest fdk-aac still has the edge, as well as handling VBR and the HE-AAC / HE-AACv2 profiles properly. [0]: https://hydrogenaud.io/index.php/topic,111085.0.html https://hydrogenaud.io/index.php/topic,111085.0.html
- alphapapa 11y ago
  On a related note, how do those options compare to Vorbis and Opus, technically and legally? Is there a compelling reason to use AAC over those choices?

454 points by vivagn 11y ago

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.

JimDabell 11y ago
Chromakey was introduced in 2.8.x.
- ericmo 11y ago
  It's in the official changelog as a new feature: http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;a=blob;f=Changelog;h=2e1cd36f5fe9cce3880697ddfe3079c0b1654473;hb=c40983a6f631d22fede713d535bb9c31d5c9740c http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;...
  - JimDabell 11y ago
    Apologies, you're correct. I was thinking of the colorkey filter: https://ffmpeg.org/ffmpeg-filters.html#colorkey https://ffmpeg.org/ffmpeg-filters.html#colorkey This was introduced in 2.8 and does the same thing as chromakey, except in RGB rather than YUV.
Veratyr 11y ago
Is Intel QSV available on Mac/Linux yet by any chance?
- tmm1 11y ago
  There's a patchset for this feature being discussed on the mailing list: http://ffmpeg.org/pipermail/ffmpeg-devel/2016-February/189533.html http://ffmpeg.org/pipermail/ffmpeg-devel/2016-February/18953...
- willkelleher 11y ago
  FFmpeg on Linux supports QSV either through the h264_qsv encoder or through some soon-to-be-merged va-api changes. On Mac I think you need to use the VideoToolbox API to access the GPU codec, and there is support for this in FFmpeg as well, but I haven't used it myself.

Aissen 11y ago

This screams for proper release notes. The official ones are pretty light (http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;a=blob;f=RELEASE_NOTES;h=861dc04a1316c8333cc49e9231fd4a6ffabe8282;hb=c40983a6f631d22fede713d535bb9c31d5c9740c 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;a=blob;f=Changelog;h=2e1cd36f5fe9cce3880697ddfe3079c0b1654473;hb=c40983a6f631d22fede713d535bb9c31d5c9740c 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.0-Released 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.

ux 11y ago
Yeah, sorry about that. It was indeed done in a hurry. I think the main highlights are: - The API/ABI break (implied by the major bump) - The many improvements in the native AAC encoder making it the recommended one (libaacplus and libvo-aacenc are removed) - A ton of filters were added - Many ASM optimizations that weren't mentioned in the Changelog (it will take a while to make highlights on those, I don't remember them) Hopefully a proper news will be posted soon. Sorry again.
- cm2187 11y ago
  Any plan to support QuickSync?
  - JoshTriplett 11y ago
    Looking at the release notes, I see several mentions of QSV support.
    - cm2187 11y ago
      I think earlier versions had an x264 module supporting QSV but which was never included in the official windows build. I wonder if that changed.

danso 11y ago

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/ 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/ffmpeg/rules.mak;h=85fea9c43e5b7e46ab9a2902e7279b9e0674acc0;hb=HEAD http://git.videolan.org/?p=vlc.git;a=blob;f=contrib/src/ffmp...

0x0 11y ago
It really does seem like the original ffmpeg is the way to go these days.
gerjomarty 11y ago
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 https://github.com/mpv-player/mpv/wiki/FFmpeg-versus-Libav
- diimdeep 11y ago
  Thats nice one: - Libav - Pretends FFmpeg doesn't exist, though sometimes merges individual patches. - FFmpeg - Pretends Libav doesn't exist, but merges absolutely everything it does. Sometimes with consequences; for example there are now 2 prores decoders, and 3 prores encoders.
11y ago

djm_ 11y ago

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/developerguide/limits.html http://docs.aws.amazon.com/elastictranscoder/latest/develope...

douglasfshearer 11y ago
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.
- bagels 11y ago
  EC2 + SQS + ffmpeg is 1/5 the cost of elastic transcoding for me, and that's not even using all the ec2 capacity.
Exuma 11y ago
Wow... I would truly appreciate if you could share a bit more about your specific setup. I found myself working on a new project yesterday that I was really really excited about, until I saw the costs to transcode video. How does doing all this in-house compare price wise (say, per minute), compared to using elastic transcoder? Edit: The ultimate lowest cost I can find is $0.0125-0.015
- djm_ 11y ago
  I wish I could edit my parent comment but alas. The key point was missed: we were dealing with very short, small videos. If you are dealing with longer or large videos, it's simply not feasible on Lambda. As for costings, unfortunately I cannot retrieve them as this project was mid last year and I've since moved on to other clients. They can be calculated though with a few short tests I'm sure.

_kyran 11y ago

Thanks for all the work on FFmpeg!

hiphopyo 11y ago

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

nakodari 11y ago

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're happy to contribute to this open source project. Here's the fix if anyone is interested: https://github.com/FFmpeg/FFmpeg/commit/00c73c475e3d2d7049eed73ea956f6798365b36a https://github.com/FFmpeg/FFmpeg/commit/00c73c475e3d2d7049ee...

ux 11y ago
You can backport it easily, and it will be present in 3.0.1. Ask on IRC or the dev ML.
exadeci 11y ago
First time that I hear about your service and it seems like a copy of Dropbox but with way more features. (the interface) Just a suggestion: Jumpshare Plus link should either be at the top or renamed "Pricing" because you don't see it directly and the usual ctrl+f of pricing gives nothing. Plus your pricing is nothing to be ashamed of :)
- nakodari 11y ago
  Hi, thank you for the feedback and suggestions. We will make sure to include the pricing in the new homepage we're working on. :) By the way, we're more about quick sharing than syncing. We will be overhauling our homepage to make that clearer. Here's the app if you're using a Mac (Windows app is coming soon): https://itunes.apple.com/us/app/jumpshare/id889922906 https://itunes.apple.com/us/app/jumpshare/id889922906
  - alphapapa 11y ago
    Syncing (and its related attributes of backup and redundancy) are more useful, and Dropbox facilitates both that and sharing. So what's your angle? :)

fareesh 11y ago

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

krullie 11y ago
From the list given by @imaginenore the major one for me is CineformHD support. We work on a lot of VR stuff and there are quite some GoPro users out there that generate material in this codec. Not having to transcode to an intermediate is nice. Also hardware acceleration is always good to have.
- theoh 11y ago
  FYI, the phrase "quite some users" is not uncommon among (continental european?) non-native speakers of English, but it's not correct. "In the British National Corpus, for example, most examples of quite some are "quite some time", others are "quite some distance". If you replace "quite some" with "a considerable", the meaning should be clear. If the sentence does not make sense when you do that, it's likely that "quite some" is not being used properly." From http://forum.wordreference.com/threads/quite-some.1011589/ http://forum.wordreference.com/threads/quite-some.1011589/
  - krullie 11y ago
    Thanks theoh. Dutchie here. Always nice to learn something new about a foreign language.

obiefernandez 11y ago

Why the heck do they make it so hard to figure out what's in the release?

slhck 11y ago
There will be a proper news release on the homepage soon, I suppose.

esaym 11y ago

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 "videos" using some web scrapping with perl. 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) Edit: The release mentioned hardware acceleration improvements. I never knew ffmpeg even supported any HW accel: https://trac.ffmpeg.org/wiki/HWAccelIntro https://trac.ffmpeg.org/wiki/HWAccelIntro

GhotiFish 11y ago
mplayer and mpv and vlc and most native players can speed videos up on the fly, tempo-shifting or pitch shifting the audio based on preferences. Usually the [ and ] keys.
- esaym 11y ago
  Yes, those are players. But I don't want to sit in front of my computer or cell phone while on lunch break, I want to sit on the couch in front of a TV. Natively, neither plex or roku allows videos to be speed up, so they have to be reencoded at a different speed.

pdknsk 11y ago

If ffplay supported hardware decoding, it'd be the perfect player. You could not make a more minimal player. It does not, and it doesn't seem to be high on the priority list, rather in last position perhaps. https://trac.ffmpeg.org/ticket/3359 https://trac.ffmpeg.org/ticket/3359

cm3 11y ago
Have you tried mpv?
deleted 11y ago
[deleted]

mkagenius 11y ago

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

cm3 11y ago

Is the built-in aac encoder better or as good as fdk-aac? I've been using fdk-aac because it gives lower bitrates and better/same sound.

slhck 11y ago
libfdk historically always was a bit better and supports VBR properly. See also: https://trac.ffmpeg.org/wiki/Encode/AAC https://trac.ffmpeg.org/wiki/Encode/AAC
- cm3 11y ago
  That's why I've been using it. Is the improved built-in encoder on par now?
  - slhck 11y ago
    I haven't done or seen any tests, but I suppose if you require VBR and/or HE-AAC support, go for libfdk, otherwise for bitrates ~128k or higher, use the internal AAC encoder.
lozf 11y ago
Official docs say that it's competitive at 128kbps, but these[0] listening test from Kamendo2 (who's very experienced in ABX listening tests of lossy codecs) suggest fdk-aac still has the edge, as well as handling VBR and the HE-AAC / HE-AACv2 profiles properly. [0]: https://hydrogenaud.io/index.php/topic,111085.0.html https://hydrogenaud.io/index.php/topic,111085.0.html
alphapapa 11y ago
On a related note, how do those options compare to Vorbis and Opus, technically and legally? Is there a compelling reason to use AAC over those choices?