<!--
{
  "availability" : [
    "iOS: 15.0.0 - 27.0.0",
    "iPadOS: 15.0.0 - 27.0.0",
    "macCatalyst: 15.0.0 - 27.0.0",
    "macOS: 12.0.0 - 27.0.0",
    "tvOS: 15.0.0 - 27.0.0",
    "visionOS: 1.0.0 - 27.0.0",
    "watchOS: 8.0.0 - 27.0.0"
  ],
  "documentType" : "symbol",
  "framework" : "Foundation",
  "identifier" : "/documentation/Foundation/NSNotification/Name-swift.struct/AVSampleBufferAudioRendererOutputConfigurationDidChange",
  "metadataVersion" : "0.1.0",
  "role" : "Type Property",
  "symbol" : {
    "kind" : "Type Property",
    "modules" : [
      "Foundation"
    ],
    "preciseIdentifier" : "c:@AVSampleBufferAudioRendererOutputConfigurationDidChangeNotification"
  },
  "title" : "AVSampleBufferAudioRendererOutputConfigurationDidChange"
}
-->

# AVSampleBufferAudioRendererOutputConfigurationDidChange

A notification the system posts to indicate that the hardware configuration doesn’t match the enqueued data format.

```
static let AVSampleBufferAudioRendererOutputConfigurationDidChange: NSNotification.Name
```

## Discussion

The output configuration of the playback hardware might change during the playback session if other apps play content in different formats. In these cases, the media content format doesn’t match the hardware configuration which would produce suboptimal rendering of the enqueued media data. When the framework detects such mismatch it posts this notification, so an app can flush the renderer and re-enqueue the sample buffers from the current media playhead, which configures the hardware based on the format of newly enqueued sample buffers.

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)