Fix mute status on Big Sur #2
Open
Conversation
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
isMuted always returned true in Big Sur Fixed by switching from BOOL to UInt32
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hey Andrew,
Your btt automation services have worked really well for me, so thanks for making them available.
I recently switched to Big Sur and found that while the volume was reflected in the control strip icon, mute status was always True.
It seems that AudioHardwareServiceGetPropertyData (and AudioObjectGetPropertyData) need a uint32 rather than a bool (test script in swift), and a couple lines fixed the issue.
This change may not be backwards compatible but I'm posting it just in case anyone else has the same issue.
Aaron