Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let LC cut at NOT-key-frames - auto-calculate first key (B) frame? #1855

Closed
4 tasks done
pstein opened this issue Jan 16, 2024 · 1 comment
Closed
4 tasks done

Let LC cut at NOT-key-frames - auto-calculate first key (B) frame? #1855

pstein opened this issue Jan 16, 2024 · 1 comment

Comments

@pstein
Copy link

pstein commented Jan 16, 2024

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

In general I appreciate LC very much. But one feature needs an improvement:

Occasionally I want to cut sections in the mid of a *.mp4 video at NON-key-frames (not at key frames).

Steps currently:
I navigate to the next key frame after the planned cut start position,
then click frame backward icon until my target cut start position is reached
and mark in LC the start position simple frame
and finally export the video section interval.

Unfortunately LC exports it with/including the video stuff left (=before) the cut point until the previous key frame.
I wonder whether this couldn't be done more precisely.
LC could take the previous key-B-frame, then add the next simple "I" frames on top of it and finally insert the current cumulated "B" frame as new key frame at the first position. of the exported video interval.

Can this feature be added in the next release?

Thank you

@pstein pstein changed the title Let LC cut at NOT-key-frames - auto-calculate first key (B) frame Let LC cut at NOT-key-frames - auto-calculate first key (B) frame? Jan 16, 2024
@mifi
Copy link
Owner

mifi commented Jan 31, 2024

Unfortunately I have no idea how to implement what you suggested using the ffmpeg CLI. But suggestions are welcome. See also #1216

@mifi mifi closed this as completed Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants