Studio Display and Studio Display XDR Get Firmware Update

[mightysashiman]

still cant update the monitor, same issue for third day, im on phone with apple support and just passed my return time frame, this is so frustrating on a brand new premium monitor.

What was their reply?
If this is a monitor issue though, this shouldn't be capped by the return policy, but be a warranty case. Either there's a serious hardware issue that needs service, or it's a more minor and manageable software issue (in which case it'd be a pity to return such a great device just because of a fw updater glitch).

A few (obvious) questions:

• take a look here: https://support.apple.com/en-us/103989
• Can you confirm you've updated your mac (which mac btw?) to 26.4 stable?
• Are you using the included TB5 black cable that came with the screen?
• Have you tried using another TB port on your Mac?
• Have you tried doing some MacOS maintenance with OnyX? reboot and try again?

 

[tenthousandthings]

still cant update the monitor, same issue for third day, im on phone with apple support and just passed my return time frame, this is so frustrating on a brand new premium monitor.

Me too, I haven't had any problems other than this failure-to-update, but I'm running it at 60Hz (for now) -- let us know what Apple Support says or does!

My answers re: the questions above are -- original cable (also tried with CalDigit TB5 2m), 26.4 (not involved in beta testing, so stable by default), M1 Mini 16GB, tried both TB ports.

I have it set to "download updates when available," so I've been wondering if there is some way to remove the downloaded firmware update and start again...

 

[JMalone]

Why can't you boot macOS on this monitor?

Pointless question really. It’s not a Mac.

But to be more specific:

1. It’s a cut down logic board. They use iOS to manage the energy, internal cooling, ports and firmware.
2. There’s no on/off switch.
3. The iMac exists for an all-in-one system.

 

[raveelement]

spent an hour with apple support, very highly knowledgeable and we actually exhausted all the options. she collected screen recordings and kernel level package we submitted directly to apple engineers. because its a new premium product they will be on this right away and will get back to me. they do not seem to have any reports of this being a widespread issue yet. i'll report back here when i have more info

we unplugged everything but mac studio and xdr, we did safe mode, we did hard reboot, we checkd off login items, we disabled vpn and any blockers, we changed ports, we changed usernames, we disabled ethernet, etc.

im hoping its a corrupted file name because it starts already at like 85% when i hit update meaning there may be a file already downloaded that got corrupted but we tried to locate it and didnt see any hidden or lingering update files in the system folders. we'll see what apple engineers say when they back to me. maybe they will issue a hotfix serverside, thats what im hoping as i do not want to carry this brand new expensive monitor to a damn apple store

 

[tenthousandthings]

spent an hour with apple support, very highly knowledgeable and we actually exhausted all the options. she collected screen recordings and kernel level package we submitted directly to apple engineers. because its a new premium product they will be on this right away and will get back to me. they do not seem to have any reports of this being a widespread issue yet. i'll report back here when i have more info

we unplugged everything but mac studio and xdr, we did safe mode, we did hard reboot, we checkd off login items, we disabled vpn and any blockers, we changed ports, we changed usernames, we disabled ethernet, etc.

im hoping its a corrupted file name because it starts already at like 85% when i hit update meaning there may be a file already downloaded that got corrupted but we tried to locate it and didnt see any hidden or lingering update files in the system folders. we'll see what apple engineers say when they back to me. maybe they will issue a hotfix serverside, thats what im hoping as i do not want to carry this brand new expensive monitor to a damn apple store

I’m in the process of updating our M2 MacBook Air to macOS 26.4 — I will try it using that, for a fresh start.

 

[mightysashiman]

