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.

Sign up for GitHub

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

Jump to bottom

Crackling sound when using "Assign to all" and WASAPI Device failed to start #46

Open
Trouffman opened this issue Feb 15, 2022 · 0 comments
Open

Crackling sound when using "Assign to all" and WASAPI Device failed to start #46

Trouffman opened this issue Feb 15, 2022 · 0 comments

Comments

@Trouffman
Copy link
Contributor

Hi,
On this one I am not sure if this is my system or another bug.

When doing so this have a crackling sounds and slowness while perf. usage seems acceptable (beside 3 (Logical) cores).
image

Log File excerpt

18:40:08.256: Audio monitoring device:
18:40:08.256: name: Speakers (Intel® Smart Sound Technology (Intel® SST))
18:40:08.256: id: {0.0.0.00000000}.{182439e0-3bb9-40bf-ba0c-952042a7046c}

0.0.0.00000000 is my laptop audio device I use for testing the audio monitoring.

Later I get a bunch of WASAPI error :

18:40:09.508: [win-wasapi: 'Input Audio (Mic)'] update settings:
18:40:09.508: device id: {0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}
18:40:09.508: use device timing: 0
18:40:09.533: [win-wasapi: 'Desktop Audio'] update settings:
18:40:09.533: device id: {0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}
18:40:09.533: use device timing: 1
18:40:09.534: [WASAPISource::TryInitialize]:[Microphone (NVIDIA Broadcast)] Failed to activate client context: 88890004
18:40:09.534: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:09.534: [WASAPISource::TryInitialize]:[Headphones (Intel® Smart Sound Technology (Intel® SST))] Failed to activate client context: 88890004
18:40:09.534: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start

and later : (usually when assigning Audio monitoring source)

18:40:12.535: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:12.535: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:15.535: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:15.535: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:18.536: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:18.536: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:21.536: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:21.536: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:24.537: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:24.537: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:27.537: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:27.537: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:30.537: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:30.538: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:33.538: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:33.538: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:36.538: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:36.538: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:39.539: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:39.539: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:42.539: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:42.539: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:45.539: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:45.539: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:48.539: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:48.540: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:51.540: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:51.540: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:54.541: WASAPI: Device '{0.0.1.00000000}.{d9ba5ac3-7bcd-40b1-8dd3-88bf22e41d64}' failed to start
18:40:54.541: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
18:40:57.541: WASAPI: Device '{0.0.0.00000000}.{da1b22ad-2a7c-409e-abad-6e45122b9347}' failed to start
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Trouffman