In the next article we are going to take a look at LosslessCut. This is considered by some to be the Swiss army knife of video editing.
  • xapr [he/him]@lemmy.sdf.orgdeleted by creatorEnglish
    8·
    3 年前

    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.

  • nutbutter@discuss.tchncs.de
    4·
    3 年前

    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
      13·
      3 年前

      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
          41·
          3 年前

          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.

          • ReversalHatchery@beehaw.org
            1·
            3 年前

            I think they were talking about a special kind of media file, that is not compressed but instead stored losslessly. I think H264 can do that too.

            • mudeth@lemmy.ca
              2·
              3 年前

              LosslessCut doesn’t only use lossless codecs. It losslessly cuts video files encoded in lossy codecs.

      • Hadriscus@lemm.ee
        1·
        3 年前

        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@lemm.eeEnglish
          2·
          3 年前

          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

    • folak@lemmy.world
      2·
      3 年前

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