Difference between revisions of "Proposal Auto Detect Audio Device Changes"
From Audacity Wiki
PeterSampson (talk | contribs) (→Developer/QA Backing: added my backing) |
PeterSampson (talk | contribs) ({{tip|This proposal has been transferred to GitHub as [https://github.com/audacity/audacity/issues/2409 Issue #2409]. }}) |
||
| Line 1: | Line 1: | ||
{{Proposal_Header|This page is a proposal to detect changes in devices as they happen, e.g. plugging in or out a USB audio device. |}} | {{Proposal_Header|This page is a proposal to detect changes in devices as they happen, e.g. plugging in or out a USB audio device. |}} | ||
| + | {{tip|This proposal has been transferred to GitHub as [https://github.com/audacity/audacity/issues/2409 Issue #2409]. }} | ||
__NOTOC__ | __NOTOC__ | ||
==The Problem== | ==The Problem== | ||
Latest revision as of 17:21, 11 January 2022
| Proposal pages help us get from feature requests into actual plans. This page is a proposal to detect changes in devices as they happen, e.g. plugging in or out a USB audio device. |
| Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.
|
- Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.
|
This proposal has been transferred to GitHub as Issue #2409. |
The Problem
When a new device is plugged in after Audacity has started, Audacity does not detect it.
- You have to explicitly request a rescan.
- This is not just a USB problem.
- Some headphone-or-microphone jacks detect plug-in or removal of a device.
This issue was in bugzilla as Bug 41
Proposed Features
- Rescan devices when the relevant dialog is opened, if they have not been scanned in the last 5 seconds.
Developer/QA Backing
- Peter - we get countless posts on the Forum regarding this ...
