Hmm, you’d still have to draw a mask…or you’d get global scope of HSL for that layer…
1 Like
I mean it is just like with all other layers almost. First you create a local layer and then you populate it with for example a color picker. In Capture One though it works inverted. There you can make acolor pick and then turn it into a layer.
In fact there is a possibility even now to create a global all covering “mask” even locally. It is just to select the white ball instead of picking a color.
Thansk for the effort, John! Well done!
3 Likes
Has there been any response anywhere from DxO about the local adjustment shortcomings?
Some hundreds of photos edited with PL7 so far and though I’m used to the ‘quirks’ of the updated tools, it is still considerably slower to use than the previous arrangement. For example, the mask engaging while you try to place or move control points and lines is infuriating.
Has any of this been reported directly as bugs? As much time has passed, it seems to me that DxO have walked away from the mess they’ve imposed upon us.
I am still using 6 even though I have 7 as the local editing is such a mess.
2 Likes
Yes, before it was easy to see the (B&W) mask changes in real time – but now one has to stop & release the mouse button to see the result. And the same ‘disability’ when trying to adjust chrominance and luminance.
1 Like
I am with you on this and will not be upgrading until it is sorted out!
1 Like
Its concerning they appeared to ignore it during BETA so it well be one of the many botched changes that never realy get fixed
Isn’t it strange that DXO missed so much of the problems during the Beta testing that the users here on the Forums saw immdiately the first week after version 7 was released?
What makes you think that any of it was missed during testing? It wasn’t.
Mark
3 Likes
Hi David, I’d be relaxed and am sure they’re monitoring this forum carefully. They will realise that the desire to upgrade is less than it used to be. The price problem and the compulsion to upgrade FP also comes on top of this. There will be a solution at some point. But even if there is: I don’t really need the new features. And I don’t know anyone who has asked for them by the way. In the meantime, I’m happy with 6.11.
(Note: I’m a loyal customer since 2009 DXO OP6 and never skipped an update!)
Meanwhile my (Eilte7 and obligatory FP7) upgrade price is reduced by Black Friday from €248,- to €178,-, still way too expensive, was (about) 69,- usually. But again, would’nt buy in this constitution.
1 Like
I did ask for a few things! I wanted a consistent interface that handles local adjustments like we always have been able to do with the global side. I want a to be able to turn a color pick into a layer and I want a Color Wheel that works like it does globally.
… and I would appreciate a masking- and layer-system llke the one in Capture One.
… and I want to get rid of all these bugs we have got in version 7 and nothing have happened since the release so far. They are just keeping us ghosted without the slightest sign of dialog.
1 Like
As a developer I have never met such a stance among other developers I have met both in the Nordic countries where I have worked, or in the US where I have been on quite a few developer forums and Tech Meet and met developers from all over the globe. I have never met a developer that have let bugs pass that they have been aware of.
Well, then this company is in a lot more severe trouble than even I thought. Releasing a product, you know have serious bugs, is really a sign of severe disrespect for their users and a good recipe for a lot of bad will and even worse disasters. Professional R&D with some kind of self-respect and quality awareness would not allow a release like version 7. If this really is true you say, I’m speechless.
I didn’t read all the points above, but from what I remember following topics which lead to this one, it seems it is more a loss of features and interface feedbacks than bugs.
This suggest (to keep an optimistic outlook) DxO team have completely rewritten some parts of the software and did not have time to put back missing features.
This could be a good thing for future.
2 Likes
There were some poor design choices made in PL 7 Local adjustments that need to be addressed to make using those adjustments faster, more logical and more user friendly, but what Local Adjustment bugs are you referring to?
Mark
… but a local Color Wheel without a color picker ???
That is hard to miss isn´t it??
Exactly!
Mark
1 Like
Why do you think it was missed? It was not a bug, but a design decision. After much discussion about it, it remains unclear whether DxO will eventually add the picker. Some people did not think it was necessary. I do. However, for those using the Windows version of PL 7 there is a work around. Using the global color wheel picker also selects the same area on the local adjustments color wheel. It is inconvenient but it works. Unfortunately, that trick does not work on the Mac version.
Mark
1 Like
It (color picker) is needed there of course (even if there is an uneasy workaround to get the picker here) - and is needed at a lot of other places in photolab too.
Maybe when it will appear again, it will be a part of code thought to be inserted (called) anywhere else it is needed.
1 Like
Really ?
Everywhere a color, a hue, or a value needs to be selected, a color picker should be avalaible (curve tool for instance).
Isn’t that obvious ?
…
2 Likes