It’s done
Pascal
2 Likes
For PhotoLab 6 the following are remaining:
- (Custom) Keyboard shortcuts : while some are available, for me to effectively use any application I need good and preferably customisable keyboard shortcuts. Capture One and Final Cut Pro are gold standards here, almost everything has a shortcut and is user configurable. PhotoLab at the moment is very biased towards mouse users, and also requires extreme precision to hit toggles and sliders.
- Comparing images : sometimes I just want to compare two images side-by-side to figure out which one is the absolute best. PhotoLab offers no easy way to do this.
- Token based file naming : use image metadata or other available variables to name files on import AND export. I currently need to use another app just to achieve this.
- (AI) Intelligent Auto White Balance : white balance is one of the most critical elements for a photo and nowadays it is possible for AI/algorithms to make a pretty good guess. I would like to have this as a starting point. For me it is the key AI/Auto thing missing compared to other software, and one I would expect PhotoLab to do an amazing job at given the results of Prime/Smart Lighting/Clear View.
- Stacking : I would like to be able to stack my virtual copies with the master image to declutter my filmstrip. I also would like a way to name my virtual copies e.g. [master name] [copy title].
- HEIC/HIEF-support : seems to me like this is the image codec of the feature which would give results closer to TIFF files but with much smaller file size. Would love to have this as an export option since I think JPEG is very limited and outdated.
- LUT support : they have become pretty much universal and I think when they would be integrated in the pipeline in a smart way (e.g. preventing blowing out highlights) it could be a game changer, which many people would use since there are so many available for sale/download.
- Support for color labels : I think this is a common standard across applications (extending to the video space) and it would give more flexibility in marking images for individual workflows in addition to the already existing stars. Please also ensure these can be read from and written to .xml metadata.
And I would like to see the following as well by now:
- Native Mac interface : I have recently switched from dual Windows desktop/Mac notebooks to 100% Mac Notebooks. I find the DxO interface styling on Mac outdated, inefficient with space and also not on the same level as the Windows interface which is much more edible. So I would like a redone interface (not necessary location of elements in terms of UX, but mostly styling that is in line with apps like Pixelmator Pro, Capture One and new Lightroom (cloud).
- Full native M1 support : It’s OK to be the last one in the class, but not for too long ;). The performance gains are really remarkable. But good to see that core image processing already uses M1 well trough good use of standard macOS frameworks and APIs.
- AI search : auto-tagging of images underwater for search purposes only. Can be very intelligent e.g. “photos with 2 people, 3 people”, “close-ups of people” etc. Again, no auto-tagging or anything, just improved search to drill down to certain photos.
And from DxO as a company I would like to see the following “Kaizen” gestures:
- Camera and lens updates : support the latest cameras and lenses in the latest version + one version back. This shouldn’t be too much work, will maybe cost some business, but will also buy tons of goodwill from customers and the community.
- Better OS support : support one OS version further back for at least macOS (since Windows has less versions).
3 Likes
Assuming it is not copyrighted by Topaz, I would like the windscreen wiper interface that they have for comparing two images before and after. It is the one advantage that Topaz has for me.
Comme on dit chez nous : « Pourquoi faire simple quand on peut faire compliqué ? »
Voilà qui est curieux et inattendu !!! Ceux qui se sont plaints du non-support de Mojave par PL5 ont pourtant été unanimement considérés ici comme des râleurs pénibles et un peu idiots…
David: PhotoLab has this feature when in Full Screen Viewer mode … via F11.
Is that what you mean ?
John M
1 Like
Now we have keyword and iptc editing and xmp support i am not sure if the present userinterface is sufficient in tagging large amount of images.
Templates and and group stamping features would be neccaserry.
1 Like
Thank you, John! I never used F11, and when I got there, I was reminded that I am useless in understanding what icons signify…
I dont recall reading about this in any user manual – is there one?
I shall explore further.
Best,
David
1 Like
Yes 41 votes one is mine, so i think it’s offious we need it… 
Thank you Pascal for the link to your tuto !
I’m quite a “newbie” with PL5 and didnt realize - understood - at first sight all the possibilities of this new Control Line tool with the luma and chroma adjustments.
It looks very powerful… need some time to manage !
1 Like
Thanks, Wolfgang.
But in Topaz I can do this and make changes without going to full screen. In PL I have no idea what the magnification is, and have to go back and forth to make changes. Another thing I notice in Topaz is that the area to click on to grab the slider is much larger. On the refinement of this particular feature, the competition wins at present.
Support Nikon’s NEF data, please!
Thanks for treating the raw data so nicely, I’m happy to switch off in camera lens correction, which is why I got PL, but I have years of jobs shot with in camera settings that are vital and want to keep using.
What is the point of this request? Nikon NEF files are already supported going back to the D200.
I can confirm this, all my NEF and NRW files are supported.
I worded that poorly. I meant the data contained therein which dictates saturation, contrast etc etc, but sorting this out myself customising PL Presets, referencing from previous work, or more accurately having my assistant wielding a colorimeter across a screen for a few hours.
RAW files do not contain any such data, simply the data recorded from the light falling on the sensor. They don’t even contain white balance.
I’m talking about the whole NEF, which in fact does contain other processing data (in camera settings WB, contrast curve, lens distortion etc), which could be manipulated in their software, in addition to the base RAW file. I sat through a half day lecture with Nikon when they introduced the D3 where they couldnt shut up about how wonderful the damn thing was 
In essence, it’s the data that would automatically fill the Preset parameters in PL.
Ah! You are referring to the fact that the “Picture Settings”, which are applied directly to a JPEG.
What happens is that their own software takes the RAW data in the NEF file and applies it to their rendering of the image.
Personally, I only ever use the flattest of the flat Picture Settings in camera, knowing that that leaves me with the most neutral version of the image that I can then work on in PL.
You can do something similar in the Colour Rendering Palette in the FilmPack add-in to PhotoLab by selecting a DCP profile…
If you don’t find your settings there, you can download Adobe DNG Converter and it will also include all sorts of DCP files for all sorts of cameras…
2 Likes