Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FFmpeg 3.0 released

ffmpeg.org

Post reply on HN
Print view View original

51–60 of 95 posts

Re: FFmpeg 3.0 released

#51

Post by JoshTriplett »

cm2187 wrote: post #21
ux wrote: post #11

Earlier quoted context omitted.

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…

Any plan to support QuickSync?

Looking at the release notes, I see several mentions of QSV support.

Re: FFmpeg 3.0 released

#52

Post by theoh »

krullie wrote: post #47
fareesh wrote: post #23

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

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.

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/

Re: FFmpeg 3.0 released

#53

Post by cm2187 »

JoshTriplett wrote: post #51
cm2187 wrote: post #21

Earlier quoted context omitted.

Any plan to support QuickSync?

Looking at the release notes, I see several mentions of QSV support.

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.

Re: FFmpeg 3.0 released

#55

Post by bagels »

douglasfshearer wrote: post #8
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.

EC2 + SQS + ffmpeg is 1/5 the cost of elastic transcoding for me, and that's not even using all the ec2 capacity.

Re: FFmpeg 3.0 released

#56

Post by cm3 »

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.

Re: FFmpeg 3.0 released

#57

Post by cm3 »

pdknsk wrote: post #49

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

Have you tried mpv?

Re: FFmpeg 3.0 released

#58

Post by [deleted] »

pdknsk wrote: post #49

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

[deleted]
Post reply on HN