Talking about the audio part of the Studio Display XDR (I suppose also applies to the non-XDR version):
- it's audio output is I find quite subpar, not remotely as good as my 14" M3-series one. It sound hollow, like out of a tin can, especially the bass.
- I've tried doing a multi-device output setup, first using SoundSource's (Rogue Amoeba, third party) Output Group feature, and alternatively tried using MacOS's own system utility Audio MIDI setup "Multi-Output Device" feature to output simultaneously to my MBP's internal speakers and my Studio Display's speakers. It works, but it seems the OS isn't capable of perfectly syncing outputs (there is some automagic matching up that is happening under the hood since the delay reduction is audible), giving the resulting combined output a noticeable microdelay (that can sound more like a "metallic" filter, reverb, echo, or even real delay). This is easy to test out using sharp rythmic music. My guess is that the sound getting output through the Studio Display speakers is getting more processing latency (USB over TB, DSP, DAC...) ⇒ Can someone confirm please confirm? My issue is that there is apparently no way (either included in MacOS or through third-party) to manually compensate latency per audio device so they better match up 🙁
- Interestingly, when browsing through the Audio MIDI setup utility, selecting the Studio Display speakers, it appears as an 8 channel 24-bit integer, by clicking on "Configure Speakers..." it seems to be supposed to be 5:1:2 Atmos. However, no per channel adjustment is possible. This is real shame as tweaking between speakers would probably help reduce that hollowing effect.

When testing out audio samples on each channel, it does seem though that sound is actually only coming out of a pair of L and R speakers. And there is no actual subwoofer. Might an ATMOS emulation gimmick...
- Playing a 6ch audio channel ATMOS movie file in IINA, I have no idea if (and how?) these 6 channels get mapped to the (supposely) 8channels of the Studio Display.

 

[tenthousandthings]

I’m in the process of updating our M2 MacBook Air to macOS 26.4 — I will try it using that, for a fresh start.

On a related note, I noticed that others have posted screenshots of this update, and the update size is listed as 2.19 GB. Your screenshot reads 1.96 GB, which is the same as what I am seeing.

~ @ScorpioPotato @raveelement

Success! Switching to the M2 MacBook Air resolved it for me. The new download (on the Air) was listed as 2.19 GB, and the firmware update ran perfectly. Now typing this in the M1 Mini, which recognizes the update and no longer asks for it. The non-working download on the Mini was listed as 1.96 GB as ScorpioPotato said and as you can see in my original screen shot showing the failure alert.

 

[ScorpioPotato]

What was their reply?
If this is a monitor issue though, this shouldn't be capped by the return policy, but be a warranty case. Either there's a serious hardware issue that needs service, or it's a more minor and manageable software issue (in which case it'd be a pity to return such a great device just because of a fw updater glitch).

A few (obvious) questions:

• take a look here: https://support.apple.com/en-us/103989
• Can you confirm you've updated your mac (which mac btw?) to 26.4 stable?
• Are you using the included TB5 black cable that came with the screen?
• Have you tried using another TB port on your Mac?
• Have you tried doing some MacOS maintenance with OnyX? reboot and try again?

I still haven't been able to update the firmware. Answers to your questions:

• Can you confirm you've updated your mac (which mac btw?) to 26.4 stable?
  Yes
• Are you using the included TB5 black cable that came with the screen?
  Yes
• Have you tried using another TB port on your Mac?
  Yes
• Have you tried doing some MacOS maintenance with OnyX? reboot and try again?
  Yes, didn't help

The firmware update still shows as 1.96 GB (instead of 2.19 GB) and fails. Based on tenthousandthings's report, I am starting to think wiping the Mac clean and starting over might work, but that is a lot of work for which I don't have time at the moment.

 

[ScorpioPotato]

~ @ScorpioPotato @raveelement

Success! Switching to the M2 MacBook Air resolved it for me. The new download (on the Air) was listed as 2.19 GB, and the firmware update ran perfectly. Now typing this in the M1 Mini, which recognizes the update and no longer asks for it. The non-working download on the Mini was listed as 1.96 GB as ScorpioPotato said and as you can see in my original screen shot showing the failure alert.

Thanks for the report @tenthousandthings! This makes me think that a partial / corrupt update download is stuck somewhere, but I have yet to find a way to expunge it. I am still seeing the 1.96 GB update with no joy.

 

[raveelement]

.

 

[raveelement]

Thanks for the report @tenthousandthings! This makes me think that a partial / corrupt update download is stuck somewhere, but I have yet to find a way to expunge it. I am still seeing the 1.96 GB update with no joy.

.

 

