Version 7.1 and 7.2 - Fixing some bugs? ... while creating new ones!

[Stenis (Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))]

The main reason why I still use Photolab is that it until now have integrated so well with Camera Bits PhotoMechanic Plus 6 - BUT NOT ANY MORE!

I happen to have tested metadata sych with Capture One successfully so I have tested a few things recently even with Photolab and this is what I have found:

Suddenly synchronization doesn´t seem to work at all now between PM Plus and Photolab version 7.1 and 7.2. This BUG have been introduced already with version 7.1. as it seems (but I haven´t even bothered installing version 7.1. since it was just about new camera support) BUT this problem really is there both in version 7.1 and 7.2. and with both these versions the auto-synchronization doesn´t work at all with PhotoMechanic

I have managed to reproduce this error several times now with version 7.1 and 7.2 (during several installs, deinstalls and new installs, so now I have been forced to uninstall both these versions for good and have stepped back to 7.0.2 which seems to be the last version that works correctly.

My application is configured as follows:

I have tried even to manually update metadata via File - Metadata - Read metadata from file but without any success with version 7.1 and 7.2.

This reminds me about a really old IT-company joke from the nineteen nineties:
"Our business idea is to fix one bug while we create two new ones - that way there will always be a nice demand for our services.

So dear user friends, feel free to falsify my theses but beware to use 7.1 or 7.2 in production. If you are dependant on autosynch between PhotoMechanic and Photolab it seems to be better to stick with Photolab 7.0.2 instead until DXO have fixed this.

[noname (Captain Obvious)]

@Stenis

feel free to falsify my theses

I do not see any C2PA metadata in your posting, so for sure

[platypus (Canon & Mac (Intel and M1))]

@Stenis

If you are dependant on autosynch between PhotoMechanic and Photolab

The right tool for the job: PM for metadata management, PhotoLab for the edits…and I’d not use automatic XMP sync, but manual read. Sticking to what @Joanna calls SPOD, I usually don’t even notice such issues.

[Stenis (Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))]

This has worked perfectly fine for years and I use PM only for the metadata jobs when applying metadata but there are better tools than PM often when it comes to viewing metadata and that´s why I like to do that where ever I also consume metadata regardless if that is in Photolab or XnView.

XnView for example is very useful for controlling that all the kind of metadata I´m interested in really is in place. XnView has labels that indicates the metadata status on the images. You would understand this if you had over 70 000 images and about a third of these are ready made. XnView is far better viewing and controlling metadata status than PM is and so is Photolab. For example, it is crucial to be able to control status of the virtual copies because if they once were created before metadata was applied in PM there will be no metadata on these if the master gets updated after the virtual was created.

As you can see I can very quickly get access to hundreds of metadata elements tied to Image Properties EXIF, IPTC, XMP Exif Tools and even get the GPS-coordinates mapped on a map or a Satellite View. PM is not even close to this and the same goes for Photolab.

Also, only Photolab can give me info about where a search is hitting the various images. Since I publish reports and illustrated stories at my blog I´m interested where the hits occur. Keywords for example are pretty useless on the Internet. I rather get the hits via filenames, IPTC or search paths. Via those people can get to back to my blog from a single image and meet the rest of my stories.

It is very effective and useful to use all these three applications PM Plus - Photolab and XnView in sort of an automatic symbiosis and this synch has been rock solid the last years from version 6 to version 7.0.2. Before that the import to Photolab was manual through the File-menu but the flow has worked since version 4 and Photolab have never fucked up the data since then when exporting derivates in JPEG.

I need them all but of different reasons when it comes to viewing and controlling.

[mwsilvers (Mark - New Jersey, USA)]

Not that it helps you, but does DxO indicates it supports synchronization with PhotoMechanic Plus 6? I also noticed that PhotoMechanic has itself been updated 3 times since September 20th. I don’t use that software myself, so I have no knowledge regarding what could be causing the issue.

I see in their forums that PM supports PhotoLab but I can’t find anything regarding PhotoLab’s support of PM. My question is if PM was never officially supported by DxO but PM supports PhotoLab and has implemented their own updates during the same time period, why do you characterize this as a DxO bug.?

Mark

[Stenis (Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))]

What do you mean with if DXO supports synchronization with Photolab 6? It works and have done so since I turned it on. When you change something i PM Plus it will get propagated to PL in a second or two if Photolab is open. If it’s not you will see these changes the next time you open the folder with these images. It´s completely reliable and safe. It even works the other way around even if I don´t do that. It is truly automatic and bidirectional.

