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

Use frames for progress ratio #393

Merged
merged 4 commits into from
Aug 25, 2022
Merged

Use frames for progress ratio #393

merged 4 commits into from
Aug 25, 2022

Conversation

Willy-JL
Copy link
Contributor

Using timestamps for progress was very inconsistent for me. When starting it would be stuck at 0% for quite a long time, then work normally up until 57%, stay stuck there a long while and then jump to 100%.

Using frames seems to work better, it starts the progress counter nearly instantly and it gets up to 100% just fine. It does stay stuck at 100% for a bit though, probably as it is finalizing.

@Willy-JL
Copy link
Contributor Author

Just realized that fps can have decimals like 23.976, will fix that in a bit

@jeromewu
Copy link
Collaborator

Sounds good, wonder if this works for audio files as well?

@Willy-JL
Copy link
Contributor Author

Right, audio, will add support for that too

@Willy-JL
Copy link
Contributor Author

Added audio support (reverts to using duration for the ratio), fixed for fps values with decimal points and also ported the same logic to src/util/parseProgress.js (not sure where it is used but it was basically the same original function so i thought id give it the same treatment).

Let me know what you think!

@jeromewu
Copy link
Collaborator

LGTM! Thanks for the PR!

@jeromewu jeromewu merged commit f07b1e9 into ffmpegwasm:master Aug 25, 2022
@Willy-JL Willy-JL deleted the frame-progress branch August 25, 2022 18:55
jeromewu added a commit that referenced this pull request Aug 10, 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

Successfully merging this pull request may close these issues.

None yet

2 participants