Hacker News new | past | comments | ask | show | jobs | submit login

Great software in term of both quality and active development, and I also have very positive experience interacting with their dev/contributors (reporting bugs etc.).

But not sure why this is on front page today, as it has been released almost a month isn't it?

Perhaps they finally did put down that cocktail.

I've always been a little unclear on the barriers between Handbrake and its dependencies. Does Handbrake maintain custom forks/patchsets that get applied to ffmpeg, etc.? I knew Handbrake as a GUI for ffmpeg, and in my research, I have come across one or two things that implied there was something unique about their backend that wasn't yet upstream, but ultimately not much else.

Since you're familiar with the project's development, would you mind clearing some of this ambiguity up for me? Thanks.

Handbrake applies about a dozen patches on top of the FFmpeg tree. See them at https://github.com/HandBrake/HandBrake/tree/master/contrib/f...

Note that HB uses a release (4.1) rather than git master HEAD. So, some of those patches may get rescinded with new ffmpeg releases.

Also, it's best to think of ffmpeg as having two parts: the libraries (codec, format, ...) and the API controller which sets up the processing pipeline and manages its run i.e. parsing the commnad line, registering input/output streams, and executing the required operations. The latter for ffmpeg is in fftools/. Handbrake implements its own top-level controller.

I noticed that it hadn't been submitted, perhaps because it was so close to Christmas. It's one of my favourite examples of free software in active development, and wanted to flag the update. Plus there are some pretty significant changes, like the move to ffmpeg.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact