Skip to content

feat: add playback speed control and visualization for video segments #506

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

virajbhartiya
Copy link

Features Added

  • New "Clips" tab in the ConfigSidebar for controlling segment speeds
  • Speed presets (0.25x to 4x) and custom speed input
  • Visual indicators in the timeline when a clip has modified speed
  • Current speed indicator in the player during playback
  • Visual styling with blue stripes for clips with non-default speed

Motivation

I've been wanting this feature for so long that I decided to implement it myself! Cap has become an essential tool in my workflow, and the ability to speed up/slow down specific sections will make it even more powerful for creating polished videos.

I love this product and hope this contribution helps make it even better for everyone. Looking forward to your feedback!

@virajbhartiya
Copy link
Author

@richiemcilroy @Brendonovich Can you Please take a look at this?

@Brendonovich
Copy link
Member

Does this PR actually implement clip retiming or is it just the editor UI?

@virajbhartiya
Copy link
Author

Yes it implements the functionality and the editor UI changes

@Brendonovich
Copy link
Member

Did you forget to push some code? You've made no changes to the Rust code in charge of playback or exporting that would be necessary to implement this

@virajbhartiya
Copy link
Author

Oh yes I had forgotten to push the backend changes

@virajbhartiya
Copy link
Author

Pushed the backend changes as well @Brendonovich.

@EricWiener
Copy link

Could this be merged?

@EricWiener
Copy link

This wasn't working for me and I needed speed editing soon so I added #632 but feel free to use this instead

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

Successfully merging this pull request may close these issues.

3 participants