Model Name │ iMac (iMac21,1)
Chip │ Apple M1
Cores │ 8 (4 performance and 4 efficiency)
Memory │ 16 GB
macOS Version │ macOS 14.2.1 (23C71)
Keyboard Maestro version │ 11.0.2
GPU │ Apple M1 (8 cores)
Display │ iMac
Current resolution │ 2240 x 1260 (2,822,400 pixels)
Display │ HISENSE
Current resolution │ 3840 x 2160 (8,294,400 pixels)
Total pixels │ 11,116,800
Test Details │ 100 tests in 50.08 seconds (0.5008 secs/test)
──────────────────────────│─────────────────────────────────────────────────
Find Image On Screen │ 22,196,863.3 pixels per second
Model Name │ MacBook Pro (MacBookPro16,1)
Processor Name │ 8 Core Intel Core i9
CPU │ 2,4 GHz (1 CPU, 8 cores)
Memory │ 64 GB
macOS Version │ macOS 13.6.3 (22G436)
Keyboard Maestro version │ 11.0.2
GPU │ Intel UHD Graphics 630
GPU │ AMD Radeon Pro 5500M
Display │ Color LCD
Current resolution │ 2048 x 1280 (2 621 440 pixels)
Total pixels │ 2 621 440
Test Details │ 100 tests in 8,83 seconds (0,0883 secs/test)
──────────────────────────│─────────────────────────────────────────────────
Find Image On Screen │ 29 700 943,2
I must say I find it odd that your M1 iMac performed this test so much slower than mine and yours Intel Macs, @troy. The M1 iMac's screen resolution have about four times more pixels than my screen resolution, but still. The pixels per second calculation also shows the M1 to be slower than your Intel Macs. EDIT: Or I see now, that you also have an external screen hooked up to your M1 iMac there, which brings your total pixel count up even higher, but still I would have assumed an Apple Silicone Mac should have performed faster.
There also seems to be a slight bug with how my data is displayed. The last line does not come out as complete. Might it have something to do with me living in Norway where we use comma as a decimal symbol (and space/ hard space as thousand separator), instead of the point/dot/period (and comma as thousand separator)? I see a commas showing up as decimal symbols in the second to last line also
EDIT2:
Here are my results (with my UHD OLED connected):
Model Name │ MacBook Pro (MacBookPro16,1)
Processor Name │ 8 Core Intel Core i9
CPU │ 2,4 GHz (1 CPU, 8 cores)
Memory │ 64 GB
macOS Version │ macOS 13.6.3 (22G436)
Keyboard Maestro version │ 11.0.2
GPU │ Intel UHD Graphics 630
GPU │ AMD Radeon Pro 5500M
Display │ Rec. ITU R BT.709 5
Current resolution │ 3840 x 2160 (8 294 400 pixels)
Display │ Color LCD
Current resolution │ 1792 x 1120 (2 007 040 pixels)
Total pixels │ 10 301 440
Test Details │ 100 tests in 38,70 seconds (0,3870 secs/test)
──────────────────────────│─────────────────────────────────────────────────
Find Image On Screen │ 26 621 023,4
Yes, perfectly correct! Only surprised that it would return commas, when I am so used to having to use points/dots/periods instead while using KM and other technical applications. However I do not know how used people from different regions are to looking at commas as a decimal separator though, when comparing results here and such. (I kind of didn't even realise myself at first, that the last line result was in fact a correct result, apart from the missing text at the end.)
So in this case I think I would actually personally prefer it returning the results with the English languages system of number punctuation. (Something it is almost strange for me to admit, as I often criticise how we allow anglicisation to shape allot of our languages evolution.)
That's actually trickier, as I'm using KM's built-in format token and it respects the local setting for separators. To not do that, I'd have to write my own rounding and formatting functions :).
Oj, wow, I actually did not know that this feature changes dots to commas here on my system. Good thing for me to be aware of, as I now know that any formatted calculation will fail for any further calculations on my system. Thanks for pointing this out to me!
Image of how calculations of formatted numbers are dealt with on my system.
Yea, I ran into this with another macro, and asked Peter to put a more-clear note on the time formats wiki pages, which he has now done:
Note that numeric values in Keyboard Maestro allow only “full stop” decimal (.) and no thousand separators (except optional underscores), so the output of this token will likely not be a valid number for a Keyboard Maestro calculation. It should be used only for display purposes.
So I now make a copy of any variable I need to keep using, and format the copy.
