Inspiring

P: Unable to advance to the next photo

Forum|Forum|2 years ago
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.

Show previous replies

Martinomac

Participating Frequently

Its working really well. I processed a full wedding without any issues. Thank you for the fix.

mlphoto.raw

Known Participant

https://www.youtube.com/watch?v=Qny1jg46Z3s

Been editing for good hour+:
1. It appears to run much faster because they must have fixed some kind of race condition.
2. No more issues with non-displaying photos.

Good job Lightroom Classic Team. Albeit it took far too long for us who have been on the #strugglebus working around this bug for two months...
Fix is certainly welcome, and it works.

KaylaM67

Participating Frequently

downloaded 13.0.2 this morning and havent had the issue at all.

kbarre

Inspiring

Am I the only one who is thinking there's no way on the planet I'm installing 13.0.2 until there are lots of people here saying their problems are fixed? I'm going to need to know that it ACTUALLY works, and isn't just another "step along the way" as a few thousand more people have their catalogs bricked.

mlphoto.raw

Known Participant

Yay! updating now. fingers crossed.

Rikk Flohr_Photography

Community Manager

Greetings all,

The Lightroom Classic Team has just released version 13.0.2 with a fix for this issue.

(Note: this release contains no additional bug fixes or new camera/lens support.)
See: https://helpx.adobe.com/lightroom-classic/kb/fixed-issues.html

If you do not see the update in your Creative Cloud application, you can refresh the app by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

We thank those who’ve volunteered to test the build in pre-release. Your time and effort allowed us to release this fix sooner to a broader audience.

Thank you all for your patience.

Rikk Flohr: Adobe Photography Org

A

adamr86174301

Participant

Without going back and forth through every single image in a gallery before export to makesure the edits we have added to an image have actually been applied to that image and not the previous one, this is what happens.

Now even more time wasted reuploading LR catalog, removing edits and masks, reapplying edits and masks, exporting, uploading, checking.

Thanks Adobe for you fantastic comunication and help on this issue. NOT!

Please, we need a fix asap!

M

MiroslavMajstorovic

Participating Frequently

@mijbil250456 One thing that occured to me is that if you are working with raw files i.e. you are not just editing with smart previews, you could select all images in the catalog, save metadata to files (which will create xmp files for everything), then install an older version and create a new catalog and then import from your local storage again into that catalog. There is nothing in principle that should prevent you from being able to do it, and I am guessing only the adjustments added in this version wouldn't trasfer over (like the new blur tool).

It would probably be slow to import given the amount of images you work with but might be worth the effort. Then upgrade the catalog once they finally sort this mess.

FrostyOfTheNorth

Known Participant

Day 56 since 13.0.1.

It's disappointing, isn't it? You would hope that a company with the resources that Adobe has would be capable of fast-tracking a fix to minimize the impact on users. But here we are 56 days in.