Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS Monterey 12.4 With Support for Studio Display Webcam Update
- Thread starter MacRumors
- Start date
- Sort by reaction score
HobeSoundDarryl
macrumors G5
USB was working great for me after the White Sierra Cheetah update.
More seriously: I'm hoping hardware connection issues- particularly the aggravating "unexpected ejections" have been dealt with here too. About to test that with my own hardware (AGAIN) right now: Mac Studio Ultra through several brand new cables hooked to an HDD RAID enclosure that remains consistently connected with my Intel Macs running macOS < Big Sur but won't through ANY cable- directly connected (USB-C or USB-A) or through powered hubs, whether allowed to sleep or not. I'm hoping this update finally fixed it and will add an edit line if it did or not soon. It usually only takes up to 3 hours to see "unexpected ejection."
I'm also hoping the promised speeds of jacks and the actual speeds got fixed too.
Both make me feel like there is great opportunity for debugging hardware ports in Monterey.
Update: a whopping 73 minutes later...
Maybe next update
I miss "just works." Still hoping for Snow Monterey at WWDC... maybe 2 years worth of "Snow" bug fixes.
And before I get 10+ posts trying to blame everything but Monterey, I have tested through EVERYTHING to rule out as much as possible that would not be Monterey. Same cable(s) to same drive hooked to other Macs running Mac OS BEFORE Big Sur is perfectly stable. Per searches- including on Apple's own forums- this problem is commonplace with many kinds of enclosures but some work fine, so it's not a problem for all equipment... just some, with no easy way to tell short of hooking things up and seeing what happens. SSD stuff seems to work better than HDDs, HDD RAIDs seem to have more trouble than anything else... but some HDD RAID enclosures seem to work too. Sleep seems to be a strong catalyst but ejections occur without either sleeping too. I've objectively tested through everything and am convinced the problem is Monterey... and probably Big Sur too based on others experiences with the same.
Last edited:
Try this, I found this page which tells you how to increase mouse speed in terminal. It works great for me.https://gadgetstouse.com/blog/2021/06/01/increase-mouse-sensitivity-on-mac-beyond-max/
Updated on 13" MacBook Pro (2016, 2017, and 2018) and MacBook Air (2017, 2018, and 2020). No problem so far.
Follow-up to previous post:
I updated to 12.4 on my MBA, took around 10 minutes to install - pretty quick. iOS 15.5 updated automatically while I was away so I don't know how long it took.
Did NOT fix the "drop shadow" problem (the text normally has a bit of a drop shadow but this is really exaggerated). Here's a screenshot in case anyone's wondering what it looks like (also happens with the Avid Link icon as you can see)
This is when you turn on Do Not Disturb. The Avid icon looks like that no matter what.
I updated to 12.4 on my MBA, took around 10 minutes to install - pretty quick. iOS 15.5 updated automatically while I was away so I don't know how long it took.
Did NOT fix the "drop shadow" problem (the text normally has a bit of a drop shadow but this is really exaggerated). Here's a screenshot in case anyone's wondering what it looks like (also happens with the Avid Link icon as you can see)
This is when you turn on Do Not Disturb. The Avid icon looks like that no matter what.
Attachments
Last edited:
And with this update, Apple has fixed the FireWire/DV video capture bug that was present in version 12.3(.1)!
Even though I very rarely shoot DV/HDV footage nowadays (I usually use my Canon VIXIA HF-R600 camcorder that records higher-quality MP4s onto SD cards that greatly simplify the import process), it's good to know this feature is still available for archiving such tapes. (Here I've got my Canon VIXIA HV40 camcorder hooked up to the FireWire port on my Apple Thunderbolt display, hooked up to my CalDigit TS3-Plus dock (via a Thunderbolt 2-to-3 adapter) hooked to my M1 MacBook Air for use in clamshell mode and whatnot.)
Even though I very rarely shoot DV/HDV footage nowadays (I usually use my Canon VIXIA HF-R600 camcorder that records higher-quality MP4s onto SD cards that greatly simplify the import process), it's good to know this feature is still available for archiving such tapes. (Here I've got my Canon VIXIA HV40 camcorder hooked up to the FireWire port on my Apple Thunderbolt display, hooked up to my CalDigit TS3-Plus dock (via a Thunderbolt 2-to-3 adapter) hooked to my M1 MacBook Air for use in clamshell mode and whatnot.)
Guess I'll waste a few hours to update to 12.4 before wasting a good part of the day to go back to Big Sur because of excessive beach balls vs only after using SMB file/copy on Big Sur. Would be nice if Apple also fixes broken palm rejection that hasn't worked since the product was released over a year ago.
Update: About 45 minutes for ~3GB update so not terrible. Initially, beach balls are less frequent but time will tell. Can still move mouse pointer with meaty palm so still broken.
Update: About 45 minutes for ~3GB update so not terrible. Initially, beach balls are less frequent but time will tell. Can still move mouse pointer with meaty palm so still broken.
Last edited:
Have they fixed any of the usability killing bugs that have existed since 12 on M1?
* Wakes from darkwake due to NUB.SPMISw3IRQ interrupt
* Pinch-zoom randomly stops working
* Programs using OpenGL segfaulting when resizing windows (https://github.com/glfw/glfw/issues/1997)
* AMFId randomly deciding half the time to disallow coredumps for crashed processes (And this isn't a codesigning issue, I shouldn't need to grant task_for_pid to get a coredump for my own compiled binary. Besides, AMFId will sometimes allow the coredump for the exact same binary, so clearly it's a matter of AMFId being cranky)
* (Less significant) sometimes changing AXAPI permissions for an app in system preferences causes all keyboard events to be dropped. It doesn't happen all the time, but you can bet that it will happen right when you're in the middle of trying to debug something important.
It's a good thing I'm not using this as my main dev machine, because otherwise it'd have been chucked out the window long ago.
* Wakes from darkwake due to NUB.SPMISw3IRQ interrupt
* Pinch-zoom randomly stops working
* Programs using OpenGL segfaulting when resizing windows (https://github.com/glfw/glfw/issues/1997)
* AMFId randomly deciding half the time to disallow coredumps for crashed processes (And this isn't a codesigning issue, I shouldn't need to grant task_for_pid to get a coredump for my own compiled binary. Besides, AMFId will sometimes allow the coredump for the exact same binary, so clearly it's a matter of AMFId being cranky)
* (Less significant) sometimes changing AXAPI permissions for an app in system preferences causes all keyboard events to be dropped. It doesn't happen all the time, but you can bet that it will happen right when you're in the middle of trying to debug something important.
It's a good thing I'm not using this as my main dev machine, because otherwise it'd have been chucked out the window long ago.
Last edited:
Keyboard language icon on menu bar is now two letters, as in "US" for English or "ES" for Spanish.
Before the update the icon was a country flag.
Carlos
Before the update the icon was a country flag.
Carlos
USB was working great for me after the White Sierra Cheetah update.
More seriously: I'm hoping hardware connection issues- particularly the aggravating "unexpected ejections" have been dealt with here too. About to test that with my own hardware (AGAIN) right now: Mac Studio Ultra through several brand new cables hooked to an HDD RAID enclosure that remains consistently connected with my Intel Macs running macOS < Big Sur but won't through ANY cable- directly connected (USB-C or USB-A) or through powered hubs, whether allowed to sleep or not. I'm hoping this update finally fixed it and will add an edit line if it did or not soon. It usually only takes up to 3 hours to see "unexpected ejection."
I'm also hoping the promised speeds of jacks and the actual speeds got fixed too.
Both make me feel like there is great opportunity for debugging hardware ports in Monterey.
Update: a whopping 73 minutes later...
Maybe next update
I miss "just works." Still hoping for Snow Monterey at WWDC... maybe 2 years worth of "Snow" bug fixes.
And before I get 10+ posts trying to blame everything but Monterey, I have tested through EVERYTHING to rule out as much as possible that would not be Monterey. Same cable(s) to same drive hooked to other Macs running Mac OS BEFORE Big Sur is perfectly stable. Per searches- including on Apple's own forums- this problem is commonplace with many kinds of enclosures but some work fine, so it's not a problem for all equipment... just some, with no easy way to tell short of hooking things up and seeing what happens. SSD stuff seems to work better than HDDs, HDD RAIDs seem to have more trouble than anything else... but some HDD RAID enclosures seem to work too. Sleep seems to be a strong catalyst but ejections occur without either sleeping too. I've objectively tested through everything and am convinced the problem is Monterey... and probably Big Sur too based on others experiences with the same.
The issue is most likely the ports itself. Software would not be able to fix that. I have issues myself with a Mac mini M1 and unmounting drives at login and when I plug new devices into my USB hub.
There are lots of cases documented here and consensus is that it is the ports:
The Thunderbolt/USB-C ports on M1 Macs don’t work
If you are thinking of buying a M1 powered Mac and rely on fast, external, storage via a USB-C interface, you may want to reconsider. The Thunderbolt/USB-C ports on M1 Macs don’t work. They work to some degree, they just don’t work properly; they don’t allow attachment of many external USB-C...
benfrain.com
HobeSoundDarryl
macrumors G5
Let’s hope it’s not hardware, as that is unfixable… requiring some kind of recall & exchange scenario.
If it helps any, in my own substantial efforts to find a solution, I’ve come across many who had no issues on existing Macs until they upgraded to Big Sur or Monterey. That would imply it is NOT hardware.
It’s not just a Silicon thing, as it happens to upgraded Intels too. And it’s not all enclosures, just some. So I still suspect Monterey but have seen enough of the same with Big Sur to think it started there.
Whatever it is, it IS frustrating! I wish the U in USB applied. It seems most made for the fading perception of “just works.”
If it helps any, in my own substantial efforts to find a solution, I’ve come across many who had no issues on existing Macs until they upgraded to Big Sur or Monterey. That would imply it is NOT hardware.
It’s not just a Silicon thing, as it happens to upgraded Intels too. And it’s not all enclosures, just some. So I still suspect Monterey but have seen enough of the same with Big Sur to think it started there.
Whatever it is, it IS frustrating! I wish the U in USB applied. It seems most made for the fading perception of “just works.”
Last edited:
I successfully put my Mac Studio base to sleep and it did not auto-wake seconds later!
Same chronic problem occurred with Mini M1 16 GB from day one. Only solution was to use the keyboard shortcut.
This could be a sign that Apple actually addressed a Bluetooth bug...
Same chronic problem occurred with Mini M1 16 GB from day one. Only solution was to use the keyboard shortcut.
This could be a sign that Apple actually addressed a Bluetooth bug...
nonsense ... every macOS at X.6 version works almost perfect
Did anyone notice date format changing on the clock with new MBPs? I immediately noticed as it's apparently deep in my productivity memory to check it for date info. Format now is "Tue 09:23:00" but it used to be "Tue 17 May 09:23:00" which is weird because current format isn't event an option.
I'm also using Bartender so maybe that's involved. Seems related to notch somehow because MBAM1 doesn't do this.
I'm also using Bartender so maybe that's involved. Seems related to notch somehow because MBAM1 doesn't do this.
I use Bartender also; you have to go to Dock and Menu Bar in System Preferences and change Show Date to "always".
And also the latest Catalina security update. Interesting that there is no mention of this on MacRumors.
I can't imagine why not!!!
All seems ok on my Mini. On the display the update seems OK, not been in a call yet but the preview on teams looks pretty good but face time not so. The true tone seems to be less yellow
Just installed it on my 24” M1 iMac, coming from 12.3 it was a 2.97 gb update and took about 20 minutes to install. Seems to be working fine.
I have a brand new 16in MBP on a stand next to a new studio display. The MBP cam is not good but still better than the ASD cam even after the display OS update tonight.
There is no fixing the problem they created with the center stage decision. They don’t have enough pixels to crop from on the hardware sensor when there is only one subject on camera and the subject is sitting in front of the display. Apple could’ve just put the last revision iMac 5K camera on the ASD and everyone would’ve been satisfied.
There is no fixing the problem they created with the center stage decision. They don’t have enough pixels to crop from on the hardware sensor when there is only one subject on camera and the subject is sitting in front of the display. Apple could’ve just put the last revision iMac 5K camera on the ASD and everyone would’ve been satisfied.
Universal Control has been pretty neat so far and I've used it more than expected. I love the fact I can just drag a Keynote from my computer directly onto the iPad instead of having to use Airdrop to do it.