I luckily have three versions left and that saved me this time (7.0.2., 7.1 and 7.2.) Just the first one works.

[mwsilvers (Mark - New Jersey, USA)]

@Stenis

What do you mean with if DXO supports synchronization with Photolab 6?

I asked whether DxO indicates it supports synchronization with PhotoMechanic 6, not PhotoLab 6. If DxO doesn’t indicate official support of PM then I fail to how the fact that it no longer works the way you expected is a DxO bug that they would be responsible for fixing.

Mark

[Stenis (Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))]

@mwsilvers

I see in their forums that PM supports PhotoLab but I can’t find anything regarding PhotoLab’s support of PM. My question is if PM was never officially supported by DxO but PM supports PhotoLab and has implemented their own updates during the same time period, why do you characterize this as a DxO bug.?

Photolab has been supporting this communication automatically since it started to read the XMP-data in sidecars or embedded in JPEG and made synchronization automatic with the images in its indexes.

This is not a bug that just affects PMPlus as it looks. It seems like it affects all applications that updates XMP-data. I can´t even import this updated metadata manually via File- Metadata-Read from Image when using version 7.1 or 7.2 but as soon as i install 7.0.2. it works again. So, I can´t get this data into PL even manually. That´s also why I consider this a bug.

If they don´t fix this for the future versions this will definitely be a show stopper for me. For now, I will stick with 7.0.2. and that is what I suggest others who experiences the same kind of problems to do too.

It is in the interest of DXO to fix this because there are quite a few that uses PM Plus with PL and there are even some others that use other XMP-editors than PM Plus together with Photolab, that most likely will get the same problems that I have seen. This will probably affect even those who use Lightroom together with PL.

[mwsilvers (Mark - New Jersey, USA)]

I understand the conundrum, but it comes downs to whether DxO feels the obligation to fix this issue and provide support to 3rd party applications the way you expect them to. It may be a short term bug that they will correct, or not.

Mark

[Stenis (Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))]

This is general problem Mark. Version 7.1 and 7.2 have stopped reading the XMP-metadata from the images in the index of Photolab - even manually.

Have you seen this??

This is the "External Searches list and feature in PL. It is the second link to applications that might be used when cooperation between these and PL. When I and some other work in PM Plus we often switch between these two applications. For example, we might add some metadata on a selection of images in PM and then we open these very images with the “Edit”-function in PM, typically to reexport these images in order to update the JPEG-files that have been previously exported.

The thing is that if I have done virtual copies on some images (like I often do with my historical repro photographed analog images) i might have to update the metadata on them manually before I can update the JPEG-derivates of those files. It can´t be done from PM today.

In this list you can see the upper part of the list that has the PM-icon on the searches and below a bunch of XnView entries. Doesn´t matter really where an image will be changed normally these changes in the XMP-data use to get updated automatically. Today it isn´t even possible manually in version 7.1 and 7.2.

They better fix this because if they don´t even less people will feel for upgrading to version 7 since this works good already in version 6.

[JoPoV]

@mwsilvers

DxO feels the obligation to fix this issue and provide support to 3rd party applications

Culling images in photolab is horrible. They should better support it.
Or better, rewritte pl image brower ???

[mwsilvers (Mark - New Jersey, USA)]

@JoPoV

Culling images in photolab is horrible. They should better support it.

I don’t cull my images in Photolab. I use FRV or FastStone to do that. For the couple of thousand images a year I may keep after culling, all of which are processed only in DxO software. I have no need for a 3rd party asset manager like PM since PhotoLab meets my minimal needs in that regard adequately.

I tried a few of the better regarded asset managers and they each provided additional levels of complication and detail to control my assets that went far beyond my needs. I like to keep things fast and simple and never have any issues finding what I want quickly between using PhotoLab’s built in tools, Faststone, and my Windows file manager Directory Opus. Maybe if I was a professional photographer with many hundreds of thousands of images and videos to store, catalog and manage I would consider something like PM, but for me it is just unnecessary overkill.

Mark

[mikerofoto]

@JoPoV

Culling images in photolab is horrible

because it’s not made for that.
the right software for the right tools, there’s better tools than folder readers.

[JoPoV]

@mikerofoto

because it’s not made for that.

Indeed.
This is why they shouldn’t break working workflows.

@mwsilvers

it comes downs to whether DxO feels the obligation to fix this issue and provide support to 3rd party applications the way you expect them to

Because it is not made for that (culling), people invest in other softwares (money, but more important : TIME), so they should keep what works working.
And PM is a widely used software.
(Anyway I hope PM new licensing system will make some people change their workflow and use other software. I already know some which have choosen this way).

[BHAYT (Bryan [WIN10, PL8, VP4, FP7, G9 & EM1 Mkii, RTX 3060])]

@Stenis I have yet to read this thoroughly and I will attempt to do so later today but the first thing that I have to say is that DxPL has done well in tests with most software I have tested at automatically detecting metadata changes.

However, PM is probably the messiest program I have tested when it comes to updating the metadata!

This is from a Python Folder Monitor program (my version of Folder Monitor available from NodeSoft).

This is PM changing the ‘Rating’ in of a JPG image and this is a straight log of the File/Directory events generated

2023-12-20 09:10:43.833482 PFM starting
2023-12-20 09:11:49.153852 <FileCreatedEvent: event_type=created, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\__TMP__XXYYZZQ__.tmp', is_directory=False> 

2023-12-20 09:11:49.166847 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.186842 <FileDeletedEvent: event_type=deleted, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\__TMP__XXYYZZQ__.tmp', is_directory=False> 

2023-12-20 09:11:49.206835 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.224829 <FileCreatedEvent: event_type=created, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG.DOP', is_directory=False> 

2023-12-20 09:11:49.245822 <FileModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG.DOP', is_directory=False> 

2023-12-20 09:11:49.270814 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.298806 <FileModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG.DOP', is_directory=False> 

2023-12-20 09:11:49.319799 <FileCreatedEvent: event_type=created, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG', is_directory=False> 

2023-12-20 09:11:49.338792 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.358785 <FileModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG', is_directory=False> 

2023-12-20 09:11:49.375781 <FileMovedEvent: src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\P1107801.JPG', dest_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{37d9fc45-4618-4fcd-80a6-4d750b1c0c28}.JPG', is_directory=False> 

2023-12-20 09:11:49.393775 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.413769 <FileMovedEvent: src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG', dest_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\P1107801.JPG', is_directory=False> 

2023-12-20 09:11:49.432762 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.450758 <FileDeletedEvent: event_type=deleted, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\tmp.{37d9fc45-4618-4fcd-80a6-4d750b1c0c28}.JPG', is_directory=False> 

2023-12-20 09:11:49.469750 <DirModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV', is_directory=True> 

2023-12-20 09:11:49.487744 <FileModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\P1107801.JPG', is_directory=False> 

This is what ExifPro generates for a ‘Rating’ change, DxPL doesn’t recognise a change made to a JPG by ExifPro because having detected the event DxPL then checks the ‘Date Modified’ timestamp and ExifPro sneaks its changes in without changing that field.

I consider this a DxPL bug and it was the first thing I reported in my first post during PL5 Beta Testing because most other software must apply a more intelligent test mechanism and find the change made successfully!

2023-12-20 09:22:26.861389 <FileModifiedEvent: event_type=modified, src_path='F:\\___BETA DXO PL5 - TESTS\\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\\Test 17 - Run 01 - PL670\\Testing FRV\\P1107801.JPG', is_directory=False> 

The problem with PM is that it creates a number of temporary JPGs on the way which are detected by DxPL and DOPs are created which get left in the Folder (I actually reported that to DxO during PL5 Beta Testing but didn’t know about the eventing mechanism than).

I believe that IMatch avoids the problem by delaying its investigation of a File/Directory event which “lets the dust settle” but actually I believe that the delay was intended to avoid “lock conflicts” with the originating program.

My slightly sanitised log of the events (which still needs some work)

2023-12-20 09:10:43.833482 PFM starting

2023-12-20 09:11:49.153852 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\__TMP__XXYYZZQ__.tmp - FILE - created

2023-12-20 09:11:49.166847 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.186842 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\__TMP__XXYYZZQ__.tmp - FILE - deleted

2023-12-20 09:11:49.206835 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.224829 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG.DOP - FILE - created
2023-12-20 09:11:49.245822 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG.DOP - FILE - modified

2023-12-20 09:11:49.270814 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.298806 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG.DOP - FILE - modified

2023-12-20 09:11:49.319799 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG - FILE - created

2023-12-20 09:11:49.338792 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.358785 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG - FILE - modified

2023-12-20 09:11:49.375781 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\P1107801.JPG - FILE - moved or renamed
2023-12-20 09:11:49.375781 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{37d9fc45-4618-4fcd-80a6-4d750b1c0c28}.JPG - FILE - renamed

