Is photolab "reverse ?" compatible?

@platypus Thank you for confirming that.

You have mentioned it before and the only reason for my “caution” was that I have not personally tested it extensively.

Arguably, it needs to be tested on Windows to ensure that it works that way but I am not volunteering for that task, its time for some other users to start testing DxPL(Win) for the benefit of the wider user community.

I do thank them for that one small “mercy” but I would like to have reasons to thank them for a lot more!?

2024-12-03_082221_

Impossible to have DOP Read and Write both turned off with DxPL(Win) unless you want a guaranteed VC.

2024-12-03_082426_

When DxPL(Win) has the Load setting off it will ignore the DOP but for a new discovery that will mean creating an empty database entry (actually using the ‘Auto-apply Preset’) and allocate a new UUID.

If you then Load the DOP manually, there is a clash between the new database entry and the DOP, for a start the edits aren’t going to match and neither will the UUID so the [M] will contain the ‘Auto-apply’ edit and VC[1] will contain the edits from the DOP.

Thanks to the super elegant coding of DxO (sorry sarcasm, is the lowest form of wit) there is no easy way to swap the entries over “en masse” or to tell DxPL to just use the DOP (or vice versa).

So, particularly when testing a new release, for those where the database matters (with Projects etc), the safest option to use with a new release, with the “restored” database that DxPL will automatically convert and create for that release, from an old one it can find, is

2024-12-03_083348_

But beware where you leave any session in DxPL because I believe it will automatically start the new release essentially where you left off your editing session with the old release!

That is now less of a problem because DxPL does not appear to run off and create a whole load of DOPs for images in the directory on which it starts immediately.

There is a window of opportunity to go and set the ‘Preferences’ as suggested above to ensure that DOPs will not be overwritten with the edits from any “experiments” with the new release.

However, at this point the user is relying on the database because no DOP updates will occur automatically, they will only occur when the user does an explicit ‘Sidecar’/‘Export’. At that point the DOPs are now useless to the previous release, essentially the reason this topic was created.

I am tired of making such statements without access to the code and any assistance from DxO whatsoever. DxO support appears to be highly variable and the users let down by any inadequate support wind up here and we try to help the other users pick up the pieces.

I have one last mega post to write, maybe two and then I will try to avoid the forum as much as possible.

In the meantime my count program could be used to undertake some form of verification of the database before and after the upgrade and before any damage is done to the DOPs by user edits.

PL7 “Parked up”, PL8 is also "Parked Up:-

PL7 Counts:-
This indicates an error in my assumptions! There doesn’t seem to be an ‘Iptc’ entry for every ‘Items’ (images including VCs) entry!?

PL8 Counts before the Restore:-

PL8 directory with the pending Restore:-

The PL8 database will remain as when PL8 was closed down until it is re-opened.

PL8 after the restore, Oops we appear to have no ‘Projects’ @Brunok1 what a surprise!

Comparison:-

Why oh why did I get involved with this one!!

Edit:-

A summary of the counts which shows that DxO have a question to answer about ‘Projects’, I will make a formal Support request later today.

I need to investigate what I believe is going on with the other fields unless DxO feel like helping @DxO_Support-Team?

The counts are consistently down by 5 except ‘Projects’ which have vanished completely.

Please see Edit 4, the problem in this case is that I was Restoring directly from the PL7 database which was still open in PL7 and it lost the ‘Projects’ I had been editing at the time.

In Edit 3 a repeat of the test with PL7 closed worked.

In Edit 4 a repeat after adding another Project in PL7 caused the PL8 Restore to fail to include the newly added Project.

Sorry!

Edit 2:-

A directory is missing completely from PL8 after the ‘Restore’ of the PL7 database

which contains 5 images

I only visited that directory recently for reasons I have forgotten!!! Actually it was to create an arbitrary ‘Project’ entry for the test

2024-12-03_105901_PL7 Projects

Oh boy!?

Edit 3:

But repeating the test worked as it should have so what went wrong the first time? In this test I completely removed the PL8 database before the ‘Restore’ operation, i.e.

  1. Remove PL8 DB
  2. Start PL8
  3. Restore PL7 DB in PL8
  4. Restart PL8

Edit 4:-

I believe the problem was that I was Restoring from a PL7 database that was still open in PL7. The counts program managed to get it OK but not DxPL Restore.

PL7 counts:-

PL8 Counts after Restore, minus the new Project 3:-

As you might have seen im my post above, I rename or delete the database before discovering images with modified dop files. So far, I’ve never had unwanted VCs, but that might be another difference between Mac and Win versions of DPL.

@platypus

  1. Start with a deleted database on PL8, i.e. nothing in it
  2. On PL7 create a test case

using 5 stars (metadata) Red Label (Metadata) and (red) Flag (DOP)

  1. Check PL8 options
  2. Navigate to test directory. Metadata will still be imported from the image metadata but the Flag is missing because it is only in the DOP
  3. Import the DOP

I get VCs but what has happened to the Flag?

It is present in the DOP


but absent in PL8!?

Repeated the test but with obvious edits and we have another bug I believe, PL8 is not importing the Flag!?



@BHAYT , this thread is about reverse compatibility. Opening images in PL7, images that have been customised in PL8.

Editing the DOP version numbers lets me transport PL8 edits to PL7 (except for the ones of PL8 specific features) on Mac.

YWXMBD (your Windows experience might be different)

@platypus I will try the reverse i.e. PL8 modded DOP taken to PL7 but in the meantime it appears that the flag doesn’t work at all in PL8(Win).

@platypus Modifying the PL8 DOP by amending both these fields
in every other one of 6 images, i.e. image 1, 3 and 5 while image 2, 4 and 6 remain with an unaltered PL8 DOP

results in PL7

from this in PL8

so the principle works and the current settings for PL7 are

2024-12-03_181753_

So what now?

Thanx to all for all the tips you’ve given to try and get around my problem.
Very very appreciated.

Maybe I solved what happened.
I’ll have to check this further, but it seems that when I’m using photolab and firefox (v129.0) is open on my workstation, photolab becomes very unstable (this is not due to a lack of resources, this workstation is oversized for photolab, it’s designed for extremely resource-hungry applications).

I use other applications that use graphics cards very intensively in this way or with other software that allows workstations to be shared over the internet in order to communicate quickly with the team or the customer and have no problems whatsoever, even during phases of very intense GPU and CPU use.
But it seems that photolab doesn’t support it.

I hope this solves my problem.

Thanx again to all !!!

It’s the confirmation that it is possible to go back to PL7 with (a limited amount of) images customised in PL8.

When I do this (also with older versions), I make sure that the automatic import and export is off and the database has been deleted. Please note that I always set PL to not i/e dop sidecars and that I often delete the database. My asset manager is Lightroom Classic and that therefore, PhotoLab’s database and proprietary sidecars are irrelevant, considering that I export to 16 bit TIFF in most cases.

@JoPoV It is s bit strange that anything like a Browser could interfere with DxPL!?

@platypus A VC every time on Windows if auto import is off and the user chooses to Import a DOP!, I am afraid.

The trick of Version adjustment seems to work on Windows and would be relatively easy to build into my DOP analysis program, i.e. automatically back up the DOPs and then “adjust” the version number, i.e. exchange a designated Version with a new one or Replace the version without checking the old value.

Yes. But I had a completly bug-free cession without it. Have to test it more to be sure.

EDIT : instead of nightmare buggy cessions. crashes after crashes. Fortunately .dop were saved and work could progress at a very very slower pace.
But maybe this bug-free cession didn’t involve cases as complex (less local adjustment, combinations in masks (masks + erazer), retouch tool, etc …) as buggy cessions.

@JoPoV I need to go and get on with gutter clearing and exciting jobs like that but if you have a test image with a DOP containing the more complex edits you have been using then I could set up a batch of exports and try running Firefox alongside, if it is actually the exports which are failing rather than the edit sessions themselves that are being interrupted.

I don’t typically use any of the features you mentioned so I am not the right person to try breaking it editing with those features.

I could also run another batch of exports from PL7 alongside to see if its competition for the GPU that could be causing the problem.

My machine with PL8 currently installed is a 5900X so all the graphics traffic has to pass through the GPU which is currently an RTX 2060, a somewhat lower spec than you use if my memory serves me correctly.

Export works fine anytime. PL8 crashed when tweaking settings. Not when exporting.
So adjusting images was nightmare. (sometime up to 5 crashes on the same one and so some operations could not progress - DxO has a bunch of autogenerated bug reports about that now. But any export worked totally fine).

1 Like