click → “my hand”
or at the bottom right corner
Thanks for that! Back to familiar territory.
A little update on this one.
Work/life commitments have seriously limited my time to play around with PL9 but the brief play I have had leaves me currently with no concerns on the capability of the M4Pro in the configuration I have purchased.
Everything flies along. Noticing no lag/stutter and masks (ai) are quick and responsive.
The only question really is whether the M4 Air with the same ram would have been the same but regardless ultimately the Pro suited me better for the other non ram/chip differences.
Will continue with the trial and experimenting but can see myself returning to the DxO fold again.
The Mac Mini M4Pro doesn’t come with a more powerful processor with more cores, you also get higher internal memory bandwith (120 vs 270GB/sec), faster SSD and TB4 ports instead of TB3.
With the TB4 ports you can connect a dock with additional M2 SSD slots and ports (USB, LAN … This allows you to overcome Mac restrictions in terms of connectivity and storage at a very affordable price with excellent performance. Your Mac mini still remains compact, powerful and energy efficient
Really?? Maybe not always, but I have frequently cursed the huge slowdown when I get into masking a complicated subject, along with other masks.
Often with a bird photo I will have a mask for the bird (AI to start with but often supplemented with brushing), one for everything else, one for the eye, and one or two more for directional lighting effects.
I just opened one I had done earlier in the month. Even the act of doing additional brushing on an AI+brush mask resulted in the brush strokes being rendered only around 3-5 seconds after I make them. After closing the mask edit, I make slider adjustments and they are also delayed by around the same amount of time.
Well with the caveat of me not having had the time to experiment massively yes I have seen zero issues so far but also I haven’t done huge edits on the couple of files I have worked on.
I intend to continue trialling this week and next even though I will miss the Black Friday saving as a result but so far for what I need it seems fine.
Also. I will add that maybe I am experiencing some lag but due to the abysmal performance of my old machine running PL5 then maybe at the moment I am not noticing it but will at some point.
I guess I need to find a file where I can go to town on the masking and see how things re with that then.
Plus the machine is fresh with only the bar minimum I need installed on it which may be helping.
Anyway More testing to be done and I’ll continue to update as I go.
Well maybe I was too hasty!
Found some time to see and play with a couple of shots.
Pre mask/denoise everything is ‘instant’ and no complaints (caveat with these two files).
One file was wildlife the other landscape.
DeepPrime XD2 for both.
Made several adjustments to the landscape photo. Usual levels etc. removed a couple of distractions. Masked the subject (AI) plus linear grad on sky with negative control point where grad touches subject. Finished with a B&W conversion.
Experienced no lag or no noticeable lag at any point and exported in under 4secs.
The wildfire one was more basic but noticed slight lag with the AI mask adjustments. Talking maybe a 1-2sec and then perfectly responsive after that initial lack of.
This shot was edited completely with local masking and noticed the export took longer at 14secs.
So yes. Some lag evident but not in all cases. No lag would be preferable though wouldn’t it?!
As it stands though I am happy enough and hopefully things will only improve.
<Exports taking less than 4mins each (compared to my old machine running PL5) is nice though!>
I don’t care how long the exports take and I can cope with slow rendering of slider changes, but not being able to see brush strokes for 3 seconds, and some of those simply not being recognised is incredibly frustrating.
I’m not sure I can!
I often turn off masking all together if I need to adjust sliders outside of the masking itself, because it slows down that much.
It shouldn’t be this way. Other programs don’t operate so poorly. DxO needs to work on this.