I just applied some local adjustments on one image.
And now all 1000+ images in the same directory have those 2 local adjustments applied.
Obviously I didn’t had all those images selected when I applied those local adjustments.
I had to kill photolab because it was freezed - idle in task manager and not responding, and I discovered the disaster after running it again.
And all previously local adjustments already applied are lost : so about 100 images lost !
And of course no way to reproduce the bug, so no chance support will listen.
I seem to remember this problem happening to someone quite some time ago on this forum.
If anyone has any idea of certain circumstances that may generate this bug, or any idea to avoid it, it would be appreciated (please don’t recommend to put less images in directories to limit risk, this not an option).
Maybe a clue : one of the last local adjustment I did on the last image before the bug was a very tedious lines painting on some motifs with lot of curves which slowed down my station enormously (and I have an extremly fast station - not dedicated to photo only) and which I had to disable for the time it took to do the following.
Photolab 6.12.0 - Win11pro 23h2 - threadripper pro - RTX 3090ti drivers up to date.
I remember several times when users accidentally selected all images at once (Ctrl+A or a rushed mouse operation), applied a local adjustment, and then saw what happened and couldn’t undo the adjustment. I’ve not seen a case where multiple images weren’t selected and yet this happened.
I also remember several cases whereby other operations were performed accidentally.
I believe there’s at least one feature request to add a confirmation dialog before a batch operation is performed.
He specifically indicated he did not have all the images selected when he applied the adjustments. I don’t know what to make of it. It could be user error or perhaps a software corruption.
Given that your “extremely fast station” was brought to its knees (so that you had to kill PL) suggests that, in fact, you did have multiple images selected when you applied the LAs. I’ve had this experience too (more than once) - without realising I had not undone a “select all” action.
My observation is not helpful, I know (and I appreciate how upsetting the result is for you) - but that’s the most likely explanation.
Its a problem many of us used to have rotating in error batches in PhotoSupreme. The difference is they, within days of having this raised and the need of a confirmation before it happened, introduced an update with that as an option. It prevented me and others from it since. No help here but but shows the difference between a firm that’s customer based and DxO
This could happen: If you hide the image browser at the bottom while editing the images, Control A is still active. Without realizing it, all images are selected in the background. Nasty software bug!
“extremely fast station” for photolab because it never use more than something like up to 10, 15 % of cpu and maybe less.
I had to kill it when PL was idle but not responding : no activity at all checked during several minutes , so it had crached.
After this bug I stopped working. So now I opened again the only one image with local adjustments applied (since I deleted every wrong other local adjustments) and indeed my station isn’t slowed down.
This indeed may support the hypothesis of an inadvertent CTRL+A.
Any reminder of the basic principles is useful.
Anyway there is a bug since photolab has crashed. A crash is always a bug. No misuse on the part of the user.
It’s likely (but not 100% certain) that an unfortunate keyboard shortcut has selected all the images.
Obviously, when more than 1000 images are selected (if this is the case) a warning should be displayed, because even if it only happens once, it can have extreme consequences (imagine I have a job to deliver to the customer today).
Anyway, the fact remains that photolab has crashed and there’s a bug somewhere. No developer can blame a crash on misuse.
