GNOME Bugzilla – Bug 428784
preload the next n images in editing mode and fullscreen
Last modified: 2018-07-12 00:05:33 UTC
Switching Photos in fullscreen and editing mode is very slow. It seems to take a lot of time for loading the picture. Why don't preload the next n (configurable in preferences) pictures (and scale down), so switching photos can be done much faster. It would be nice to keep the previous photos in cache, so switching back would be faster, too.
Just adding myself to CC and saying "others would like that too". Feature seems to be popular on ubuntu brainstorm (http://brainstorm.ubuntu.com/idea/2738/) and still not supported in 0.4.2 - in fullscreen low-res version appears at once, but proper photo starts to render only after switching to next picture.
Just a me too. The “2 pass” loading of images is slow, and could be avoided with preloading next photo and keeping last photo in memory (for fast rewind). Preloading seems to be the default in Gthumb, and EOG seems to load images many times faster than F-Spot. I can't even find why it is so slow on my 2.2Ghz machine compared to other image viewers... It is not a critic per se, I use F-spot heavily, it is my main image software. But for “quick filtering” photos at the end of a photo shooting, i must use another soft to delete out-of-focus or any other bad photos. That done, I can use F-spot on remaining photos.
*** Bug 539854 has been marked as a duplicate of this bug. ***
what about using something like Clutter to get hardware accelerated performances ? Ubuntu Netbook Remix, Login Experience (aka GDM face browser), Eye of GNOME (maybe) are making use of it. In the other hand, Eye of GNOME is already faster than F-Spot without OGL trick...
*** Bug 556820 has been marked as a duplicate of this bug. ***
Speaking of cache, I'd like an option to keep a version of the photo at the screen resolution saved as a jpeg file, for ultra-fast browsing. Also, the preloading should use threads (don't block the GUI, and make use of multi-core).
*** Bug 591232 has been marked as a duplicate of this bug. ***
Is someone considering this bug? It would still be a nice and easy to implement feature :)
F-Spot has moved to https://github.com/f-spot/f-spot/issues If this Bugzilla ticket is still valid in a recent version of F-Spot, please feel free to post this topic as a ticket in the F-Spot project on GitHub. Closing this report as WONTFIX as part of Bugzilla Housekeeping as we are planning to shut down GNOME Bugzilla in favor of GNOME Gitlab.