Fix device selection #40
No reviewers
Labels
No labels
2230
2243
App version
Apple OS errata
Apple SDK
bug
bugsnag
build
dlt
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: chris/Cog#40
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-device-selection"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I have cleaned up the output device code. Everything's seems to be working fine. I could reproduce that an unavailable (in this case USB) audio device will cause no device to be selected in the preferences pane. This seems like reasonable behavior to me. That’s probably what causes the empty selection in your case. We could select the system default in this scenario.
I must admit, it wasn't an empty USB device, that I am aware of. The default device in the system is configured to my internal sound output (hack, AppleALC, going to my onboard sound device's back panel front speaker output), and it had selected the first device in the list, my HDMI speakers, which I don't normally use, but keep connected anyway.
The speakers are helpful, too. They also help fix an issue, where my 4k primary monitor will disconnect due to DPMS/power save, and not reconnect on display wake unless there's that third "monitor" connected to cause a full outputs cycle, which in turn reconnects everything proper.
The 4k monitor does the disconnect thing on Windows 10 and Linux, too, so I'm blaming the monitor.
This is a strange issue. Using a Hack as well. Funny thing is, I couldn’t use breakpoints inside of any of the plugins. Is there any magic that allows this? Maybe I’m working on dead code in the Core Audio plugin…
For me, breakpoints do work within the plugins, but require you to be running the latest version of each plugin, and they have to be loading. I found the cases where breakpoints weren't resolving, was because something caused that plugin to not even load.
Maybe it's time for a clean and rebuild?