-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
'to_gif' raises IOError/OSError when no 'program' parameter is given #43
Comments
I am not sure I understand. If you have ffmpeg, you can do:
Doesn't this work ? I have seen your other commits, I am not sure it is a good idea to have a global variable for the gif program. Most of the time, I use ImageMagick, but sometimes the result is not good, so I want to try with ffmpeg (they yield very different results). |
So does it work with the line I gave above ? |
1 similar comment
So does it work with the line I gave above ? |
I was also getting something like:
But adding the |
@sergiobuj This error means that the program cannot detect ImageMagick. Did you install ImageMagick ? |
I didn't install ImageMagick, but the extra parameter worked. |
The default parameter for "program" is "ImageMagick", and it will only work if ImageMagick is installed on your computer. If you change it to ffmpeg you can make gifs using ffmpeg (but these are generally heavy and ugly). Pygame is not needed for gifs, it is needed if you want to make previews of your gifs/videos before writing them to a file, it is especially useful if you use the IPython Notebook. Thanks for the feedback, I will make more explicit error messages for the "couldn't find imagemagick" case. |
Got it, thanks! |
Because the to_gif function uses the ImageMagick as default program to generate the gif. But when there's no ImageMagick, there is no fallback for ffmpeg.
I fixed it by manually changing the parameter to 'ffmpeg' (which is bad) but maybe the best thing would be to add a GIF_PROGRAM variable in the conf.py for people to choose from imagemagick or ffmpeg ?
The text was updated successfully, but these errors were encountered: