I remember this has changed at some point, but I don’t remember what terms were used.
Maybe Noise model was named force details. Or is it new term in v7 ?
It seems it is more sensible with very noisy images :
No noise reduction
noise model -100
noise model 100
noise model 100 + dead pixel 100
But without a real preview window it is too much time consuming, as you can see here, to make good comparison and be usefull - my image is about 1500x this size - (unless screen grabing several zones with different settings like this one or rendering several virtual copies, comparing, then rendering others to refine. But those are not a sustainable options). So settings often remain about default.
I think I read somewhere that this preview problem has been solved in pureraw4. If this is the case, it should also be in v8 (in the hope that the solution if exists is truly effective and manageable).
Need to have a resisable zone in the main window to check (and not this ridiculously small zone - cameras have now 50Mp), and option to cache and cycle several tests with user editable order for comparison.
Best wish : a list growing as those tests are made. Selecting an item in the list instantly displays the corresponding test and recalls associated settings. And a clear list button to free memory of those tests when done.
Yes, “noise model” changed to “force detail”.
In my experience it matters only when there is a lot of noise. It is a balancer between eliminating all of the noise and losing details, or allowing some amount of noise to retain more details.
The typical use case I’ve seen is where obvious fine details are present in a high-ISO shot as this one.
It can be subtle, but notice how the diagonal panel lines are more pronounced with the boosted details. It seems almost not worth the effort, but when shrunk on export it can make the difference between the lines being visible at all or not.
What version number do you use ? on Mac or PC (it seems PC)?
Your image preview seems to have a bigger resolution than mine. As well as the whole Window too.
That’s because it’s a modern Mac. Unlike Microsoft, Apple have figured out how to do “high DPI” displays properly.
Unfortunately the internet hasn’t quite settled on a standard, so sometimes (in fact often) it is displayed as if it were not high dpi.
The short version is Mac screens are measured in “points” and, by default, there are four pixels per point (2x2). Software that knows how to deal with this will render images at twice the resolution. I can also set it to a non-cardinal resolution and the OS will scale to that as well. Kind of like the old CRT days. Even then, software that knows what it’s doing will still render whole pixels, just the overall scale of the image will be different.
I’ve recently tried hooking up a brand new Lenovo ThinkPad with Windows 11 to my Apple Studio Display and it was a tragic mess. Either I get the full 5120x2880 resolution, which at 27" is almost impossible to see, or I could set display scaling to 200% which seemed to work, right up until it turned into a screaming mess. In one case an application displayed a single pop-up window in two different scales. Oh… and that application was written by Microsoft. In the end I just told Windows to drive the display at 2560x1440 and let the display hardware handle the (very straightforward) upscaling.
Thanks for those clear infos on apple high dpi display.
Does it mean photolab renders 4 time more pixels in your preview window than in mine or is its render upscaled ?
( EDIT :
The ratio between your preview size and mine does not seems to be 2 if we compare images posted. Yours seems more than twice mine.
Your image is : 560x530 pixel, mine is 308x332. Not twice the size.
Ok, your screen grab is incomplete, but high of your cropped view is more than twice heigh my uncropped view when I superimpose them :
That’s not my experience, even the own Apple app Preview does not scale properly, look at 100% zoom and see what you get, anything but 100%. Unfortunately scaling is still a mess with both Windows and Mac and on the web even more. It seems it depends mostly on the software developers to implement it properly.
Yes, and differences can best be seen side by side after export.
Here’s a direct comparison between two virtual copies processed with Force Detail set too -100 and +100 respectively. As seen in Lightroom Classic’s compare view at 300%:
The original photo was taken 45 minutes before midnight and camera set to iso 25k. Differences are more apparent if the image is looked at with a dark background and room.
Processed with DeepPRIME XD in PhotoLab 7.8.1 on macOS 14.6.1
So far, I’ve never bothered with the force details slider, but I expect the slider to be near +100 (yes, plus 100) a lot more in the near future.