Skip to content
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

Progress/cancellation #229

Open
loganhope560 opened this issue Jul 31, 2017 · 5 comments
Open

Progress/cancellation #229

loganhope560 opened this issue Jul 31, 2017 · 5 comments

Comments

@loganhope560
Copy link

Is there any way when using Guetzli as a library to insert checkpoints where one could check an early exit flag and abort the compression operation? Thanks.

@khavishbhundoo
Copy link
Contributor

khavishbhundoo commented Jul 31, 2017 via email

@loganhope560
Copy link
Author

I don't know anything about the algorithm(s) that Guetzli uses. What I'm asking is if there exist any natural "rounds" or such where a callback could be made and the callback could decide to free the resources associated with the operation.

@kornelski
Copy link

Yes, guetzli is an iterative algorithm so earlier abort (with larger/less optimized result) is possible.

@loganhope560
Copy link
Author

Thanks, pornel. Do you happen to have any pointers on how I might hook that in? Currently I am using a single call to guetzli::Process.

@kornelski
Copy link

kornelski commented Jul 31, 2017

Look for stop_early variables in the code. You'll need to hook them up (or another variable in similar places) to whatever mechanism you want to use for stopping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants