3 ms·
The problem is that ffmpeg does a lot more than handbrake exposes, that's all anyone is trying to say.
by CyberDildonics 3y ago
The problem is that ffmpeg does a lot more than handbrake exposes, that's all anyone is trying to say.
- mort96 3y agoListen to me. The thing I have a problem with, specifically, is your statement that Handbrake doesn't use ffmpeg. That statement is incorrect. I have no problem with the statement "Handbrake doesn't make a good ffmpeg GUI, because it only exposes a small part of what ffmpeg can do". That part is totally 100% fine. I have a problem with the statement "Handbrake doesn't use ffmpeg", which you claimed here: https://news.ycombinator.com/item?id=39943516 https://news.ycombinator.com/item?id=39943516. And I have a problem with the response "ffmpeg is a lot more than just a wrapper around the libraries" (https://news.ycombinator.com/item?id=39941964 https://news.ycombinator.com/item?id=39941964), given the fact that ffmpeg project is the libraries and that the ffmpeg CLI tool is just an interface to them. "ffmpeg is more than a wrapper around the libraries" is strictly speaking true (because ffmpeg is both the libraries themselves and the "wrapper" ffmpeg command line tool), but it doesn't make sense as a response in context. Do you understand? Or do I need to break it down further?
- CyberDildonics 3y agoA wrapper would be some sort of straight pass through and ffmpeg does more than that. That's how you can create big commands that rewire channels, use audio from a different source, subtitles from a specific language, filter, overlay text then stream it all out. That's not trivial, but I don't know why you're getting upset over it.
- mort96 3y agoDo you agree that handbrake uses ffmpeg
- CyberDildonics 3y agoYeah I meant to say it doesn't use all of ffmpeg of course.
- mort96 3y agoOkay, good. So we agree.
- CyberDildonics 3y agoffmpeg is not a trivial wrapper and handbrake uses very little of ffmpeg.