-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
RuntimeError: Could not get number of frames
(with ffmpeg-6.1?)
#99
Comments
It looks like the output text has changed a bit. It looks for a line starting with imageio-ffmpeg/imageio_ffmpeg/_io.py Lines 173 to 187 in 9ab981a
|
I think it doesn't output |
😢 any idea about how we can modify the command to make ffmpeg include the frame count again? |
I'm afraid I don't know. I was able to find a solution involving ffprobe but I haven't tested it. |
Same issue here... I quickly looked at ffmpeg code. It looks like the print command is still there but with an additional requirement for a filter: ffmpeg 6.1: ffmpeg 5.1: Changing imageio-ffmpeg/imageio_ffmpeg/_io.py Lines 150 to 160 in 9ab981a
to cmd = [
get_ffmpeg_exe(),
"-i",
path,
"-map",
"0:v:0",
"-vf",
"copy",
"-f",
"null",
"-", There is also a |
This aims at addressing imageio#99
PR submitted in #107 but note that I haven't tested it with ffmpeg 5.X so hopefully the CI will do that |
Bug: imageio/imageio-ffmpeg#99 Pull-Request: imageio/imageio-ffmpeg#107 Signed-off-by: Michał Górny <[email protected]>
* Add a null filter to re-enable frame count This aims at addressing #99 * Relax testing criteria in test_read_nframes See #107 (comment)
Fix imageio/imageio-ffmpeg#99 by adding a null filter to re-enable frame count.
When running the test suite today, I'm getting a number of failures:
Also some similar failures when running imageio's test suites. I'm pretty sure it worked around release time, so I suspect something changed on my system. I suspect it's because of ffmpeg upgrade to 6.1 but can't check right now.
Full log:
imageio-ffmpeg.txt
The text was updated successfully, but these errors were encountered: