Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



First Last Prev Next    This bug is not in your last search results.
Bug 1627 - Scrub/Seek when the selected playback device is unavailable spawns continual errors, requiring force quit
Scrub/Seek when the selected playback device is unavailable spawns continual ...
Status: RESOLVED QUICKFIXED
Product: Audacity
Classification: Unclassified
Component: Audio IO
2.2.0
Per OS All
: P2 Repeatable
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-04-07 22:17 UTC by Gale Andrews
Modified: 2018-08-20 11:45 UTC (History)
8 users (show)

See Also:
Steps To Reproduce:
1. Restart Audacity and create some audio. 2. Disable or disconnect one of the playback devices listed in Device Toolbar. On Windows 10 make sure ALL playback devices are disconnected or disabled. 3. Start Scrub or Seek by any method (Scrub Ruler, Transport Menu, shortcuts). Audacity spawns repeated errors opening the playback device and must be force quit to regain control. On Windows 10 this may not be apparent as the error messages will be on top of each other. A reboot rather than a force quit may be needed to close Audacity.
Release Note:
GROUP: Scrubbing and Seeking * '''Starting Scrub or Seek spawns continual playback errors requiring force quit''' if there are no available playback devices or if the selected playback device has become unavailable.
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00
petersampsonaudacity: Test‑OK‑Win+
petersampsonaudacity: Test‑OK‑Mac+
stevethefiddle: Test‑OK‑Lin+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2017-04-07 22:17:59 UTC 
Not a regression. Same thing happened in 2.1.1 with CTRL + click scrubbing. So I rate as P2 rather than P1. 

Quick Play is not affected.
Comment 1 James Crook 2017-05-15 10:27:11 UTC 
Does not happen for me on Windows 10.  Playback switches from the USB sound card (headphones) to the built in speaker.
Comment 2 Gale Andrews 2017-05-15 23:23:42 UTC 
(In reply to James Crook from comment #1)
> Does not happen for me on Windows 10.  Playback switches from the USB 
> sound card (headphones) to the built in speaker.
IIRC my test, according to the original report, was to disable or disconnect a built-in device in Windows Sound. Can you reproduce it with no playback devices? 

Also IIRC, Mac is much less graceful than Windows in falling back to the built-in device after removing an external device.
Comment 3 James Crook 2017-05-16 05:53:22 UTC 
*** STEPS UPDATED ***

Thanks Gale.  The steps were incomplete.
Comment 4 Gale Andrews 2017-05-16 21:49:35 UTC 
(In reply to James Crook from comment #3)
> On Windows 10 make sure ALL playback devices are disconnected or disabled.
I find that depends. If you have interdependent speakers and headphones then you need to disable both. If you can set them up in the sound card control panel to be independent, so that plugging in the headphones does not shut off the internal speakers, then the Audacity problem should occur (or at least does so here).   

Also I can reproduce the problem I if have a SoundMeeter input enabled as well as speakers/headphones, then disconnect one of the devices.
Comment 7 Peter Sampson 2017-07-22 12:40:40 UTC 
(In reply to Paul L from comment #6)
Testing on W10 audacity-win-ra45f3bb-2.2.0-alpha-22-jul-17
and on macOS Sierra 10.12.5 Cliff's 21Jul17 build

Now looking good on both platforms.

Plugged in my external USB Edirol UA-1EX set input and output to it.
Renoved the USB plg to disconnect
TRied Scrubbing - get now just the one error message - no more looping
Tied normal play al]and TQP - also just the one error message
Comment 8 Steve Daulton 2017-07-31 19:02:27 UTC 
(In reply to Peter Sampson from comment #7)
Just one error message here too.
First Last Prev Next    This bug is not in your last search results.