I don’t know what the lazy caching does and I suspect it to be only relevant when entering new folders, but simply try it. There is also an option in pref > file browser “showing embedded jpeg as thumbnail…” you could try. You might need to delete/rebuild the cache for this option to take effect. A little further down on the same page. I don’t have this delay, all my options are pretty much default.
A funny thing: Be sure there is no compatibility mode set for ART.exe in Windows… I once had that for DT and wondered why its browser was so laggy until I accidentally found out. No idea why it was activated. Maybe there was a crash and Windows did some “problem solving”.
I don’t know for sure what it does but ISTR in other apps similar features allowed folder contents to populate “unthumbnailed” (with a generic icon, etc.) for a moment or two while the thumbnail population caught up rather than wait on each individual image and cause delays. But there’s already a setting for that, so I dunno… Maybe @agriggio can help clarify.
There’s this:
But I like the idea of that, which is the same way darktable works.
I’m fully “incompatible”!
At any rate, I tried toggling all these options (restarting in between) and it made no difference. It’s no biggie, just a curiosity.
I found only one post referencing Lazy Caching and it was just Alberto recommending someone disable it (and another option) to work around a particular issue.
No further enlightenment… that’s me, searching for enlightenment!! LOL
It might be exiftool – on windows it’s particularly expensive to run. You can try disabling it by clearing “Preferences → Image Processing → Exiftool command” and see if that makes a difference.
Normally exiftool is run only as a fallback if exiv2 can’t decode the metadata properly. If this happens, maybe you can share one of your raw files so I can take a look…
Yeah, exiftool is Perl, right? That means it’s gotta compile to bytecode first (IIRC) and that’s slow on Windows. Anyway, without it there’s no EXIF at all - Zilch. Several images remained black in the browser until I deleted all sidecars, now they’re OK - Just no EXIF.
Also, did this version pick up the other things you’ve changed (e.g., single click folders, etc.) or is that a different branch? No change on that, either.
OK, so apparently I had to clear cache One More Time… working now. Weird but I’ll take it. It’s also recognizing my Sigma lens properly now! Woo Hoo! I assume the other commits are a different branch which will make it into the next “full” release.
Yes, it’s “just” a new build of the current release. I gues that no commit was made, but just a fix while compiling. Therefore the version info hasn’t changed.
That also relieves me from having to specify focal length in my dynamic rule. I have a 17-70 and a 70-300. Since exiftool wasn’t recognizing the 17-70 I put a focal length range in the rule to avoid ambiguity and make sure the correct processing profile was loaded.
Actually, the lens is the only difference between the two profiles and they’re both in lensfun, so I could dump the dynamic rule entirely. But lensfun has no vignetting correction for them, while the Adobe LCPs do, so I’ll just remove the focal length from the dynamic rule and be good to go.