-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
[Bug]: Number of frames in setting not equal number of generated frames #506
Comments
Could you please share your console output? It contains additional information for troubleshooting. What is the format of your input video? |
most likely this is due to ffmpeg. my command will remove some trivially similar frames. there are at least 3 approaches to deal with this problem
|
The source format is mp4
|
First of all, I would like to thank you for your great work. And I am convinced that this little bug will not be a disaster. |
This is not a bug, but an intended behavior. ffmpeg has a lot of arguments and some of them can remove similar frames. However, your use case is a new one that I have never thought of and I think it’s worth making an additional option. |
In animatediff_utils.py you can comment out lines 82 and 83 to get around this problem
|
Is there an existing issue for this?
Have you read FAQ on README?
What happened?
When using a video source the expected generated frames don't match. See the attached image and the actual comand line settings.
When using other command line tools to extract every frame of the video by 30 fps it really are 423 images generated.
But at the end only 297 are generated which makes the video too short.
Steps to reproduce the problem
What should have happened?
I expected 423 images to be generated in the output folder. But only 297 are generated.
Commit where the problem happens
version: v1.9.0 • python: 3.10.6 • torch: 2.0.1+cu118 • xformers: N/A • gradio: 3.41.2 • checkpoint: 93ed864a22
What browsers do you use to access the UI ?
Google Chrome
Command Line Arguments
Console logs
Additional information
No response
The text was updated successfully, but these errors were encountered: