-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
noLoop() not honored by saveGif() #7354
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
Comments
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you! |
Looking at how
While I definitely think there are times where you'd want to manually grab frames and export the lot as a GIF, I would be hesitant to call the current behavior a bug. After all, if I save the individual frames using Though I'm sure you've already come to the same conclusion by now. |
@MartinParrish Interesting. With your change, I there is still an unconditional Could you try to see if the following sketch will call
|
Most appropriate sub-area of p5.js?
p5.js version
1.11.0
Web browser and version
130.0.6723.92
Operating system
macOS
Steps to reproduce this
Steps:
Snippet:
It'd be great to have the ability to create animated Gifs from graphics that aren't possible to create real-time (e.g. because each frame requires a web API call, which takes multiple seconds to complete). p5's
redraw()
function would be great for this to use (i.e. this invokes draw whenever a frame is ready to be added to the animation). Unfortunately, the current implementation ofsaveGif()
does not seem to honornoLoop()
- as the draw function is called periodically regardless.The text was updated successfully, but these errors were encountered: