Difference between revisions of "Windows Bugs"
|Line 12:||Line 12:|
Revision as of 14:13, 1 October 2018
This page is solely for recording Audacity issues that are specific to the Microsoft Windows operating system (or to different versions of it), and are thus issues which do not occur with Audacity on Mac or Unix/Linux systems.
If you are looking to request a new feature for Audacity, please go to our Feature Requests page.
|This page is intended as a reference point only. It is not constantly monitored by the Audacity team and is thus not meant as a direct method for obtaining technical support.
Before adding a report here, please:
|To search for Windows only bugs:
Table of not-'all-platform' Bugs
- 154 bugs as of 1st Oct 2018.
|ID||OS||P||Status||Summary (60 tasks) ⇒||ID|
|Windows and Linux|
|677||Windows and Linux||P4||NEW||Win/Linux: Cannot interact with log if already open when called from Sequence Tags warning||677|
|2614||Windows 10||P4||NEW||Windows: hang/crash when more than 36 projects are opened||2614|
|2686||Windows 10||P4||NEW||Win: floating toolbars can block access to the menu commands||2686|
|47||Windows (all)||P4||NEW||Windows: LADSPA Multiband EQ plug-in may not be visible in Effect menu and crashes soon after opening||47|
|2619||Windows (all)||P4||NEW||Win/Mac: Quiescent Audacity eventually loses ability to record||2619|
|1399||Windows (all)||P4||NEW||Windows: VST plug-in ReaEQ tabs cannot be enabled/disabled without restarting playback||1399|
|1956||Windows (all)||P4||NEW||Windows: MME and WDS playback cursor is buffer length ahead of actual audio playing||1956|
|1082||Windows (all)||P5||NEW||Windows: VST - MDA Tracker plug-in crashes in RTP||1082|
|macOS and Linux|
|1713||macOS and Linux||P3||NEW||Linux: MIDI: Note track playback requires additional set up||1713|
|306||macOS and Linux||P3||NEW||Linux: xrun glitches when recording with software playthrough, caused by too demanding PortAudio latencies||306|
|848||macOS and Linux||P4||NEW||Linux/Mac: Shortcuts don't display in menus for effects that have the same name||848|
|1483||macOS and Linux||P4||NEW||Linux/Mac: Shortcuts using NumPad keys not shown in menus||1483|
|2756||macOS and Linux||P4||NEW||Linux/Mac: Cryptic error message when using NAS||2756|
|1519||macOS and Linux||P4||NEW||Linux/Mac: Grids: extra Tab presses needed to reach buttons using (SHIFT +) CTRL; grid still selected after CTRL + SHIFT + Tab on Mac||1519|
|2094||macOS and Linux||P4||NEW||Linux/Mac: Incorrect rewind on Play||2094|
|1055||macOS and Linux||P4||NEW||Linux/Mac: Too generic error if an incompatible LV2 plug-in is enabled||1055|
|2355||macOS||P3||VERIFIED||Mac: Moving focus within the toolbar with tabbing gets stuck at playback meter.||2355|
|1441||macOS||P4||NEW||Mac: Imported file names containing '/' change the slash to ':' in the trackname (and in the project window header)||1441|
|2359||macOS||P4||NEW||Mac: Audacity mouse pointers used when system dialogs displayed||2359|
|2674||Linux||P3||NEW||Linux: Mixer Board sliders slow to respond when multiple tracks||2674|
|2201||Linux||P3||NEW||Linux: Audacity does not follow the XDG Base Directory Specification||2201|
|1314||Linux||P3||REOPENED||Linux: Audacity doesn't remember being extended across multiple displays||1314|
|1071||Linux||P3||NEW||Linux: Ubuntu Unity: Crash accessing non-RTP effect in another project when a non-RTP effect is already previewing||1071|
|276||Linux||P3||NEW||Linux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams||276|
|2675||Linux||P3||NEW||Linux: Malformed tool tips in Mixer Board||2675|
|1834||Linux||P3||NEW||Linux: Help -> Quick Help dialog produces an empty second dialog||1834|
|2678||Linux||P3||NEW||Linux: Source will not build if path contains a space character||2678|
|2361||Linux||P3||NEW||Linux: High-dpi displays are not supported||2361|
|1826||Linux||P3||REOPENED||Linux: Dropout detection fails to detect dropouts on Linux||1826|
|908||Linux||P4||NEW||Linux: ASSERT playing audio after adding a label||908|
|1515||Linux||P4||NEW||Linux: Extended Import: Cannot mouse drag importers up or down the list||1515|
|1413||Linux||P4||NEW||Linux: ASSERT (Intermittent) when time shifting audio clips||1413|
|611||Linux||P4||NEW||Linux: Muted track at different rate to project rate un-necessarily resampled||611|
|1328||Linux||P4||NEW||Linux: Spectrum Export location not remembered||1328|
|1961||Linux||P4||NEW||Linux: No icon for Audacity in dock||1961|
|321||Linux||P4||NEW||Linux: Long unresponsive delay after recording||321|
|910||Linux||P4||NEW||Linux: WX3: Segfault manually locating FFmpeg||910|
|118||Linux||P4||NEW||Linux: Audacity doesn't recognize locally installed FFmpeg library||118|
|871||Linux||P4||NEW||Linux: Built-in effects not modal when an RTP effect is open||871|
|1490||Linux||P4||NEW||Linux: The Scrubbing pointer is not consistent on Ubuntu||1490|
|2414||Linux||P4||VERIFIED||Linux: Selection toolbar doesn't resize correctly||2414|
|1646?||Linux||P4||REOPENED||Linux: Stretch operation in Note tracks needs many improvements||1646|
|1369||Linux||P4||NEW||Linux: Sound activated recording erratic during Timer Record||1369|
|323||Linux||P4||NEW||Linux: Audacity does not report aborted recording||323|
|2791||Linux||P4||NEW||Linux: VSTs behaving differently between "Apply" and "Play"||2791|
|289||Linux||P4||NEW||Linux: Mixer Board: Slow meter response at start of playback||289|
|1545||Linux||P4||NEW||Linux: intermittent crash on exit||1545|
|135||Linux||P4||NEW||Linux: Custom FFmpeg Export dialog does not respond to ENTER after clicking in the Formats or Codec selector||135|
|907||Linux||P4||NEW||Linux: WX3: Automatic Crash Recovery interface issues||907|
|1504||Linux||P4||NEW||Linux: ASSERT (frequent) when pasting audio within a clip||1504|
|708||Linux||P4||NEW||Linux: Selection un-frozen after effect preview||708|
|1448||Linux||P4||NEW||Linux: ESC does not cancel toolbar move/resize||1448|
|475||Linux||P4||NEW||Linux: Selection shading inconsistent on MIDI tracks||475|
|2810||Linux||P4||NEW||Linux: Summary: Wayland issues||2810|
|1283||Linux||P4||NEW||Linux: Track dropdown menu enabled after previewing an effect||1283|
|1056||Linux||P4||NEW||Linux: Fomp *VCO LV2 oscillator plug-ins incompatible when they shouldn't be||1056|
|1700||Linux||P4||NEW||Linux: Record volume stuck at max on some systems.||1700|
|2385||Linux||P5||NEW||Linux: wxgtk3: Background fails to update with i3 Window manager||2385|
|2196||Linux||P5||NEW||Linux: Label editor: after it closes, focus is shifted to the Device Toolbar||2196|
|267||Linux||P5||NEW||Linux: PortAudio warnings on startup||267|
Soundcards and drivers
A limited number of high-end professional PCI soundcards are reported to be incompatible with Audacity. As a result, Audacity will crash on launch if its Devices Preferences are set to use the card. This can occur not only when the card is explicitly selected in Preferences, but also if "Microsoft Sound Mapper" (Audacity's default option as shipped) is selected when the soundcard is the current default Windows device. As a workaround, explicitly select a different device in Preferences.
If you've already set Audacity explicitly to use your soundcard and it now won't launch, you must clear the Audacity preference settings for PlaybackDevice and RecordingDevice before you can use Audacity again. To do this, reset your Windows default sound device to your inbuilt sound device, then install or reinstall the latest version of Audacity and enable the checkbox "Reset Preferences" half way through the installer.
Note that certain other custom devices or applications may similarly be incompatible with Audacity. A known example that has been reported in the past is the Total Recorder application which uses "virtual drivers" to capture sound directly before it reaches the inputs of any other installed sound devices. If you want to use Total Recorder as the default Windows device you may need to set Audacity explicitly to use your inbuilt sound device. Alternatively you can leave Audacity set to "Microsoft Sound Mapper" but set the Total Recorder preferences so that the Total Recorder drivers load only when Total Recorder is in use. If you've already explicitly set Audacity to use the Total Recorder drivers and it won't launch, reset the Windows sound device then Audacity's preference settings as per the above paragraph. As a possible alternative to Total Recorder, you can try SoundLeech which is a free application running from the system tray. It records to lossless WAV format only.
If your high-end card or device consistently crashes Audacity, make sure you are using the latest drivers supplied by the manufacturer (but note Audacity will not work with any kind of ASIO driver). Also please try the latest version of Audacity. This will always incorporate the latest available version of PortAudio, which might solve the problem. If that doesn't help, please report the soundcard or device to us here or by writing to our feedback address.
Some high-end soundcards will work with Audacity but don't use the Windows standard mixer interface. As a result, you won't be able to select your input sources such as microphone or adjust their recording levels in Audacity. You can do so in the custom mixer application shipped with the card.
Audio devices built into the computer motherboard almost always are compatible with Audacity, but may exhibit crashing behavior due to being supplied with outdated or generic sound drivers. This is a common problem on Windows systems. For the same reason, built-in audio devices may fail to record properly or not allow you to select input sources or recording levels in Audacity. To solve these problems, you can try selecting your sources and levels in the Windows Control Panel. If problems persist, we strongly recommend you update your sound device drivers so that you have the latest drivers for your computer model made by the manufacturer of the device or motherboard.