• ferret
    link
    fedilink
    English
    699 months ago

    The swiss army knife for lossless video and audio editing is ffmpeg

  • xapr [he/him]
    link
    English
    89 months ago

    I’ve been using LosslessCut for a few years now. It’s really easy and smooth. It does exactly what I want and what the name says, and I couldn’t ask for more.

  • amigan
    link
    fedilink
    English
    4
    edit-2
    9 months ago

    lol@typescript and appImage. Yuck. Just use mpv to find cutpoints and man ffmpeg

  • @nutbutter@discuss.tchncs.de
    link
    fedilink
    49 months ago

    It is a good tool, but for me it only trims from the keyframes. To trim precisely, it has to re-encode, which, unfortunately, does not work on my machine for some reason. So, I just stick to ffmpeg cli.

    • @eceforge@iusearchlinux.fyi
      link
      fedilink
      139 months ago

      I suppose that makes sense given that information is encoded as a series of key frames interspersed by 'I-frames" that simply encode the delta to the previous key-frame when using most compressed video algorithms. So cutting in-between key-frames doesn’t really make sense since the I-frame would no longer have anything to reference it’s delta to.

        • @mudeth@lemmy.ca
          link
          fedilink
          39 months ago

          You’re confusing cause and effect. It’s lossless because it cuts at keyframes and does not re-encode.

          If it did what you’re suggesting it wouldn’t be lossless anymore.

      • @Hadriscus@lemm.ee
        link
        fedilink
        19 months ago

        This has always bothered me, I suspect it’s the same underlying reason most video players can’t do reverse frame-by-frame. But Quicktime allowed it twenty years ago, so it’s possible. I suppose you’d have to actually decode the entire keyframe interval and use the resulting frames as new “baked-in” keyframes so to say. I suppose that’s more or less what djv and other frame checkers do under the hood. But I don’t know what I’m talking about so…

        • gila
          link
          fedilink
          English
          2
          edit-2
          9 months ago

          That’s what I’ve always assumed it does since back when quicktime player barely even ran on my PC yet for timeline operations it was significantly more responsive than WMP/MPC.

          For Losslesscut I just get around this by encoding my input from source using keyint=n:scenecut=0 in ffmpeg where n is a manually set keyframe interval.

          So e.g. if my expected cut occurs on a frame that occurs at t+10 seconds of footage, n can be the same as the fps and then there’ll always be a keyframe exactly at timestamp 00:00:01, 00:00:02 and so on. I can then open it in losslesscut and easily snap to the frame I want and make the cut losslessly.

          Yeah the first encode generally means a lossy transcode by the time I get to my final video but being realistic that’d be a part of my workflow either way and this way it’s less

  • fmstrat
    link
    fedilink
    English
    49 months ago

    Or Shotcut, which can trim and so much more?

    I mean, they all use ffmpeg.

    • @folak@lemmy.world
      link
      fedilink
      29 months ago

      Different tool, different usage. There are things impossible to do with losslesscut such as upscaling, editing colors…