• eceforge@iusearchlinux.fyi
    link
    fedilink
    arrow-up
    13
    ·
    8 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
        arrow-up
        4
        arrow-down
        1
        ·
        8 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.

        • ReversalHatchery@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          8 months ago

          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
            link
            fedilink
            arrow-up
            2
            ·
            8 months ago

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

    • Hadriscus@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      8 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…