Skip to content

Cut at the nearest audio (key-) frame instead of the next one #1433

Closed

Description

@DreckSoft

I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first

Description

I'm using LosslessCut to cut AC3/EAC3 files to sync audio. Those are using 32ms frames at 48k sampling rate. If I cut 0.000-2.568 the closest cut would be 2.560 seconds, so an 8ms difference. LosslessCut however produces a file with 2.592s, leaving a 24ms difference. This adds up over various cuts. So the cuts should be made on the closest keyframe. This will usually result in a +- 0ms result over various cuts.

As an alternate option to solve this a setting "snap to xx ms" would be helpful. So one can only enter a multiple of xx ms as cut points.

Activity

  1. changed the title [-]Cut at the nearest (key-) frame instead of the next one[/-] [+]Cut at the nearest audio (key-) frame instead of the next one[/+] on Jan 27, 2023
  2. mifi commented on Jan 27, 2023

    @mifi
    Owner

    Is this keyframe cut or normal cut mode? Not sure how to control this, and not sure how exactly ffmpeg deals with keyframes when seeking in audio. See #1216

  3. DreckSoft commented on Jan 28, 2023

    @DreckSoft
    Author

    In Keyframe cut mode. According to the description it should be the nearest key frame but it is always the next.

  4. added a commit that references this issue on Aug 7, 2024
    3daf257
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions