[mort96]

Handbrake does use ffmpeg. My whole point is that the libraries are ffmpeg, so I don't understand why you're saying it back to me.

Gah. I give up.

[CyberDildonics]

Handbrake isn't a GUI for all of ffmpeg, it does a very limited set of what ffmpeg can do.

[mort96]

Never argued otherwise. Specifically, the thing I'm saying is wrong is:

> someone recommended a GUI that doesn't use ffmpeg

Handbrake uses ffmpeg.

But I recognize your username. I don't remember from where but I remember reading or having a conversation with you which went nowhere. I think I'm done.

[CyberDildonics]

Using ffmpeg for one thing doesn't mean a GUI is a GUI for all of ffmpeg.

[mort96]

You said it's not using ffmpeg.

It's using ffmpeg.

That's the problem.

[CyberDildonics]

The problem is that ffmpeg does a lot more than handbrake exposes, that's all anyone is trying to say.

[mort96]

Listen 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.

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), 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?