4 ms·

ffmpeg is a lot more than just a wrapper on libraries. It can do a lot of filtering and rewiring of audio channels, video channels and subtitles. Handbrake doe

ffmpeg is a lot more than just a wrapper on libraries. It can do a lot of filtering and rewiring of audio channels, video channels and subtitles. Handbrake doesn't do any of that. You can't even drag a bunch of audio files on to handbrake because handbrake doesn't do audio, while ffmpeg is great for encoding audio.

mort96 3y ago
What I'm saying is that ffmpeg is the libraries. When you use the ffmpeg CLI to filter and rewrite audio, the ffmpeg command is just decoding it using a decoder in libavcodec, filtering using a filter from libavfilter, and encoding again using an encoder from libavcodec. The ffmpeg CLI is "just" an interface for the libraries. The fact that Handbrake doesn't expose the same features as the ffmpeg CLI tool is frankly irrelevant.
- CyberDildonics 3y ago
  The fact that Handbrake doesn't expose the same features as the ffmpeg CLI tool is frankly irrelevant. It's not just relevant, it's the whole thing. They asked for an ffmpeg GUI and someone recommended a GUI that doesn't use ffmpeg and doesn't do what ffmpeg can do. ffmpeg can not only rewire channels, it can stream video, capture video from the screen, capture video from a tv tuner, overlay text etc. Also the libraries you listed are part of the ffmpeg project. They come from ffmpeg. https://ffmpeg.org/about.html https://ffmpeg.org/about.html Also they asked for a GUI to ffmpeg, not necessarily a GUI to the command line tool.
  - mort96 3y ago
    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 3y ago
      Handbrake isn't a GUI for all of ffmpeg, it does a very limited set of what ffmpeg can do.
      - mort96 3y ago
        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 3y ago
        Using ffmpeg for one thing doesn't mean a GUI is a GUI for all of ffmpeg.
        mort96 3y ago
        You said it's not using ffmpeg. It's using ffmpeg. That's the problem.
        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 ago
        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 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?
  - ranger_danger 3y ago
    to be fair, I have never seen a GUI that could do everything its complex command-line equivalent could do, that wasn't, in the end, just simpler and easier to use the command-line in the first place. so when people ask for "a GUI", I think a lot more information is needed about what it should be able to do.

mort96 3y ago

What I'm saying is that ffmpeg is the libraries. When you use the ffmpeg CLI to filter and rewrite audio, the ffmpeg command is just decoding it using a decoder in libavcodec, filtering using a filter from libavfilter, and encoding again using an encoder from libavcodec. The ffmpeg CLI is "just" an interface for the libraries. The fact that Handbrake doesn't expose the same features as the ffmpeg CLI tool is frankly irrelevant.

CyberDildonics 3y ago
The fact that Handbrake doesn't expose the same features as the ffmpeg CLI tool is frankly irrelevant. It's not just relevant, it's the whole thing. They asked for an ffmpeg GUI and someone recommended a GUI that doesn't use ffmpeg and doesn't do what ffmpeg can do. ffmpeg can not only rewire channels, it can stream video, capture video from the screen, capture video from a tv tuner, overlay text etc. Also the libraries you listed are part of the ffmpeg project. They come from ffmpeg. https://ffmpeg.org/about.html https://ffmpeg.org/about.html Also they asked for a GUI to ffmpeg, not necessarily a GUI to the command line tool.
- mort96 3y ago
  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 3y ago
    Handbrake isn't a GUI for all of ffmpeg, it does a very limited set of what ffmpeg can do.
    - mort96 3y ago
      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 3y ago
        Using ffmpeg for one thing doesn't mean a GUI is a GUI for all of ffmpeg.
        mort96 3y ago
        You said it's not using ffmpeg. It's using ffmpeg. That's the problem.
        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 ago
        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 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?
- ranger_danger 3y ago
  to be fair, I have never seen a GUI that could do everything its complex command-line equivalent could do, that wasn't, in the end, just simpler and easier to use the command-line in the first place. so when people ask for "a GUI", I think a lot more information is needed about what it should be able to do.