{"id":24702,"date":"2021-11-06T14:57:07","date_gmt":"2021-11-06T21:57:07","guid":{"rendered":"https:\/\/www.podfeet.com\/blog\/?p=24702"},"modified":"2021-11-06T16:41:40","modified_gmt":"2021-11-06T23:41:40","slug":"m1-max-mac-musings","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2021\/11\/m1-max-mac-musings\/","title":{"rendered":"More M1 Max Mac Musings"},"content":{"rendered":"<p>Last week I gave you a few early musings on the M1 Max Macs and this week I\u2019d like to give you a few more. There&#8217;s nothing super unexpected but so many things that have delighted me.<\/p>\n<h2>Speed<\/h2>\n<aside>\n<strong>Optional Math Explanation:<\/strong>You might be wondering about how I calculated &#8220;faster&#8221;. Steve and I both have Masters in engineering and yet we still had to spend about a half hour debating how to correctly calculate this. We didn&#8217;t just compare the times of the operations, because speed should be &#8220;something per time&#8221;, not just time. For the video rendering calculation we worked with &#8220;rendered the video in X time&#8221;. The math would then be:<\/p>\n<ul>\n<li>Intel speed is then 1\/18:52 = 1\/18.9 = .05 renders\/time<\/li>\n<li>M1 Max speed is 1\/8:50 = 1\/8.8 = .11 renders\/time<\/li>\n<li>The % faster is then (.11-.05)\/.05 = 114%<\/li>\n<li>AKA the M1 Max performed one render 114% faster than the Intel<\/li>\n<\/ul>\n<\/aside>\n<p>I finally got a chance to do a couple of speed tests.<\/p>\n<p>My baseline machine is a 2019 16\u201d Intel quad-core i9 with 64GB of RAM, so no slouch on its own.  My new machine is a 2021 M1 Max 14\u201d with a 10-core CPU and 32-core GPU and 64GB of RAM.<\/p>\n<p>The most impressive test was transcoding my latest video tutorial for ScreenCastsOnline.  The native ScreenFlow file was just under a TB and I exported it to an mp4.<\/p>\n<p>The Intel machine took just under 19 minutes to export the file, and the M1 Max took a little under 9 minutes. If my cipherin\u2019 is correct, that means the M1 Max was 114% faster than the Intel, or slightly more than twice as fast as the Intel.  If time is money for you, that\u2019s an impressive number.<\/p>\n<p>A nice little surprise is how fast apps launch. For the most part, they weren\u2019t slow before, but because they launch so quickly now, I am more likely to quit and reopen them than I am to just leave everything running.  I always blamed my giant Photos library (86,260 as of last count) for why Photos took so long to launch but on the M1 Max, it opens so fast that I don\u2019t mind quitting and reopening it.<\/p>\n<p>This got me to thinking. If you\u2019re trying to choose a configuration and you\u2019re waffling between RAM sizes, and the reason you want more RAM is because you like to keep a lot of apps running concurrently, maybe you don&#8217;t need as much RAM if you can quit and reopen them super fast.  If your RAM needs are because you run high-end applications with giant files, then this observation has no bearing on your decision.<\/p>\n<h3>Launch Times<\/h3>\n<p>The race for the slowest app to launch on my computers is between all of the Affinity products (Affinity Photo, Affinity Designer, Affinity Publisher) and Excel. It\u2019s possible all of the Office 365 apps are slow but I only install Excel so I can\u2019t speak definitively on that.<\/p>\n<p>Affinity Designer launches 116% faster on the M1 Max than it did on the Intel, which matches pretty close to the 114% improvement in video transcoding observation. Here\u2019s the bad news: on the M1 Max Affinity Designer still took nearly 19 seconds to launch!  That is a LOT of dock bounces. It\u2019s better than the nearly 39 seconds it took on my Intel, but still, that\u2019s way too long.<\/p>\n<p>I ran some test with similar results on Affinity Photo and sent them to Serif, the makers of the Affinity products, asking them what the heck is going on.  I got a very quick (and more importantly encouraging) response back from Dan at Serif:<\/p>\n<blockquote><p>\n  Our developers have identified a change within MacOS that started in Big Sur and has been carried to Monterey &#8211; this was a security change in Apple&#8217;s system that affects how &#8216;just in time&#8217; (JIT runtime) apps are checked, and Affinity currently uses the JIT runtime method.<br \/>\n  \u200b<br \/>\n  We&#8217;re currently working to hopefully release a beta version shortly that will no longer use this method and this should hopefully resolve the slow loading of the apps for our customers.\n<\/p><\/blockquote>\n<p>While that&#8217;s &#8220;hopeful&#8221; it does bother me that they&#8217;ve gone over a year now with this abysmal launch time and have only now just figured out &#8220;hopefully&#8221; how to fix it. I offered to beta test and &#8220;hopefully&#8221; they&#8217;ll take me up on it!<\/p>\n<p>While Affinity products did win the contest for slowest apps to launch, Excel took an impressive second place. It takes 15 seconds to launch on the Intel Mac, and around 7 seconds on the M1 Max. That speed up with the M1 Max was 118% faster, which is curiously right in line with the other two measurements.  But still, 7 seconds to launch on one of the fastest Macs on the planet?  What gives, Microsoft???<\/p>\n<p>There\u2019s another category of apps that is still really slow to launch and it\u2019s <em>some<\/em> Electron apps.  As you may already know, Electron is a technology to provide cross-platform support with essentially web apps. My observations on speed prove that it can be done well, done ok, or done poorly.  1Password is an example of how to do it right because it launches instantaneously and all operations using the app are lickety-split. They say it has something to do with their development using Rust, but all I know is it&#8217;s speedy.<\/p>\n<p>My development environment Visual Studio Code is pretty darn fast too, but GitKraken, one of the version control apps I use when coding is like watching grass grow while you wait for it to finish opening up a repo.<\/p>\n<p>Folge for documentation with screenshots and annotations and text is kind of in the middle in terms of launch performance. It&#8217;s not snappy, but I don\u2019t want to go take a walk around the block while I wait for it either. Joplin, my new favorite note-taking app is a little sluggish but I can stand it.<\/p>\n<p>There are good Electron apps and bad Electron apps so blaming the technology alone is probably not valid, and it was interesting to me that switching to this new hardware didn&#8217;t substantially affect the performance of the sluggish ones.<\/p>\n<h2>Display<\/h2>\n<p>When Apple announced the new 14 and 16\u201d MacBook Pros, they went on and on about the new display.  I don\u2019t know about you, but my eyes kind of glaze over on talk of 1000 nits of sustained brightness, 1600 nits of peak brightness, 10,000 mini-LEDs, 1M:1 contrast ratio, and a <em>billion<\/em> colors. What I hear is \u201cblah blah blah it\u2019s amazing.\u201d<\/p>\n<p>To combat this spec-fatigue, Apple is very good at is coming up with marketing terms that are memorable.  Remember years ago when they talked about going to higher resolution and our ears glazed over, but then they called it \u201cRetina\u201d? We scoffed at the term at first, but the term really stuck and we could tell at a glance what was a Retina display and what was not.<\/p>\n<figure style=\"float: right; margin-left: 10px\"><img decoding=\"async\" src=\"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2021\/11\/M1-Max-Display-Set-to-P3-1600-nits.png\" alt=\"M1 Max Display Set to P3 1600 nits\" title=\"#title#\" width=\"450 \" height=\"183\"><figcaption style=\"text-align:center\">M1 Max Display Set to P3-1600 nits<\/figcaption><\/figure>\n<p>During the \u201cUnleashed.\u201d Event they referred to the display on the new M1 Pro Max Macs as \u201cLiquid Retina XDR\u201d.  That got me very excited because Liquid Retina XDR is what they call the very expensive Pro Display XDR display.  I was skeptical that these new laptops would really look as good as that. I&#8217;m not a display fanatic but since I have a Pro Display XDR (because my husband is crazy), I can make some comparisons.<\/p>\n<p>Remember buried in the stream of tech specs about the new MacBook Pros they talked about nits of brightness and peak brightness?  That&#8217;s one place I can describe a difference.<\/p>\n<p>The 2019 16&#8243; MacBook Pro has 500 nits of brightness. The M1 Max has 1000 nits of brightness and if the Display Preferences are set to P3-1600 nits, that means it will go up to a peak of 1600.  Ok, that still sounds like a pile of specs. What is the real-world case where you would see this difference?  The peak brightness is only reached on high dynamic range content and it hits 1600 nits only on the highlights of the photo or video.<\/p>\n<figure style=\"float: left; margin-right: 10px\"><img decoding=\"async\" src=\"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2021\/11\/dew-drop-lines-on-leaf.jpeg\" alt=\"Dewdrop lines on leaf\" title=\"#title#\" width=\"450 \" height=\"600\"><figcaption style=\"text-align:center\">Photo I Used to Compare High Dynamic Range<\/figcaption><\/figure>\n<p>I brought up a photo I took with the iPhone 13 Pro on the Intel and M1 Macs side by side.  The image is of a water droplet on a leaf, and there&#8217;s a bright area in the center of the water droplet. On the 14&#8243; M1, that area of light is far brighter than it is on the previous screen and it looks kind of grey and bland on the 500 nit screen. It doesn&#8217;t look bad on the older screen but it really pops on the new one.<\/p>\n<p>The effect is even more dramatic in video.  If you have an iPhone X or later, you can capture and view HDR video. If you have your phone set to light mode, when you look at photos or videos that are not full screen, you&#8217;ll see white bars either on the sides or top and bottom.<\/p>\n<p>When you start playback of an HDR video, suddenly the video kind of pops out at you and gets super bright.  The white bars will look like the phone actually turned them grey. In fact, your brain probably won&#8217;t believe that they didn&#8217;t get darkened, but it&#8217;s an optical illusion because the white parts of your video playback are just so much brighter.<\/p>\n<p>This same effect happens now on the M1 Pro\/Max Mac displays. The other day I was in our dimly-lit TV room and I brought up an HDR video I had taken on the iPhone and it lit up the entire room! I\u2019m not joking, I saw the light go everywhere it was so bright! I showed Steve the effect, flipping from some normal photo in my library to this HDR video and he was amazed at the brightness as well.<\/p>\n<p>I was hoping to report on how amazing Pro Motion is on the new Mac &#8211; that&#8217;s Apple&#8217;s marketing term for an adjustable refresh rate up to 120Hz. I sat there for quite a while scrolling up and down on both of my laptops side-by-side and I could not tell the difference. It wasn&#8217;t until Saturday that I found out that <a href=\"https:\/\/9to5mac.com\/2021\/10\/29\/not-so-smooth-scrolling-macbook-pro\/\" rel=\"noopener\" target=\"_blank\">according to 9to5 Mac<\/a>, most apps don&#8217;t support ProMotion yet &#8211; including Safari! Now I&#8217;ve got a dollar that says I still won&#8217;t be able to tell the difference even when it is available.<\/p>\n<p>What I should notice on the new M1 Max is the higher screen resolution. It went from 227 pixels per inch up to 254 PPI, but even with my bionic human-made lens eyes I still can\u2019t tell the difference.  The Pro Display XDR is &#8220;only&#8221; 218 PPI but I really can&#8217;t see any difference in jagged edges on crisp text between the 2019 16&#8243;, the XDR and the 2021 14&#8243;. Maybe I&#8217;m just not worthy of these displays.<\/p>\n<p>One minor place where the M1s outperform in the display area is how quickly they can change Display preferences. If you connect a second display to your Mac, you\u2019ll often want to rearrange the positioning of the displays with respect to each other.  On an Intel Mac, when you drag one representation of a display into a new position and let go, both of displays will turn black for a second, and then they\u2019ll come back in the new position.<\/p>\n<figure style=\"float: center; margin: 10px\"><img decoding=\"async\" src=\"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2021\/11\/Displays-Preferences.png\" alt=\"Displays Preferences Showing Arrangement\" title=\"#title#\" width=\"600 \" height=\"\"><figcaption style=\"text-align:center\">Displays Preferences Showing Arrangement<\/figcaption><\/figure>\n<p>With an M1 (regular, Pro or Max), there simply is no black screen blink.  It just changes the positions. The first time I did it, I had only made a minor adjustment and I thought it actually didn\u2019t work because I didn\u2019t see the blink! I know this isn\u2019t a huge deal but how many times have you had the displays arranged <em>almost<\/em> right but you put up with a corner where your cursor didn\u2019t slide over and would get stuck because the process of fixing it was just a little bit annoying?<\/p>\n<h2>Camera<\/h2>\n<p>One of the more minor upgrades with the Pro\/Max configurations is the new camera system.  While it only went from 720p to 1080p, Apple touted it as a much bigger improvement than the resolution alone would imply.<\/p>\n<p>The new camera system has a wider aperture combined with a larger image sensor, both of which mean it should have better low light performance.  With more light, we should get less noise in the image.  Noise is the smudgy look you can get in darker areas, and you\u2019ll see it in weird-looking colored dots where a single-color surface should be seen.<\/p>\n<p>Additionally, Apple said in their press release:<\/p>\n<blockquote><p>\n  Apple\u2019s custom image signal processor, along with the Neural Engine, uses computational video to enhance image quality for sharper video and more natural-looking skin tones on the built-in camera.\n<\/p><\/blockquote>\n<p>It was time for a comparison of the cameras on my two laptops. As a quick test, I set up my studio lighting and took the same photo with my 2019 16\u201d Intel MacBook Pro and my M1 Max both using Photo Booth.  There is no question that the new camera system and associated signal processing is dramatically better.<\/p>\n<figure style=\"float: center; margin: 10px\"><img decoding=\"async\" src=\"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2021\/11\/720p-Camera-from-2019-Intel-MacBook-Pro.jpg\" alt=\"720p Camera from 2019 Intel MacBook Pro\" title=\"#title#\" width=\"800 \" height=\"\"><figcaption style=\"text-align:center\">720p Camera &#8211; 2019 Intel MacBook Pro<\/figcaption><\/figure>\n<figure style=\"float: center; margin: 10px\"><img decoding=\"async\" src=\"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2021\/11\/1080p-Camera-M1-Max-MacBook-Pro.jpg\" alt=\"1080p Camera M1 Max MacBook Pro\" title=\"#title#\" width=\"800 \" height=\"\"><figcaption style=\"text-align:center\">1080p Camera \u2013 2021 M1 Max MacBook Pro<\/figcaption><\/figure>\n<p>The exposure is much better on the new camera, allowing you to see fine details in my hair along with the varied colors of my hair from dark brown to auburn to grey.  The older camera only captured a continuous brown blob with one grey highlight. Sadly both cameras seemed equally capable at capturing the wrinkles in my neck and face.<\/p>\n<p>The vertical blinds behind me in the photo should be a rather continuous tan color, but the older camera is very noisy in the form of lots of purple and green dots. You can also see that same color noise in the chair back behind me.<\/p>\n<p>The new camera more accurately captured the color tone as well. In the older camera, my blue shirt is dark and saturated, which might be a pleasing color to some, but it&#8217;s not the true color of my shirt.  The older camera shows the right side of my face with a dark shadow but the new camera adapted much better to the slightly off-center balance of my lighting setup, leaving my face is far less shadowed.<\/p>\n<p>Across the board, I would say the new camera, while only 1080p, is a massive improvement.<\/p>\n<h2>Keyboard &amp; Touch ID<\/h2>\n<p>I\u2019ve been lucky enough to have Touch ID on my MacBook Pro for the last couple of years, but it has not been as reliable as I would have hoped. I have always assumed it was because I have relatively dry fingers, so a slight lick of my finger would allow me to actually unlock my Mac, unlock 1Password, and <em>sometimes<\/em> would help me authenticate for Apple Pay.  I found myself using my Apple Watch to unlock and pay because it was much more reliable.<\/p>\n<p>I\u2019m not sure what they did differently on Touch ID for the new Macs, but so far, it has been a lick-free experience. One time in the last few weeks it didn\u2019t respond the first time I tried it, and even then I didn\u2019t have to lick, I just tried again and it worked.  It is so reliable now that I authenticate with Touch ID faster than I can on my Apple Watch.<\/p>\n<p>Speaking of the keyboard, I really truly love it. I was a big fan of the very last butterfly keyboard Apple put into their laptops. 2 years and 11 months into AppleCare on my 2016 MacBook Pro, the battery swelled and broke the keyboard and trackpad, so Apple repaired it at their expense. The keyboard they supplied me in October 2019 was fantastic. I actually wasn\u2019t a big fan of the scissors switch keyboard they introduced in 2019 because it took a lot more effort to push the keys.<\/p>\n<p>Keyboards are a very personal preference so I will not say the keyboard on the 14&#8243; MacBook Pro is better than the keyboards, but I personally prefer it to the 2019. I find I\u2019m choosing to type directly on it more often even when I have my beloved Magic Keyboard sitting right next to it.<\/p>\n<p>One more delight with the keyboard &#8211; there\u2019s a dedicated emoji key just like on iOS keyboards. Maybe emoji don\u2019t blow your dress up, but I&#8217;m trying to be like the cool kids and use them from time to time. I mostly use the facepalm emoji every time I do something dumb.  I found it very tedious to scroll through the emoji to find the right one on my 2019 MacBook Pro, even with Touch Bar there to help.<\/p>\n<p>On my previous Mac, I installed a great little app <a href=\"https:\/\/matthewpalmer.net\/rocket\/\" target=\"_blank\" rel=\"noopener\">app called Rocket<\/a> that let me use a trigger character and then start an inline search for emoji. I also experimented with using the Keyboard Viewer and switching to emoji but that was a little bit tedious.<\/p>\n<p>Now with the new Mac, I can hit the emoji key and it automatically launches the keyboard viewer right to emoji search so I can instantly type in the nerdy glasses emoji whenever I need it! &#x1f913; That makes the price of a new MacBook Pro totally justifiable, am I right?<\/p>\n<h2>Migration without Migration Assistant<\/h2>\n<p>This next bit has nothing to do with the model of computer I moved to, but more about the process of moving to a new computer.  You know I\u2019m a big fan of the nuke and pave process around once a year to clean out cruft, and I always do a pure pave when I go to a new computer. By &#8220;pave&#8221; I mean I don&#8217;t use Migration Assistant to move over my apps and settings, and I don&#8217;t even let it move my data. I drag my data over manually.<\/p>\n<p>Doing a clean pave on your first Apple Silicon Mac is really important because the last thing you\u2019d want to do is bring over a bunch of Intel-native apps when Universal versions that run natively on the M1 architecture probably exist.  You could end up running in the Rosetta 2 emulation mode when you could have the light speed of a native app.  Sure you can upgrade after you move but that means leaving cruft around and wasted effort trying to figure out which ones can be native.<\/p>\n<p>As always I\u2019ve been using my Mind Map of Doom (&#x2122;&#xfe0f;Donald Burr) to install all of my apps from scratch and do all of my configuration changes to get things the way I like them. I know this takes a long time, but it helps me <em>know<\/em> my system inside and out.  I do a lot of weird stuff on my Mac so it takes longer than it would for normal people but I still love the process.<\/p>\n<p>The main reason I don&#8217;t even use Migration Assistant to move my data is because of my giant Photos library.  I\u2019m following a process developed with the help of Apple support many years ago. I used to drag my Photos library over to the new Mac, but then iCloud Photo Library would have to check every single photo to see if it had the original yet. The checking process takes far more time than the download process. This would take 3+ weeks and more importantly it would not import any new photos I took with my iPhone during that entire time.<\/p>\n<p>Apple taught me not to drag the library over, but instead to simply start with optimized images. When that\u2019s complete in a day or two, then they told me to turn on the full-sized images.  With good bandwidth, this is a firehose of file downloads. This takes the three-week process down to a matter of days.<\/p>\n<p>This time through the process, the optimized image download seemed to take longer than it has in the past. It&#8217;s tricky these days to figure out how to force the Mac to stay awake 24&#215;7, which has contributed to the longer-than-expected download time.  There is no Energy Saver Preference Pane so I\u2019m learning the new Battery Preference Pane with only limited success.  I did get all the optimized images down in about 5 days, which is longer than I liked. I can live with it since I can play with my library while it churns away in the background. If I needed an old photo, I can still scroll to the time period where I think the image is and start clicking on the blank squares to force specific images to come down.<\/p>\n<p>I switched to the full-size image download in iCloud Photo Library preferences, and they started coming down quickly as expected. It <em>should<\/em> have been done in the usual 3 days, but, it seems to have stalled late on the second day and isn\u2019t changing so I\u2019ve got that to diagnose that pesky problem now. That should keep me entertained for a bit don&#8217;t you think?<\/p>\n<h2>Bottom Line<\/h2>\n<p>The bottom line is that I&#8217;m still besotted with this new Mac and I am so very glad I downsized to 14\u201d. I carry it around the house so much more than I ever did the 16\u201d just because it\u2019s so light and small. Because I have a big screen to attach to when I need real estate, I literally don&#8217;t miss the 16&#8243; size at all. I love typing on it so it\u2019s stealing time from my beloved 12.9\u201d iPad Pro as my couch device too.  Here&#8217;s a bonus prize &#8211; I used to have to very carefully position my 16&#8243; on the 12 South stand so that the boom arm of my mic didn&#8217;t crash into it when I swung it into position.  With the 14&#8243; I&#8217;ve got a good 3&#8243; of clearance so I don&#8217;t have to be quite so careful.<\/p>\n<p>I\u2019ve not found one thing to dislike on the new Mac and everything to love about it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Last week I gave you a few early musings on the M1 Max Macs and this week I\u2019d like to give you a few more. There&#8217;s nothing super unexpected but so many things that have delighted me. Speed Optional Math Explanation:You might be wondering about how I calculated &#8220;faster&#8221;. Steve and I both have Masters [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":24697,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[147],"tags":[4604,4852,51,556],"class_list":["post-24702","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-posts","tag-m1","tag-m1-max","tag-mac","tag-speed"],"jetpack_featured_media_url":"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2021\/11\/M1-Max-Display-Set-to-P3-1600-nits.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/24702","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=24702"}],"version-history":[{"count":5,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/24702\/revisions"}],"predecessor-version":[{"id":24707,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/24702\/revisions\/24707"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media\/24697"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=24702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=24702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=24702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}