Difference between revisions of "Release Checklist"

From Audacity Wiki
Jump to: navigation, search
(Under p3 for system mixer level sliders, added problem also occurs under windows xp for logitech usb desktop microphone)
(removing gaclrecords link)
 
(307 intermediate revisions by 19 users not shown)
Line 1: Line 1:
 
{{Template:Audacity Devel}}
 
{{Template:Audacity Devel}}
  
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.
 
  
 +
{{Introrel|This was the de facto bug list for all Stable and Beta releases of Audacity until February 2010. A modern installation of [http://www.bugzilla.org/ Bugzilla] is now used instead.|Go to [[Bug Lists]] to see various categorised lists of bugs in our current Bugzilla database.|Patches are currently tracked on [https://bugzilla.audacityteam.org/ Bugzilla].}}
  
__TOC__
 
  
<!--{{alert|1='''19 September 08:''' In order to focus on the existing priority issues for 1.4 and actually have it appear in a reasonable time frame:
+
{{Advice|'''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.
*<font color="red">P1</font> and P2 bugs listed here should be addressed '''first'''. '''Note:''' for purposes of GSoC polishing, GSoC bugs (currently all in P3) are being treated as <font color="red">P1</font> for 1.3.6 Beta release.
 
*Newly discovered <font color="red">P1</font> or P2 issues, or proposals to change the scope or priority of existing issues, are to be '''added to [[Pending Release Issues]]'''. They will need approval from at least two of Vaughan, Gale and James before the change can be made here.  
 
}}-->
 
  
 +
There is a [[Talk:Release Checklist#integration|discussion]] on the Talk Page about what to do with various other pages/tools more or less associated with the Checklist.}}
  
{{adviceopen|1=<ul><li>Items added as Priority <font color="red">P1</font>, 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.</li></ul> 
+
__NOTOC__
*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 [[#Not aiming to do for 1.4.0|bottom of Release Checklist]]. 
 
*Testers should refer to [[Release Checklist Watching Brief|Watching Brief]] (now on its own page) for intermittent/not fully understood issues.}}
 
  
{{Hint|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 {{external|1=[http://sourceforge.net/tracker/?group_id=6235&atid=306235 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 ==
 
== Essential changes ==
These are other changes to source code that are deemed essential   We will do all of these for final 1.3.7 release candidate or 1.4.0 release as noted below.
+
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'''.  These are needed for '''1.3.7 rc''':
 
** Repair the script to extract zipped html help from the Manual Wiki. If this is impossible, James could make a snapshot zip using {{external|1=[http://www.audacityteam.org/manual/index.php?title=ToDo#Wget Wget and a file rename script]}}. 
 
** Installer to be modified to also install Html help. Consider giving Windows installer an option to install help for all users, not just current user. 
 
** Address [[Documentation Checklist|documentation]] issues, including website updates.
 
** '''For 1.4''', "completing the Manual". Needed before we can release any versions of 1.4.
 
 
 
* '''Nyquist plug-ins (for 1.4):''' 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.  
 
  
 +
* '''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/maketarball.sh.
  
 
== Rating Keys for Issues ==  
 
== Rating Keys for Issues ==  
Line 51: Line 27:
 
|colspan="2" align="center"|All issues are given a '''Priority Rating''' of 1 to 5 as follows:
 
|colspan="2" align="center"|All issues are given a '''Priority Rating''' of 1 to 5 as follows:
 
|-
 
|-
|valign="top"|<font color="red">'''P1'''</font>
+
|valign="top"|'''P1'''
 
|Blocks any Release - See the [[Talk:Release Checklist|discussion page]] for a guide to what may be deemed an issue that blocks release.  
 
|Blocks any Release - See the [[Talk:Release Checklist|discussion page]] for a guide to what may be deemed an issue that blocks release.  
 
|-
 
|-
Line 70: Line 46:
 
|-
 
|-
 
|valign="top"|<font color="red"> '''''R''''' </font>
 
|valign="top"|<font color="red"> '''''R''''' </font>
|'''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.  
+
|'''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.
|}
+
|-
 +
|colspan="2" align="right"| There is some more information about P numbers on the [[Talk:Release_Checklist|talk]] page...
 +
|}  
 +
 
 +
 
 +
<h2 style="border-bottom: 1px solid #aaa;padding-bottom:0.1em;">Blocking Issues</h2>
  
 +
<!--<h3 style="border-bottom: 1px solid #aaa;padding-bottom:0.1em">P1 (Block any Release)</h3>
  
<h2 style="border-bottom: 1px solid #aaa;padding-bottom:0.1em; color:red">Blocking Issues</h2>
 
<!--<h3 style="border-bottom: 1px solid #aaa;padding-bottom:0.1em"><font color="red">P1 (Block any Release) </font> </h3>
 
 
 
{| cellpadding="10px"   
 
{| cellpadding="10px"   
 
|-
 
|-
|valign="top" width="25px"|<font color="red">'''P1'''</font>
 
|<font color="red"> ''' '''
 
 
|}-->
 
|}-->
  
Line 87: Line 64:
 
{| cellpadding="10px"
 
{| cellpadding="10px"
 
|-
 
|-
|valign="top" width="25px"|'''P2'''
+
|valign="top" width="25px"|'''P2'''  
|'''Nyquist effects, SoundTouch, SBSMS and Generators remove or corrupt cut and split lines in the modified region.''' Cut lines are completely removed, split lines are replaced with new, unwanted split lines at the left and right region boundaries. Probably any effect using HandleClear() will exhibit the same problem.
+
|<font color="red"> '''''R''''' &nbsp;</font>''(Windows)'' '''Projects crash when applying repeated effects on zoomed in regions towards the end of audio tracks'''
* '''LLL:''' I believe this to be fixed now...just needs some verification.
+
* '''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 http://n2.nabble.com/Various-P2s-and-P3s-a-repeatable-case-td4040974.html 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.
 
|-
 
|-
 
|valign="top"|'''P2'''
 
|valign="top"|'''P2'''
|'''Preferences menu in some locales overflows using smaller screen sizes/larger fonts, or default Mac at 1024x768.''' See [[Preferences Improvements]]
+
| ''(Windows 7)'' '''Runtime Error Program: (location) R6034 on launching Audacity.'''
* '''GA:''' Seems fixed apart from minor polishing, except that the meaning of checking/unchecking the boxes on the Warnings tab is reversed. You get the warning about saving a project if you uncheck the box "Show Warnings/Prompts When saving projects, and if you check "Don't show again" in that warning, this checks the box in Preferences.  
+
* '''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.    
 
|-
 
|-
 
|valign="top"|'''P2'''
 
|valign="top"|'''P2'''
|'''Ensure all Edit menu items consistently enabled and work consistently when select-all-on-none enabled.''' See {{external|[http://www.nabble.com/Greying-out-of-items-t4536420.html#a12947298 here]}}.
+
| ''(Windows Vista, 7)'' '''Input sources cannot be selected in Mixer Toolbar.'''  
*'''JC:''' Is it really what we want?  E.g click split-new twice, and we get four tracks.  Is it not less confusing to leave it greyed out?
+
* '''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 [http://n2.nabble.com/%22Improved%22-Mixer-Toolbar-tp2252375p2252375.html here] and [http://n2.nabble.com/P2-Windows-Vista-7-Input-sources-cannot-be-selected-in-Mixer-Toolbar-tp3710193p3718888.html how it might look].      
*'''GA:''' If you turn off select-all-on-none, and with one track on screen, Select All, Split New, Select All and Split New, you also get four tracks, so I think it is what we want. Now, if you have a track selected with no time area selected, nothing on the clipboard and click the Edit menu, all the edit menu is enabled except Paste. But if we click outside the track(s) so that none are selected, we lose ability to click on  Split Cut, Trim, Delete, Split Delete, Silence, Join, Disjoin, Duplicate and Find Zero Crossings - yet we could still Cut, Copy and Split (FWIW) and Split New. I think that will be very confusing as it's a halfway house between Select-all-on-none and not. So all Edit menu items, and File > Export Selection to be available even if no tracks are selected and when clicking outside the tracks.  
 
*David B. suggests longer term having two [[Release checklist not_ aiming for 1.4#Other|independent preference options]] for selecting all tracks and selecting all audio to give more control.  
 
* '''MJS:''' I suggest (after reviewing the menus):
 
**Leave grey:
 
***"Export Selection..." - there isn't a selection.
 
***"Split Cut" / "Trim" / "Split Delete" / "Split" / "Split New" - they make little sense without a selection.
 
**Allow with "select all":
 
***"Cut" and "Copy" - to cut/copy the whole lot and paste into another project, maybe?
 
***"Delete"
 
***"Silence Audio"  I note it deletes labels as well (and perhaps shouldn't).
 
***"Join" - to join up everything
 
***"Detach at Silences" - as above
 
***"Duplicate" - as above
 
***"Mix and Render" - makes sense
 
***"Resample" - makes sense
 
***"Remove Tracks" - makes sense
 
***All (most?) of the effects.  
 
 
|-
 
|-
 
|valign="top"|'''P2'''
 
|valign="top"|'''P2'''
|''(was P3)'' <font color="red"> '''''R''''' </font>&nbsp; '''Export Multiple fails with no export or warning if an empty label is encountered.'''
+
|''(Windows Vista, 7)'' '''Audacity input/output level sliders act independently of/incorrectly with system level sliders.'''
<ul><li>'''GA:''' To reproduce:
+
Symptoms:
# Generate a tone
+
* 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).
# Click in track, CTRL + B, click, CTRL + B along the track
+
* ''(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.  
# File > Export Multiple and hit Export
+
* 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.
# Click Export button but nothing happens</li></ul><ul>If "Include audio before first label" is checked, the metadata window appears for the "audio before" file, then returns on OK to the Export Multiple dialogue.<p>In 1.2.6, export multiple with empty labels creates files ".wav", "-2.wav", "-3.wav" (or whatever format) and so on. Maybe that should be followed here (except "-1.wav" for the first automatically generated file might be better).</p></ul> 
 
* '''LLL:''' Or would it be better to ask the user to specify a name if it encounters a blank label?  Similar to the dialog you get if you have a ":" or "/" in the label.
 
* '''GA:''' It's a good idea, but the case for it is not so clear as it is with illegal characters. I know some users who always export empty labels to save typing and are happy with the autonaming, so would not welcome a large number of prompts. Could the prompt include a checkbox "Always export empty labels automatically" and that is then set in .cfg?
 
* '''LLL:''' If that's the concern, then they should be just as happy with us providing a name for them, like "untitled" or "unnamed" or "empty" or "Automatically Generated Name Because It Was Blank".  The empty name causes unnecessary coding hackage to create the "-1" file and on at least OSX, a file beginning with a "." will be hidden and not seen if the user tries to open it.
 
* '''GA:''' Obviously I assumed recreating the 1.2.6 behaviour did not have such problems.  The issue is not the name itself, but that user will not want prompts for every track (as happens with the "illegal" prompt) if they prefer to use empty labels. So are you OK with one prompt, they choose what it is (or use our default), then we append a suffix as per "numbering consecutively")?<p>Just remembered: the "numbering consecutively" suffix is described as a "prefix" in the Export Multiple dialogue, and a few have been complaining about that misnomer. Some users think it should actually be a prefix but looks as if too much work (?). Either way, I'd like to see the "nn" form as per standard on audio CDs, so we lose the problem with folks who don't have natural number sort. Or, it could be an option, default is "nn". 
 
* '''LLL:''' Give it a try.  I applied Rupinder's patch to correct this P2 and instead of blank names they'll be called "untitled" and I added a list of files exported on the final status dialog to let the users know what the final names were.  See how it feels.  It can be easily removed.
 
* '''GA:''' I like it. 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".
 
* '''LLL:''' 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.
 
 
|-
 
|-
 
|valign="top"|'''P2'''
 
|valign="top"|'''P2'''
|''(was P3)'' '''Labels should move with all the timeline changing effects.''' They do not move with Effect > Repeat, Reverse, and Truncate Silence.   
+
|''(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.   
 
|}
 
|}
  
Line 140: Line 100:
 
{| cellpadding="10px"
 
{| cellpadding="10px"
 
|-
 
|-
|valign="top" width="25px"|'''P3'''
+
|valign="top" width="25px"|'''P3'''  
|'''Exporting audio with a length of 22,752072 samples or multiples thereof causes samples to be missing from the end of the exported file.'''
+
|'''Unmodified Transport shortcuts write label at cursor position after user adds a label at playback position.'''
* '''GA:''' To reproduce, create a tone of 22,752072 samples, and use Draw Tool to modify the last sample so you can recognise it. Export as PCM 16-bit WAV, and re-import. The modified last sample will be missing. Now exit and restart and create a tone of 45504144 samples (22752072 * 2), modify the last two samples, export and re-import. The last two modified samples will be missing.  
+
* '''GA:'''
 +
# Set Play, Stop and Play/Stop shortcuts to unmodified characters like "S" or "U"
 +
# Generate a 30s tone
 +
# Use shortcut to start play
 +
# Use shortcut to add label at playback position then hit ENTER to confirm label
 +
# 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.
 +
<ul style="list-style-image: none; list-style-type: none">
 +
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. </ul>
 +
|-
 +
|valign="top"|'''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 [http://n2.nabble.com/Save-As-dialog-filter-bug-tp4138343p4185153.html 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.
 +
|-
 +
|valign="top"|'''P3'''
 +
|<font color="red"> '''''R''''' </font>&nbsp; '''No longer possible to overwrite a closed project.'''
 +
* '''JC:''' Reported by Doug Grinbergs.
 +
* '''GA:''' Was a P1 ([http://n2.nabble.com/P1-Overwriting-existing-project-makes-the-original-unusable-and-SaveAs-doesn-t-prompt-the-overwrite-tp4127291p4127291.html 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:Release Checklist|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. 
 +
|-
 +
|valign="top"|'''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...  
 +
|-
 +
|valign="top"|'''P3'''
 +
|''(Windows)'' '''Visible scanning dialog on every launch of Audacity when no VST plug-ins present.'''
 +
* '''GA:''' See [http://n2.nabble.com/Hang-when-scanning-for-VST-effects-on-Mac-tp3874601p3874601.html 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.    
 
|-
 
|-
 
|valign="top"|'''P3'''  
 
|valign="top"|'''P3'''  
|<font color="red"> '''''R''''' </font>&nbsp;'''Unreliable project re-opening with orphaned and missing blockfile errors.'''  
+
|''(was P2) (Mac 10.5.8 PPC)'' '''Hang when scanning for VST effects on fresh install.'''
* '''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...
+
* '''GA:''' See [http://n2.nabble.com/Hang-when-scanning-for-VST-effects-on-Mac-tp3874601p3874601.html 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. 
 +
|-
 +
|valign="top"|'''P3'''
 +
|'''Effects processing/waveform rendering after process completion much slower than 1.3.8.''' 
 +
* '''GA:''' Reported several times on Windows. See [http://n2.nabble.com/Process-and-display-times-running-effects-in-1-3-9-tp3630583p3630583.html 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.  
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''Unreliable Automatic Crash Recovery.'''  
+
|'''Nyquist effects join separate clips together, and add spurious split lines if applied over clip boundaries.'''
* '''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:''' SBSMS now fixed by DH, leaving the subject problem. See [http://n2.nabble.com/Removing-items-from-release-checklist-tp3541524p3545856.html this thread].
* '''GA:''' These known problems have been reported. They should be verified and escalated to P2 if valid:
+
* '''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:
** If a crash occurs with two tracks open, multiple projects are recovered
+
** simply running 'detach at silences' after the effect (I haven't looked at how this works yet but it seems hopeful)
** Recovery fails if a track is imported then another added after the autosave interval
+
** changing the nyquist interface (e.g. the 'nil means white space' option) which would involve changing all of those plug-ins
** Complete recovery failures (empty projects) seen on single tracks which are only generated tones.  
+
** recognising the known plug-ins by file name and dealing with them appropriately (pretty unpleasant temporary solution)
** ''(Mac)'' freeze on Intel Macs when starting recovery
+
* '''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.
** ''(Mac)'' (Intel and PPC) "Junk after document" warnings then recovered project is empty. See [http://www.nabble.com/forum/Search.jtp?query=%22junk+after+document%22&local=y&forum=4506 here] and download [http://www.gaclrecords.org.uk/sussexbooks.zip here] an example auto save file and _data folder.  
+
* '''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.  
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|<font color="red"> '''''R''''' </font>&nbsp;'''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.'''  
+
|'''Cursor jumps to start of scroll after playback cursor goes past scroll'''
*'''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. [http://n2.nabble.com/Problem-with-AIFF-files-td2515198.html More details here].
+
* '''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.  
*'''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.
+
*'''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:''' 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.  
+
* '''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.  
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|<font color="green">'''''&radic;'''''&nbsp;'''</font> MP3s exported with Unicode metadata tags can't be played by Windows Media Player (WMP) and neither WMP or Explorer can see or edit the tags.'''
+
|'''Track groups are limited to one label track.'''  
* '''LL:''' It's because libid3tag exports Unicode data as big-endian and Explorer/WMP seem to require little-endianAnd I don't see a way to coax libid3tag into writing in little-endian format without change the library...which I may just do since it will be short lived due to taglib coming post-1.4.
+
* ''Only release note for releases where linking-labels enabled''
* '''GA:''' Well as an interim fix that would of course make Windows users who only use WMP much happier - but would that then break MP3 export on Mac, or on iTunes on either platform? And how does taglib avoid this issue?
+
* '''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 groupWe 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).
* '''LL:''' I've changed it...give it a try.  WMP, Explorer and iTunes on Intel Mac sees them just fine.  Looks like taglib write little endian tags by default.
+
* '''GA:''' moved up from P4, given the Manual says a group can have multiple label tracks and we decided not to change the Manual.  
* '''GA:''' Looks fine to me. Will be cleared unless Forum complainants find a problem with the fix.  
 
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''Advanced Mixing Options dialogue displays and permits routeing of all tracks in project even if they are muted (and thus won't be exported).'''
+
|'''SBSMS, Change Speed, Change Tempo do not keep group synchronisation.'''
* '''zachelko:''' How are you getting to the Advanced Mixing Options dialog? I'd like to look into this and submit a patch. Thanks.
+
* ''Only release note for releases where linking-labels enabled''
* '''GA:''' Thanks. Multi-channel export is enabled on the Import / Export tab of Preferences by checking "Use custom mix..." in the "When exporting tracks..." panel.  
+
* '''GA:''' To reproduce:
* '''zachelko:''' Submitted patch to mailing list on 3/17/2009
+
# Turn linking on, create 30 seconds default tone, select 5 - 10 seconds and Amplify by -20 dB to see it
 +
# Duplicate the track
 +
# 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)
 +
# Neither labels nor the audio in the other track moves.  
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''Modal block circumventable using File > New (Mac only) or shortcuts, leading to risk of crash.''' See [http://n2.nabble.com/Method-to-circumvent-modal-block-on-Windows-td2184609.html this thread].
+
|''' 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.
 +
|-
 +
|valign="top"|'''P3'''
 +
|'''Mixer Board release-noted issues:'''
 +
* '''GA:'''
 +
* Meter range does not reflect a change in the dB range meter preferences until restart
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''Files > Recent Files drops file paths when list used or updated.''' Path returns on restart.
+
|'''Automatic Crash Recovery: disregards track zoom level and position.'''
* '''LLL:''' The wx class does this on purpose. I've been considering doing our own class to handle history since there's an issue with Unicode characters in filenames on the Mac in regards to the wx history class. There's no easy way to override that class to get around the problem and there's no easy way to stop it from removing the path, so maybe our own class is in order.
+
* '''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.  
 
|-
 
|-
|valign="top"|'''P3'''  
+
|valign="top"|'''P3'''
|''(was P2)'' '''If shortcut for "Add label at playback position" is an unmodified character, the second time the label is confirmed by ENTER, that shortcut will be entered in a label placed at the start cursor.''' Using up arrow instead of ENTER avoids this problem.
+
|'''Time Track disables audio/label linking.'''
 +
* ''Only release note for releases where linking-labels enabled''
 +
* '''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
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''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.'''
+
|'''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 [http://n2.nabble.com/P2-Ensure-all-Edit-menu-items-consistently-enabled-tp1683420p3552298.html this thread].
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.'''
+
|'''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. 
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''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().
+
|'''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.  
 +
|-
 +
|id ="timer" valign="top"|'''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.
 +
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''When a Time Track and Label Track is present, audio is not pasted into all tracks, leading to desynchronisation.'''
+
|''(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.  
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''Residual FFmpeg issues:'''
+
|'''Modal block circumventable using File > New (Mac only) or shortcuts, leading to risk of crash.''' See [http://n2.nabble.com/Method-to-circumvent-modal-block-on-Windows-td2184609.html this thread].
* "Select file(s) for batch processing..." dialogue lacks "All Supported files" and "FFmpeg-compatible files" filters
 
* <font color="green">'''''&radic;'''''</font>&nbsp; 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.''
 
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''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.'''
+
|'''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.'''
* '''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:''' [http://n2.nabble.com/Release-Checklist%3A-Relegating-from---promoting-to-P2-tp1666362p2388531.html 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 (open vs import). 
 
* '''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? 
 
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''Preferences window: OK button does not work when a tab is selected in the left-hand panel.'''
+
|'''WAVEX (Microsoft) headers: GSM 6.10 files cannot be exported, and U-Law/A-Law files may not be playable.'''
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''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).  
+
|'''LADSPA Multiband EQ may not be visible in Effect menu (occurs on Windows XP), and crashes soon after opening.
* '''LL:''' It looks like this has been partially fixed...the track menus now change, but tooltips are still an issue.
+
*''' 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.
 +
|-
 +
|valign="top"|'''P3'''
 +
|'''Residual FFmpeg issues:'''
 +
* <font color="green">'''''&radic;'''''</font>&nbsp; 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.''
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|'''<font color="red">''R''</font> Pressing Play (but not spacebar) or clicking on the timeline in a second project when another is already playing stops playback of the first project.'''
+
| '''When changing language in Preferences, some elements in Unicode Release don't change until restart.'''  
* '''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: 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:
* '''GA:''' Because 1.2.6 does not have this problem, the bug is marked '''<font color="red">''R''</font>&nbsp;''', 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.
+
** "Left-click and hold" slider tooltips (except gain slider)
* '''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...
+
** Gain slider "left and right"
* '''zachelko:''' Submitted patch to mailing list 3/19/2009 to address Play/Pause/Stop spanning across all open windows. Timeline issue still exists.
+
** 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.
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
Line 234: Line 274:
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
 
|''' Tag import/export occasionally non-orthogonal.''' Some known specifics:  
 
|''' 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.  
 
* 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/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:''' 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. 
 +
|-
 +
|valign="top"|'''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. 
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
|''(Windows only)''  
+
|<font color="green">'''''&radic;'''''</font>&nbsp; ''(Windows only)'' '''After a period launching correctly, Audacity opens minimised.'''
'''LADSPA plug-ins not categorisable despite compiling with USE_LIBLRDF defined and installing RDF data files in Audacity data directory.''' See [http://n2.nabble.com/Recent-LV2-updates-tp725755p728551.html this thread]
+
* '''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: <p>[Window] X=-4 Y=-4 Width=1288 Height=778 Maximized=1 </p>
 +
* '''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.
 +
|-
 +
|valign="top"|'''P3'''
 +
|''(Windows only)'' '''LADSPA plug-ins not categorisable despite compiling with USE_LIBLRDF defined and installing RDF data files in Audacity data directory.''' See [http://n2.nabble.com/Recent-LV2-updates-tp725755p728551.html this thread]
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
Line 246: Line 299:
 
*'''GA:''' Is slv2 building on Linux?  
 
*'''GA:''' Is slv2 building on Linux?  
 
*'''DanH:''' For me it fails (on Linux) but can be fixed by running libtoolize.
 
*'''DanH:''' For me it fails (on Linux) but can be fixed by running libtoolize.
|-
 
|valign="top"|'''P3'''
 
|''(Windows Vista only)'' '''System mixer level sliders and Audacity level sliders act independently. As a result, achieved recorded level only matches level indicated on the Recording VU meter if the Audacity input slider is at 100%.''' Reported by David Bailes. Should also be checked on Windows 7.
 
* '''DB:''' Logitech USB desktop microphone gives similar behaviour with independent system and Audacity input sliders, and the Audacity slider applies a gain not reflected in the Recording VU meter. For the Logitech USB desktop microphone, the same problem also occurs on Windows XP.
 
* '''GA:''' My experience with USB external sound cards and USB turntables on a number of XP machines shows no replicable problems as described. Needs further verification by others.
 
 
|-
 
|-
 
|valign="top"|'''P3'''
 
|valign="top"|'''P3'''
 
|''(Linux only)'' '''JACK issues:'''
 
|''(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)   
 
* 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
 
* 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 [http://linuxmusicians.com/viewtopic.php?f=28&t=552 Linux musicians thread] and this [http://audacityteam.org/forum/viewtopic.php?f=11&t=6646 Forum post]
 
* 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 [http://linuxmusicians.com/viewtopic.php?f=28&t=552 Linux musicians thread] and this [http://audacityteam.org/forum/viewtopic.php?f=11&t=6646 Forum post]
Line 260: Line 309:
 
* Crashes when recording full duplex?  
 
* Crashes when recording full duplex?  
 
* Audacity must have same sample rate as JACK (seen in 1.3.4 Ubuntu repository builds)   
 
* Audacity must have same sample rate as JACK (seen in 1.3.4 Ubuntu repository builds)   
 +
|-
 +
|valign="top"|'''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.       
 
|-
 
|-
 
|valign="top"|'''P3'''  
 
|valign="top"|'''P3'''  
Line 271: Line 324:
 
   
 
   
 
{| cellpadding="10px"
 
{| cellpadding="10px"
 +
|-
 +
|valign="top"|'''P4'''
 +
|'''Nyquist working directory inconsistent.'''
 +
* '''SD:''' See [http://n2.nabble.com/Setting-Nyquist-working-directory-td4134139.html 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 [http://n2.nabble.com/Setting-Nyquist-working-directory-tp4134136p4151749.html 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. 
 +
 
|-
 
|-
 
|valign="top" width="25px"|'''P4'''
 
|valign="top" width="25px"|'''P4'''
|''(Windows only)'' '''Audacity executable does not appear in Explorer "Open With" dialogue when right-clicking over an .aup file, nor in the "Open With" list after browsing in the dialogue, selecting the .exe and clicking OK.'''  
+
| '''Desynchronised tones playback'''
* '''RS:''' Started to fix this bug 04 Apr 2009
+
* '''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.
 +
|-
 +
|valign="top"|'''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").     
 +
|-
 +
|valign="top"|'''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
 +
|-
 +
|valign="top"|'''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.
 +
|-
 +
|valign="top"|'''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 
 +
|-
 +
|valign="top"|'''P4'''
 +
| '''About box not modal.'''
 +
* '''JC:''' Reported by Doug Grinbergs. 
 +
* '''GA:''' Would be more useful, but contrary to Windows behaviour
 +
|-
 +
|valign="top"|'''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?     
 +
|-
 +
|valign="top"|'''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
 +
<ul>Does not happen with imports, or at waveform/meter dB ranges of -36, -120 or -145. </ul>
 +
|-
 +
|valign="top"|'''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. 
 +
|-
 +
|valign="top"|'''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.'''
 +
|-
 +
|valign="top"|'''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
 +
|-
 +
|valign="top"|'''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.
 +
|-
 +
|valign="top"|'''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.
 +
|-
 +
|valign="top"|'''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.
 +
|-
 +
|valign="top"|'''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. 
 +
|-
 +
|valign="top"|'''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 [http://audacityteam.org/forum/viewtopic.php?f=20&t=9897 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.
 +
|-
 +
|valign="top" |'''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
 +
|-
 +
|valign="top"|'''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.
 +
|-
 +
|valign="top"|'''P4'''
 +
|'''"Automatically fit" preference: tracks not re-fitted if tracks added or deleted then undone/redone.'''
 +
|-
 +
|valign="top"|'''P4'''
 +
|'''"Automatically fit" preference: Time, Label, and Note tracks not re-fitted.''' 
 
|-
 
|-
 
|valign="top"|'''P4'''
 
|valign="top"|'''P4'''
 +
|'''"Advanced Mixing Options": Names of all input tracks scaled unreadably small if any input tracks have a long name.'''
 +
|-
 +
|valign="top" |'''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).
 +
|-
 +
|valign="top" |'''P4'''
 +
|'''Selection bugs when zoomed in'''
 +
* '''GA:''' may also be (partly) responsible for unpredictable behaviour dragging clips - see [http://n2.nabble.com/Selection-bug-td2668675.html here]
 +
|-
 +
|valign="top" width="25px"|'''P4'''
 
|'''When Control Toolbar is undocked, its associated shortcuts only work if the main application has focus.'''
 
|'''When Control Toolbar is undocked, its associated shortcuts only work if the main application has focus.'''
 
|-
 
|-
Line 284: Line 449:
 
|valign="top"|'''P4'''
 
|valign="top"|'''P4'''
 
|'''Memory leaks:'''
 
|'''Memory leaks:'''
* '''Effect::CountWaveTracks''' Reported by LL.
 
 
* '''SLV2 libraries''' [http://n2.nabble.com/Recent-LV2-updates-tp725755p731852.html Reported by MJS]
 
* '''SLV2 libraries''' [http://n2.nabble.com/Recent-LV2-updates-tp725755p731852.html Reported by MJS]
 
* '''Effect Previews''' [http://n2.nabble.com/Memory-Leaks-on-Effect-Preview-in-src-effects-Effects.cpp-tp777570p782512.html Reported by Dawson Written]  
 
* '''Effect Previews''' [http://n2.nabble.com/Memory-Leaks-on-Effect-Preview-in-src-effects-Effects.cpp-tp777570p782512.html Reported by Dawson Written]  
 +
|-
 +
|valign="top"|'''P4'''
 +
|'''Nyquist implementation: [http://n2.nabble.com/Memory-bug-with-Nyquist-in-Audacity-td257313.html#a257313 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.
 
|-
 
|-
 
|valign="top"|'''P4'''
 
|valign="top"|'''P4'''
Line 307: Line 475:
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''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.  
+
| '''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.    
 
|-
 
|-
 +
|valign="top"|'''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.
 +
|-
 +
|valign="top"|'''P5'''
 +
|'''"Latency problem" warning when audio is pushed behind zero occurs for both tracks of a stereo pair.'''
 +
|-
 +
|valign="top"|'''P5'''
 +
|<font color="red"> '''''R''''' </font> ''(Windows only)'' '''Executable will not launch in Safe Mode but runs  an unkillable process.'''
 +
|-
 +
|valign="top"|'''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. |-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
 
|'''Debug Log window and Help > Index... browser do not escape.'''  
 
|'''Debug Log window and Help > Index... browser do not escape.'''  
Line 316: Line 500:
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
|'''Dependencies Dialogue: If click on "Copy Selected Audio Into Project" in error, the copying cannot be cancelled from the progress dialogue.'''
+
|'''Dependencies Dialog: If click on "Copy Selected Audio Into Project" in error, the copying cannot be cancelled from the progress dialog.'''
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
|'''Re-enable file writing within Nyquist so that Nyquist plug-ins can remember user settings.''' Be careful about permissions with file writing, and whether and when we allow over-writing of existing files. Needs someone with detailed LISP knowledge to look at it.  Assumption is that we need to re-enable code intentionally disabled, not write new code. 
+
|'''Nyquist implementation: (dribble [fname]) function'''
*'''JC:''' xlisp functions such as xwrchar, xprint and xopen :OUTPUT seem to be already present and correct. Can't find disabled code.  DS hypothesises it is code missing in 'the bridge', whatever that is.
+
* '''STF:''' Creates a file as expected, but the file is empty (zero bytes). Not a problem in standalone Nyquist.
* '''LL:''' This isn't an issue.  All XLisp and Nyquist functions are now available.
+
* '''GA:''' LL has noted previously that all XLisp and Nyquist functions are now available, so file writing in itself should not be a problem.
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
|'''When writing a file as a result of a Nyquist prompt, file either is not written, or written to a location that is not asked for.''' See [http://www.nabble.com/Not-properly-able-to-write-to-a-file-in-1.3.4-rc0.0-Nyquist-t4657140.html here] for details.
+
|'''Nyquist Prompt should be categorised as "Utility".'''
* '''LL:''' I don't believe this to be a problem.  In the first example, the file will go to whatever the current directory is.  The Lisp function (setdir) can be used to discover/change what that is.  In the second example, you'd have to use a double backslash "c:\\progr..." to get it work work properly.
+
*'''GA:''' It would not then be left unsorted if EFFECTS_CATEGORIES was on.
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
|'''Issues believed to result from Audacity implementation of Nyquist:'''
+
|'''Nyquist: s-add-to sound max-samples "file-name"and s-overwrite issues'''
* [http://n2.nabble.com/Memory-bug-with-Nyquist-in-Audacity-td257313.html#a257313 Excessive memory usage]
+
* '''Dave Storer:''' see [http://n2.nabble.com/Problems-with-Nyquist-on-Audacity-1.3.8-td3305897.html these details].
** '''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.
+
* '''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.  
* Inaccurate length generation on first use of the plug-in at the default value offered. Correct duration obtainable by using slider or text box to change the value away from, then back to the default (example: pluck.ny)
 
** '''LL:''' I'm unable to reproduce this and experimenting shows that it has probably been fixed.
 
* Other inconsistent length generation issues which vary from time to time/one plug-in to another/one Audacity version to another for no apparent reason. 
 
** '''LL:''' This was probably related to the *WARP* variable not being set consistently and should now be fixed.
 
* Values of sliders in the Audacity effect 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 launching/re-using 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 [http://n2.nabble.com/Re%3A-Slider-Bug-Investigations---was%3A-Pluck-in-Audacity-td238683.html 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.
 
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''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.  
+
|''(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.  
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
Line 345: Line 523:
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
|''(Linux only)'' '''Reproducible (but not entirely consistent) crashes reported when using Undo command.''' Reported by Darren on Ubuntu Gutsy 7.10 with 2.5 GB projects. Also, adding a Label Track in any projects causes Edit > Paste to flicker (the code does currently enable it), then closing the Label Track causes a crash every time irrespective of the actions taken before.
+
|''(Linux only)'' '''Intermittent crashes using Undo command (irrespective of command being undone).'''  
* '''GA:''' None of these crashes are reproducible on Windows XP, but retained on "Watching Brief" just in case (it could affect Mac as well?)
+
* Reported by Darren on Ubuntu Gutsy 7.10 with 2.5 GB projects.  
 
|-
 
|-
 
|valign="top"|'''P5'''
 
|valign="top"|'''P5'''
Line 371: Line 549:
  
  
[[Category:For Developers]]
+
[[Category:For Developers]][[Category:Quality]]

Latest revision as of 13:58, 4 December 2017



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/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.
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 http://n2.nabble.com/Various-P2s-and-P3s-a-repeatable-case-td4040974.html 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.

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 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.

Non-blockers

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