Difference between revisions of "Windows Bugs"

From Audacity Wiki
Jump to: navigation, search
Line 12: Line 12:
{{tip|1=To search for Windows only bugs:
* [https://bugzilla.audacityteam.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=15620&op_sys=Windows%20XP&op_sys=Windows%20Vista&op_sys=Windows%207&op_sys=Windows%20Vista%20%2F%207&op_sys=Windows%208&op_sys=Windows%2010&op_sys=Windows%20%28all%29&query_format=advanced Bugzilla Table of Windows-Only Bugs] (47 as of 1st October 2018)
==Table of not-'all-platform' Bugs==
* 154 bugs as of 1st Oct 2018.

Revision as of 14:13, 1 October 2018

Gale 19May14: ToDo-2 I removed unwanted / fixed legacy issues from this page and updated the information about soundcards and drivers. I can't think of a lot of issues that might go here that are not already covered on Windows 7 OS and the other Windows OS pages. Perhaps the material here would be more useful incorporated into Mixer Toolbar Issues which it is suggested should become a Windows only page, possibly called Windows System Mixer.

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:

  • Check the existing reports below thoroughly, plus our extensive online help resources as listed on our Reporting Bugs page, to see if your issue is already known.
  • Only add an issue on this page if you're sure it is something specific to Macs only, you're sure of your facts, and that there is not some other explanation for the problem. In all other cases, please follow the instructions on Reporting Bugs to get help and/or give us a useful bug report that we can follow up.
Bulb icon To search for Windows only bugs:

Table of not-'all-platform' Bugs

  • 154 bugs as of 1st Oct 2018.
IDOSPStatusSummary (59 tasks) ID
Windows and Linux
677Windows and LinuxP4NEWWin/Linux: Cannot interact with log if already open when called from Sequence Tags warning677
Windows 10
2614Windows 10P4NEWWindows: hang/crash when more than 36 projects are opened2614
Windows (all)
47Windows (all)P4NEWWindows: LADSPA Multiband EQ plug-in may not be visible in Effect menu and crashes soon after opening47
2619Windows (all)P4NEWWin/Mac: Quiescent Audacity eventually loses ability to record2619
1399Windows (all)P4NEWWindows: VST plug-in ReaEQ tabs cannot be enabled/disabled without restarting playback1399
1956Windows (all)P4NEWWindows: MME and WDS playback cursor is buffer length ahead of actual audio playing1956
macOS and Linux
1713macOS and LinuxP3NEWLinux: MIDI: Note track playback requires additional set up1713
306macOS and LinuxP3NEWLinux: xrun glitches when recording with software playthrough, caused by too demanding PortAudio latencies306
1519macOS and LinuxP4NEWLinux/Mac: Grids: extra Tab presses needed to reach buttons using (SHIFT +) CTRL; grid still selected after CTRL + SHIFT + Tab on Mac1519
848macOS and LinuxP4NEWLinux/Mac: Shortcuts don't display in menus for effects that have the same name848
2094macOS and LinuxP4NEWLinux/Mac: Incorrect rewind on Play2094
1055macOS and LinuxP4NEWLinux/Mac: Too generic error if an incompatible LV2 plug-in is enabled1055
2756macOS and LinuxP4NEWLinux/Mac: Cryptic error message when using NAS2756
1483macOS and LinuxP4NEWLinux/Mac: Shortcuts using NumPad keys not shown in menus1483
2355macOSP3VERIFIEDMac: Moving focus within the toolbar with tabbing gets stuck at playback meter.2355
1441macOSP4NEWMac: Imported file names containing '/' change the slash to ':' in the trackname (and in the project window header)1441
2359macOSP4NEWMac: Audacity mouse pointers used when system dialogs displayed2359
2675LinuxP3NEWLinux: Malformed tool tips in Mixer Board2675
1314LinuxP3REOPENEDLinux: Audacity doesn't remember being extended across multiple displays1314
1071LinuxP3NEWLinux: Ubuntu Unity: Crash accessing non-RTP effect in another project when a non-RTP effect is already previewing1071
1834LinuxP3NEWLinux: Help -> Quick Help dialog produces an empty second dialog1834
276LinuxP3NEWLinux: PULSE-AUDIO issues. Freeze repeatedly starting/stopping streams276
2678LinuxP3NEWLinux: Source will not build if path contains a space character2678
2361LinuxP3NEWLinux: High-dpi displays are not supported2361
335LinuxP3REOPENEDLinux: wxWidgets locale translations not being used335
2674LinuxP3NEWLinux: Mixer Board sliders slow to respond when multiple tracks2674
2385LinuxP3NEWLinux: wxgtk3: Background fails to update with i3 Window manager2385
1826LinuxP3REOPENEDLinux: Dropout detection fails to detect dropouts on Linux1826
2201LinuxP3NEWLinux: Audacity does not follow the XDG Base Directory Specification2201
2791LinuxP4NEWLinux: VSTs behaving differently between "Apply" and "Play"2791
1056LinuxP4NEWLinux: Fomp *VCO LV2 oscillator plug-ins incompatible when they shouldn't be1056
135LinuxP4NEWLinux: Custom FFmpeg Export dialog does not respond to ENTER after clicking in the Formats or Codec selector135
908LinuxP4NEWLinux: ASSERT playing audio after adding a label908
1490LinuxP4NEWLinux: The Scrubbing pointer is not consistent on Ubuntu1490
611LinuxP4NEWLinux: Muted track at different rate to project rate un-necessarily resampled611
1369LinuxP4NEWLinux: Sound activated recording erratic during Timer Record1369
321LinuxP4NEWLinux: Long unresponsive delay after recording321
2810LinuxP4NEWLinux: Summary: Wayland issues2810
910LinuxP4NEWLinux: WX3: Segfault manually locating FFmpeg910
1545LinuxP4NEWLinux: intermittent crash on exit1545
871LinuxP4NEWLinux: Built-in effects not modal when an RTP effect is open871
1504LinuxP4NEWLinux: ASSERT (frequent) when pasting audio within a clip1504
2414LinuxP4VERIFIEDLinux: Selection toolbar doesn't resize correctly2414
1448LinuxP4NEWLinux: ESC does not cancel toolbar move/resize1448
1646?LinuxP4REOPENEDLinux: Stretch operation in Note tracks needs many improvements1646
2196LinuxP4NEWLinux: Label editor: after it closes, focus is shifted to the Device Toolbar2196
323LinuxP4NEWLinux: Audacity does not report aborted recording323
1283LinuxP4NEWLinux: Track dropdown menu enabled after previewing an effect1283
289LinuxP4NEWLinux: Mixer Board: Slow meter response at start of playback289
1700LinuxP4NEWLinux: Record volume stuck at max on some systems.1700
118LinuxP4NEWLinux: Audacity doesn't recognize locally installed FFmpeg library118
907LinuxP4NEWLinux: WX3: Automatic Crash Recovery interface issues907
1515LinuxP4NEWLinux: Extended Import: Cannot mouse drag importers up or down the list1515
708LinuxP4NEWLinux: Selection un-frozen after effect preview708
1413LinuxP4NEWLinux: ASSERT (Intermittent) when time shifting audio clips1413
475LinuxP4NEWLinux: Selection shading inconsistent on MIDI tracks475
1328LinuxP4NEWLinux: Spectrum Export location not remembered1328
1961LinuxP4NEWLinux: No icon for Audacity in dock1961
1209AllP3REOPENEDLinux: Vertical ruler shows no numbers at extreme zoom level with non-linear Track spectrogram frequency1209

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.