Skip to main content
Inspiring
October 8, 2023

P: Unable to advance to the next photo

  • October 8, 2023
  • 326 replies
  • 54884 views

Why no one writes about the fact that in develop mode, after any manipulation with a photo, it is impossible to go to the next photo in the feed? You go, but the photo remains the same as it was, you have to go back and only then go to the next photo. This is a global problem!!  Anyway, I did some research and I realized why many people are silent about it, because this problem occurs only when using the +\- buttons on any keyboard, even on macbook !!!!. If you use only mouse or touchpad, there is no problem with photo transition. That's why many photographers don't pay attention to it, because they don't use the keyboard. Therefore, ADOBE does not react in any way.

This topic has been closed for replies.

326 replies

johnrellis
Legend
November 11, 2023

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

@DdeGannes "I wonder how many users who experience this bug have the option to "Automatically write changes into XMP", selected."

 

That's a good hypothesis. But I'm able to reproduce the bug easily without Automatically Write Changes Into XMP enabled.

 

It's clearly a race condition in the UI, and maybe writing changes to XMP makes the race more likely for some users.

 

 

 

 

 

 

DdeGannes
Community Expert
Community Expert
November 10, 2023

@mlphoto.raw , you are correct, if you go back to LrC 12 you would have to use a Catalog from that version.

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.0.1, PS 27.0; ) Camera Oly OM-D E-M1.
DdeGannes
Community Expert
Community Expert
November 10, 2023

Just a thought, I wonder how many users who experience this bug have the option to "Automatically write changes into XMP", selected.

Regards, Denis: iMac 27” mid-2015, macOS 11.7.10 Big Sur; 2TB SSD, 24 GB Ram, GPU 2 GB; LrC 12.5,; Lr 6.5, PS 24.7,; ACR 15.5,; (also Laptop Win 11, ver 24H2, LrC 15.0.1, PS 27.0; ) Camera Oly OM-D E-M1.
mlphoto.raw
Known Participant
November 9, 2023

I thought since I updated my catalog, it isn't backwards compatible. 

Known Participant
November 9, 2023

@mlphoto.raw 

Why you use the 13.01 ?

just  go back to 12.5

13 version of LR should be out of the creative Cloud.

 

mlphoto.raw
Known Participant
November 9, 2023

I just culled/finished a wedding set, and delivered. 

And the amount of times I had to review the images to make sure I didn't accidently skip an image to edit, because of this bug, was over dozens.

I recognize that as a professional, we need to review our work over and over again to make sure its up to the standard of our own brands..........

But the significant anxiety, literally, caused by this bug, that I may accidently deliver a subpar product, because of my "industry standard" software consistently and constantly skipping over images & not displaying them. Or worse yet, it causes me sometimes to reject an image because it makes me think it is a duplicate, is unacceptable. 

Thanks for the AI stuff, Adobe, but I'd much rather go back to when things were working as its supposed to, v. the computational photography trickery garbage & these bugs. 

TomReesFramer
Known Participant
November 9, 2023

The arrow keys sure are a long way from the "1" key but I guess you could make that mistake when using a band aid to fix broken arm. Between me and my editor we've processed many more than 7000 image over the last few days and I can tell you there are more than a few bugs in this "industry standard" software.

I think patience is part of the adobe subscription sign-up isn't it? $9.99 a month + a minimum of 18 months patience while we get our STUFF together regarding the latests bug. That's how long we waited for the autosync issues to be resolved.

<Moderator> Personal comments are not acceptable. Please review the terms for this forum, found at the bottom of this page. 

Inspiring
November 9, 2023

@TomReesFramer  I've processed 7k photos in two days I've had the error pop up a few times, just from accidentally switching arrows. In general, Patience, Wait, ADOBE is aware of the problem and solves it, probably not so easy, need to test and only then release to the world! 

TomReesFramer
Known Participant
November 9, 2023

It doesn't occur after every photo under any circumstances. Regardles of smart previews being used, capslock metadata advancment shortcuts or any other trick, the issue is prevelant across the entire develop module. Sometimes I can edit 50+ photos without the issue appearing and then suddenly it will happen several times within 10 images. This is simply another bug that adobe has not picked up on during their latest itteration of what is quickly becoming the most unusable of all their unsuable apps. The biggest issue of the last 2 years (the autosync plague) was resolved with the latest release and I'm fairly certain this issue is a result of the resolution of the autosync issue. 2-steps forward....1 step back, ay Adobe?

Inspiring
November 9, 2023

@TomReesFramer  Yes, I saw everything, and you handled everything well, well done! But agree with me that without the capslock you would face this problem after every photo, in the first video where the error appeared, you went back to the photo with the left arrow, so this error appeared, in the second video the error appeared only at the end, and then maybe you accidentally pressed the arrow key. Therefore, I advise you to process this method through the capslock, because there is no other way out, I hope an update to the program with a solution will be released soon! And believe me, I edit many times faster than you, because I have slightly different needs, only exposure, but this does not affect the transition to another photo through the arrow