2023-12-20 09:11:49.393775 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.413769 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{0b66db34-889e-4812-b531-5ed4866fa561}.JPG - FILE - moved or renamed
2023-12-20 09:11:49.413769 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\P1107801.JPG - FILE - renamed

2023-12-20 09:11:49.432762 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.450758 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\tmp.{37d9fc45-4618-4fcd-80a6-4d750b1c0c28}.JPG - FILE - deleted

2023-12-20 09:11:49.469750 -<DIR> - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV - <DIR> - modified

2023-12-20 09:11:49.487744 - FILE - F:\___BETA DXO PL5 - TESTS\TEST 17 - DIRECTORY NAME CHANGE (SMALL DIRECTORIES)\Test 17 - Run 01 - PL670\Testing FRV\P1107801.JPG - FILE - modified

However, @Stenis I will read these posts more thoroughly later.

PS:- if you find strange DOPs in a folder when using PM then move DxPL to another directory while making PM metadata changes and then let DxPL discover them after the “dust settles”.

[platypus (Canon & Mac (Intel and M1))]

@mikerofoto

@JoPoV

Culling images in photolab is horrible

because it’s not made for that.

DxO markets PhotoLab as an asset manager anyways. Add, remove and change are key functions, which can be done in DPL, albeit without much joy…

If there were an option to stick to built-in previews - argh, there’s that “if” again.

[mikerofoto]

@JoPoV

Anyway I hope PM new licensing system will make some people change their workflow

i’ll use it as long as it work, the last updates were to make it work with apple silicon and sonoma. should work for a least 1 year

[platypus (Canon & Mac (Intel and M1))]

@Stenis

Suddenly synchronization doesn´t seem to work at all now between PM Plus and Photolab version 7.1 and 7.2.

Tried with DPL 7.2.0 build 42 on macS Monterey 12.7.2 and keywords added in Lightroom Classic 12, saved to XMP sidecar files.

DPL 7.2 shows the badge for metadata change and offers the following options, once I clicked in the “S” badge.

With DPL set to autosync keywords, there is no badge, but the new keyword I added in LrC immediately showed in the keyword tool in Photo Library view.

Looks like the sync issue is limited to the WIN version of DPL.
_

Attn @Musashi : While testing, I noticed that the keyword list showed keywords without leading checkboxes. Adding such keywords worked with the context menu though. When I switched images or select all of them, the boxes seemed to toggle on or off - and sometimes, they came up after a delay of a 3-5 seconds.

[Joachim (Joachim Seehusen)]

It works perferctly on my Windows 11 computer. I first selected some old images and added both description/caption and keywords in Photo Mechanic plus. Every change I had made in PM plus popped up in DXO PL 7.1 emmediatly. I installed 7.2, worked as supposed. Then I took some new images, ingested them and filled in caption and keywords. They all popped up in DXO.

[Stenis (Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))]

@mwsilvers

Not that it helps you, but does DxO indicates it supports synchronization with PhotoMechanic Plus 6? I also noticed that PhotoMechanic has itself been updated 3 times since September 20th. I don’t use that software myself, so I have no knowledge regarding what could be causing the issue.

I see in their forums that PM supports PhotoLab but I can’t find anything regarding PhotoLab’s support of PM. My question is if PM was never officially supported by DxO but PM supports PhotoLab and has implemented their own updates during the same time period, why do you characterize this as a DxO bug.?

Mark

Mark, believe me PhotoMechanic has nothing to do with the fact that PL 7.1 and 7.2 doesn´t read the file XMP-metadata properly anymore and that bug have to be fixed and no one else than DXO R&D is responsible for this. The problem is exactly that: It doesn´t read that data at all - even manually, period and I can´t see that this isn´t a bug no matter how thick DXO biased glasses I or you put on.

I have tried it several times: installed 7.1 and synch didn´t work. Installed 7.02 and it worked, Installed 7.2 and synch didn´t work and installed 7.02 and it started to work again. Is it really that likely that the problem is PM Plus??

To my knowledge there has only been one single problem with the PM Plus integration and that was concerning the Edit-function in PM that suddenly stopped working when trying to select and open more than one image at the time with the Edit-function in PM Plus but that was already with Photolab 4. Kirk Baker at Camera Bits fixed that and after that I have never experienced any problems with that function and the integration through “External Search” in Photolab.

DxO PhotoLab and Photo Mechanic Plus (camerabits.com)