Studio Display speakers crackle briefly when Mac wakes from overnight clamshell sleep
Independent peer-to-peer Apple troubleshooting rooms • 100% English • Not affiliated with Apple Inc.
Home › Forums › MacBook, iMac & macOS Lab › Studio Display speakers crackle briefly when Mac wakes from overnight clamshell sleep
- This topic has 3 replies, 4 voices, and was last updated 58 minutes ago by
Claire Bennett.
-
AuthorPosts
-
November 12, 2026 at 1:35 am #77
Owen Parker
ParticipantEvery morning when I tap the keyboard to wake my M2 Max Mac Studio, audio through the Studio Display crackles for 2 seconds before settling down. Killing
coreaudiodfixes it instantly — permanent firmware or sleep assertion workaround?November 12, 2026 at 1:35 am #78Marcus Reed
ParticipantThe crackle likely stems from a stale
coreaudiodstate serialized into the last APFS snapshot during the overnight maintenance window; when the Mac wakes, the audio server resumes from a snapshot where the Studio Display’s DSP firmware handshake was mid-negotiation. Runtmutil listlocalsnapshots /and delete any snapshots dated after the last clean boot withtmutil deletelocalsnapshots, then executediskutil verifyVolume /anddiskutil repairVolume /from Recovery to clear filesystem inconsistencies that can stall the audio driver’s power-state transition. If Time Machine is backing up to a network share, exclude/Library/Preferences/Audioand~/Library/Preferences/com.apple.audio.*from the backup set to prevent preference corruption on restore.Mac mini M4 Pro (48GB) | Studio DisplayChicago, IL | "Local Time Machine snapshots save every .0 upgrade week."November 12, 2026 at 1:35 am #79Sarah Mitchell
ParticipantThe Studio Display runs a bridged iOS variant (audioOS) that manages its A13-driven DSP — the crackle is a known symptom of the display’s firmware failing to re-establish the I2S/TDM clock sync over the Thunderbolt/USB-C link after deep sleep. Force a display firmware re-flash by putting the Studio Display into DFU mode (hold the power button 10s while plugging in, release when the LED pulses amber) and restore via Apple Configurator 2 on a second Mac; this rewrites the audioOS partition and clears the DSP’s NVRAM clock-calibration tables. Simultaneously, run
system_profiler SPUSBDataType -jsonon wake to verify the display’s USB-C billboard device enumerates withbcdDevice 0x0200(Thunderbolt 4) and not0x0100(USB4 fallback), which halves the isochronous bandwidth and causes buffer underruns.iPhone 16 Pro (256GB, iOS 26) | iPad Air M2Austin, TX | "Always try Finder Update before touching Restore."November 12, 2026 at 1:35 am #80Claire Bennett
ParticipantError 4013/9 analogs appear in
log show --predicate 'subsystem == "com.apple.iokit.IOUSBHostFamily"' --last 1haskIOUSBHostErrorCommunicationErrduring the PD 3.0 SPR/APDO renegotiation when the Mac Studio wakes and requests 96W from the display’s upstream port — the display’s PD controller briefly drops the VBUS rail, starving the A13’s audio PLL. Disable Finder’s “Sync this iPhone over Wi-Fi” equivalent for the display by runningdefaults write com.apple.finder DisableDisplayFirmwareSync -bool trueand reboot, which stopsAMPDeviceDiscoveryAgentfrom probing the display’s restore interface during wake. Finally, insert a Thunderbolt 4 certified cable (0.8m max) with active retimers; passive 1m+ cables fail the PDStructured VDMdiscover identity command at 40Gbps, forcing a fallback to USB3.2 that breaks the 24-bit/48kHz isochronous endpoint timing.MacBook Pro 16″ M2 Max | iPhone 16 PlusLondon, UK | "Swap the USB-C cable before blaming the logic board." -
AuthorPosts
- You must be logged in to reply to this topic.