-
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
ValueError: Invalid value for quantizer: 'wu' #368
Comments
I see the same problem. The problem seems to be that convertToPIL() in imageio/plugins/pillowmulti.py 'wu' seems to come from the default parameter specified in Versions: Backtrace:
|
I have the same problem - I think this is related to changes in the v2 update to imageio. For now using v1.6 of imageio is working for me while I try and figure it out. |
You just need to remove the quantizer in gif_writers.py: def write_gif_with_image_io(clip, filename, fps=None, opt='wu', loop=0,
colors=None, verbose=True):
if not IMAGEIO_FOUND:
raise ImportError("Writing a gif with imageio requires ImageIO installed,"
" with e.g. 'pip install imageio'")
writer = imageio.save(filename, loop=loop,
fps=fps or clip.fps, palettesize=colors or 256)
verbose_print(verbose, "\n[MoviePy] Building file %s with imageio\n"%filename)
for frame in clip.iter_frames(fps=fps, progress_bar=True, dtype='uint8'):
writer.append_data(frame) Really, though, having that wrapper at all is pretty ridiculous. |
@metaperture What's ridiculous is the lack of a test suite. |
You can also change from @metaperture Would you consider making a PR to fix the issue? |
Okay, so I was going to create a pull request to fix this by setting the quantizer to 'nq', but I found this comment: It says that 0 is the best quantizer. Should I make 0 the default and allow people to select nq, 1, or 2 through the options, or just stick with nq? |
pull request #460 should fix this issue. Hopefully we can get it merged very soon! |
this has been fixed in the repo. |
I get the error
|
programe:
The text was updated successfully, but these errors were encountered: