Differences Win / Mac

[Franky (Frank Legame - Win 10 - PL7 - FP7 - VP4 - NC6 - Sony α)]

Hi,

What if we helped DxO identify the differences between Win and Mac ?

After a long time without activity on this post, I will continue, please help me update if there have been changes with the last versions.

Not present in Win

• Add items on palets with icon at the extreme right in the title bar
• Rename virtual copie
• The Advanced History is not saved after relaunch
• The option grid color
• Be able to move pallets between other pallets and not just after
• Adjustments with up / down arrows for local adjustements
• A floating palette visible in the PhotoLibrary tab (camera settings, arrows to navigate and trash)
• The brush floating panel for repair tool
• The brush floating panel for local settings
• The check box for “disable automatic update checking”
• A compare tool, before and after images together with slider in customize tab
• There is no distance reading on Sony E lenses
• Not status of optics module
• Focal Distance and Focus Distance sliders are automatically displayed
• The program selects the last image edited at the opening of a session

Not present in Mac

• In source browser, no right click for create, rename and open a folder in finder.
• A compare tool, images side by side
• Delete icon on thumbnail
• Image status information on thumbnail - Image correction has been modified after export
• Can’t set database location in preferences
• Focal Distance and Focus Distance sliders are permanently displayed
• Zoom value change while cropping ( add in v6.2 )

Different between Win and Mac

• The switch to display only active tools (blue on Mac, gray on PC)
• Organisation the menus and shorcuts
• Undo is managed differently on Mac or Windows

Please tell me what you found as a difference, I will update the list, thanks

[noname (Captain Obvious)]

@Franky

There is no distance reading on Sony E lenses

are you saying that DxO PL6 does read focusing distance from .ARW raw files in Mac version, but not in Windows ?

[Franky (Frank Legame - Win 10 - PL7 - FP7 - VP4 - NC6 - Sony α)]

Yes from what I understood, but a Mac users can confirm.

[noname (Captain Obvious)]

`Curiouser and curiouser !’ cried Alice

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

@Franky

Mac users can confirm

Post an image file for us to check.

[John7 (John Barrett)]

I posted one at the start of this PL not reading distance from Sony ARW

[noname (Captain Obvious)]

@platypus

Post an image file for us to check.

any Sony .ARW from dpreview will do

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

DPL 6.7 on macOS does not read the distance either.

This is what DPL shows with a module installed:

Distance is not recognised and the slider is activated.

Without a module, DPL shows this:

The slider is inactive, there’s no module anyway

Did another test, read about it here:

PL not reading distance from Sony ARW

Checked with another ILCE-6400 file from preview.com and found that it does not read distance either. Testing this, I found the following The distance slider has no handle No matter the distance range I select in the distance tool, DPL cannot fully correct distortions Distance is initially set to 128m, but will not exceed 60m, even when I select the deepest range offered.

[noname (Captain Obvious)]

at least the code base OK - because it will be too strange even for DxO to differ between platforms in this matter … the situation with Fuji raw files and lenses like 35mm ( where distortion is visibly different based on variation in focusing distance ) is much worse - there is no way to manually fix the problem like with Sony by correcting DOP files …

[John7 (John Barrett)]

It looks like we do have one less Win Mac difference, they just need to fix the ability of PL to read the distance in both program’s again. Support have again passed it back to the developer but I suspect neather program will get distance back very soon if they have to look.for distance information in a diffrent way, as done by other program’s that can get it with no problem

[gerarto]

@Franky

Hi,
…

• There is no distance reading on Sony E lenses
  …

Under Windows, the absence of shooting distance is not systematic: for some lenses, the distance is indeed found.

[Franky (Frank Legame - Win 10 - PL7 - FP7 - VP4 - NC6 - Sony α)]

@gerarto

Under Windows, the absence of shooting distance is not systematic: for some lenses, the distance is indeed found.

Ok I just checked and whatever the lens, I’m still on “infinite”.
Should this be dependent on the camera + lens couple too ?

[John7 (John Barrett)]

I found one kit lense it works on but with 5 other’s
not. It used to work but it was taken off rather than DXO make some changes as they said there were problems. Nothing like the problems for the lense users them not geting the distance working again.

[Franky (Frank Legame - Win 10 - PL7 - FP7 - VP4 - NC6 - Sony α)]

@John7

I found one kit lense it works on but with 5 other’s

Which ones work or not ?
What is your camera ?

[John7 (John Barrett)]

I have a6000 and a64000. The only lenses I found to work is Sonykit lense 55-210 and Tamron 11-20. Not working are Sony 90mm macro, 70-350, 16-70 my wife had some but as she got rid of her camera and lenses I don’t have a record of them but there was a Sony short macro, kit 16-50 that didn’t work and a longer one.

[JoJu (Joachim)]

@Franky

Should this be dependent on the camera + lens couple too ?

Yes. Not all cameras provide recording a distance, no matter which lens. And likewise, not all lenses (especially the manual ones, and here the contactless Laowas and the like) can measure the distance of the focus unit and give the data towards the camera. Usually the lenses with focus limiter have some sort of distance estimation, else the limiter would be pointless.

Also, although some “distance readouts” provide a number with 4 or more digits behind the decimal, these values still are estimations, approximated values. And as it is in the EXIF jungle, there are more than one values. Had to use the PC apps in the office:

Left Affinity Photo, Right Adobe Bridge:

Subject distance in AP is “more precise”, at least delivers one digit more right of the decimal.
XMP has in AP the same value, whereas Bridge’s “Distance range to the subject” is rather clueless.

I had to check 5 different cameras to find one deliveringa value.

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

@Franky

Should this be dependent on the camera + lens couple too ?

Short answer

• Yes

Long answer

• Lens and body talk to each other. Understanding can be limited due to different firmware versions used in the lens and the body. I’ve seen such differences in files written by my old Canon 5D when I used it with lenses that had been released after the latest camera firmware release date. Newer cameras and firmware versions can fill such gaps, but not all manufacturers provide updates for older bodies.

Nevertheless, this will affect PhotoLab independently on both Win and Mac platforms.

[JoJu (Joachim)]

@platypus

but not all manufacturers provide updates for older bodies.

And for the lenses (at least the genuine ones) it’s even worse.

[noname (Captain Obvious)]

@gerarto

Under Windows, the absence of shooting distance is not systematic: for some lenses, the distance is indeed found.

reading focusing distance shall depend on camera model - firmware writes ( or not ) that info in the same tag for a given camera model regardless of the lens ( that can be checked using exiftool - worst case if it is some 3rd party lens that can’t properly communicate w/ the body there will be no real data in that tag )… now if DxO PL6 for a given camera model can read -OR- not the data from that tag based on DxO body+lens module installed then it is a rather odd call on their part

[noname (Captain Obvious)]

@JoJu

Left Affinity Photo, Right Adobe Bridge:

they do round up data from that tag… the proper way is to use exiftool to see the exact value…