Release Checklist

From Audacity Wiki
Jump to: navigation, search

This was the de facto bug list for all Stable and Beta releases of Audacity until February 2010. A modern installation of Bugzilla is now used instead.
Go to Bug Lists to see various categorised lists of bugs in our current Bugzilla database.
Related article(s):
  • Patches are currently tracked on Bugzilla.

Warning icon Gale: 05 Feb 2010: Please do not make any further modifications to this Checklist. I'll use it for a while for any residual correlations with Release Notes and Bugzilla, then retire it.

There is a discussion on the Talk Page about what to do with various other pages/tools more or less associated with the Checklist.

Essential changes

These are other changes to source code that are deemed essential. We will do all of these for final release candidate for 2.0.

  • Help/Manual issues
    • Installer versions of Audacity now install Html help. Suggestion has been made that Windows installer should have an option to install help for all users, not just current user.
    • Address documentation issues, including website updates.
    • Completing the Manual.
  • Nyquist plug-ins (for 2.0): Gale to keep an eye on the Nyquist plug-ins provided in the Audacity "Plug-Ins" folder, possibly commit others requested by users if they work satisfactorily, such as binaural tones and Sequencer. On Windows/Mac, add the src/plug-ins folder to the installer but also add latest versions of GVerb.dll, Hard Limiter.dll and sc4.dll which are not in CVS. No special action is needed on Linux, as any *.ny plug-ins from the plug-ins dir are installed, except those deleted when the tarball is created using scripts/

Rating Keys for Issues

All issues are given a Priority Rating of 1 to 5 as follows:
P1 Blocks any Release - See the discussion page for a guide to what may be deemed an issue that blocks release.
P2 Blocks a Stable Release, but not a Beta. Maybe only affects a limited number of users.
P3 Not a blocker, but deemed worthy of release-noting if unfixed, so should not be ignored and left to mount up.
P4 Clear benefits from fixing, but not sufficiently important to release note. May include easy fixes giving considerable benefit relative to the time involved.
P5 Only just important enough to be fixed. It could be done in "spare time", or by someone learning the code.
Believed fixed but awaiting confirmation (cross-platform issues should be tested on at least two platforms)
R Regression on 1.2.6. Mainly used as an indication that a lower priority item could be promoted. Many issues not marked as regressions may well be so.
There is some more information about P numbers on the talk page...

Blocking Issues

P2 (Stable Release Blockers)

P2 R  (Windows) Projects crash when applying repeated effects on zoomed in regions towards the end of audio tracks
  • GA: Experienced on Windows XP in one project that crashed regularly on separate days but now won't do so, also several similar anecdotal reports. There is also an implication that Noise Removal is more likely than other effects to trigger the problem. JC suggested and was agreed we should aim to do stress-testing with small block sizes to try and force the problems to occur and (later added) that we should use the scripting feature to do this (improving our chances that we can repeat the problem) .
  • JC: A label issue? (I have not seen this crash yet).
  • GA: Without labels in my case, with in others, so believed that labels not relevant.
  • MJS: There appear to be no recent reports of this bug, and no repeatable evidence. I suggest this is demoted to a 'watching issue'.
  • GA: Initialise blockStatus in Sequence.cpp (8Nov09) and possibly fix for spurious clips at the track end after Change Speed (4Nov09) may have helped some cases, but still reports from one user 5 and 11 Nov09 of clicking to right of a zoomed in selection near the end of a project causing a crash. NB the act of zooming itself does not usually cause a problem. Further changes by AWD 19Nov09 to WaveTrack::ClearAndPaste() to help eliminate zero-length clip creation in ChangeSpeed and similar also noted.
  • MJS 23 Nov 09: the thread at gives some insight. This appears to be fixed although Gale has not confirmed that the test cases replicates the original problem. Since it is a 'moon phase' bug he can't really do that, but I have provided a good case, and Al has addressed the issues, so I think this is fixed.
P2 (Windows 7) Runtime Error Program: (location) R6034 on launching Audacity.
  • GA: Fixable by user changing compatibility mode to Vista SP2 or XP SP3. Reports where this error occurs say Audacity installs without compatibility, but that isn't in itself a condition to reproduce it.
P2 (Windows Vista, 7) Input sources cannot be selected in Mixer Toolbar.
  • GA: A significant problem for support workers. On some systems, running Audacity in compatibility mode for XP seems to make the inputs appear in Mixer Toolbar and work/be selectable. Best solution could be to integrate Device Toolbar into Mixer Toolbar, making sources appear as separate devices for all Windows versions, with the sliders above the respective dropdown. Cheaper short-term solution may be to turn Device Toolbar back on as it is. See here and how it might look.
