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

Support WASAPI Loopback #251

Closed
rawhat opened this issue Nov 24, 2018 · 0 comments · Fixed by #339
Closed

Support WASAPI Loopback #251

rawhat opened this issue Nov 24, 2018 · 0 comments · Fixed by #339

Comments

@rawhat
Copy link

rawhat commented Nov 24, 2018

The WASAPI supports loopback, where you are provided a listening device for each output device. There are a handful of libraries which support this, might be nice to have here?

I'm poking around at the source to see if I can figure it out, but I am quite inexperienced with Rust (and winapi, for that matter). winapi provides a flag for this (used in other libraries I have found): AUDCLNT_STREAMFLAGS_LOOPBACK. Simply adding this doesn't work, at least for device enumeration.

Going to keep digging, but also curious if this is something that has been discussed/considered before. Thanks!

Edit: Oof, randomly found this while perusing some examples: // note that AUDCLNT_STREAMFLAGS_LOOPBACK and AUDCLNT_STREAMFLAGS_EVENTCALLBACK // do not work together... so this may not be doable, since this lib is using that flag.

lucy added a commit to lucy/cpal that referenced this issue Oct 12, 2019
This works by detecting output devices in build_input_stream() and
setting the AUDCLNT_STREAMFLAGS_LOOPBACK flag to enable loopback
recording.

closes RustAudio#251
lucy added a commit to lucy/cpal that referenced this issue Oct 27, 2019
This works by detecting output devices in build_input_stream() and
setting the AUDCLNT_STREAMFLAGS_LOOPBACK flag to enable loopback
recording.

closes RustAudio#251
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