Automatic recognition of camera model on import

MarieDxO staff

mar '20

Hello @jemadsen,

Category: Camera body in the Color / Color rendering is often misunderstood. Its purpose is to provide possibility to apply a rendering of another camera than the one you used to shoot your photo.
Mike1 is correct, if you select a color rendering with your camera in the label it won’t apply anything. It’s meant to be able to harmonize a set of photos taken with different cameras.

Regards,
Marie

This is a very interesting answer really from one of the DXO staff members Marie.

Some years ago when my Sony A7 IV was new we in Sweden got it much earlier than they did for example in the US, and that caused a real problem for me since it took DXO no less than six month to fix us a camera profile for A7 IV. Ad we often do some of us we solved it while waiting by rename the model code in the files with a HEX-editor.

It is and was completely impossible for me to understand why it is/was possible and perfectly fine to select another profile when using a proper A7 III (yes I can change to a profile for a Z7 even if I want) but was not allowed to open an A7 IV and then select for exemple the A7 III-profile instead. In the latter case all users with new cameras are locked out because we try to open a file that is not yet supported of Photolab. Can anyone like @Marie try to explain this for me?? Some people have tried to convert to DNG too but even DNG is not allowed for unsupported file types.

Personally, I think this just has to be a deal breaker for professionals to use Photolab professionally. This is really to expose DXO for a totally unnecessary self-harming. DXO has a lot going for it with Photolab, but this is not, sorry to say, one of the more useful features of the product but get me right.

… but get me right, I´m not against using your camera profiles but I just can´t accept that this profiles logic is locking users out from the possibility to use a product they have payed the license fee to use.