P2 (Windows Vista, 7) Audacity input/output level sliders act independently of/incorrectly with system level sliders.


  • Achieved recorded level only matches level indicated on the Recording VU meter if the Audacity input slider is at 100%. (DB finds similar behaviour on XP with Logitech USB microphone, but GA can't reproduce with USB external soundcards).
  • (DB finds this only on Vista) Launch Audacity > Record > Stop > adjust the system input level > Record again; or Launch > adjust system input level > Record resets system level to that before the adjustment, unless monitoring is on. Please test with both motherboard and external USB devices. Adjusting system slider is necessary if it happens to be set above clipping level because lowering the Audacity slider only scales down the clipped signal instead of lowering the system slider. Especially confusing for VI users.
  • Many updates for this committed up to 25th Nov. Mac now reported to be all working fine. Requires re-test on all platforms with builds from after this date, we hope this may be largely cleared now.
P2 (Windows) Input and/or output sliders for the inbuilt sound device have no effect when an external device is connected.
  • GA: Widely reported on XP, one or two on Vista/7. Input slider appears active, not greyed out and maxed as it would be if emulated. Sometimes input selector will disappear too, but reappear when USB device removed.
    • Also a couple of reports of the same symptoms (input slider active but has no effect, input selector missing) when apparently no external device is connected. Selector will re-appear in 1.3.9 and disappear in 1.3.10.
    • Couple of reports on XP (including Peter) of inbuilt input and output slider moving in sympathy when USB device is connected.


P3 Release Noted (Prioritised non-blockers)

P3 Unmodified Transport shortcuts write label at cursor position after user adds a label at playback position.
  • GA:
  1. Set Play, Stop and Play/Stop shortcuts to unmodified characters like "S" or "U"
  2. Generate a 30s tone
  3. Use shortcut to start play
  4. Use shortcut to add label at playback position then hit ENTER to confirm label
  5. Use any shortcut to stop, or default P for pause (or Play shortcut or any unmodified character by accident). That shortcut will be written to a label at cursor position. Track can't be stopped with shortcut except by using up arrow first.
    Bug does not occur if you CTRL + B to add a label at the point you want to play from, as long as you start playback from the point where you added the CTRL + B label.
P3 (Windows 7) Clicking in a file open or save dialog may cause the files or some folders to disappear from the list.
  • GA 30Dec09: Only occasionally reported, and exact behaviour seems to vary per machine. Ed has clarified in email that \audacity\lib-src\FileDialog\win\FileDialogPrivate.cpp v 1.18 2009/11/13 05:21:43 llucius is the code in question. Ed believes wxWidgets 2.9 would eliminate the need for Leland's code but wouldn't be a fix in itself. Meantime we have a patch from Ed to turn filtering off on Win7 which works fine for me. Ed has suggested resubmitting the patch against CVS HEAD to be sure. (EFMv (Ed) 30Dec09 new "ignore" patch submitted) Ed also said a Windows 7-style file dialog would work fine with native filtering on 7, Vista and XP (but not pre-XP). This would mean wrapping every file dialog call in an OS/version test however. (EFMv 30Dec09 patch demonstrating this submitted)
  • EFMv 30Dec09 I think this should be a P2 unless my "ignore" patch is applied.
    • GA: Maybe, I'm going on number of complaints. Do we know why this occurs so infrequently? I agree it seems better to apply the patch to turn filtering off for Windows 7. We don't want this issue sullying an announcement of support for Win7.
    • EFMv 30Dec09 I think this is a race condition. When I first started investigating this I had a slow dual core CPU; with that CPU, if I single stepped through the code with the debugger, the original code would occasionally work. I am now running a very fast quad core CPU and even with single stepping the problem always presents.
P3 R   No longer possible to overwrite a closed project.
  • JC: Reported by Doug Grinbergs.
  • GA: Was a P1 (see thread) where overwriting an open project made the original project freeze when trying to play it, and SaveAs didn't even prompt the overwrite.
  • GA: MC committed a fix 08Dec 09 that prevents overwriting an open project with either Save or SaveAs. However it also removes the ability to overwrite an existing project that isn't open. GA and MJS think this is not desirable, so bug demoted from P1 to P2 rather than removed.
  • JC: I've fixed the double prompting issue in MC's update and reduced this to a P3.
  • GA: As per talk page, the only definite flaw with the 1.2.6 overwrite functionality was that if you initially saved a project as empty with SaveAs before adding data, then saved it as another closed project, the project you started with SaveAs would be empty. So it's agreed this is a high priority P3 which was (almost) judged as a P2.
P3 Screen reader issues.
  • GA: The following usually do not read correctly in screen readers:
    • Labels
    • Time values in Silence Generator (JAWS or Window Eyes report the time as 000,000 seconds when the displayed value is 30 seconds).
    • Accelerators in Preferences
    • Metadata Editor: David B: JAWS 11 says something like "table tag artist name edit unavailable type in text". I think the "type in text" at the end is potentially quite confusing. It's obviously better than it not reading at all...
P3 (Windows) Visible scanning dialog on every launch of Audacity when no VST plug-ins present.
  • GA: See this thread. I do not see the dialog if I launch the .exe from my build folder, but if I download the same build from my website, unzip into an arbitrary folder and launch it, I get the dialog. I can't see what in the build folder might be stopping the scan, but nothing is written to plug-ins.cfg.
P3 (was P2) (Mac 10.5.8 PPC) Hang when scanning for VST effects on fresh install.
  • GA: See detailed comments by Bill
  • GA: LL committed possible fix on 14Nov09, Bill not tested yet
  • GA: 23 Nov09 Bill and LL tested extensively. Problem 100% replicable on Bill's 10.5.8 PPC machine, but 10.5.8 Intel and 10.4.11 PPC and Intel seem OK.
  • GA: 26Nov09 Demoted because only two confirmed instances known so far (both on 10.5.8 PPC). P3 lets us release note it and see if we can find other instances where person is able to debug. The inability to add more than one VST effect to plug-ins.cfg must be fixed as well as the initial hang.
P3 Effects processing/waveform rendering after process completion much slower than 1.3.8.
  • GA: Reported several times on Windows. See this thread.
  • AWD: I tried these tests on Linux and don't see it. In particular, waveform display is nearly instantaneous for me. Maybe it's a Windows-specific thing?
  • GA: 25Dec09: Two more user reports on unknown versions of Windows. One report cites 90 seconds in 1.3.10 for VST or built-in EQ in a four minute track, against 10 seconds in 1.3.8.
P3 Nyquist effects join separate clips together, and add spurious split lines if applied over clip boundaries.
  • GA: SBSMS now fixed by DH, leaving the subject problem. See this thread.
  • DH: Nyquist will probably need further discussion (was mentioned in the original 'white space' thread I believe) - really processing clips separately could produce artefacts... possible solutions include:
    • simply running 'detach at silences' after the effect (I haven't looked at how this works yet but it seems hopeful)
    • changing the nyquist interface (e.g. the 'nil means white space' option) which would involve changing all of those plug-ins
    • recognising the known plug-ins by file name and dealing with them appropriately (pretty unpleasant temporary solution)
  • GA: I always recommend complainants to detach at silences but it won't work at 16-bit quality because the effect will add dither noise. The only P2 part of this is to stop the clip boundaries being removed. Longer term I'm still getting the impression having absolute silence between clips rather than white space would solve a lot of issues.
  • JC: Agreed that this should not block a 2.0 (stable) release. This is a 100% repeatable problem however with at least two established team members keen to see it cleared. From a programmer's perspective it is natural to solve this at the same time as doing discontinuous selections since both involve looping through selections with the same effect.
  • GA: Another issue is that when applied over clip boundaries Nyquist effects actually add clip lines at the region borders. I think the "understanding" is that only Generate and timeline changing effects should do this. If this understanding is wrong, or if different built-in effects are behaving differently in this regard, maybe this should be a separate bug (P4?) to sort this out.
P3 Cursor jumps to start of scroll after playback cursor goes past scroll
  • GA: Import a file, place cursor in centre and zoom in four or five times. Then play a few seconds of audio so that the cursor goes past the scroll. Press Space and the timeline remains where stopped (maybe OK). Press Space again and playback restarts from original point but that is now at far left of scroll, not in the middle. The context preceding that playback position is now lost, requiring a fiddly drag back on the horizontal scrollbar, or a zoom out and back in. Or, you must draw a selection region when you may not want to do so. Very irritating for repeated zoomed-in editing at one spot.
  • JC: This is a P4, or better still a feature request for improved scrolling/zooming behaviour. Let's get some detailed usability enhancements written up for a GSoC 2010 idea? Then drop this as a P2. In this area I'd see 'zoom to selection' should be 90% not 100% zoom, so that we get context, plus also option for smooth scroll on sufficiently fast machines. Can we replace this P2 with a detailed/motivated feature request?
  • GA: Need time to consider exactly what may or may not be a feature request, however I and several others regard the subject issue as excessively disruptive to "repeat editing" workflow, and completely unacceptable. I've sometimes actually exported WAV and used other editors in order to be free of it.
P3 Track groups are limited to one label track.
  • Only release note for releases where linking-labels enabled
  • AWD: The manual says that you can have multiple label tracks at the end of a track group. List discussion indicates that we do want multiple label tracks at the end of a track group. We really need to make all grouping behavior dependent on TrackGroupIterator and TrackAndGroupIterator, but I think in order for that to be practical we need to make sure that iterating over all the groups, and then over each group's tracks, iterates over all tracks in the project (even if there are note tracks and a time track).
  • GA: moved up from P4, given the Manual says a group can have multiple label tracks and we decided not to change the Manual.
P3 SBSMS, Change Speed, Change Tempo do not keep group synchronisation.
  • Only release note for releases where linking-labels enabled
  • GA: To reproduce:
  1. Turn linking on, create 30 seconds default tone, select 5 - 10 seconds and Amplify by -20 dB to see it
  2. Duplicate the track
  3. In the lower track, place label at 15 seconds, select 3 - 12 seconds and Effect > Sliding Time Scale (20% start and end tempo change), or Change Speed or Change Tempo (20% change)
  4. Neither labels nor the audio in the other track moves.
P3 Truncate Silence does not keep labels in sync
  • Only release note for releases where linking-labels enabled
  • RA: If a single track is being processed by the Truncate Silence effect, the linked label track is not changed to match. This should be simple to fix for the case where there is only one audio track and the associated label track. This bug does not cover the case where there are multiple audio tracks selected for truncation - that is a much lower priority bug.
  • To illustrate, generate a 30 seconds DTMF sequence
  • Add labels to some visually obvious places on the waveform
  • Select the audio, and Truncate Silence
  • Notice the labels haven't moved, when they should have.
P3 Mixer Board release-noted issues:
  • GA:
  • Meter range does not reflect a change in the dB range meter preferences until restart
P3 Automatic Crash Recovery: disregards track zoom level and position.
  • GA: Always opens track fitted to project window. This is an improvement (by Sam Lewis) over previous behaviour where track was recovered at default zoom level.
  1. Import a 3 minute or longer file into fresh project, which fits to project
  2. Generate a 30 seconds tone, wait the autosave interval, select a region of a few seconds at 1 minute 30 seconds, zoom into it and amplify.
  3. Force quit and recovered track captures the amplify but is fitted to project.
P3 Time Track disables audio/label linking.
  • Only release note for releases where linking-labels enabled
  • GA: Steps to reproduce:
  1. Add a tone of 30 seconds in a clean project with linking enabled
  2. Select 5 - 10 seconds, CTRL+B and name label
  3. Tracks > Add New > Time Track
  4. Select 2 - 4 seconds in the tone and Edit > Cut; audio is cut but label does not move
  5. Edit > Undo
  6. Remove Time Track and repeat step 4; label moves back to respect cut audio
P3 All Edit menu items to be consistently enabled and work consistently when select-all-on-none enabled.
  • GA: Demoted from P2 because has been significantly improved, but still inconsistencies between enabled items when track is selected or not, and when it isn't selected but cursor is or isn't in track. See this thread.
P3 Label tracks: typing "j" or"k" in a label may activate the "move cursor" shortcut instead.
  • GA: Not reproducible to order, but very likely to occur with large numbers of labels in a track. Once it occurs, typing "j" or "k" in any label in that track will move the cursor to start/end of the track.
P3 Changes in available devices not detected without restart.
  • GA: A significant reason for users' USB devices not appearing in Audio I/O Preferences.
  • GA: LL changed MixerToolBar.cpp 23Nov 09: "Update Audacity's input source in the Mixer toolbar if the source is changed outside of Audacity." If this was to address this P3, it doesn't work for me on XP as at 05Dec 09, testing swapping in/out with a USB soundcard and USB turntable.
P3 (reported on Windows) Timer Record unreliable with recordings straddling midnight
  • GA: If recording starts on one day and end on another, recordings may carry on after scheduled end time and cannot be cancelled, requiring a force quit of the application. Elapsed and remaining time will appear frozen at some values with the schedule range. No repeatable scenario is known, but for those regularly scheduling midnight spans, the freeze occurs quite regularly. A system clock change is a possible explanation (see next item). Problem still occasionally being reported in 1.3.9 and later.
  • GA: 23Jan10: Peter reports an instance on XP with 1.3.11 where the above symptoms occurred with a recording starting at 19:00, and there was a dropout in the recording at the time the timer froze. Ed and Gale agree that this is probably insoluble unless it can be debugged when it happens, or a system event is identified that causes this.
P3 (reported on Windows) Timer Record cannot maintain scheduled duration if system clock changes
  • GA: 19 Oct 09
    • Schedule a five minute recording for immediate start (start time immaterial), OK, then change system clock to one minute before end of recording. Elapsed time and remaining time will jump to reflect changed system time, and recording will end having produced just over one minute of recording. 100% replicable on XP, but according to EM, recording completes the full length on Vista.
    • Repeat above steps, but advance clock to after end of recording - recording stops (cleanly) at once. 100% replicable on XP, but according to EM, recording completes the full length on Vista.
    • Repeat above steps, but set clock back to before recording start time. Progress bar freezes and recording carries on indefinitely, similar to the reported "recordings straddling midnight" behaviour. 100% replicable.
    • Are these fixable by relying on some kind of Widgets duration timer for duration, and not on the system time? Many people synchronize system time to online atomic clocks (Windows XP does it by default). Most system time changes will be forwards, when synchronisation corrects the tendency of computer clocks to lose time.
P3 Modal block circumventable using File > New (Mac only) or shortcuts, leading to risk of crash. See this thread.
P3 Muting specific time-shifted mono tracks when exporting produces audio at wrong point on timeline in exported file if muted tracks are to left of unmuted.
P3 WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.
P3 LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening.
  • VJ: The logic needs to be fixed to set rstart to a valid value in all cases, because after initializing rstart to 0, it crashes in LadspaEffect::ProcessStereo().
  • LL: I think we've gotten past that, but now there's a crash during cleanup. It's due to a memory overwrite past end of the "comp" array in the mbeq source. It's been fixed in the LV2 version of the plug-in, but AFAIK has not been fixed in the v1 plug-in. Correctly the logic allows the plug-in to process without crash.
P3 Residual FFmpeg issues:
  •   Importing FFmpeg formats when FFmpeg library missing should raise the "FFmpeg not found" error, not the generic "not supported" error. Provisional fix in place, but throws multiple FFmpeg errors per file, then the relevant error for the particular format
  • In non-FFmpeg builds, attempting to import FFmpeg-supported formats should give an error that suggests downloading FFmpeg. Impossible to fix completely without breaking Importer abstraction: in non-FFmpeg builds ImportFFmpeg plug-in does not exists and cannot suggest anything to user, while Importer should not know which formats are supported by ImportFFmpeg, thus being unable to suggest anything either.
P3 When changing language in Preferences, some elements in Unicode Release don't change until restart.
  • GA: 30Dec09 Meter channels and "Repeat Last Effect" now fixed. Agreed with Ed that current behaviour where pre-existing generic track name ("Audio Track" in English) is not translated with language change, but a new track shows new language without restart, is OK. This leaves to be fixed:
    • "Left-click and hold" slider tooltips (except gain slider)
    • Gain slider "left and right"
    • Name of effect at Edit > Undo and > Redo
    • "Nyquist Prompt" on Effects menu
    • Selection Toolbar elements running into each other when Selection Format is hh:mm:ss+samples now fixed (tested on Windows XP, 7 and Ubuntu). However when launching on Windows 7 in French after updating to the fix, I got missing TimeText controls. They reappeared after exit and relaunch. I have the .cfg file that produced the missing controls.
P3 Calculation of "disk space remains for recording (time)" incorrect when recording in 24 bit quality. Macro now created by RA to return size on disk of 16/24/32 bit sample formats as 2, 3, 4 respectively as first part of a fix, but Audacity does not currently record in 24 bit.
P3 Tag import/export occasionally non-orthogonal. Some known specifics:
  • GA: ID3v2 Comments tag not seen by Windows Explorer or Windows Media Player 10 on Windows XP SP2
  • WAV fields only seen patchily by other apps. as their support is patchy, but Genre tag consistently not seen.
    • GA/LL: Although it's a valid WAV info tag (IGNR), we don't support it because current and next libsndfile doesn't. We could patch libsndfile locally, but may be better to switch to taglib when they next release, as that will have AIFF and WAV support. Also because AIFF is written to an ID3 RIFF chunk, that will support AIFF tags in iTunes as standard instead of the current ad hoc adding on to libidtag.
  • GA: OGG metadata seems perfect on Windows except VLC sees no tags at all. How is Linux/Mac? Taglib should improve compatibility with VLC, K3b and Amarok.
  • GA: (Linux) As of 26 Dec09, Audacity can now see its own FLAC tags in 1.3.11-alpha on Linux. Still OK on Windows XP.
  • GA: Album art and lyrics are deleted in the exported file, instead of being ignored.
P3 Truncate Silence doesn't work well on multiple tracks
  • RA: Selecting multiple tracks of audio and then trying to Truncate Silence doesn't work in a terribly useful or intuitive manner. No agreed specification exists for what the behaviour should be in all the possible circumstances, devising and documenting this specification is the first task.
  • GA: Promoting to P3. There does seem an expressed demand for this to work, first of all in its basic form on unlinked, unlabelled tracks.
P3   (Windows only) After a period launching correctly, Audacity opens minimised.
  • GA: Audacity does not come up on top after launch, requiring right-click > "Maximize" or "Restore" over Taskbar icon, ALT - tab or resetting .cfg (the latter always works). Some users believe Audacity has "stopped working". One user claimed these were the .cfg settings before resetting them:

    [Window] X=-4 Y=-4 Width=1288 Height=778 Maximized=1

  • GA: Fix committed for case where relaunching executable when it was already open was causing the second project window to be hidden, then the x,y position would be saved in .cfg as off-screen. Not known if this cures the many cases reported, but GA has pushed the Nightly to a sample of users who complained about the problem.
  • GA: 05Dec 09 - one user report of a similar problem in 1.3.10 being looked into.
P3 (Windows only) LADSPA plug-ins not categorisable despite compiling with USE_LIBLRDF defined and installing RDF data files in Audacity data directory. See this thread
P3 (Windows only) The slv2 library needed for LV2 support does not build.
  • GA: Is slv2 building on Linux?
  • DanH: For me it fails (on Linux) but can be fixed by running libtoolize.
P3 (Linux only) JACK issues:
  • in 1.3.5 from Ubuntu repository, Audacity crashes as soon as play or record started if JACK device selected in preferences (not tested built from CVS)
    • GA: Nov 2009 Al committed change preventing choice of different API's in Device Toolbar, which on Linux seemed to cause incorrect or no devices in Preferences. This might help.
  • JACK has to be shut down before starting Audacity
  • Connections in qjackctl not persistent in Audacity session: they only become visible when playback or recording starts, and close when playback or recording stops. Several Linux applications have this problem, but for example alsaplayer seems to have solved it by changing their code? See this Linux musicians thread and this Forum post
  • Recording dropouts - these are grouped together with similar Mac problems as a P4 issue, but they might not be related
  • Crashes when recording full duplex?
  • Audacity must have same sample rate as JACK (seen in 1.3.4 Ubuntu repository builds)
P3 (Linux only) Effects and other dialogs do not have focus on opening.
  • GA: This is a bug in wxGTK for which there is no current workaround. Click in the dialog to navigate it and change parameters.
P3 (Linux only) After opening a sufficiently long audio file, opening a second file of any size leads to locked GUI/console messages until first file completes play. Reported by Michael Schwendt on Fedora 8 test rpms of Audacity CVS from 11 Jan 08 and Jim Cline on Debian 31 Jan 08.
  Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1034
  Expression 'AlsaOpen( hostApi, parameters, streamDir, &pcm )' failed in
  'src/hostapi/alsa/pa_linux_alsa.c', line: 1066
  • DanH: Confirmed on Arch
  • JC: Therefore promoted from P4

P4 / P5 Other Issues (not Release Noted)

P4 Nyquist working directory inconsistent.
  • SD: See this thread. Nyquist working directory, as reported by (setdir "."), is the audacity program folder in some builds and the modules folder in other build.
    • On Linux, both of these directories are write protected for user accounts.
    • On Windows, the Nyquist working directory may be changed for some Audacity builds by setting the "Start In" option of the Audacity launch icon. On other builds (including RC1) it cannot be set this way.
  • GA: Roger D has committed a GET-ENV function in xlsys.c to get environment strings. It seems this would allow you to look up "HOME" on any system. So this P4 can be solved when we update to the latest Nyquist version.
P4 Desynchronised tones playback
  • GA: On XP and Vista (but not Linux), generate a 60s tone and select and duplicate a number of regions 5 seconds in length. Invert each duplicate in turn and play it. On regions after the first, there is (instead of silence) an audible noise right at the end of playback which also shows in the meters. Unable to reproduce with music, but it clearly isn't correct.
P4 Transport and Tracks menu items wrongly enabled when no tracks.
  • GA: Transport menu: disable all six items in first divider ("Play" to "Skip to End" inclusive). Tracks Menu: Disable "Mute All Tracks" and "UnMute All Tracks" (and change "UnMute" to "Unmute").
P4 Analysis effects that create labels should give focus to label track.
  • GA: To reproduce:
  1. Generate DTMF tone sequence
  2. Edit > Duplicate twice to create four tracks in all
  3. Select the top track and Analyze > Silence Finder (default settings)
  4. Analysis track (the object of the last action) invisible without scrolling
P4 "Specify Command Line Encoder" needs a dropdown to store entries.
  • GA: This is agreed with LL now that FFmpeg supported as well as LAME.
P4 Phaser and Wahwah: some sliders do not respond to arrow keys.
  • GA: Sliders affected: Phaser: LFO Start Phase, Feedback; Wahwah: LFO Frequency, LFO Start Phase, Resonance
P4 About box not modal.
  • JC: Reported by Doug Grinbergs.
  • GA: Would be more useful, but contrary to Windows behaviour
P4 Wording on Save dialog better as "Don't Save/Cancel/Save..." (more mac Like).
  • JC: Reported by Doug Grinbergs. Better for PC too.
  • GA: I was proposing to track all those Mac suggestions as Feature Requests as per Leland's view, like support for dotted close button and proxy icon. I think those ideas could possibly be implemented in a cross-platform way. But I can't see why we would go to Mac style buttons (we'd have to do it globally, not just in this dialog) so go out of kilter with our majority platform. We already change the Yes/No/Cancel order for Mac and Linux to respect those platform's sensibilities, so why not make the "Don't Save" change for Mac only?
P4 Vertical ruler scale only has zeros on a recorded track displaying Waveform (dB) view.
  • GA: Steps to reproduce:
  1. Launch Audacity
  2. Record a few seconds of stereo audio
  3. Stop
  4. Change to Waveform (dB) view if Default View Mode in Preferences not already set to it
  5. Only figures on the vertical scale are "0" and "0"
  6. Drag track down to see the real figures
    Does not happen with imports, or at waveform/meter dB ranges of -36, -120 or -145.
P4 Analyze > Plot Spectrum needs progress dialog.
  • GA: On slower/stressed machines, selecting audio near to/exceeding the 237.8 seconds analysis length can result in excessive wait before plot or warning appears. I've seen up to 20 seconds' wait selecting an hour long track on a 2.4 GHz 1GB RAM machine with Firefox running. Warning should occur before progress dialog.
P4 Play-at-Speed slider should have 6 steps using page up/down, and 60 using arrow keys. For input/output sliders, 5 up/down and 100 using arrow keys.
P4 Export Multiple success dialog: can't view long file names.
  • GA: There is no horizontal scrollbar triggered by width, and no ability to resize. However a horizontal scrollbar is triggered by height. Needs normal horizontal and vertical scrollbars, and to be resizable.
  • EFMv 12Jan10 patch submitted
P4 Export Multiple success dialog: untitled files after the first should still include "untitled" or "empty" in the name
  • GA: Since there is no other specific information to help users who have left just one label blank, I wondered if we should replace "untitled" with "empty_label" which makes it clear? I think people would prefer that the second and subsequent files included "empty_label" or "untitled" though. So, "empty_label.wav", "empty_label-2.wav" and so on. Is that easily done? I do think "empty_label-1.wav" for the first file "would" have been better, given we adopt this -1, -2, -3 ... scheme for "numbering consecutively".
  • LL: Not sure if "empty_label" would work if there are other cases when a blank file name were possible. I can't think of any off hand though, so if you can't either, we'll change it to "empty_label". The problem with having "-1" is that it really isn't a counter of the label being exported, it's a counter of what files already exist with the name. But, let me fiddle with it a bit. I think I have a solution.
P4 Chains: all effects should remember settings applied via chain and Effect menu independently.
  • GA: Leveller, Normalize and Truncate Silence already do this, including applying the effect menu settings when you use "Repeat last effect", even if the effect was last applied in a chain. Equalization still needs fixing in this regard. If you apply one EQ in Effect menu, another in a chain then Repeat last effect, the EQ from the chain will be applied even though the one visible if you open EQ from the Effect menu is the one last applied from the menu.
P4 Toolbar and track gain/pan slider tooltips should display on hover
  • GA: Too fiddly and undiscoverable for sighted users to have to click on slider to read the current setting. Also consider a finer increment for tooltip (at least 0.0, 0.05, 0.1 ...?) given the wide spacing of the ticks. Isn't the 6 point accuracy of the text input specious (as well as outside Audacity's control)? I'd prefer to see 2 point accuracy and probably that accuracy should be used for the tooltip as well.
P4 Name in Track Control Panel should have tooltip which displays full name.
  • GA: As well as being user-requested, matches with Mixer Board which has this feature.
P4 Users insufficiently aware of "export" because the word is not found or understood.
  • JC: Possible solutions include moving export next to save-as in menu and navigation from save-as to export.
  • GA: Navigation solution probably too confusing; naming/ordering of menu items, and (possibly) tooltips over menus or status bar indications probably more productive. See this Forum topic. Issue is more than cosmetic because of support overhead answering "how can I join the .au files I saved so I can play them in iTunes"; and because greater prominence of "export" would reduce the risks from over-reliance on projects. These are fragile in novice users' hands, and occasionally unreliable due to not-understood bugs in the code.
P4 Recordings of audio played in Audacity are truncated by approximately 100 ms.
  • GA: To reproduce:
  1. Generate 2 seconds tone
  2. Record from stereo mix (or line-out patched to line-in) with "overdub" on
  3. observe the last 100 ms of the track above is missing from the recording
P4 "Automatically fit" preference: resized track snaps back to fit after any edit or gain/pan change.
  • GA: Many users find this irritating because you cannot adjust gain and pan in one step, or leave track dragged down while adjusting gain/pan.
  • GA: Agreed solution is to change behaviour so that fitting only occurs automatically when adding or deleting a track.
P4 "Automatically fit" preference: tracks not re-fitted if tracks added or deleted then undone/redone.
P4 "Automatically fit" preference: Time, Label, and Note tracks not re-fitted.
P4 "Advanced Mixing Options": Names of all input tracks scaled unreadably small if any input tracks have a long name.
P4 "Advanced Mixing Options": right channel of unsplit stereo pair called "Audio Track - Right".
  • GA: Confusing if you have other tracks not renamed from default because you cannot tell which is which unless you know ordering is done by track position. Note: If you "Split Stereo Track" the fault is corrected (even if you "Make Stereo Track" again).
P4 Selection bugs when zoomed in
  • GA: may also be (partly) responsible for unpredictable behaviour dragging clips - see here
P4 When Control Toolbar is undocked, its associated shortcuts only work if the main application has focus.
P4 Minimum and maximum frequency display in Spectrograms preferences don't work for spectrum log (f) view.
P4 Memory leaks:
P4 Nyquist implementation: Excessive memory usage
  • LL: This will have to be resolved by adding memory pool tracking to lib-src/libnyquist/nyquist/nyqsrc/falloc.c so it can be freed when needed.
P4 (Mac only) Command-modified shortcuts that are also system shortcuts always perform the system action. For example, Command-M does not add label at playback position, but minimises the app. List of system shortcuts.
P4 (Mac only) CoreAudio crash when input device's sample rate is 44100 and the output device's sample rate is 48000.
P4 (Mac only) Envelope points do not restore properly when reopening a saved project -see here .
  • BP: Reproduced on 1.3.3 - 10.5.1, PPC iBook G4 on 28 Mar 08, but *not* on Intel Mac
  • GA: Should be tested with CVS HEAD and PPC, and escalated to P2 if confirmed?
P4 [LL] (Mac *and* Linux only) Random bits of silence occur during recording (Jack and non-Jack versions of this problem).
  • JC: Progress: Udo tried smaller blocksize in linux/jack version of this problem and can now fault after 4 mins. Perhaps small blocksize will help us track down the problem on non-Jack set ups too. However, perhaps Udo's progress is only relevant to using Jack and no help to Mac? And this problem does not occur consistently on a given system?
P4 (Linux only) Defining EXPERIMENTAL_SCOREALIGN prevents building on Linux.
P5 Find Clipping: needs decision on optimal behaviour with regard to when/where created, linking, and label retention if re-run in same track.
  • AP: Create a Label track and call it Clipping, now add chirp track and Find Clipping. All the labels will be added at the above label track even when linking is on. Shouldn't we create a new track named Clipping at the bottom in this case?
  • GA: +1. Rather than add multiple behaviour options maybe we should decide "best behaviour". IMO this is that Find Clipping opens a new "Find Clipping" track if there isn't one already that has been created by that action; extra clipping (or normal) labels can be added to it, but it's disregarded as a linked track.
  • JC: I prefer that 'clipping detected' labels do participate in linking. However if any analysis effects clear out labels before adding new ones then they should always do so without affecting audio....
  • GA: But that exposes the contradiction that removing labels in a normal label track *would* delete the audio. Plus if the clip track is created underneath a linked group, it won't behave as a linked label track anyway. So I came to the conclusion the least confusing solution is that clip track behaves independently of groups.
P5 Meter Toolbar: Right-edge hover corrupts cursor.
  • GA: Hover over the right edge without dragging, then the cursor will always have drag icon wherever the mouse hovers over the meters, until that window is closed.
P5 "Latency problem" warning when audio is pushed behind zero occurs for both tracks of a stereo pair.
P5 R (Windows only) Executable will not launch in Safe Mode but runs an unkillable process.
P5 - P5 Debug Log window and Help > Index... browser do not escape.
P5 Links from built-in text to Wiki to be locally over-ridable in the same way that links from built-in text to external html files can be. This way we can have a local copy of the relevant Wiki pages, if we want to.
P5 Dependencies Dialog: If click on "Copy Selected Audio Into Project" in error, the copying cannot be cancelled from the progress dialog.
P5 Nyquist implementation: (dribble [fname]) function
  • STF: Creates a file as expected, but the file is empty (zero bytes). Not a problem in standalone Nyquist.
  • GA: LL has noted previously that all XLisp and Nyquist functions are now available, so file writing in itself should not be a problem.
P5 Nyquist Prompt should be categorised as "Utility".
  • GA: It would not then be left unsorted if EFFECTS_CATEGORIES was on.
P5 Nyquist: s-add-to sound max-samples "file-name"and s-overwrite issues
  • Dave Storer: see these details.
  • GA: I've noted this so it might provide a reminder for Roger D. to take a look, but as you note, these issues are in Nyquist, so not a specific problem with our implementation of it.
P5 (Windows only) Timer Record progress dialog reappears underneath programs restored to the desktop after hiding the dialog with "Show Desktop". Also the progress dialog ought to disappear with the WIN + M equivalent shortcut, but doesn't.
P5 (Mac only) When Preferences set to "Update display", trying to change timeline position during playback (for example by dragging horizontal scrollbar) causes playback cursor to desynchronise until playback stopped.
P5 (Linux only) Intermittent crashes using Undo command (irrespective of command being undone).
  • Reported by Darren on Ubuntu Gutsy 7.10 with 2.5 GB projects.
P5 (Linux only) Recovery action if project rate not supported by card. OK on Windows.
  • GA: What does this mean exactly? Is it that the project rate is not remembered when recovering as reported on -devel list in May 2007? As at May 08 it is set on Windows.
P5 (Linux only) Miscellaneous OSS crashes.
  • Crash reported by SIEGERSTEIN: 'failed in 'src/hostapi/oss/pa_unix_oss.c', line: 1206'
  • Mihail's issue: PA19 uses oss; without load/compile oss support in alsa (snd-pcm-oss), Audacity crashes on init PA19.
  • GA: Are these still replicable or are they fixed with the PA updates?

Not aiming to do for 1.4.0

This has moved to release checklist not aiming for 1.4 and now includes former "Aim tos" from this page. Many of these "Aim tos" are relatively small items but could nonetheless make a worthwhile difference for the time involved. Please do not forget them.

If you claim ownership to items in "Not Aiming", please cut them from that page and park them here:

Truncate Silence needs a "remove DC bias" before running the effect.

  • RS: Started to fix this bug 04 Apr 2009