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.

[mijbil250456]

So unlike others, I can't roll back - opening my catalog in 12.5, it says it can't be used as it has been used with a newer version, because it was upgraed for 13. Can anyone help?

. 

[voyager7777]

Your old catalog from the v12 should still be there. But if you create the catalog with v13 there is no way back that i know off.

[yurii32033693wvln]

I have the same problem. i have to install the old version 12.5 because only it works properly. also i noticed that even when you mouse click on another photo  it may not switch immediately either. i use loupdeck + with it too it works horribly. Very unpleasant that such a banal error continues as in 13.0 version and in 13.0.1, I had hoped that in 13.0.1 they would fix it, but no.

[Rafael _ Oz]

Its like Adobe not even tested at all Lightroom with at least 20 photos in the develop mode.

[vitalyn38151610]

@yurii32033693wvln  Wait, ADOBE has responded here that they are aware of the problem and are looking into it. Hopefully it will be fixed soon.

[kylec85330911]

When I'm in the Develop module, when I advance to the next image the screen sometimes gets stuck on the previous image. If I advance, again, then it'll go to the next image and sometimes I won't be aware that I've accidentally skipped an image. But when I catch it and go back then the image that was skipped will display. It's happening pretty frequently. Haven't tested if the same behavior happens in other modules. But it's super annoying because I'll advance to next image and be waiting, waiting, waiting for the next image to show up. Sometimes I'll think that maybe I didn't press the arrow key correctly, so I'll press it, again. And that effectually will skip over an image, and often I won't realize until later when I go back through the whole take that some images didn't get edited because they were skipped over. Please fix this. My version of Lightroom is up to date. Version 13.0.1. Thank you!

[kylec85330911]

Also, to clarify, I've attempted to restart Lightroom multiple times. I've tried working with files directly on my drive and smart previews. I've optimized the catalog. but nothing seems to fix the behavior.

[Sean McCormack]

This is working correctly for me on a Mac Studio with Ventura 13.4.1 and Lightroom Classic 13.0.1. 

Does this happen with GPU turned off in the Performance tab of Preferences (in the Lightroom Classic menu)?

It may also be a faulty preferences file. 

[kylec85330911]

I'm on a 2021 Macbook Pro running Sonoma 14.0. "Using Graphics Processor" is set to Auto. I'll try turning off. But it shouldn't being doing this regardless.

Not sure what to do about a faulty preferences file. Do you have further info?

Thanks for your insights.

[kylec85330911]

Just tested with "Using Graphics Processor" set to "Off" and it's continuing to do it.

[Sean McCormack]

https://helpx.adobe.com/ie/lightroom-classic/help/setting-preferences-lightroom.html

Lightroom stores how you've set up and use it inside this file. This page shows where the file is.. back it up first, and then use one of the suggested ways (e.g hold down Option in the General tab of Preferences to get a reset button) to reset the preferences. If nothing changes, copy the backup file back instead and restart preferences. 

[Sean McCormack]

@kylec85330911 Guess I've just learned this is a known issue, but it is working with the keyboard for me. Even using - / + and . and , to swap around for edits and then use the arrows works fine. But, I'm Ventura, not Sonoma.

[kylec85330911]

I deleted the preferences file and that seems to have done the trick, I think. It seems that Lightroom is also noticeably snappier in almost every respect. I was also having an issue with getting a spinning wheel whenever I tried to shutdown Lightroom and it would take forever to finally close. Now it closes almost immediately. Thanks for the tip! Will report back if the issue starts happening, again. Now, I just have to go through customizing Lightroom settings, again, so it works like how I had it set up previously.

[Sean McCormack]

@kylec85330911 That is the problem with resetting. When you're happy, it might be worth saving screenshots of each tab so you can just copy from them if you have to do it again. 

[kylec85330911]

Whoops, spoke too soon! It's happening, again. Seem to work at first, but after about 10 photos it's now doing it regularly. I would say that the app is a bit quicker after deleting the preferences file, and closes better. But the issue with getting stock on an image when advancing seems to remain.

[kbarre]

Is anyone still having the issue after reverting back to Lightroom Classic 12.5?

To me, if that is happening, this may not be an actual Lightroom issue, and more of how raw files are interpreted within the Adobe ecosystem. Adobe RAW was included in the update on the same day. It makes me wonder if we're all looking in the wrong direction for a solution, and Adobe RAW needs a fix.

[Rafael _ Oz]

Even In Windows 10 in a PC I have the same problem. Its not only on my Mac Mini with Sonoma,

And no....Its not a Raw issue. I work only with .jpg in 3200px resolution. I don`t work with Raw files at all.

[vitalyn38151610]

@Sean McCormack @kylec85330911  Friends, have you even read here in the chat room about the problem? Why are you repeating yourselves again? ADOBE has already admitted that there is a problem and it is currently being solved by engineers, here ADOBE replied to wait for the next update. In the meantime, either go back to version 12.5 or work with mouse or touchpad. in this case there is no problem! 

[mijbil250456]

Something else I am experiencing linked to this issue - when I do get the correct image showing in the develop pane, if I then go to apply an adjustment, it jumps back to showing the previous image in the filmstrip and then applies the adjustment there. it's really unstable. Is anyone else experiencing this?

[yurii32033693wvln]

same situation

[Rafael _ Oz]

mijbil250456

yes...Is not usable the 13.01 to use in batch developer mode at all. 

That version is a beta. Adobe not tested at all .

Adobe should make Lightroom from now on like the other sofwares. Use a Beta before release.

I loose 2 catalogs in this mess.

[yurii32033693wvln]

and when do they plan to release the update? what will adobe say about this?? how long do we have to wait and put up with this discomfort...?? it makes work very difficult

[DdeGannes]

@mijbil250456 , you stated "

yes...Is not usable the 13.01 to use in batch developer mode at all. 

That version is a beta. Adobe not tested at all .

Adobe should make Lightroom from now on like the other sofwares. Use a Beta before release.

I loose 2 catalogs in this mess.".

What is a beta?

[Sean McCormack]

@vitalyn38151610 Stop assuming things here. My reply was done in a separate post which was then merged into this post. As with other bugs, new posts get merged to keep the information related to the bug together. My first reaction to all bug posts is to test the behaviour, which I'm not seeing here. Rikk has access to the currently known bugs here, but not everyone has knowledge of all these, and it was only on the merge that I became aware of this one. 

[kylec85330911]

Yeah, man, my separate post was merged with this one. Relax. Thanks for the tip to go back to the older version tho!