P: Unable to advance to the next photo

@FrostyOfTheNorth 

"Radio Silence?" 

@Sameer K  Posted on this forum on October 18th that "The team is aware of this and is currently working on it."

Until this morning, there had been no change in that status - at which point I posted. 

Adobe has no incentive not to provide updates when updates are available. 

And that's only one of the issues that v13 introduced

Luckily the biggest problem was fixed immediately the day after release of v13.

Let's hope that also the general performance degradation issue will be handled as well.

@Rikk Flohr: Photography Thanks for the update.  Hopefully the potential fix does solve the issue and it is released soon.  Overall, is the team aware of how poorly this issue was handled -- from the fact that the bug made it into a public release, to the radio silence from Adobe about this, to the glacial pace of issuing a fix?  If your mesage today had been posted weeks ago, I would have been satisfied.  It would have been a case of "a bug made it in, we're on it ASAP" rather than "there's a bug, let's ignore it, uh oh now our customers are <removed>, let's keep waiting, well now that we look bad I guess we should say something".  From a customer perspective, IMO this sure could have been handled better.

Greetings all,  Please see the new Pinned Post. 

(Nov 26)
Thank you to those who've requested testing access.  We are no longer needing additional eyes on the proposed fix. 

November 20: Update - We still need additional testers for this proposed fix. Please review the information below and follow the instructions if you can participate.

(Nov 6)

I met with the Lightroom Classic team today on this issue, and they've identified the issue and a potential fix for wide release. Prior to that, we are looking for a few testers who can verify that this fix addresses the issue for all workflows. Participation in the Prerelease build would require the signing of an NDA in order to access the private prerelease system and download the test build. Additionally, you will be asked to download, install, and use (in a production environment) this prerelease build. The team will also need rapid feedback on the efficacy of the fix and, potentially, logs from your local environment. 

• Particularly needed are Customers who have access to the original files but for whom the workaround is not functioning. 
• Additionally needed are Customers who cannot use the workaround due to a lack of local originals.

If you are willing and able to participate, please Direct Message me (via this forum) with your Full Legal Name and your Adobe ID you use for your subscription.

This post will be updated as soon as additional information is available. 

Thank you for your consideration and your patience. 

@Martinomac  Aren't we paying? My bank card is consistently charged by ADOBE every month. But you are right, a month has passed, and there is no result, and the most frustrating thing is that we can do nothing, there is nowhere to complain about them, except to sue and sue for moral damages. Why there is no reaction from ADOBE in this chat, except that they are just aware of the problem.

There have been 4 or 5 Photoshop Beta updates since this v13.0.1 bug and yet not one mention from Adobe regarding any progress? I can see where their priorities are. As paying customers, a simple progress update would be appreciated at this point or are we just waiting for Dec update now?

Just adding my voice to the chorus of folks who are really, really frustrated with this. It's wedding and event season in the Southwest of the US and I have about 25k files I need to work through. I literally got a new computer to address this issue as I just assumed it was because mine was too old to run the new version. So disappointed to see that not only was the issue caused by Adobe clearly not testing the new release properly, but that it's been known for a month and nothing's been done about it. At this point I have too many catalogs in v13,  I'm not able to downgrade anymore. Now that I have a computer that is capable of running competitors to LR I am seriously considering switching. I like new features as much as the next person but at the end of the day I'm running a business, and the core functionality of this software, like simply switching from one photo to the next, is critical. Sameer can you please provide an estimate of when this will be resolved? I do not use smart previews, I have never had that box checked, and the issue persists. 

Can confirm that the "Adobe Employee" (un-taggable Sameer K) workaround is not only ludicrous and unacceptable, it is also not a 100% workaround as I am still having the issue intermittantly even with "use smart previews instead of original for iamge editing' is turned off. The delay when swithcing images is crazy considering the machines users having this issue are running lightroom on. I am still getting the issue whereby it sticks on the previous image even with the above settign turned off.

Hello, I have the same problem - when I burn through the images in development mode (the final check before exporting)  and correct exposure, sometimes the image jumps back. And I have to move back/forward to advance.

I found the workaround that works for me:

1. In the library mode: "Photo -> Auto advance" is selected (so after pick/reject/rating/color it jumps to the next image)

2. The catalog has all images "Pick" flag set

3. I move to the next image not with the arrow key (!) but with "P". I kind of pick again, but that makes the image advance

4. Never had any glitches or jumps back.

First it was very frustrating but Adobe makes me learn new tricks. First I unlearned to use "Done" button, now I unlearn to use the Right arrow key.

What's next, Adobe??? 🙂

@vitalyn38151610 I'm not a forum guru. Of course I'm serious, it happened to me just this week. If you have a solution feel free to solve it, don't bother.