* Create AudioObjectPropertyListener type, providing an easy way to attach a Rust callback.
* Refactor the existing sample rate update mechanism to use AudioObjectPropertyListener.
* Add an optional property listener that registers a callback that is triggered on device disconnection.
* Create a set_on_disconnect method to register the disconnection callback.
I migrated to `windows-rs` in this PR since exposing the buffer size range for hardware-offloaded audio processing requires `IAudioClient2`, which isn't exposed in the `winapi` crate, and `winapi` seems to be more or less unmaintained at this point.
* Basic type conversion
* Make everything compile!
* Fix warnings
* Implement buffer sizing for wasapi
* Convert tabs to spaces
* Run cargo fmt
* Remove winapi from Cargo.toml
* Remove unused commented code from wasapi, and fix lingering TODOs
* Fix compile error
* Update to windows 0.37.0
* Run rustfmt
* Work around rustfmt nested tuple issues
* Improve readability of guid comparison code
In most cases, device with index 0 is NOT the default output device - in my case it happens to be the ear speaker. Returning Device(None) there makes Oboe choose the default input/output device - everything works as expected.
both feedback.rs and record_wav.rs have "bleep" as their application name when constructing clap::Command. This commit changes the constructor argument for each example to match their filenames.
`ndk-glue` suffers one fatal flaw: it's "only" supposed to be used by
the crate providing `fn main()` and only supposed to end up in the
dependency graph once as it has `static` globals which get duplicated
across versions.
In the current case with `winit 0.26` still on `ndk-glue 0.5` but
`cpal` on `ndk-glue 0.6` it'll always panic in `fn native_activity()` as
the `static` globals on this version is not initialized.
Introducing `ndk-context`: a crate that holds these `static`s, with the
intention/premise to not see a breaking release /ever/ and make this a
problem of the past. The crate is currently initialized with the VM and
Android Context on `ndk-glue` 0.5.1 and 0.6.1 (0.4.1 pending) making it
compatible with whatever is current, and the possibility for backporting
to older `ndk-glue` versions too.
See also:
https://github.com/rust-windowing/android-ndk-rs/issues/211https://github.com/rust-windowing/android-ndk-rs/pull/223