P: Unable to advance to the next photo

@johnrellis  This is absolutely correct and I can vouch for this, I can reliably replicate this on 2 machines, one running Win11 (on Intel CPU+AMD GPU) and one running Mac OS Ventura (Apple Silicon M1).  Lightroom version 13.0.1 on both. If I do any adjustments on the +/- keys and advance quick enough, basically EVERY single image gets stuck. If I wait for the pop-up that shows what the adjustment is to disappear, then I avoid the bug. But that adds 2 second for each advance, which is a pain when I am doing quick final adjustments and advancing at my own pace.

For those who might be testing new versions of LR, I've found the following simple recipe reliably reproduces the bug on my LR 13.0.1 / Mac OS 14.1 / Macbook Pro M2 Max.

1. Disable Catalog Settings > Metadata > AutomaticallyWrite Changes To XMP.

2. Import at least 20 - 50 raws that are at least 6000 pixels wide, e.g. sample Nikon Z 6 II .nefs from dpreview.com, and place them in a folder.

3. Go to Develop.

4. Repeatedly and quickly type "=" (increment current Basic slider) followed by right arrow.

5. Observe that within 5 - 15 photos, often sooner, the photo in Loupe doesn't match the photo selected in the filmstrip.

Since this bug is obviously a race condition (dependent on the timing of asynchronous events), it wouldn't be at all surprising if this recipe fails to reproduce the bug in other installations.

@Sebastian33688021njp7  Thank you, always happy to help, and as for the fact that you sometimes have this problem, it's because you automatically pressed the arrow instead of 1, I had that happen a lot. And as for the update, ADOBE is putting the finishing touches on it and it will be out soon. It's almost ready, you can trust me) 

Excellent work around! Thanks!

I am having exact same problem since the V13 update

Hi @vitalyn38151610,

thank you for this workaround and your testing. It indeed helps me. But only to - let's say - 80%. I just postpdroduced around 1.000 pictures with your recommendation and the problem occured not that often any more but strangely enough it still did once in an while. So yes, it makes sense to use your workaround but nevertheless I hope for a quick official update. 😉

This is anecdotal, but I had this with version 12 but it hasn't happened once to me in V13

What has also changed is when I used to select the crop tool I would go to drag the points to reframe an image and there would be a certain 'stickiness' to the movement which is absent in V13.

It's the weirdest thing that I put down to a GPU issue.

My wife who sits opposite me with the same specced machine machine (but a 1070ti and a slightly different motherboard) does experience the issue of images not advancing in V13 but didn't with V12.

My machine is a 7950x, 64gb DDR5, Windows 10, 3070ti, Crossfire motherboard

Her machine is a 7950x, 64gb DDR5, Windows 10, 1070ti, Asus Tuf motherboard

I also am forced to export CR3 files to DNG using DNG convertor version 14 as the latest version exports at 10% of the speed that 14 does.

https://petapixel.com/2023/11/17/adobe-working-to-fix-a-bug-that-broke-lightroom-workflows-for-many-users/

@Sebastian33688021njp7  Read my post above and turn to page 10! There I wrote a temporary solution to the problem for you!

Hi @Sameer K,
thanks for this workaround recommendation. It indeed helps here (13.0.1) but unfortunaltely still doesn't make sense cause it massively slows down the overall performance. If you have any other idea until the bug is fixed I would very much appreciate it.
Best,
Sebastian