[MikhailT]

In the week I have had it, using it on a 14"M3Max through 26.4RC and then 26.4Stable (before and after FW update), 0 issues. Seems I'm part of the lucky ones for once. 😅

At the Apple forums, some developers speculated that the M2 Max (which I use for work) with its dual pipes for the display would cause it to crash, while the M4 with a single pipe was just fine.

I did notice I did not see it crash on my personal M4 Pro, altho I did not use it much yet.

 

[ScorpioPotato]

At the Apple forums, some developers speculated that the M2 Max (which I use for work) with its dual pipes for the display would cause it to crash, while the M4 with a single pipe was just fine.

I did notice I did not see it crash on my personal M4 Pro, altho I did not use it much yet.

I do not believe that to be the case. It crashes on my M4 Pro with the original firmware (have not been able to perform the 26.4 firmware update yet).

 

[MikhailT]

I do not believe that to be the case. It crashes on my M4 Pro with the original firmware (have not been able to perform the 26.4 firmware update yet).

To be fair, there are multiple type of crashes being reported. But yea, only Apple knows for sure.

 

[ScorpioPotato]

To be fair, there are multiple type of crashes being reported. But yea, only Apple knows for sure.

I am referring to the crash reported here. There are user reports indicating that although there was an initial M2 speculation, the crash is also observed on M4 Pro, M4 Max, and M5 Pro systems.

Unfortunately, there is a new user report today stating that the 26.4 firmware update did not fix the issue.

 

[SDAVE]

View attachment 2616430
just did 🙂

>2.19GB update for a monitor
Yeah, we definitely live in the future

 

[raveelement]

apple support suggested i setup a new hd volume and install a fresh version of Tahoe 36.4 on it, boot to it and update then. i submitted to them the fact that some of us are seeing updates that are either 1.96gb or 2.14gb for the same exact xdr monitor which is weird. whoever sees 1.96gb update seems to have trouble updating like myself and others on here.

they said its related to the mac the xdr display is plugged into rather than the monitor itself, wish i had another mac base or laptop so i could try this. im installing mac os x to a new volume now and will report back shortly

 

[raveelement]

finally solved the issue: it has something to do with your current profile and some internal conflict within, creating a new volume and installing tahoe took about 30 mins and new xdr update finally showed up as 2.14 and update went smoothly. i then deleted the new volume and we're back in the saddle.

its not the monitor boys, its the base unit and current login/volume that cause issues for some of us

 

[ScorpioPotato]

finally solved the issue: it has something to do with your current profile and some internal conflict within, creating a new volume and installing tahoe took about 30 mins and new xdr update finally showed up as 2.14 and update went smoothly. i then deleted the new volume and we're back in the saddle.

its not the monitor boys, its the base unit and current login/volume that cause issues for some of us

Thanks for the update, @raveelement! I might just take the plunge and do the same over the weekend. Although, I am less inclined to do the firmware upgrade now that multiple user reports have come out stating that the new firmware did not solve the kernel panic issue.

 

[Jrshelby]

Talking about the audio part of the Studio Display XDR (I suppose also applies to the non-XDR version):
- it's audio output is I find quite subpar, not remotely as good as my 14" M3-series one. It sound hollow, like out of a tin can, especially the bass.
- I've tried doing a multi-device output setup, first using SoundSource's (Rogue Amoeba, third party) Output Group feature, and alternatively tried using MacOS's own system utility Audio MIDI setup "Multi-Output Device" feature to output simultaneously to my MBP's internal speakers and my Studio Display's speakers. It works, but it seems the OS isn't capable of perfectly syncing outputs (there is some automagic matching up that is happening under the hood since the delay reduction is audible), giving the resulting combined output a noticeable microdelay (that can sound more like a "metallic" filter, reverb, echo, or even real delay). This is easy to test out using sharp rythmic music. My guess is that the sound getting output through the Studio Display speakers is getting more processing latency (USB over TB, DSP, DAC...) ⇒ Can someone confirm please confirm? My issue is that there is apparently no way (either included in MacOS or through third-party) to manually compensate latency per audio device so they better match up 🙁
- Interestingly, when browsing through the Audio MIDI setup utility, selecting the Studio Display speakers, it appears as an 8 channel 24-bit integer, by clicking on "Configure Speakers..." it seems to be supposed to be 5:1:2 Atmos. However, no per channel adjustment is possible. This is real shame as tweaking between speakers would probably help reduce that hollowing effect.
View attachment 2617093
View attachment 2617094
When testing out audio samples on each channel, it does seem though that sound is actually only coming out of a pair of L and R speakers. And there is no actual subwoofer. Might an ATMOS emulation gimmick...
- Playing a 6ch audio channel ATMOS movie file in IINA, I have no idea if (and how?) these 6 channels get mapped to the (supposely) 8channels of the Studio Display.

