v1.9.2 - Capture method selection per Output Device, Stability improvements

[nodeful]

• Allowing to select which Capture method to use per device (macOS 14.2+ only)
• Fixed Bypass not working in System/Output settings
• Fixed Super Preset logic, allowing manual override and making the Condition check less eager
• Fixed Volume Mixer not working sometimes with some apps
• Spectrum Analyzer now takes into account both channels

---

This discussion was created from the release v1.9.2 - Capture method selection per Output Device, Stability improvements.

[marnovo]

Glad to see new updates!
Question I wasn't able to find any info about elsewhere: What's the new "driverless" capture method about, and how does it differ from "driver" method in terms of technical approach and pros/cons?

[ragauskl]

Driverless uses newer macOS APIs, when it's in use you'll see a blue (or purple depending on theme maybe) dot in top right corner. The driver method is older solution when those APIs were not available. If dev will answer he may be able to point out more differences but from what I know:

Driverless is less likely to have issues as it's native API, developed and maintained by Apple who know macOS inside out and they have access to many more otherwise hidden private functionality.

Driver is more useful to people on versions of macOS before 14.2 when that API was not available yet, also if the blue/purple dot bothers anyone (there are some people).

Developer has more control over the driver too so I assume there could be a case where certain feature would be possible only by using the driver (not because Apple can't add it to the API but because they wouldn't prioritize it), but at least for now all features are also supported/work with driverless.