I’m currently on PL8 (so an AI masking ‘noob’) so this is probably operator error, but I am trying to select all skin so I can invert the selection and apply ClearView everywhere but the skin.
I am trying to follow the tutorial about AI masking at Learn DxO PhotoLab 10: tutorials and support - DxO and I realize my problem is that there is no mode bar at the bottom of the image when I go to local adjustments and select AI masking. It doesn’t appear when I press the ‘+’ to create a new mask.
This is on Win 10, PC meets the requirements specs (AMD Ryzen 7 9700X, 32G DDR5, Radeon RX 9070 16GB GDDR6, 8+TB free space) and yes I know how to submit a ticket - but I’m enough of a noob here that I’m not at all sure it is a bug. Sigh.
Anyone care to point out what step I’ve missed? Thanks!
Please note, the videos were made with Mac and the ergonomics may be different with Win.
In this case the bar you describe is located at the top left of the image.
As usual there are a lot of difference between the two. Given its thought Windows users are a significant majority they really should use it for demos. At least then fewer customers would have this problem that always effecting windows users
lmolter54
(Larry [Nikon D750, Mac Mini M2 Pro, Hobbyist])
4
Yes, but, how many different variables are there? CPUs, GPUs, Video cards, etc.? The Mac architecture is far more standardized.
The computers may be more variable butvyhats not what the demos are about its the program. There are big differences between Mac and Windows versions that always causes issues for many Windows users who make up the majority of customers.
lmolter54
(Larry [Nikon D750, Mac Mini M2 Pro, Hobbyist])
6
I was thinking that creating a product to work seamlessly across all the variables encountered in the WidowsVerse is a major undertaking; hence occasional issues with certain combinations of CPU and GPUs. That’s all I meant. No knocks on Windows users.
mwsilvers
(Mark - New Jersey, USA, Win10, RTX 4060, PL9, FP8, VP5, Nikon Zf )
7
That standardization comes at a cost with fewer choices that tend to be more expensive and are far less configurable. I don’t own or use a Mac or an iPhone precisely because of the very limited configurability of those devices compared to Windows machines and Android phones. Mac and iPhone users obviously don’t mind the limited flexibility. In the end, It is great there are devices available that meet the use cases of diverse groups of end-users.
Mark
lmolter54
(Larry [Nikon D750, Mac Mini M2 Pro, Hobbyist])
8
In retrospect, I may have assumed things that are not true. PhotoLab is an application, and as such talks to the operating system through dedicated APIs for memory management and graphics among other things. The idiosyncrasies of the various video cards and such are handled by the drivers within the Windows OS, so my statement about it being more difficult to develop Windows apps to accommodate the myriad of different hardware versus MAC OS apps is unfounded methinks.
I use softwares much more complex than photolab. They work seemless on any (powerfull enough) PC (and on mac and linux).
But yes, it seems development is more and more complicated in the field of graphics : friends who work a in major game company (4 years to create a game with hundreds of people - not to mention the delays) said me it is a lot more expensive to create games now than just before because thing become more and more complex at the gpu level (but this is video game, and they have to run on computers and video game consoles, so more things to handle).