I do not share the same experience as you do mine is preset to 48'000 Hz and not 96'000 Hz don't know if that matters. I had a 2019 Studio Display and the sound coming from the XDR spekers are a substantially great improvement.

 

[mightysashiman]

I had a 2019 Studio Display and the sound coming from the XDR spekers are a substantially great improvement.

Great but besides the point. You are comparing a 2026 SD to a 2019 SD speakers. I'm comparing 2026 SD to 2024 MBP speakers.

I do not share the same experience as you do mine is preset to 48'000 Hz and not 96'000 Hz don't know if that matters

So are you telling me that you are playing from both MBP internal speakers and SD speakers at the same time through output device grouping, and that you are having no micro-delay whatsoever?

 

[Jrshelby]

Great but besides the point. You are comparing a 2026 SD to a 2019 SD speakers. I'm comparing 2026 SD to 2024 MBP speakers.


So are you telling me that you are playing from both MBP internal speakers and SD speakers at the same time through output device grouping, and that you are having no micro-delay whatsoever?

I had a 16" MBP and these IMO are far superior. Like no contest. Matter of fact when I had it I much preferred the 2019 ASD speakers. But we all perceive things differently. As to your question never aware you could play both sources at once I certainly do not. If you could I would for sure expect a delay but still don't believe it's possible. And sorry never meant to offend anybody. I was suggestion also a lower frequency might work for the Studio Display speakers as a higher frequency might start sounding bright. Maybe this higher frequency works on the smaller speakers on the MBP as each speaker system does not mean they all share the same frequency responses.

 

[mightysashiman]

Folks, I'd like to report successful full calibration of my Studio Display XDR using my Calibrite HL Plus colorimeter.

A word of warning:
- You need time: MacOS's calibration process starts by a mandatory 30min white full brightness screen warming step, before it actually proceeds with various colour patches. The whole process takes around 35min and is fully automated.
- The process seems very picky about ambiant light pollution.

Initial state:

The first calibration I ran was in a semi-dark room with closed shutters, a bit of day light seeping into the room from the next room. The calibration process with this error:

I closed the room in pitch black darkness, relaunched the process, it cycled through that 30min warming step again, but then what seem to completed the calibration successfully within seconds. Seems to be able to resume partial calibration process.

Just to be sure, I used the "erase all..." button, and relaunched the calibration. This time it ran fully without any error.

edit:
I'd like to report that calibrating the same way my internal MBP screen also works!
No more need for clunky calibrite software. The way Apple seems to implement colour calibration seems to be at a lower level than using colour profiles, much nearer to bare-metal "screen" level (probably something closer to HW LUT), since the user doesn't get to decide on a "target" (white, gamma, black...). Colour profiles / presets seem to get applied on top of this refined screen colour calibration.
If anybody is better versed in colour management, please share your interpretation of Apple's implementation.

 

[benwiggy]

If I buy two, will music come from both monitors?

Yes: create a Multi-output (virtual) device that uses both sets of speakers in macOS's Audio MIDI Utility.app.

 

[SDAVE]

Yes: create a Multi-output (virtual) device that uses both sets of speakers in macOS's Audio MIDI Utility.app.

Unfortunately you can't adjust volume if you do this (I tried). So you have to individually adjust to match and then select the multi-output device you've made.

There are other ways to do this, I haven't tried this open source app yet