Bugzilla – Bug 2080
Windows: Using WASAPI, after recording, playback can fail with "opening sound device error"
Last modified: 2019-03-29 09:10:31 UTC
There's a possible fix in my fork: https://github.com/DavidBailes/audacity/commit/a136670a187dc60a1ea59c35aabb44587a0b5256 If a developer lets me know they think it's OK, then I'll commit it.
Changed my mind, and when for a more conservative fix, which I've committed: https://github.com/audacity/audacity/commit/b8b2f4380efa2a42df6275482b6e718bbfe0cf0a
Is this related to Bug #1968 Windows: Recording or monitoring from a USB sound device using WASAPI host yields "Error opening recording device" ?
(In reply to Peter Sampson from comment #3) > Is this related to Bug #1968 > Windows: Recording or monitoring from a USB sound device using WASAPI host > yields "Error opening recording device" ? They are related, in that they both involve WASAPI, and recording and playback devices which have different shared sample rates. However, this bug was caused by an bug in the Audacity code. Whereas bug 1968 isn't a bug, and I've made a comment to that effect in the comments in that bug.
(In reply to David Bailes from comment #2) Testing on W10 with audacity-2.3.2-alpha-203-d71a54b4e9682223802f70d2af90854d393b8789 Using My Edirol UA-1Ex as input and onboard speakers (via Realtek soundcard) as output this looks mow to be fixed. To be sure I tried the same on 2.3.1 where it failed.