Live data from Hacker News

FFmpeg 3.0 released

ffmpeg.org

81–90 of 95 posts

Re: FFmpeg 3.0 released

#81
post #61
post #59

Earlier quoted context omitted.

libfdk historically always was a bit better and supports VBR properly. See also: https://trac.ffmpeg.org/wiki/Encode/AAC

That's why I've been using it. Is the improved built-in encoder on par now?

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.

Re: FFmpeg 3.0 released

#82

Earlier quoted context omitted.

I'm yet to find a limit that they won't adjust - what ones are you referring to?

S3 buckets are one I've seen. But there's not really a reason to have 100 s3 buckets, much less more than that.

Yes, that's one that you may not be able to change. From memory, they put that one in place to prevent the equivalent of bucket name squatting (since every bucket has a corresponding public domain name).

Re: FFmpeg 3.0 released

#83

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…

Chromakey was introduced in 2.8.x.

It's in the official changelog as a new feature: http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;...

Re: FFmpeg 3.0 released

#84
post #46

Earlier quoted context omitted.

@imaginenore's comment below ( https://news.ycombinator.com/item?id=11103063 ) has a detailed list of the 29! new filters.

Wait, are you @majorsheep ? If yes your illustrations are really good :) http://www.king-sheep.com/star-wars-the-force-awakens-fan-ar...

Nope. I can't take credit for the illustrations, but I might have to get in touch with Nathan since there is some nattaylor out there who likes to put my gmail address for all of their online services.

Re: FFmpeg 3.0 released

#85
post #83

Earlier quoted context omitted.

Chromakey was introduced in 2.8.x.

It's in the official changelog as a new feature: http://git.videolan.org/gitweb.cgi/ffmpeg.git/?p=ffmpeg.git;...

Apologies, you're correct. I was thinking of the colorkey filter:

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.

Re: FFmpeg 3.0 released

#86
post #76

Earlier quoted context omitted.

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

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

Syncing (and its related attributes of backup and redundancy) are more useful, and Dropbox facilitates both that and sharing. So what's your angle? :)

Re: FFmpeg 3.0 released

#87
post #56

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.

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?

Re: FFmpeg 3.0 released

#88
post #79

Earlier quoted context omitted.

With all due respect, you are not answering the question that the parent poster asked. If someone created a hostile fork of QuassalDroid, and made decisions that you disagreed with, I doubt you would be OK with them using the same name for the project. The right to fork is fundamental in open source, but there is no right to present someone else's work as your own, or to confuse the general public about which version…

The fork would only be "hostile" because I disagreed with it. And why should I have any more say on this than the other contributors? This is open development, the very idea is that people are replaced all the time.

Trademarks can be held by an organization, not just by one person. This is how Apache software works, for example. In that case, there are bylaws in place to ensure that the interests of different people are represented, decisions can be made fairly, and toxic people can be prevented from killing the project.

In contrast, projects such as Python have a "benevolent dictator" moderl where one person has the final say about the direction of development. There is nothing unethical about a BDFL model in open source; it's just a choice that a community can make.

You seem to be deliberately confusing yourself about the distinction between forking, which is always allowed, and representing your fork as the original project, which is never allowed. If you are still confused, think about it this way: would you want someone to attach a bunch of malware to your project and redistribute it under its original name, as if it were your version? You can't prevent this without trademark law.

Re: FFmpeg 3.0 released

#89
post #68

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…

Is Intel QSV available on Mac/Linux yet by any chance?

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.

Re: FFmpeg 3.0 released

#90
post #19
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…

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

[deleted]
Post reply on HN