Based on their marketing blurb, I am SO glad DxO has finally implemented HDR Merge, Panorama Stitching, and Focus Stacking… they did, right?
And you can adjust blue/yellow, green/magenta tint in JPEGs and TIFFs… right?
And surely we can finally develop any and all DNGs… right?
And the option to manually select lens profiles for manual/old/incorrectly identified lenses too, didn’t they?
Allow custom hotkey mapping?
Aah but it’s not like all of these requests have been here for years… have they?
What complete workflow? My workflow includes freeware programs that brilliantly surpass DxO’s inexcusable lack of functionality: IrfanView + FastStone for quick viewing/culling/proper comparing of images, Microsoft Image Composite Editor for panoramas, Sequator for stacking, OM Workspace/GIMP for frame merging [focus or DR].
There has to be some French law for false advertising…
Are you happy with how (a few) other RAW development tools handle HDR merging, focus stacking, and pano stitching? Some people are - I’ve not been impressed. I use dedicated tools for those functions, which I only had to buy once and for not much money. If DxO implements those in PhotoLab, it will be at the expense of other things they could add. Actually, DxO already has HDR Efex Pro for one of those tasks, and I find it to have been broken since DxO acquired it from Google. They have yet to fix the problems I’ve had which make it unusable for me.
While I agree with your complaints, DxO developers have explained why PhotoLab lacks these capabilities. I think you should take it up with them. Or just move on with what makes you happy.
I wish I knew why DxO still hasn’t implemented this. I suppose it’s to prevent conflicts with new functions that DxO adds in the future. Or it’s just to simplify their jobs. You can vote for remappable keyboard shortcuts here:
(Very few feature requests have received as many votes. I’ll bet it can receive still more.)
Yes, I’ve posted this before. That’s exactly the reason of my rant, and I continue to do it because it’s the only way to bring attention to these issues that DxO hasn’t addressed for so long. Every year it’s the same story. This time I didn’t even bother to link all the other threads [it’s not just me that’s pointing out these issues].
Yes - Affinity and Adobe do a good job. Are they as good as specialised tools? Maybe not, but the features are there and they do work. DxO doesn’t have any of them, so it’s not even a potential “complete workflow”, which then makes it not optional, but mandatory to buy/use other programs, creating a disjointed and un-streamlined workflow by default.
On tint, there are threads and threads and it boils down to the devs saying “this is the way we want to do it, whether people like it or not”, which is a very, very paying-customer-unfriendly attitude.
Thanks for linking the last one! I had voted for other threads that ask for the same thing [custom keybinding] but not that particular one. Voted!
Well next time you decide to do this you should make it a bit more complete and add the other 20 or 30 issues with a wide variety of existing features that need to be addressed.
Ah thanks, I did see that post, but it’s not what’s needed.
I mean, it can be done, sure, and I know how to use curves, but that’s not really their purpose. Curves are used once colour temperature/white balance is correct, and then curves come in. Plus this is a workaround that requires studying a tutorial vs using 2 simple sliders that are arbitrarily taken out. So as a community workaround, it helps, but DxO should enable the proper tools to ease our workflow… not force us to jump through hoops.
