Repository navigation
Core Audio: Fix bug in which callback is never triggered when hardware device exceeds MA_MAX_CHANNELS - #1174
Merged
mackron merged 1 commit intoOct 21, 2026
Conversation
…e device exceeds MA_MAX_CHANNELS.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am working on Core Audio, using hardware devices with lots of output channels (512).
If the hardware device exceeds
MA_MAX_CHANNELS, I found that the audio callback was never fired, because the CoreAudio audio unit config did not match the (clamped) internalChannels.This PR clamps CoreAudio's channel count to
MA_MAX_CHANNELS. Verified on a MacBook Pro 2025 running macOS 26.0.1.