Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS: A backend-specific error has occurred: core foundation unexpectedly returned null string #398

Closed
thavlik opened this issue May 1, 2020 · 1 comment · Fixed by #399

Comments

@thavlik
Copy link
Contributor

thavlik commented May 1, 2020

Mac Mini 2018 (Catalina 10.15.4)

Calling device.name() returns the error string A backend-specific error has occurred: core foundation unexpectedly returned null string for my audio interfaces. I am opening this issue to document its existence. Will make audio hardware specs known if it ends up being necessary, but I'm assuming this hardware-specific since the issue doesn't exist yet.

Thanks a ton for cpal. Everything else works really well :)

@thavlik
Copy link
Contributor Author

thavlik commented May 1, 2020

Looks like there is a slow route available for getting the device name that can serve as a fallback. I'm guessing my driver doesn't want to give up its name without you supplying the memory, and that makes sense. Now it'll use the existing (fast) code path and fallback to creating a buffer on the stack to call CFStringGetCString if CFStringGetCStringPtr returns nil.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant