Interesting approach.
Curious how this behaves with larger datasets or longer sessions.
I’m assuming the build step doesn’t resize images that have already been processed. Other than that this approach seems to handle plenty of images per album. Albums are a UX principle, so they shouldn’t be very big anyway.
Correct - if the resized image is already there it is skippped (this can be overwritten with -force flag).
I’m assuming the build step doesn’t resize images that have already been processed. Other than that this approach seems to handle plenty of images per album. Albums are a UX principle, so they shouldn’t be very big anyway.
Correct - if the resized image is already there it is skippped (this can be overwritten with -force flag).