P: Unable to advance to the next photo

[vitalyn38151610]

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.

[kleinski]

This bug is a pain in the butt, the workaround about turning off smart previews is not applicable for my job. I work as a wedding photo editor to various clients and we work using smart catalogs with smart previews. Each wedding has more or less 5000 photos. I have lots of backlogs because of this bug, imagine my workflow going back and forth because it keeps getting stucked with the previous photo instead of going forward to the next. I could not use a v12 LR because my clients are always up to date with LR. Please release the fix ASAP. Here's a screenshot of 1 of my catalog I am working.

[Martinomac]

@kleinski apply for the LrC prerelease program, trust me, you'll thank me later. You'll be able to use new prerelease versions with your clients catalogues. 

[johngillooley]

@Martinomac how do we do that?

[DdeGannes]

[Martinomac]

@johngillooley send a DM to the admin Rikk

[johngillooley]

ok - done - thanks

[rickm1970]

If this fix will also possibly fix my issue https://community.adobe.com/t5/lightroom-classic-bugs/p-windows-crash-8880582/idc-p/14252538#M49438

I would be more then happy to help test it. I used to be in QA and still work in the software industry as a PO. 

[julius_s]

If you don't message Rikk with exactly the information he requested in his original message, he will reject your application to test flat out, no "I think you forgot to send your subscription ID, can you please send that as well?", so make sure to read it in entirety prior to messaging him as apparently you only have one chance to get it correct.

[rickm1970]

How do I message Rikk with my information? 

[kglad]

@rickm1970 

use ampersand username to flag someone.

[julius_s]

He left a post pinned to the top of this thread to message him if you'd like to test. But if you simply message him about it, he will reject your application because you must unfortunately search through all 14 pages of this discussion to find another post that he made where he lists his strict requirements. It's the same with finding the correct workaround - instead of pinning the only functional workaround, Adobe has decided to keep the response about Smart Previews, which does not resolve the issue. You must again search through all 14 pages for that information. I think maybe you must also be knighted by a king, at which point you can have the privilege of helping Adobe fix their bug.

[Rikk Flohr: Photography]

@julius_s  This is not correct. 

If you look at the pinned post, in the lower right is a link that says: Jump to Reply
Click it and it takes you precisely to the full post with instructions.  No need to read even one page...

[julius_s]

Thanks for the tip!

[kleinski]

Thanks! Sent my request.

[julius_s]

An additional symptom that seems related but who knows - I find that when deleting a photo from a collection now, sometimes it just doesn't delete. Like pressing the delete key does nothing whatsoever. But then once LR is restarted, the image is indeed deleted. Also, command+arrows no longer goes forward and back when in the crop tool. The main bug persists even with the latest update. 

[Tom33632351ve1e]

I can confirm I'm also having this issue and multiple crashes per hour.

[Tom33632351ve1e]

46 days and counting 
332 replies in this thread.

[Arran29578646zlne]

I'm still getting this issue after uninstalling and reinstalling. It's driving me nuts! Not using smart previews and on the latest version of LR.

Almost everytime I go to the next image, it stays on the previous image but advances in the thumbnail panel.

[adamr86174301]

Is there an option somehow to revert back to an old software as LR is becoming completely unusable at this point. After the latest update my LR cat was updated also.

I edit 75+ weddings per year and at the moment I am having to add approximately 2hrs+ editing time on to each and every wedding due to this fault which is still noted as "investigating" on this page although many many professioanls are experiencing the same problem.

- Can not progess to next image after any edit of previous image in developement tab.

- Adding BnW preset or changing WB to image sometimes adds on to previous image.

- Edit changes do not show until I cursor right and left and go back to the edited image.

- Have to cursor right, then left, then right again to progress to the next image.

These faults I am having are intimitant so don't always happen on every edit, most of the time they do but not always. A simple workflow change isn't possible. Zero workarounds suggested work for me and my workflow, the only workround that works for me is the one I pay monthy to Adobe for. The one I have used for year til this update.

Please provide us with more updates or get this sorted asap. It is now costing me and many other professionals time and money.

[FrostyOfTheNorth]

