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

[Feature Request] Playback Speed adjustment per segment for time-lapse and slow-mo clips #586

Open
NoahIles opened this issue Jan 7, 2021 · 8 comments

Comments

@NoahIles
Copy link

NoahIles commented Jan 7, 2021

Hey love the app, it's the best I have found for cutting up footage. If I could ask for anything it would be this. Thanks for making such an amazing app!

@markusd1984
Copy link

That would require re-incoding which misses the point of the app of lossless editing /cutting, thus I'd be surprised this would be included.

At least for changing the speed per say, unless we could find a way to create slow-mo's by duplicating frames to keep it lossless and faster to export (over re-incoding) and removing frames for shorter slow-mo's / speed up clips that way. Whether end results look good enough is another question and due to the challenge of keyframe cut makes it only more difficult if not even impossible.

I love the app too and the more we can do tasks we are used in NLE's the more we stay in LC. :)

@NoahIles
Copy link
Author

NoahIles commented Jan 8, 2021

I did some googling before I made this post originally and found out that ffmpeg could "change the speed of a video stream using setpts video filter", I don't fully understand when re-encoding is necessary, using ffmpeg.
When is re-encoding is necessary? Is it not when exporting and merging multiple segments? There is a lot to this project that is new to me.

I definitely want to do more research into electron, react, and ffmpeg and try to figure out if I could at all contribute. I have a lot to learn.
What do you mean by NLE's?
In my experience with video editing exporting would involve encode a file.

@markusd1984
Copy link

The whole point of losslesscut is that it cuts segments out or merges them without re-encoding, so that one doesn't loose any quality compared to traditional video editors (NLE = Non-Linear Editors) which creating an entirely new video thus need to use encoding, also LC is way faster (seconds/minutes vs hours).

@NoahIles
Copy link
Author

NoahIles commented Jan 8, 2021

Makes some sense, thanks for the reply! Maybe I should just look into ffmpeg's documentation more.

@mifi mifi mentioned this issue Jan 18, 2021
22 tasks
@mifi
Copy link
Owner

mifi commented Jan 18, 2021

Thanks for explanation @markusd1984 - you are right. Afaik also it's not possible to do this with re-encoding. I added a point to the lossy issue #372
But to be honest, I think instead of adding many lossy features to losslesscut, I will probably instead create a new app for that.

@mifi mifi closed this as completed Jan 18, 2021
@rpanderson
Copy link

@NoahIles if you're interested in an implementation using setpts, check out autoscrub, which hastens silent intervals.

@tazztone
Copy link

tazztone commented Mar 5, 2023

shouldn't it be possible to losslessly save a clip (60fps, 1sec) to a clip (30fps, 2sec)? all the frames would remain the same, just be played over a different amount of time

@mifi
Copy link
Owner

mifi commented Mar 6, 2023

You would think so. After some googling it does seem to be possible by tricking ffmpeg (or other tools) to effectively ignore the FPS value and use some other value instead. And if there is audio, then the audio will have to get sped-up or slowed down, or re-encoded. So maybe it could be possible for LosslessCut to have such a hack also.

@mifi mifi reopened this Mar 6, 2023
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

5 participants