Release Checklist

This is the de facto bug list for all Stable and Beta releases of Audacity. The current suggestion is that Beta releases are blocked until all P1 bugs are fixed, and Stable blocked until all P1 and P2 bugs are fixed. There is no pre-determined plan for dealing with lower priority bugs.

Items added as Priority P1, P2 or P3 should be added to Known Issues, unless they are absent from the published release that page refers to. When cleared, move the items down to the "Cleared in CVS" section of that page. Former "Aim to" items from this page have now been moved to the top of Release checklist not aiming for 1.4. If you claim ownership of any items on Release checklist not aiming for 1.4, please cut them from there and and park them at the bottom of Release Checklist. Testers should refer to Watching Brief (now on its own page) for intermittent/not fully understood issues.

Please also refer regularly to these pages:

Documentation Checklist, for documentation changes needed for 1.4 Manual and any developer recruitment drive.

Wording, where we track suggested changes to the exact words that appear on a dialogue

Pending website changes where we post suggested wording or layout changes to our audacity.sourceforge.net and audacityteam.org sites (except the Wiki).

Unless indicated by discussion against particular items, these should be regarded as needing attention. When processed, please move them to the "Done" section of those pages.

• Patches are added and tracked on the Sourceforge Patch Tracker .

• There are companion pages to discuss and monitor development of our audacityteam.org sites: Wiki Development Checklist (for both this Wiki and the Manual Wiki) and Forum Development Checklist. Relevant items include security issues, bug fixes and enhanced functionality through installing additional extensions.

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 web site 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/maketarball.sh.

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.

Blocking Issues

P2 (Stable Release Blockers)

