-
-
Notifications
You must be signed in to change notification settings - Fork 840
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
[Feature] Add option to Generate thumbnails for image files #4189
Comments
Implementing this will also help people who did not choose to generate image thumbnails during scan but do want to generate them later. Currently, when they are generated during a scan, it respects the When they are generated automatically while browsing, stash currently tries to generate thumbnails for all images on the page at the same time, which might lead to stash crashing due to OOM when there are many large images (I've had stash crash due to this). |
+1 From the above, I am taking it that stash doesn't generate a new thumbnail when it detects an ohash change (i.e. the image has changed)?... If not then yes, this would be good to add. |
Well this explains a lot. I'm currently experiencing the same issue. |
Please consider both folder galleries and zip galleries 🙏 |
@elshanta please make a separate issue. Tailored issues allow for faster development. |
Kinda OT and I don't want to sound presumptuous, but I switched a rather extensive library from folder to zips. |
thanks for the recommendation. |
Any kind soul who can start this on the backlog please 🙏 Should be a quick fix. |
Is your feature request related to a problem? Please describe.
Currently it is not possible to change image thumbnails after they are initially scanned.
Describe the solution you'd like
Stash has options under the Generate heading to do similar things for a number of other options. It would be useful if image thumbnails was added to that list.
Describe alternatives you've considered
Delete the images from stash and rescan them.
The text was updated successfully, but these errors were encountered: