Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
21
Oh, they might have tried to fix it and made it worse instead of fixing it?? Do we really believe that?? Maybe you just did not pay attention when you last used it… or just didn´t use it all that much?
In fact I just don´t understand really why we need anything else than a Local Color Picker. Why two? This is a very good example of the mess DXO now have created for themselves and us users by splitting the tools that often are the same in two. That doesn´t go just for the Color Wheels but for all the tools possible to use in the Local Adjustments.
Just take a look of how it ought to have been designed in Capture One. In CO everything is layers even the picture itself since even the Background is a layer. With a design like that all relevant tools works in all layers. No need for global and local sides. No need for strange and confusing work arounds from one side to another. Any color pick can also be turned into a layer of its own if you please for further refinement in a single process.
No wonder an R&D-team like DXO:s gets exhausted having to clean up the mess after bolting on the Control Point System to the old Optics Pro in order to give Photolab a set of “Local Adjustment”-tools in one “quick and messy” blow. First they cut some corners with Optics Pro and now they still have to face the consequences of that move efter pretty many versions in Photolab … and it doesn´t work all that good I´m afraid I have to conclude. Here we now seem to be stuck with these really inefficient work around solutions, instead of designing an effective and productive workflow they pretty easily could have given us from the start.
We have an old proverb saying something like: “If the head is weak, the body suffers”
Photolab software architecture seems very hard to manage (for devs) …
And this smells bad.
1 Like
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
23
Why should that be the only option??
We have lived for many decades now with companies producing all sorts of software without having to jeopardizing the quality. Sometimes there have been problems and that we are used to but not so when these design flaws are neglected despite the users have given them all the feedback needed to fix it.
If DXO shall survive they have to deliver and if they can´t with the fundings they rely on selling “single copies” once a year they will have to do like everybody else. This business model of theirs is very dependent on that they really succeed in delivering new versions with new attractice productivity tools that will make people upgrade. If they fail to do that it will be the end of it. Version 7 is not a success it is a failure so far. DXO have to remake it and make it right before people will upgrade to any greater extent.
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
24
Indeed. A poor architecture is costly to maintain and more than one IT-software product have been redesigned pretty much from scratch when it gets to inefficient and costly to just go on as is.
I would hope for some fixes before then as I’ve bought v7 already and if there isn’t anything substantial, I’ll be very hesitant to give them any more money.
Back in the old days when I was starting out with DxO Optics Pro 8, the software was perhaps more basic but everything worked as it should. Incrementally, more functions were added and they were gratefully received.
Already though, I was hoping for attention to the basic feature set - grid settings, keyboard shortcuts and so on. Still waiting and now there are extra hopes like having local adjustment curves.
However, it seems that DxO have bitten off more than they can chew and engaging with the community 's issues with local adjustment functionality is beyond them. Perhaps I’ll be pleasantly surprised. Go on DxO, surprise me!
Actually, I used it extensively before and right after it was released. I just haven’t used very much since then. But I can tell you as an absolute fact that at an earlier time adjustments to the global HSL wheel using the color picker resulted in a virtually identical selection. I discussed it at length at the time which is how we discovered that the behavior of the Mac version was different.
one for main adjustment and the other is in the local adjustment for where it’s needed, just sad they haven’t thought of the picker for the local adjustment. hopefully on the work now coming in next update… before christmas?
yes, that should had been the way to go, but they went the old way of Nik went, Control Point System.
things are getting harder as time goes, nothing is cheap anymore, nothing is fully perfect when launch (that i can think of, in many domain), and probably why everyone wants to go subscription.
How could they not have thought of it ?
It is a basic feature when it comes to select any hue, value or color.
And this already exists in the global HSL wheel.
Hard to not think about it.
I’m more inclined to think they didn’t have time to finish this tool because they really have rewritten part of the software in order to be more efficient, and that they need time to write every tool at this new “standard”. It’s my optimistic side.
Knowing what a dead line means, I understand sometime some shortcuts must be taken.
well… there was a lot from DxO this year, PL7, Nik 6, FP7, pureRAW 3. all with major updates… so people post on this forum with what’s wrong and not working with their new release.
I agree with your sentiments. A couple of thoughts:
PureRaw is ~1/2 cost of PL7 (less if you include FP add-in). With no stats to back this up, I suspect the PureRaw market is more than 2x the PL market considering all the LRC and CO owners using PureRaw. This could be where DXO is putting its major effort.
If the users of this forum reflect the views of most PL7 users, then there is a good bit of dissatisfaction with the unpolished PL7 release. I see no reason DXO cannot communicate what fixes they plan to (or are are considering) implement in much the same way CO does on the feature request forum. Otherwise, people will fill in the blanks, usually with negative comments.
It is a weekend but in general I agree the DxO policy of ignoring most of this forum has become nearly total since the shambles of 7 and ransom program. It has just fueled the comments here and on other fourms so had been a total failure if they want to limit a bad imige. Now a late December update adds to the flames of lack of any feedback on sorting out 7.
It viewed as late as there are so many outstanding problems with 7 and PL usually gets an update towards the end of a week that would put it right on the Christmas break. Given how most firms cease work for a long time between then and the new year any bugs in a new version will not be fixed for some time. Hence many see the December update as late (indeed as are the 7 fixes that are now some months old now).
Stenis
(Sten-Åke Sändh (Sony, Win 11, PL 6, CO 16, PM Plus 6, XnView))
37
What most companies use to do when they release a new version is to focus on the feed back that always comes when people start to use the software. … and they have had plenty of time to correct the most obvious flaws, haven´t they?
I’m sorry, I must be missing something, what December update? My Windows version of PL7 has not had a ‘December update’. It updated from 7.0 to 7.1 way back in November and when I check for updates now, it says there is no update.
