I really didn’t know either but it seemed like a funny suggestion and appropriate for a slow down 
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…
Oh, I can reproduce, but only with CR3.
You can see ARW and NEF are selected instantly, CR3 with lag.
Didn’t recognize as those are not my own photos… So, just switch your camera system 
most likely this is exiftool – I have to investigate why it gets called, maybe I miscompiled exiv2
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.
Here’s a sample CR3:
Uploading: IMG_1692.CR3…
Thanks.
Check’s in the mail, I presume? 
Maybe… we see what Alberto will find out first 
Gaaned’s build doesn’t lag, which I guess confirms Alberto’s suspicion.
I’m not sure it’s because it’s Perl or simply because spawning subprocesses is slow on windows – or a combination of both. Anyway:
ok, so I might have miscompiled exiv2. I’m rebuilding right now, let’s see…
I have uploaded a new version of the windows installer (1.16.4.1, just to distinguish it from the previous one), hopefully it fixes the problem…
It does for me. Thanks
Unchanged here (no EXIF), but I’m not sure if all went properly.
I downloaded this…
…which is this…
…and says this in Control Panel…
But when I run it, Preferences | About | Version says this…
I don’t know if the missing minor number matters, but the commit date is two weeks ago…
???
I totally uninstalled / reinstalled, too.
Did you revert your config? (I mean the Exiftool command)
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.
I left the exiftool field empty, so exiv2 will do it instead…
Wait a minute, this is weird. I’m getting EXIF in some folders, but not in the one I was testing. Let me poke around and report back…
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.
Thanks for the assist.
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.
Excellent (and no more delay).
Glad you figured it out, but just to clarify, indeed this is simply a rebuild with a “proper” exiv2, I bumped the version number only for the windows installer, everything else is unchanged.
I’ll make a new release with new features “in due time” – whatever that means
1 Like
It’s all good. I just thought for a moment I had somehow gotten hold of the wrong installer, at least until cache finally cleared and it started working. It’s great now, thanks!