P2	Spurious "not writable/disk full" errors when saving projects. GA: 19 Sep 09 - Very frequent reports on Windows, occasional on Linux. Usually affects only re-opened projects. No known scenario to reproduce, though select all, copy/paste to new project and save that project always cures it. MJS: Reproducible error when project includes silence confirmed as 'fixed' on Win by GA after LL's fixing. GA: Forum and other complainants invited to try Nightly build to see if errors still occur.
P2	Desynchronised playback mixing of short regions in different tracks. GA: Not reproducible to order, but likely to occur if repeatedly duplicating short selections in a track. Discussion here. GA: Reproducible scenario found if the short clip is time-shifted away from zero and not at the current project rate. If tracks are mixed/rendered or exported, audio in the short clip may be lost. MJS: Leland has committed a fix for this 'reproducible scenario', confirmed here (Win XP). How do we know if this has fixed the 'unreproducible scenario'? GA: Confirmed the "reproducible" part of the bug is fixed for me on Ubuntu and for another user on Fedora. However that user has led me to this further reproducible scenario which seems to be an issue with loop play when another track is not at the project rate.
P2	Reverse does not reverse clip boundaries. GA: Leads to loss of association between boundaries and original audio, and loss of audio if the clips were separated by white space. See this thread. GA: Claimed by Vidyashankar Vellal
P2	Edit Labels: "start/end times display as zero" fix breaks screen reading ability.
P2	Nyquist effects join separate clips together. 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 filename 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.
P2	Boundary drawing problem with Generate and SoundTouch GA: When applied over existing split lines, these effects sometimes produce a faint or no clip line. This may be demoted, subject to discussion. See this thread.
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.
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. Symptoms: 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 sound cards). (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.

Non-blockers

P3 Release Noted (Prioritised non-blockers)

P2	Effects processing/waveform rendering after process completion much slower than 1.3.8. GA: Reported several times on Windows. See this thread.
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	Labels cannot be repeated RA: This causes an apparent bug because when you repeat a labelled selection, the labels don't get repeated. I presume this would be a relatively simple issue to fix.
P3	SBSMS, Change Speed, Change Tempo do not keep labels in sync. GA: To reproduce: Turn linking on, create 30 seconds default tone, select 5 - 10 seconds and Amplify by -20 dB to see it 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) Label does not move. Labels do move with Repeat in the above scenario, and do move with Reverse if label included in selection region.
P3	Truncate Silence does not keep labels in sync 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	R  Unreliable project re-opening with orphaned and missing blockfile errors. GA: There are reports every week of users losing data correctly reopening a 1.3 .aup file in the exact same 1.3 version they created it in. "Orphaned" or "missing" blockfile errors are received and when users accept the "recommended" course to delete, the project is silenced. This frequency of data loss is not acceptable in 1.4.0. We should be on the alert for these issues, and as soon as steps to reproduce are found, escalate the specific problem to P2. One definite scenario where this has been reported is having multiple projects open, and blockfiles are saved to the wrong _data folder. GA has not yet managed to replicate it, though still has some more reported steps to try and do so...
P3	R   (reported on Mac) Unreliable project re-opening due to duplicate attributes GA: When a saved project is re-opened it fails with "duplicate attribute" error. Almost always involves imported MP3s; the .aup file shows one or more tags with two "name" attributes, for example <tag name="ARTIST" name="ARTIST"/>. Changing second "name" to "value" allows project to re-open. GA (Windows) and a Mac tester have tried to reproduce this with an MP3 that created this issue for one user, but the projects re-opened perfectly. Bug also reported to occur if a diacritic is included in a label. GA: One report from CVS on Mac 06 July 09 finds a project with diacritics in labels that saved in 1.3.7 with duplicate attributes saves correctly in CVS.
P3	Unreliable Automatic Crash Recovery. LL: I've seen some really strange (attempted) recoveries. I haven't yet looked into them, but I shall soon since my wife is complaining about it as well. GA: These known problems have been reported. They should be verified and escalated to P2 if valid: If a crash occurs with two tracks open, multiple projects are recovered Recovery fails if a track is imported then another added after the autosave interval Complete recovery failures (empty projects) seen on single tracks which are only generated tones. (Mac) freeze on Intel Macs when starting recovery (Mac) (Intel and PPC) "Junk after document" warnings then recovered project is empty. See here and download here an example auto save file and _data folder.
P3	R  AIFF files created by Audacity from recorded or generated data import intermittently (but at times very frequently) as noise - files play fine in other software. GA: Much of the time, 1.3.7 or later on Windows cannot be relied on to import files exported with the explicit "AIFF (Apple) signed 16 bit PCM" filter. Appears to affect exports from recorded data (at any Defauit Sample Rate), or from tones generated at 24-bit. Same problem occurs with the AIFF 24-bit option accessed with "Options" button, but not apparently the comparable 16-bit option. Export Multiple seems affected the same way as regular export. Tested at 44100 Hz, reading directly. On Mac, a user 22 March 09 reports 1.3.7 "suddenly" producing noise when importing AIFF files where it did not before in many similar imports - user changed default sample format to 24-bit at about the same time. More details here. LL: Gale, have you been able to find a pattern to recreate this? I've tried numerous variations on OSX and Windows and it always seems to import ok. GA: Are you using a release build? In ANSI Release from HEAD, I created a chirp tone in 24-bit quality, recorded it using stereo mix then exported only the recorded track using the explicit (no options available) AIFF (Apple) signed 16-bit PCM choice. I changed Quality to 32-bit, closed the tracks and repeated the generation, record and export. I am not getting noise on importing the files back into Audacity but what I can replicate is that about half the time the files will crash both HEAD and 1.3.7 Unicode Release; if they don't crash they import properly. So behaviour compared to when I last tested is not the same. I have tried importing with the "All supported files" and "FFmpeg-compatible files" filter and the problem is identical. In 1.2.6 I can import these files dozens of times without problem.
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. Import a 3 minute or longer file into fresh project, which fits to project 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. Force quit and recovered track captures the amplify but is fitted to project.
P3	Time Track disables audio/label linking. GA: Steps to reproduce: Add a tone of 30 seconds in a clean project with linking enabled Select 5 - 10 seconds, CTRL+B and name label Tracks > Add New > Time Track Select 2 - 4 seconds in the tone and Edit > Cut; audio is cut but label does not move Edit > Undo 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.
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 consistent with the schedule. 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).
P3	(reported on Windows) Timer Record cannot maintain scheduled duration if system clock changes GA: 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. Schedule that recording exactly the same and change system time to one minute after the end of the recording. With 1.3.8 Alpha from 04 June 09, recording will cease immediately, having produced a few seconds of recording. In a previous test of 1.3.8 Alpha from 29 April 09, an hour long recording straddling midnight had its elapsed and remaining times frozen when system clock changed to after end of recording, and carried on after originally intended duration, but could be cancelled. Repeating that same hour long test straddling midnight in 04 June 09 build simply aborts recording when time changes, yet Timer Record code did not change between those dates. Are these fixable by relying on a Widgets timer for duration? Many people synchronize system time to online atomic clocks (Windows XP does it by default).
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 plugin, but AFAIK has not been fixed in the v1 plugin. Correctly the logic allows the plugin to process without crash.
P3	Residual FFmpeg issues: "Select file(s) for batch processing..." dialogue lacks "All Supported files" and "FFmpeg-compatible files" filters √  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 plugin 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	On-Demand: when importing a mixture of uncompressed and compressed files, on-demand loading does not start until normal import of the compressed files completes, if the names of the compressed files come earlier in the alphabet. GA: On Windows, video files with a preceding name which similarly held up on-demand loading are as of 07 Oct 08 now importing second when dragged in, so the OD file is not delayed, but the tracks are now out of alphabetical order in the track list. Also, correct alphabetical order when using File > Open or Import now depends (on Windows) on the order the files are selected in. GA suggests therefore we could prioritise OD files to import first, then re-order the non-OD files in the track list if needed. MC: Fixed 14 Dec 08. GA: 24 Jan 08 - not fixed on Windows, except that files now import in alphabetical order irrespective of the order they were selected in. The basic problem remains: using "All supported files" filter, any compressed file (audio or video) that has a preceding name prevents OD loading of an uncompressed file with a following name. until the compressed file has loaded. So, much of the benefit of OD loading is lost. MC: Discussed in Feb. 09 as resolved for the time being, but the discussion is still open. The implemented solution is different from planned to minimize UI blockage: Order of sort depends on loading method (if open is used, OD imports first). GA: Order of sort depends on loading method on Mac, but on Windows the non-OD file always comes first with both drag/import and open. Therefore, sort order is always wrong if the non-OD file comes later in the alphabet, and we're not getting any benefit on Windows of OD files loading first. Do you see a way of getting OD to come first on Windows when using Open or context-menu opening? And is a resort after load practical? Out of order loading remains I think a P3 issue in itself. MC: I forgot about the windows open behavior - it should be different. I just verified it on the mac, so I will need help or access to a windows machine to debug this. But in general the non OD files come first so that the UI isn't blocked while the OD files are being loaded, and thus the user can have the most time interacting with with the project while the files are being loaded. The new method still has sorted order, but its new sort hierarchy is filetype first, then name second, which seems like a reasonable behavior to me. A post-resort of the tracks seems actually disorienting, since the user is watching them being placed in this order as the files import. Thoughts? GA: Yes thinking about it, I agree a post-load resort probably would be disorienting. I'm just conscious though of complaints about not importing in file name order, which I think is what the user will be aware of. If we drag in B.mp3 and A.wav, can we place A.wav above B.mp3 to begin with, when it starts to load? MC: Fixed pending verification. Now all files load in alphabetical order, but the OD system is paused until the last of the modal dialogs ends.
P3	When changing language in Preferences, some elements don't change until restart. Affects Audio Track at the top of the Track Drop-down menu, and the toolbars tooltips (except Selection Bar). LL: It looks like this has been partially fixed...the track menus now change, but tooltips are still an issue. LL: This should now be fixed...just needs verification. GA: Still an issue with generic track name ("Audio Track" in English) and Meter Toolbar channel names not changing, and with Selection Toolbar elements running into each other: after changing from English to French; then restarting and changing from French to English.
P3	R Pressing Play (but not Space) or clicking on the timeline in a second project when another is already playing stops playback of the first project. zachelko: On Windows with Audacity 1.2.6 I'm not experiencing this. However, what seems to happen is that if a track in one project is playing and you attempt to play a track in another project, the play button does nothing and the track isn't started. Was this possibly the "fix" ? GA: Because 1.2.6 does not have this problem, the bug is marked R , denoting it is a regression against 1.2.6. To replicate all issues on this list and Release checklist not aiming for 1.4, please test against latest CVS HEAD. zachelko: This issue is deeper than just the "Play" function. Pressing Play, Pause, or Stop in another window while a track is playing in a different window behaves as if you hit those buttons in the window that has the playing tracks. I'm looking into a fix for this now. Was ControlToolbar.cpp over-hauled since the 1.2.6 release? By looking at it for the past 30 minutes or so, it would seem that a lot of these protections would have taken place in here... zachelko: Submitted patch to mailing list 3/19/2009 to address Play/Pause/Stop spanning across all open windows. Timeline issue still exists.
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: As of 12 Aug 09, Audacity cannot see any of its own FLAC tags in 1.3.9-alpha on Linux. Confirmed by STF. GA: Album art and lyrics are deleted in the exported file, instead of being ignored.
P3	Nyquist implementation: Values appearing in effects text boxes are not always the hard-coded/previously entered values. GA: Values seem to be re-computed from the pixel values of the slider as visible on-screen, so the nearest value obtainable by using the slider is presented when re-launching the plug-in, rather than the coded default or last entered value (example: highpass.ny). Compute the value from the text field then set the slider? See this thread LL: The first part of the issue "100 becomes 101" will have to be resolved and is happening at the lines mentioned in the report. However, this only occurs on redisplay of the dialog. So, if you enter 100 and click OK (or press ENTER), 100 is what will be used when applying the effect. The second part "1.0 = 0.997" is normal floating point behavior.
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
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) 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) Audacity output slider may affect playback meters. GA: If Portmixer uses emulated playback volume rather than native, the Audacity output slider will affect the VU playback meters and these may not then reflect the actual volume level of the waveform.
P3	(Linux only) Effects and other dialogues do not have focus on opening. GA: This is a bug in wxGTK for which there is no current workaround. Click in the dialogue 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	Truncate Silence doesn't work well on multiple tracks Selecting multiple tracks of audio and then trying to Truncate Silence doesn't work in a terribly useful on 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.
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: Generate DTMF tone sequence Edit > Duplicate twice to create four tracks in all Select the top track and Analyze > Silence Finder (default settings) 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	Vertical ruler scale only has zeros on a recorded track displaying Waveform (dB) view. GA: Steps to reproduce: Launch Audacity Record a few seconds of stereo audio Stop Change to Waveform (dB) view if Default View Mode in Preferences not already set to it Only figures on the vertical scale are "0" and "0" 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 dialogue. 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 dialogue.
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 dialogue: 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 filename 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	Export Multiple success dialogue cannot be dismissed with ENTER.
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	EQ: Can't save a flat curve. GA: Steps: Load EQ window with RIAA preset visible Click "Flat" button as save preset as "Flat" or other name. Click OK or Cancel Reload EQ window. The RIAA curve will display (as "Custom", as I think intended), and selecting "Flat" preset shows that it is actually the RIAA curve.
P4	Toolbar and track gain/pan sliders should display current slider position on hover GA: Too fiddly and undiscoverable for sighted users to have to click on slider to read the current setting.
P4	Name in Track 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: Generate 2 seconds tone Record from stereo mix (or line-out patched to line-in) with "overdub" on 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: SLV2 libraries Reported by MJS Effect Previews Reported by Dawson Written
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	Pressing OK in Preferences removes action-specific text in last Undo menu item.
P5	Standardise per-platform behaviour after changing Default Sample Rate in Preferences: On Windows, changing the rate in Preferences changes the visible project rate at once, so affects all new tracks in current project. On other platforms, visible project rate does not change until opening a new project. This creates problems in the Manual. Windows users seem to like current behaviour and report a bug if the visible rate does not change. We need to decide. Similarly, on Windows, a new track in the current project takes the changed default sample format at once.
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 Dialogue: If click on "Copy Selected Audio Into Project" in error, the copying cannot be cancelled from the progress dialogue.
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) If Windows Taskbar positioned at top, title bar of "Welcome Message" is obscured. GA: Does not affect the other three edge positions.
P5	(Windows only) Timer Record progress dialogue reappears underneath programs restored to the desktop after hiding the dialogue with "Show Desktop". Also the progress dialogue 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