I am having to add approximately 2hrs+ editing time

It is now costing me and many other professionals time and money.

That is the key point for me.  For those not affected by this bug because they are low-volume users or who have a workflow that this bug doesn't affect, you can shrug and move on.

But this bug has been affecting many, many of us (as evidenced by the comments in this thread and I would guess many others who haven't bothered to comment on this thread) for over six weeks now.  You have to wonder how many thousands of hours of lost productivity and monetary value Adobe customers have lost over this issue that never should have made it into a public release -- and if it did, should have been fixed promptly, not six weeks and counting...

We can hope that Adobe learns from this experience on 1) how to avoid significant bugs from reaching release, 2) how to publicly respond when they do, 3) how to fast-track fixes that impact so many customers, and 4) how to make it right to paying customers.

[julius_s]

Yes exactly! As professionals we have invested a huge amount of time refining a workflow with this software. It's not the specific features of LR, it's not the specific image quality (obviously we have a standard for professional quality, but many other applications can meet that standard), it's that we have a workflow which is efficient and integrated into our businesses. My image delivery CRM integrates with LR. My file intake process is deeply tied to LR. My disk layout is built around LR. And, above all, my editing workflow is the culmination of 7 years of working in this application. We put a lot of trust into Adobe by building our core business workflows around their software. And this rash of bugs, which seem to be completely unadressed, really shatters that trust. Maybe I'm naive in updating, maybe I should wait a year before installing the latest version. But there's no going back because now, like many of us, I updated too many of my critical catalogs to v13. This incident really seems like a slap in the face from a company that I think we all thought we could trust to incorporate so deeply into our businesses.

[FrostyOfTheNorth]

This incident really seems like a slap in the face from a company that I think we all thought we could trust to incorporate so deeply into our businesses.

Exactly right.

Hobbyist photographers and peachy-keeners here clearly haven't felt the impact of this bug like those of us running businesses processing hundreds or thousands of images in Lightroom every day.  Those of us who thought we could entrust our critical workflows to Adobe products feel this sting.

[Tom33632351ve1e]

Finally, some actual working professionals are commenting in this thread. 

I think the important thing to remember with this whole process of providing feedback via forums is....it relies on the moderators or "Adobe employees" of the forums to report these issues accurately to developers. That is obviously where the wheels fall off.

We, the monthly subscribers, are paying millions of dollars a month to use what is now commonly regarded as the industry       standard photo-editing software despite the fact it is currently unusable for most working professionals.

If Adobe really wants to fix the hundreds of bugs that plague this 1 App, all they have to do is remove the unreliable middlemen.

I fear Lightroom may be heading in the same direction as premier over the next little while as people realise there are alternatives that are worth the switch/learning curve if it means not dealing with such incompetent support.

I made the switch to DaVinci from premier 4 years ago and never looked back.

[mijbil250456]

It's over 6 weeks since the issue was identified, I've had to edit 15 weddings with this bug so far, thats 150,000 images and painfully going back and forth, with edits then being randomly applied to the wrong images. Like many I can't roll back to 12.5 because my catalog was updated, and I use one cat as LR was designed. I can see that Adobe have acknowledged the issue, but why the silence, and why no update on what is happening, and when a fix might be in place? We are not asking for a new feature, just for the most basic function which was present in every previous verison to be restored. When are Adobe going to acknowledge the stress and additional work this is causing to many many users? In any other business, if things don't work and customer support don't provide an answer, then you lose those customers pretty quickly. At the very least some form of refund or credit for affected users should be offered. I have seriously considered moving to Capture One, as Adobe support is appalling. I have contacted customer support many times about this issue, and as soon as I mention that it is this specific bug, the support handler hangs up my call, it is disgraceful. Bury your head in the sand for much longer Adobe, and you won't have many customers left. 

[owen-b]

I'm a professional event and wedding photographer in London UK. Started getting this exact issue on LR 13.01 the day I updated from 12, on both my M2 Pro Macs. Makes editing the MOST infuriating experience, it's driving me absolutely bonkers. 

Not as bonkers as reading through all these reports and it not being fixed yet, though!