Difference between revisions of "Feature Requests"

From Audacity Wiki
Jump to: navigation, search
(New/Modified other GUI elements: moving Markers on Waveform)
(Highest-rated Feature Requests: updated votes table)
(478 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
+
<noinclude><!--PLEASE COPY THE TEXT BETWEEN THE LINES TO YOUR CLIPBOARD TO MAKE IT EASY TO VOTE WITH THE STYLE WE ARE CURRENTLY USING FOR VOTES   
<!--PLEASE COPY THE TEXT BETWEEN THE LINES TO YOUR CLIPBOARD TO MAKE IT EASY TO VOTE WITH THE STYLE WE ARE CURRENTLY USING FOR VOTES   
 
 
-------------------------------------------------------
 
-------------------------------------------------------
  
{{votes|1}}  
+
{{votesdate|1|14Mar18}}
  
 
------------------------------------------------------
 
------------------------------------------------------
THIS MAKES IT MUCH EASIER TO SEE THE VOTES EACH ITEM HAS RECEIVED-->
+
THIS MAKES IT MUCH EASIER TO SEE THE VOTES EACH ITEM HAS RECEIVED-->{{
 
+
Intro|1=This is our '''Feature Requests''' page where suggestions from users to enhance or add new features to Audacity are logged.
{{Intro|1=This is our '''Feature Requests''' page where users can suggest new or enhanced Audacity features. You can either add your vote for existing suggestions already listed, or add a new request. |2= You can also <span style="font-style:normal">[[Talk:Audacity Wiki Home Page|comment about the Wiki]]</span> or <span style="font-style:normal">[[Talk:Pending website changes|about the main Audacity website]]</span>.}}
+
|2=To ''vote'' for a feature or suggest a new enhancement, please post to the ''"Adding Features"'' section of the [https://forum.audacityteam.org/viewforum.php?f=20 Audacity forum].
 
 
{{hint|
 
'''Voting and Editing:''' If you want to add a vote or request and have not done so before, please read [[Editing Feature Requests]]. You can vote without a Wiki account by emailing our [http://web.audacityteam.org/contact/#feedback feedback address].
 
 
}}
 
}}
 
 
:'''Quick Links:'''
 
:'''Quick Links:'''
 
:*[[Completed Features|Requested features already in released versions, or available in builds from SVN HEAD]]
 
:*[[Completed Features|Requested features already in released versions, or available in builds from SVN HEAD]]
Line 22: Line 17:
  
  
 +
== Highest-rated Feature Requests==
 +
{{note|All Feature Requests with a vote count of 20 or more qualify for a listing in the Highest Rated index here.
 +
* '''Tip:''' To sort by Category and have each Category ordered by number of votes, click the "Category" column then SHIFT-click the "Votes" column.}}
 +
{{intro|1='''This is how we get from ideas to new releases of Audacity'''|2=
 +
 +
'''[[:Category:Feature Planning|Feature Requests]]'''  &nbsp; --> &nbsp; [[:Category:Proposal|Proposals]]  &nbsp; --> &nbsp; [[:Category:Projects|Projects]]  &nbsp; --> &nbsp; [[:Category:Release_Notes|Releases]]
  
== Highest-rated ==
 
{{ednote|All Feature Requests with a vote count of 20 or more qualify for a listing in the Highest Rated index here. }} 
 
{{note|'''Index of Higest Rated Feature Requests - sorted by votecount'''
 
#[[#realtime|Real-time effects {{votes|166}}]]
 
#[[#pdfmanual|PDF version of Manual''' {{votes|82}} ]]
 
#[[#punch|Punch-in and punch-out" recording {{votes|79}}]]
 
#[[#multi|Multi-channel playback {{votes|77}}]]
 
#[[#scrub|Scrubbing {{votes|74}}]]
 
#[[#autosync|Synchronize recorded/played back tracks automatically {{votes|71}}]]
 
#[[#bars_beats|BPM and beat timecode automatic detection and beat matching {{votes|66}} ]]
 
#[[#midi|Allow direct MIDI editing/playback and incorporate MIDI sequencer''' {{votes|60}}]]
 
#[[#albumart|Support lyrics and album art in metadata tags {{votes|52}} ]]
 
#[[#reverb|Better, built-in reverb above the divider {{votes|52}} ]]
 
#[[#chains|Improvements to the "Chains" (batch processing) feature {{votes|51}}]] - ''this section has many high-rated requests''
 
#[[#appearance|Too utilitarian/outdated/generic in appearance/hard to customise {{votes|51}} ]]
 
#[[#parameterbinding|Bind particular parameters of effects to buttons or keyboard shortcuts {{votes|50}}]]
 
#[[#sar|Sound Activated Recording {{votes|50}}]]
 
#[[#categorizeeffects|Effects Categorisation {{votes|49}}]]
 
#[[#virtualdriver|Include Audacity's own virtual driver to record stereo mix {{votes|46}} ]]
 
#[[#betterupdate|Better ability to update {{votes|45}} ]]
 
#[[#soundtrack|Import/play video for synchronized soundtrack editing {{votes|44}}]]
 
#[[#globalshortcuts|Global shortcuts that operate Audacity if it does not have focus but don't return focus to Audacity. {{votes|43}} ]]
 
#[[#panenvelope|Panning envelope editing {{votes|42}}]]
 
#[[#timestamp|Timestamp metadata {{votes|42}}]]
 
#[[#coloredtracks|Assign different colors to individual tracks, clips or regions {{votes|42}} ]]
 
#[[#importappended|Import Appended {{votes|39}}]]
 
#[[#multisound|Record from multiple sound devices at once {{votes|39}}]]
 
#[[#repair|Repair: vastly increased length of track to be worked on/works when zoomed out {{votes|37}} ]]
 
#[[#markers|Markers on Waveform {{votes|36}}]]
 
#[[#signature|Let the Timeline display time signature and bars/beats {{votes|36}}]]
 
#[[#exportsame|Export to directory from which original .aup or audio file loaded (like Save Project does) {{votes|36}} ]]
 
#[[#cls|Control Audacity from command line {{votes|33}} ]]
 
#[[#diablesavechanges|Disable "Save Changes?" on exit - Simple option, even if the file has been edited. {{votes|32}} ]]
 
#[[#customwave|User-customised waveform colors for RMS and background to improve contrast {{votes|31}} ]]
 
#[[#smoothscrolling|Smoother Track scrolling on Playback {{votes|31}} ]]
 
#[[#noclipping|One-step way to avoid clipping on multiple tracks {{votes|30}} ]]
 
#[[#unitaryproject|Smaller-sized and/or more unified project storage {{votes|29}} ]]
 
#[[#multievent|Timer Record Multi-event scheduler {{votes|29}} ]]
 
#[[#fadeinout|Fade In/Fade Out  {{votes|27}} ]]
 
#[[#microseconds|Selection Toolbar: Microseconds [µs] {{votes|26}} ]]
 
#[[#pedal|Control Audacity by a foot pedal {{votes|25}}]]
 
#[[#scripting|Make Scripting (mod-script-pipe) available after enabling it in Preferences, without having to compile Audacity and the scripting module {{votes|25}} ]]
 
#[[#78curves|Reinstate 78 RPM EQ curves from Audacity 1.2 {{votes|25}} ]]
 
#[[#grid|Grid lines: Horizontal- and also in spectrogram view {{votes|25}} ]]
 
#[[#nonconsecutiveinput|Allow nonconsecutive set of input channels to be selected {{votes|23}} ]]
 
#[[#rip&burn|CD Rip and Burn {{votes|22}}]]
 
#[[#contextmenu|More Context Menu (right-click or CTRL-click) functionality {{votes|22}}]]
 
#[[#effectsmanager|Effects manager: Browse for, add and remove plug-ins from menus. {{votes|22}} ]]
 
#[[#autoextension|Provide way to automatically add extension when file name contains a dot {{votes|22}} ]]
 
#[[#nondestructiveedit|Non-destructive (non-linear) editing {{votes|21}} ]]
 
#[[#monitoring|Preference for monitoring on by default {{votes|21}}]]
 
#[[#normalizationrms|Normalization Replay Gain (RMS) {{votes|20}} ]]
 
 
}}
 
}}
 +
</noinclude><includeonly>* This table comes from the [[Feature Requests]] page.</includeonly>
 +
{| class="wikitable sortable"
 +
|-
 +
! Feature  !! data-sort-type="number"| Votes !! Category !! Status
 +
|-
 +
|[[Feature_Requests#chains|Improvements to the "Macros" (batch processing) feature]] - ''many high-rated requests, total as shown'' || 224||  [[Feature_Requests#Automation|Automation]] || {{done}} Some enhancements ([[Automation Project]]) {{todo}} Many more possibilities.
 +
|-
 +
|[[Feature_Requests#realtime|Real-time effects]] || 166 || [[Feature_Requests#Effects|Effects]] || {{done}} Basics (Effect-Preview button).  {{todo}} Full feature.
 +
|-
 +
|[[Feature_Requests#multi|Multi-channel playback]] || 84 || [[Feature_Requests#Playback_Enhancements|Playback Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#pdfmanual|PDF version of Manual''']] || 82 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] || {{done}} [https://www.fosshub.com/DarkAudacity.html Draft Experimental PDF for 2.2.0 available].  Offers of help to improve on this are welcome!
 +
|-
 +
|[[Feature_Requests#autosync|Synchronize recorded/played back tracks automatically]] || 71 || [[Feature_Requests#Playback_Enhancements|Playback Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#bars_beats|BPM and beat timecode automatic detection and beat matching]] || 66 || [[Feature_Requests#Effects|Effects]] ||
 +
|-
 +
|[[Feature_Requests#albumart|Support lyrics and album art in metadata tags]] || 62 || [[Feature_Requests#Imports_and_Exports|Imports and Exports]] ||
 +
|-
 +
|[[Feature_Requests#midi|Allow direct MIDI editing/playback and incorporate MIDI sequencer''']] || 60 || [[Feature_Requests#MIDI|MIDI]] || {{done}} Playback.  It's in 2.2.0. {{todo}} Sequencer.
 +
|-
 +
|[[Feature_Requests#sar|Sound Activated Recording pre- and post-roll: ]] || 56 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#nonconsecutiveinput|Choose which of multiple channels to record]] || 54 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#appearance|Too utilitarian/outdated/generic in appearance/hard to customise]] || 51 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] || {{done}} [https://alphamanual.audacityteam.org/man/Themes Themes] and [[Theming_HowTo|Custom Theming]] available in 2.2.0.  More ongoing work on appearance at [https://www.facebook.com/darkaudacity/ Dark Audacity].
 +
|-
 +
|[[Feature_Requests#parameterbinding|Bind particular parameters of effects to buttons or keyboard shortcuts]] || 51 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] || {{done}} Achievable via Macros now.  {{todo}} could be slicker.
 +
|-
 +
|[[Feature_Requests#categorizeeffects|Effects Categorization]] || 49 || [[Feature_Requests#Effects|Effects]] || {{todo}} Work started on blocks-based interface for configuring effects menu.
 +
|-
 +
|[[Feature_Requests#soundtrack|Import/play video for synchronized soundtrack editing]] || 49 || [[Feature_Requests#Imports_and_Exports|Imports and Exports]] ||
 +
|-
 +
|[[Feature_Requests#virtualdriver|Include Audacity's own virtual driver to record stereo mix]] || 46 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#globalshortcuts|Global shortcuts that operate Audacity if it does not have focus]] || 46 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] ||
 +
|-
 +
|[[Feature_Requests#timestamp|Timestamp metadata]] || 44 || [[Feature_Requests#Imports_and_Exports|Imports and Exports]]  ||
 +
|-
 +
|[[Feature_Requests#panenvelope|Panning envelope editing]] || 42 || [[Feature_Requests#Editing_Enhancements|Editing Enhancements]]  ||
 +
|-
 +
|[[Feature_Requests#exportsame|Export to directory from which original .aup or audio file loaded]] || 41 || [[Feature_Requests#Imports_and_Exports|Imports and Exports]] ||
 +
|-
 +
|[[Feature_Requests#importappended|Import Appended]] || 39 || [[Feature_Requests#Imports_and_Exports|Imports and Exports]]  ||
 +
|-
 +
|[[Feature_Requests#signature|Let the Timeline display time signature and bars/beats]] || 39 || [[Feature_Requests#Interface_Modifications|Interface Modifications]]  ||
 +
|-
 +
|[[Feature_Requests#multisound|Record from multiple sound devices at once]] || 39 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#repair|Repair: vastly increased length of track to be worked on/works when zoomed out]] || 37 || [[Feature_Requests#Effects|Effects]]  ||
 +
|-
 +
|[[Feature_Requests#dynamic_loop|Dynamically adjust loop playback when selection boundaries move]] || 36 || [[Feature_Requests#Playback_Enhancements|Playback Enhancements]]
 +
|-
 +
|[[Feature_Requests#markers|Markers on Waveform]] || 36 || [[Feature_Requests#Interface_Modifications|Interface Modifications]]  ||
 +
|-
 +
|[[Feature_Requests#cls|Control Audacity from command line]] || 33 || [[Feature_Requests#Automation|Automation]] || {{done}} Was part of the [[Automation Project]], for Audacity 2.3.0.
 +
|-
 +
|[[Feature_Requests#diasblesavechanges|Disable "Save Changes?" on exit - Simple option, even if the file has been edited.]] || 32 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] ||
 +
|-
 +
|[[Feature_Requests#multievent|Timer Record Multi-event scheduler]] || 32 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#noclipping|One-step way to avoid clipping on multiple tracks]] || 30 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] ||
 +
|-
 +
|[[Feature_Requests#grid|Grid lines: Horizontal- and also in spectrogram view]] || 29 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] ||
 +
|-
 +
|[[Feature_Requests#microseconds|Selection Toolbar: Microseconds [µs]]] || 26 || [[Feature_Requests#Imports_and_Exports|Imports and Exports]] ||
 +
|-
 +
|[[Feature_Requests#pedal|Control Audacity by a foot pedal]] || 25 || [[Feature_Requests#Automation|Automation]] ||
 +
|-
 +
|[[Feature_Requests#scripting|Make Scripting (mod-script-pipe) available after enabling it in Preferences]] || 26 || [[Feature_Requests#Automation|Automation]] ||
 +
|-
 +
|[[Feature_Requests#78curves|Reinstate 78 RPM EQ curves from Audacity 1.2]] || 25 || [[Feature_Requests#Effects|Effects]] ||
 +
|-
 +
|[[Feature_Requests#contextmenu|More Context Menu (right-click or CTRL-click) functionality]] || 23 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] ||
 +
|-
 +
|[[Feature_Requests#monitoring|Preference for monitoring on by default]] || 23 || [[Feature_Requests#Interface_Modifications|Interface Modifications]] ||
 +
|-
 +
|[[Feature_Requests#nondestructiveedit|Non-destructive (non-linear) editing]] || 22 || [[Feature_Requests#Editing_Enhancements|Editing Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#rip&burn|CD Rip and Burn]] || 22 || [[Feature_Requests#Unclassified_Feature_Requests|Unclassified Feature Requests]] ||
 +
|-
 +
|[[Feature_Requests#sar|Sound Activated Recording: segment each recording event: ]] || 21 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[#favorites|Include "Favorites" folder at the top for frequently used plug-ins]] || 21 || [[Feature_Requests#Effects|Effects]] || (either autogenerated and sorted by number of calls, or user-added) ||
 +
|-
 +
|[[Feature_Requests#normalizationrms|Normalization Replay Gain (RMS)]] || 20 || [[Feature_Requests#Effects|Effects]] ||
 +
|-
 +
|[[Feature_Requests#per_track_meta|Store metadata for each imported file]] ||20 || [[Feature_Requests#Other Import/Exports|Other Import/Exports]] ||
 +
|-
 +
|[[Feature_Requests#punch|Non-destructive Punch-in recording]] || 20 || [[Feature_Requests#Recording_Enhancements|Recording Enhancements]] ||
 +
|-
 +
|[[Feature_Requests#mouse|Configurable mouse bindings]] || 20 || [[Feature_Requests#pref|Preferences]] ||
 +
|}
 +
<noinclude>
  
==Temporary H2 for Highest Rated entries to aid editing ==
+
== Segmenting Tracks  ==
  
 +
* '''Automatic segmentation during Record:''' {{votes|10}} Automatically segments the audio being recorded into another track upon meeting the user defined settings for  "silence" length, threshold level and number of track to be split.
 +
{{devcomment|The best way to do this might be to add labels at the track splits, which fits in with other requests to label points where Sound Activated Recording pauses when the audio falls below the specified threshold.}} 
  
<div id="markers"></div>
+
* '''Beat Finder Improvements''':
* '''Markers on Waveform''' {{votes|36}} Add with one keystroke a vertical mark that stays on the waveform and can be labeled. Common in audio editors. Should be draggable but attached to the audio segment. Select between any two markers easily e.g. with double click. Snap a region to the markers. Should be implemented in addition to split lines. Very necessary for long-form documentary editing, where you are identifying and then going back and handling many different selections from a long file. Also important if recordings are edited afterwards by others.  
+
** See "BPM Detection" in [[#Highest-rated|Highest-rated]]
 +
** Search for periodicities, let user refine and add time measures, then redo with probability/interpolation bases on added information. Use the corrected beats and a dynamics analysis to detect musical structures like verse, refrain. See [[Beat Finder Improvements]] for details.
 +
** '''Create regions encompassing each beat''' by inputting a BPM (maybe include auto-dedection of the BPM), see [http://hdimage.org/images/csgys65npvbd6dpqaz9h.png image]. The region can then be moved, duplicated etc. as normal to create loops or re-mixes easily.  
 +
<ul>{{devcomment|This could be quite a powerful idea when Audacity supports multiple label selection, [[#paste|Paste Special]] and/or [[GSoC Ideas 2008#Intuitive cross-fading|intuitive crossfade]].}}</ul> 
  
 +
* '''Clips:'''
 +
** '''Allow left-click in track to snap to or retain split line not delete it:''' {{votes|12}} For example, right-click to remove the split-line, as is done to remove the cut line.
 +
* '''Snap to editing cursor''' and show Boundary Snap Guide {{votes|2}}
  
<div id="signature"></div>
+
* '''Export Multiple:'''  
* '''Let the Timeline display time signature and bars/beats''' {{votes|36}}. This is a useful feature in its own right, even if user had to identify the BPM manually. It could also be the means of displaying automatically detected beats if/when that is implemented. It would mean we could align to beats - see: "Snap To: Beats".
+
** {{done}} '''(version 2.4.2) Checkbox in dialog to pass metadata through to all exported files automatically:''' if identical tags wanted for all files, saves having to (remember to) File > Open Metadata Editor to add tags before export. {{votes|59}}
<ul><ul>
+
** '''File name prefix should have leading zeros''' for operating systems which don't have natural number sort (otherwise track 10 comes before track 2 etc). {{votes|3}}
<li>'''Must show complete grid with all beats having vertical line:''' {{votes|2}}
+
** '''Choice of minimum number of digits for numbering''' {{votes|2}}
<li>'''[http://en.wikipedia.org/wiki/Quantization_(music) Quantize] to a grid like [http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=EditingMIDI.38.html Sonar]:''' {{votes|14}} This corrects timing errors in MIDI or audio where you record slightly before or after the beat or hold some notes shorter or longer than intended.
+
** '''Store last used state of "Include audio before first label"''' as for "Name files" buttons {{votes|2}}  
<ul><li>Do this by dragging clip boundaries to grid lines {{votes|3}}</ul>
+
** {{done}} '''Checkbox "Do not export audio before zero"''' as per straight export: {{votes|4}} If unechecked, exports audio before zero and includes any trailing white space before zero as silence.
<li>'''Identify BPM manually''' by tapping in an interface as in web applications {{votes|7}}  
+
** '''Checkbox "Normalize on export"''' {{votes|1}} Use case is for e.g. live concert destined for individual files
<ul><li> with option to show the true tempo of the song even if I play it back at different speed {{votes|1}} </ul>
+
** '''Enumerate files in single progress dialog''' to say "exporting 1 of 5", "2 of 5...", not string of "exporting entire Project" dialogs. Still needed, even though 2.x now gives the name of the file currently being exported {{votes|12}}
<li>'''BPM Calculator''' that shows BPM based on a selection. {{votes|1}}. </ul>
+
** '''Support "Use Custom Mix"''' {{votes|6}} 
{{devcomment|1=See also this BPM calculator plugin http://forum.audacityteam.org/viewtopic.php?f=42&t=69028.}}   
+
** '''Remaining time for entire process, not (just) for each file''' {{votes|4}}
</ul>
+
** {{done}}''' "Overwrite existing files" off by default:''' {{votes|3}}  
 +
*** {{done}} '''but remembers previous state''' {{votes|2}} 
 +
** '''"Success" dialog should not have same title as main Export Multiple dialog''' {{votes|2}} Use case is this makes it possible to script actions based on the unique window title (and it "could" be argued as bad design to have two identically titled dialogs).
 +
<ul>{{devcomment|Possible title could be "Export Multiple (Results)" - the title must include the phrase "Export Multiple" IMO - Gale}}
 +
<ul><li> '''Skip export of selected labels''' {{votes|1}}
 +
<li>'''Button to export to current project location''' {{votes|1}}  </ul></ul>
  
 +
<div id="labels"></div>
 +
* '''Labels:'''
 +
** '''Multi-Label-Select:''' Ability to select multiple (not necessarily adjacent) labels (such as with control-click or shift-click) {{votesdate|11|23May18}}
 +
*** Should work on point labels, too, thereby selecting regions between labels. {{votes|5}}
 +
*** Also there could be commands to select multiple label regions or to ignore specified labels. [[Select multiple label regions and invert selection|See extra detail here]].
 +
*** '''Play Labels Only:''' Play clipped in or labelled regions only - standard feature on professional audio editing systems. skipping the non-selected regions.  This feature would be useful for comparing two regions of an audio file without delay between their playback.{{votes|5}}
 +
*** '''Change font size/color for selected text in labels''' {{votesdate|7|02Nov17}}
 +
*** '''Multiple select must work in Edit Labels too''' {{votes|1}}
 +
** '''Invert labels:''' {{votes|2}} Replace current labels with new labels that start from the end of the previous label to the start of the next label. If two of the original labels touch (but don't overlap), they will be replaced with a point label at the point where they meet.
 +
** '''Snap labels to:'''
 +
***'''Other labels''' {{votes|11}}
 +
***'''Editing cursor''' {{votes|7}}
 +
***'''Clips''' {{votes|5}}
 +
***'''Selection boundary''' {{votes|3}}
 +
** '''Mark-in and mark-out points''':  As per video editors, "I" sets Edit In Point and "O" sets Edit Out Point. Should use zero-crossing accuracy. Doesn't matter what you do between those two actions; once you press "O", everything between "I" and "O" is selected. {{votes|12}} 
 +
** '''Easy way to select a region between labels''' {{votes|9}}
 +
<ul>{{devcomment|Would the interface changes required be worth it when there is an easy solution now? Click where you want to "mark in" (can be in an existing point-label) and hold SHIFT while clicking where you want to "mark out"; a region is drawn between the click points. Currently, the SHIFT-click can't be in a label, it has to be in the waveform, but shift-clicking between labels could be added. Also see [[NavigationTips#Marking cut regions or points|Marking cut regions or points]].}}
 +
<ul><li> '''Moving a label draws original and current edge(s) in waveform''' without having to select the label {{votes|7}}
 +
<li> '''Right-click functionality:''' {{votes|3}}
 +
<ul>
 +
<li> '''Add label''' {{votes|2}} </ul>
 +
<li> '''Moving a label moves the audio:''' {{votes|2}}
 +
<li> {{done}} '''More distinction between region and point labels when zoomed out:''' {{votes|4}} so that Export Multiple does not produce a few milliseconds of audio if you accidentally drag a point label when zoomed in.</ul>
 +
{{devcomment|There already is the distinction that zoomed out and selected, the minimal region label will show no vertical line in the waveform and a double arrowhead in the Timeline, versus vertical line and single arrowhead for a point label. Still, it seems a reasonable addition for a point label to have a different-colored vertical line in label track and waveform.}}
 +
<ul><li> '''Labels include metadata''' {{votes|6}} - not a request for cue sheet support, instead this gives a way in compilation albums to pass other than track Title and Track Number to Metadata Editor
 +
<li>'''Automatic label text during playback/recording:''' {{votes|3}} When using Add Label at Playback Position, provide an option to populate labels automatically with pre-defined text then close the label. Provide an option to increment the entered numbers or letters. 
 +
<li> '''Import label by simply drag-and-drop label file''' {{votes|1}} </ul></ul>
 +
 +
<ul><ul><li>'''Expand-to-silence:''' {{votes|2}} expand selection command expands the selection leftwards and rightwards until silence between songs or beginning/end of track is found  </ul></ul>
 +
<ul>{{devcomment|Also see the [[Use_Cases#"Books on tape", field recordings, etc.|"Books on tape..." Use Cases]] for similar ideas.}} </ul>
 +
<ul><ul><li>'''Expand-to-non-silence:''' {{votes|3}} Double-click any point in a "silence" to automatically select the complete silence - useful for voice editing.  </ul></ul>
 +
<ul>{{devcomment|In Audacity 2.x, Analyze > Silence Finder labels silence, and Effect > Truncate Silence can remove these silences.}}</ul>
 +
<ul><ul><li> '''Minimum distance between labels'''  {{votes|6}} similar to Nero Wave Editor it can be very handy when handling large amount of spoken audio</ul>
 +
{{devcomment|1=There is an experimental modification to Silence Finder [https://forum.audacityteam.org/download/file.php?id=1545 here]}}
 +
<ul><li> '''Count the number of silences''' produced to cross-check with number of tracks on an LP or cassette {{votes|1}} </ul>
 +
<ul><li> '''Unified Silence Finder and Sound Finder:''' {{votes|4}} Discussed many times before but never resolved. See https://forum.audacityteam.org/viewtopic.php?p=212445#p212445.
 +
<ul><li> '''Parameters must be saved''' so that it launches in last used Sound or Silence mode  {{votes|2}} </ul></ul>
 +
<ul><li> '''New Label Track name defaults to Current Track name''' {{votesdate|1|30Mar17}} When a new label track is created then its name should default to that of the currently selected (audio?) track to which the labels relate.  The currently selected track is the most likely to be relevant to the label track.  If there are multiple unnamed Audio Tracks, then it doesn't matter what name the label track defaults to since, if the name is of any concern anyway, then it will need to be renamed anyway.  It is just as easy to rename it from 'Audio Track' as it is to rename it from 'Label Track' - both are equally un-useful. </ul>
 +
{{devcomment|If there is more than one audio track, it may not be obvious which to choose for the label name. If all the audio tracks are called the default "Audio Track" then Label Track should not be called "Audio Track".}}</ul>
  
<div id="pedal"></div>
+
* '''Time Shift Tool'''
* '''Control Audacity by a foot pedal''' {{votes|25}} attached to the game, serial or USB port so that hands are free for transcription work. Also useful for non-transcription applications, such as recording off a commercial two-way radio with a squelch output signal.
+
** '''Move Cursor Too!''' Cursor within the track being moved should move with the track, not stay at same time point. {{votes|1}} Additionally, if this cursor extended over other visible tracks, it would make it much easier to line up one track with the others. <ul>{{devcomment|You can extend the cursor through all tracks by holding down SHIFT then clicking in the [https://web.audacityteam.org/onlinehelp-1.2/menu_track.htm Track Control Panels] of the other tracks.}}</ul>
 
+
<ul><ul><li>'''Allow overlapping clips''' as in CoolEdit, but give overlap a different color {{votes|1}}
 
+
<li> '''Lock-beyond:''' {{votes|2}} Set a lock point beyond which tracks cannot be dragged. Could be set in current direction of travel or by right-click menu. '''Use Case:''' Set maximum length in a project with many overlapping tracks where you may not be able to see the end (bottom) of the project.
<div id="rip&burn"></div>
+
<li> '''An individual track locking capability''' to prevent inadvertent time shifting or changes to previously edited tracks
* '''CD Rip and Burn''' {{votes|22}}  
+
<li> '''Allow shifting by less than distance between samples''' {{votes|1}}  
{{devcomment|There is experimental code for CD Import/Export in progress.  Help welcome.}}
+
<li> '''Allow shifting while audio playing''' {{votes|1}} as in Cool Edit Pro </ul>
 
 
  
<div id="contextmenu"></div>
+
<div id="cue_sheets"></div>
* '''More Context Menu (right-click or CTRL-click) functionality''' {{votes|22}}
+
* '''Export cue sheets''' from labels e.g. for CD burning (and/or text file compatible with shntool) {{votesdate|16|06May17}}  
** '''Right-click over selection region''' - ideas:
+
** '''MP3 cue sheets''' {{votes|1}} for example compatible with MP3Cue
***'''Cut; copy; paste; delete; Undo''' {{votes|4}}
+
{{devcomment|There is a Java-based tool called [http://sourceforge.net/projects/label2cue/ label2cue] that converts Audacity's exported text files containing label information to cue information. Instructions for use of label2cue and details of other similar tools are [[Cue sheets|here]].}}
***'''Apply effects:''' Workflow and reduced mousing benefits {{votes|2}}
 
***'''Zoom in/out on selection (horizontally)''' {{votes|2}}
 
***'''Select all; Select in all tracks''' {{votes|2}}
 
***'''Silence'''
 
***'''Set start/end of selection:''' {{votes|1}} like Goldwave
 
***'''Split off a selection of a clip'''
 
***'''Duplicate a selection of a clip'''
 
***'''Send to new track:''' or to a labelled position in an existing track.
 
***'''Set Envelope Points:''' creates start and end points on the envelope automatically.
 
** '''Right-click over waveform''' - ideas, some for features that don't yet exist yet (from [[Proposal Woozle's Interface Tweaks]]): 
 
***'''Delete track''' {{votes|2}}
 
***'''Insert track below/above current'''
 
***'''Mute individual clips''' (new feature)
 
***'''Time-lock individual clips''' (Tracks Preferences can globally prevent clips moving with edits) 
 
***'''Duplicate an entire clip'''
 
***'''Delete clip'''
 
***'''Insert a split point at the cursor'''
 
***'''Edit start time, offset and length of a clip''' (new feature)
 
***'''Zoom in/out vertically''' {{votes|2}}
 
***'''Turn envelope view on/off''' (preferably per clip, which is a new feature)
 
  
 +
* '''Import cue sheets''' to labels e.g. to add internet database information to files. {{votesdate|5|27Sep19}}
  
<div id="monitoring"></div>
+
<div id="lrc_files"></div>
* '''Preference for monitoring on by default''' {{votes|21}}
+
* '''Export lrc files''' from label track to be able to create song lyric files from inside audacity. {{votes|1}}
{{devcomment|We initially didn't do this because of concerns about performance on lower powered machines.  We've since had feedback on this that is works fine and that not having monitoring "on" is causing a bigger problem - especially with new users.  This however is not such an easy change as it appears - handling the situation when a device is changed/swapped out for example but Audacity is still looking for an input to read - it may not be fixed quickly}}
 
  
== Segmenting Tracks  ==
+
*'''Split to multiple projects:''' Split the project into smaller multiple projects by labels, similar to the "Export Multiple" command. Each project retains the per-track labels of the original single project. {{votes|10}}
 +
** '''Save selection as new project:''' {{votes|3}}
  
* '''Automatic segmentation during Record:''' {{votes|10}} Automatically segments the audio being recorded into another track upon meeting the user defined settings for "silence" length, threshold level and number of track to be split.  
+
== Frequency Analysis Capabilities ==
{{devcomment|The best way to do this might be to add labels at the track splits, which fits in with other requests to label points where Sound Activated Recording pauses when the audio falls below the specified threshold.}}
+
===Plot Spectrum ===
 +
{{Hint|There are many additional single-vote suggestions at [[Suggested Frequency Analysis Capabilities]]. If any there especially appeal to you, please cut and paste them below and include your own vote for them.}}
 +
 
 +
* '''User-defined minimum dB level, but not via meter/waveform dB preference:''' {{votes|14}} This is too inflexible, and non-obvious to the user. Also given the (generally better) normalization compared to 1.2, this leaves you with an empty plot when looking at low level audio, e.g white noise at -75 dB is not visible with Preferences set at -96 dB. Set a default minimum that can never leave user with an empty plot, but let user move the minimum if they wish. 
 +
** '''Text box input for lowest visible level''' {{votes|6}}   
 +
 
 +
<div id="rtplot"></div>
 +
* '''Real time plot when playing audio:''' {{votesdate|13|07Mar17}} Or, in view of the CPU demands of calculating the spectrum, have Audacity do plot spectrum at given time intervals. {{devcomment|Plotting spectrum while recording would likely be impractical due to the risk of errors writing the recording data.}}
  
* '''Beat Finder Improvements''':
+
* '''Option to turn off auto-scaling:''' which sets the top and bottom of the dB scale according to the "significant" level measured {{votes|7}}. User can then save their own maximum and minimum by text box in Plot Spectrum, a preference or sliders. Use case is easy comparison of different plots.   
** See "BPM Detection" in [[#Highest-rated|Highest-rated]]
 
** Search for periodicities, let user refine and add time measures, then redo with probability/interpolation bases on added information. Use the corrected beats and a dynamics analysis to detect musical structures like verse, refrain. See [[Beat Finder Improvements]] for details.
 
** '''Create regions encompassing each beat''' by inputting a BPM (maybe include auto-dedection of the BPM), see [http://hdimage.org/images/csgys65npvbd6dpqaz9h.png image]. The region can then be moved, duplicated etc. as normal to create loops or re-mixes easily.  
 
<ul>{{devcomment|This could be quite a powerful idea when Audacity supports multiple label selection, [[#paste|Paste Special]] and/or [[GSoC Ideas 2008#Intuitive cross-fading|intuitive cross-fade]].}}</ul>    
 
  
* '''Clips:'''
+
* '''Zoomable/pannable sliders''' {{votes|13}}  
** '''Allow left-click in track to snap to or retain split line not delete it:''' {{votes|11}} For example, right-click to remove the split-line, as is done to remove the cut line.
+
** '''Absolute minimum dB could still be set by Meter/Waveform dB Preference''', but use slider to set minimum within that. {{votes|1}}
* '''Snap to editing cursor''' and show Boundary Snap Guide {{votes|2}}  
 
  
* '''Export Multiple:'''
+
* '''Select any area on the grid and release mouse to zoom in on it''' {{votes|1}}  
** '''(version 2.x) Checkbox in dialog to pass metadata through to all exported files automatically:''' if identical tags wanted for all files, saves having to (remember to) File > Open Metadata Editor to add tags before export. {{votes|59}}
 
** '''Allow (numerical) prefix/suffix when labelling by name, not instead of it:''' {{votes|9}}
 
** '''File name prefix should have leading zeros''' for operating systems which don't have natural number sort (otherwise track 10 comes before track 2 etc).  {{votes|3}}
 
** '''Choice of minimum number of digits for numbering''' {{votes|2}}
 
** '''Store last used state of "Include audio before first label"''' as for "Name files" buttons {{votes|2}}
 
** '''Checkbox "Do not export audio before zero"''' as per straight export: {{votes|4}} If unechecked, exports audio before zero and includes any trailing white space before zero as silence.
 
** '''Checkbox "Normalize on export"''' {{votes|1}} Use case is for e.g. live concert destined for individual files
 
** '''Enumerate files in single progress dialog''' to say "exporting 1 of 5", "2 of 5...", not string of "exporting entire Project" dialogs. Still needed, even though 2.x now gives the name of the file currently being exported {{votes|12}}
 
** '''Support "Use Custom Mix"''' {{votes|6}} 
 
** '''Remaining time for entire process, not (just) for each file''' {{votes|4}}
 
** '''"Overwrite existing files" off by default:''' {{votes|3}}
 
*** '''but remembers previous state''' {{votes|2}} 
 
** '''"Success" dialog should not have same title as main Export Multiple dialog''' {{votes|2}} Use case is this makes it possible to script actions based on the unique window title (and it "could" be argued as bad design to have two identically titled dialogs).
 
<ul>{{devcomment|Possible title could be "Export Multiple (Results)" - the title must include the phrase "Export Multiple" IMO - Gale}} 
 
<ul><li> '''Skip export of selected labels''' {{votes|1}}
 
<li>'''Button to export to current project location''' {{votes|1}} </ul></ul>
 
  
<div id="labels"></div>
+
* '''Normalization presets''' {{votes|10}} Understandable default called e.g. "music" that gives a result like 1.2 plot, so that a section with most samples close to 0 dB peaks near to 0 dB in the spectrum, not at -20 dB
* '''Labels:'''
 
** '''Multi-Label-Select:''' Ability to select multiple (not necessarily adjacent) labels (such as with control-click or shift-click) {{votes|10}}
 
*** Should work on point labels, too, thereby selecting regions between labels. {{votes|5}}
 
*** Also there could be commands to select multiple label regions or to ignore specified labels. [[Select multiple label regions and invert selection|See extra detail here]].
 
*** '''Play Labels Only:''' Play clipped in or labelled regions only - standard feature on professional audio editing systems. skipping the non-selected regions.  This feature would be useful for comparing two regions of an audio file without delay between their playback.{{votes|5}}
 
*** '''Change font size/color for selected text in labels''' {{votes|6}}
 
*** '''Multiple select must work in Edit Labels too''' {{votes|1}}
 
** '''Invert labels:''' {{votes|2}} Replace current labels with new labels that start from the end of the previous label to the start of the next label. If two of the original labels touch (but don't overlap), they will be replaced with a point label at the point where they meet.
 
** '''Snap labels to:'''
 
***'''Other labels''' {{votes|10}}
 
***'''Editing cursor''' {{votes|6}}
 
***'''Clips''' {{votes|4}}
 
***'''Selection boundary''' {{votes|1}}
 
** '''Mark-in and mark-out points''':  As per video editors, "I" sets Edit In Point and "O" sets Edit Out Point. Should use zero-crossing accuracy. Doesn't matter what you do between those two actions; once you press "O", everything between "I" and "O" is selected. {{votes|12}} 
 
** '''Easy way to select a region between labels''' {{votes|9}}
 
<ul>{{devcomment|Would the interface changes required be worth it when there is an easy solution now? Click where you want to "mark in" (can be in an existing point-label) and hold SHIFT while clicking where you want to "mark out"; a region is drawn between the click points. Currently, the SHIFT-click can't be in a label, it has to be in the waveform, but shift-clicking between labels could be added. Also see [[NavigationTips#Marking cut regions or points|Marking cut regions or points]].}}
 
<ul><li> '''Moving a label draws original and current edge(s) in waveform''' without having to select the label {{votes|7}}
 
<li> '''Right-click functionality:''' {{votes|3}}
 
<ul>
 
<li> '''Add label''' {{votes|2}} </ul>
 
<li> '''Moving a label moves the audio:''' {{votes|2}}
 
<li>'''More distinction between region and point labels when zoomed out:''' {{votes|4}} so that Export Multiple does not produce a few milliseconds of audio if you accidentally drag a point label when zoomed in.</ul>
 
{{devcomment|There already is the distinction that zoomed out and selected, the minimal region label will show no vertical line in the waveform and a double arrowhead in the Timeline, versus vertical line and single arrowhead for a point label. Still, it seems a reasonable addition for a point label to have a different-colored vertical line in label track and waveform.}}
 
<ul><li> '''Labels include metadata''' {{votes|6}} - not a request for cue sheet support, instead this gives a way in compilation albums to pass other than track Title and Track Number to Metadata Editor
 
<li> '''Improve navigation to/from arbitrary labels:''' {{votes|5}}
 
<ul><li>When the label track has focus, '''TAB or SHIFT + TAB should always navigate to the nearest label''' (from the current cursor point in the direction specified), not do this only if a label is open and otherwise go forwards from the first label or backwards from the last label. {{votes|5}}
 
<li> Selecting the label in Label Editor should move to the label  {{votes|1}} </ul></ul>
 
<ul>{{devcomment|The Label Editor problem could be solved by having it open the selected label for editing, but that may not be desirable. We could a) provide a shortcut to open a label when the label track had focus and the cursor was at a label edge; or b) allow TAB and SHIFT + TAB to operate from that label when the condition in a) was true (or provide different shortcuts to do that).}}  </ul>
 
<ul><li>'''Automatic label text during playback/recording:''' {{votes|3}} When using Add Label at Playback Position, provide an option to populate labels automatically with pre-defined text then close the label. Provide an option to increment the entered numbers or letters. 
 
<li> '''Import label by simply drag-and-drop label file''' {{votes|1}} </ul></ul>
 
  
* '''Silence Finder:'''
+
* '''User-defined frequency bands:''' {{votes|13}} CoolEdit/Audition allow this. Use case: the most relevant region for music is 20 to 8000 Hz. Could be done by:
** '''Split on silences automatically:''' Detected silences between songs or album tracks parsed into new track, or adds a label there. {{votes|9}}
+
** Zoomable/pannable frequency axis {{votes|10}}  
*** Use an online database to do this {{votes|1}}
+
** Text box for frequency cutoff point {{votes|4}} For example the user could type in 1000 to see the frequency range of the spectrum from 0 to 1000 Hz. That parallels with the choice in Spectrograms preferences.  
<ul>{{devcomment|1=Analyze > Silence Finder (available [http://audacity.cvs.sourceforge.net/viewvc/audacity/audacity-src/plug-ins/SilenceMarker.ny?view=markup here] if it's not in your copy of Audacity) creates labels at each silence, then you can export multiple. Please clean records to assist proper detection of silences.}}</ul>
+
     
<ul><ul><li>'''Expand-to-silence:''' {{votes|2}} expand selection command expands the selection leftwards and rightwards until silence between songs or beginning/end of track is found  </ul></ul>
+
* '''Export spectrum graph as an image''' {{votes|7}}  
<ul>{{devcomment|Also see the [[Use_Cases#"Books on tape", field recordings, etc.|"Books on tape..." Use Cases]] for similar ideas.}} </ul>
 
<ul><ul><li>'''Expand-to-non-silence:''' {{votes|3}} Double-click any point in a "silence" to automatically select the complete silence - useful for voice editing</ul></ul>
 
<ul>{{devcomment|In Audacity 2.x, Analyze > Silence Finder labels silence, and Effect > Truncate Silence can remove these silences.}}</ul>
 
<ul><ul><li> '''Minimum distance between labels'''  {{votes|6}} similar to Nero Wave Editor it can be very handy when handling large amount of spoken audio</ul>
 
{{devcomment|1=There is an experimental modification to Silence Finder [http://forum.audacityteam.org/download/file.php?id=1545 here]}}
 
<ul><li> '''Count the number of silences''' produced to cross-check with number of tracks on an LP or cassette {{votes|1}} </ul>
 
<ul><li> '''Unified Silence Finder and Sound Finder:''' {{votes|4}} Discussed many times before but never resolved. See http://forum.audacityteam.org/viewtopic.php?p=212445#p212445.
 
<ul><li> '''Parameters must be saved''' so that it launches in last used Sound or Silence mode  {{votes|2}} </ul></ul></ul>
 
  
* '''Sound Finder:'''
+
* '''Exported plot file should have metadata:''' {{votes|5}} giving current plot window settings and a timestamp.  
** '''Provide message (or debug output) of number of labels produced:''' {{votes|1}}.  
+
** Should also include path to project file {{votes|1}}
** '''New control for required number of output labels:''' {{votes|1}} e.g. the number of songs in the track. Then Sound Finder auto-adjusts its settings to get as close to those number of labels as possible.
 
  
* '''Time Shift Tool'''
+
* '''Manage plot files:''' {{votes|2}} import or edit the files within Plot Spectrum window.
** '''Move Cursor Too!''' Cursor within the track being moved should move with the track, not stay at same time point. {{votes|1}} Additionally, if this cursor extended over other visible tracks, it would make it much easier to line up one track with the others. <ul>{{devcomment|You can extend the cursor through all tracks by holding down SHIFT then clicking in the [http://web.audacityteam.org/onlinehelp-1.2/menu_track.htm Track Control Panels] of the other tracks.}}</ul>
 
<ul><ul><li>Allow '''multiple clips to be dragged''' onto a different track, not just single clips {{votes|1}}.
 
<li>Allow '''selection of clips by double-clicking''' whilst still in Time Shift Tool {{votes|1}} 
 
<li>'''Allow overlapping clips''' as in CoolEdit, but give overlap a different color {{votes|1}}
 
<li> '''Lock-beyond:''' {{votes|2}} Set a lock point beyond which tracks cannot be dragged. Could be set in current direction of travel or by right-click menu. '''Use Case:''' Set maximum length in a project with many overlapping tracks where you may not be able to see the end (bottom) of the project.
 
<li> '''An individual track locking capability''' to prevent inadvertent time shifting or changes to previously edited tracks
 
<li> '''Allow shifting by less than distance between samples'''  {{votes|1}}
 
<li> '''Allow shifting while audio playing''' {{votes|1}} as in Cool Edit Pro
 
<li> '''Operable by right mouse button''', rather than having to switch to Time Shift tool. {{votes|2}}
 
<li> (''2.x'') '''Using with CTRL moves that specific clip plus all clips to the right.'''  Useful for inserting or a section. {{votes|1}}</ul></ul><ul>{{devcomment|You can select a region encompassing the clips you want to move, and drag just those.}}</ul>
 
  
<div id="cue_sheets"></div>
+
* '''Longer analyzable length than 10485760 samples:''' {{votes|3}}
* '''Export cue sheets''' from labels e.g. for CD burning (and/or text file compatible with shntool) {{votes|13}}  
+
** '''Preference or option for analyzable length:''' {{votes|1}}  
** '''MP3 cue sheets''' {{votes|1}} for example compatible with MP3Cue
 
{{devcomment|There is a Java-based tool called [http://sourceforge.net/projects/label2cue/ label2cue] that converts Audacity's exported text files containing label information to cue information. Instructions for use of label2cue and details of other similar tools are [[Cue sheets|here]].}}
 
  
* '''Import cue sheets''' to labels e.g. to add internet database information to files. {{votes|3}}  
+
* '''Overwrite or append choice for exported plot file:''' {{votes|3}}
  
<div id="lrc_files"></div>
+
* '''Exported file should identify each peak and cursor position''' {{votes|3}}
* '''Export lrc files''' from label track to be able to create song lyric files from inside audacity. {{votes|1}}
 
  
*'''Split to multiple projects:''' Split the project into smaller multiple projects by labels, similar to the "Export Multiple" command. Each project retains the per-track labels of the original single project. {{votes|10}}
+
* '''Export maximum peak amplitude for each FFT bin rather than the average peak amplitude:''' {{votes|2}} This means that the result will be identical whatever length of absolute silence is included in the selection. This might make a momentary frequency too loud everywhere else if you EQ'd against a such a plot, but if the average and maximum peaks were very different, this could usefully indicate possible faults in the recording.
** '''Save selection as new project:''' {{votes|3}}
 
  
== Frequency Analysis Capabilities ==
+
* '''Remember window height/width across sessions''' {{votes|5}} 
  
===Plot Spectrum ===
+
* '''More distinctive cursor line''' {{votes|3}} bolder, different color to grid lines or partly transparent 
  
{{Hint|There are many additional single-vote suggestions at [[Suggested Frequency Analysis Capabilities]]. If any there especially appeal to you, please cut and paste them below and include your own vote for them.}}
+
* '''Alternative plot from cursor point:''' {{votes|2}} like CoolEdit, without having to select a region. Audacity could internally select the region length/position.
 +
{{devcomment| Audacity 2.x by default selects "all" on no selection, so an exception would have to be allowed for Plot Spectrum. Also, region selection must still be offered for those analyzing a specific note.}}
  
* '''User-defined minimum dB level, but not via meter/waveform dB preference:''' {{votes|14}} This is too inflexible, and non-obvious to the user. Also given the (generally better) normalization compared to 1.2, this leaves you with an empty plot when looking at low level audio, e.g white noise at -75 dB is not visible with Preferences set at -96 dB. Set a default minimum that can never leave user with an empty plot, but let user move the minimum if they wish.
+
* '''Multiple spectra window:''' {{votes|13}} Plot multiple spectra for different tracks/regions in the same project e.g. Audition has four buttons to hold spectra. Currently different spectra must be in different projects. Multiple plots in different colors in the same window would aid comparing spectra.
** '''Text box input for lowest visible level''' {{votes|6}}   
 
  
<div id="rtplot"></div>
+
* '''Plot cepstrum, energy, etc. offline:''' {{votes|1}} Plot cepstrum and other indicators at given time intervals.
* '''Real time plot when playing audio:''' {{votes|12}} Or, in view of the CPU demands of calculating the spectrum, have Audacity do plot spectrum at given time intervals. {{devcomment|Plotting spectrum while recording would likely be impractical due to the risk of errors writing the recording data.}}
 
  
* '''Option to turn off auto-scaling:''' which sets the top and bottom of the dB scale according to the "significant" level measured {{votes|7}}. User can then save their own maximum and minimum by text box in Plot Spectrum, a preference or sliders. Use case is easy comparison of different plots. 
+
* '''Plot human frequency response curve (how humans hear frequencies)''' overlaid with the frequency spectrum {{votes|1}}
 +
** '''Create a negative difference between spectrum and human response curve''' as equalizer preset {{votes|1}}  
  
* '''Zoomable/pannable sliders''' {{votes|13}}  
+
* '''Linear option for vertical dB scale:''' {{votes|4}} Use cases:
** '''Absolute minimum dB could still be set by Meter/Waveform dB Preference''', but use slider to set minimum within that. {{votes|1}} 
+
** Demonstrating  primary resonances of different instruments to elementary physics of music students without room noise and other musically insignificant peaks becoming over-prominent
 +
** Shows power in peaks as directly proportional to height.  
  
* '''Select any area on the grid and release mouse to zoom in on it''' {{votes|1}}  
+
* '''Cents qualifier for pitch-class/octave''' {{votes|2}}. For example 443 Hz displays as A4+12, meaning "12 cents sharp of A4 in equal temperament (A4 = 440 Hz)".
  
* '''Normalization presets''' {{votes|10}} Understandable default called e.g. "music" that gives a result like 1.2 plot, so that a section with most samples close to 0 dB peaks near to 0 dB in the spectrum, not at -20 dB
+
* '''Make Plot Spectrum "WINDOW" a real window:''' The problem:
 +
**Switching between one screen and another is a pain because:
 +
**# The Spectrum Window is always on top of the main window
 +
**# The Spectrum window can not be minimized
 +
**# It can not be reduced in size below a fairly large size
 +
**# The Spectrum Window does not appear on the Desktop Task Bar
 +
** Ideally I would like.
 +
**# The Spectrum window to be a real window (with a minimize button)
 +
**# To be able to resize the window like other windows (with scroll bars when reduced below the minimum size)
 +
**# To see the Spectrum Window on the Desktop Task Bar
 +
**# A tick box on the Spectrum Window for "always on top"
  
* '''User-defined frequency bands:''' {{votes|13}} CoolEdit/Audition allow this. Use case: the most relevant region for music is 20 to 8000 Hz. Could be done by:
+
=== Other analytical/statistical ability===
** Zoomable/pannable frequency axis {{votes|10}}
 
** Text box for frequency cutoff point {{votes|4}} For example the user could type in 1000 to see the frequency range of the spectrum from 0 to 1000 Hz. That parallels with the choice in Spectrograms  preferences.
 
     
 
* '''Export spectrum graph as an image''' {{votes|7}}
 
  
* '''Exported plot file should have metadata:''' {{votes|5}} giving current plot window settings and a timestamp.  
+
* '''Export text file containing amplitude data for each sample''' {{votes|18}} like [http://www.wavosaur.com/ Wavosaur]
** Should also include path to project file {{votes|1}}
+
{{devcomment|1=Audacity now has [https://manual.audacityteam.org/man/sample_data_export.html Sample Data Export].}}
 +
<ul><ul>
 +
<li>'''Import text file containing amplitude data for each sample''' {{votes|2}}
 +
<li> '''RMS data wanted not just peak values''' {{votes|1}}  
 +
<li> '''Allow selection by seconds as well as samples''' {{votes|1}}
 +
</ul></ul>
  
* '''Manage plot files:''' {{votes|2}} import or edit the files within Plot Spectrum window.
+
* '''Track sample data:''' headroom to dBFS (audio level), peak minimum and maximum sample, RMS volume, replay gain etc. see SF, Wavelab, Cool Edit etc. over an arbitrary length of audio, even the whole file. {{votes|8}}
 +
** '''This could go in Status Bar''' {{votes|1}}
 +
<ul>{{devcomment|This could work well with the new Vamp analysis plug-ins/}}</ul>
  
* '''Longer analyzable length than 10485760 samples:''' {{votes|3}}
+
* '''Find Clicks''' producing labels like "Find Clipping", possibly using sine-wave-curve-fit prediction algorithm and labelling where waveform diverges from prediction. {{votes|2}}
** '''Preference or option for analyzable length:''' {{votes|1}}  
 
  
* '''Overwrite or append choice for exported plot file:''' {{votes|3}}
+
* [[Suggested Volume Analysis Capabilities]]:
 +
** [[Suggested Volume Analysis Capabilities#Volume Spectrum analysis tool|Volume Spectrum analysis tool]]: Stepped volume envelope with histograms of volume against channel, and gain against volume steps.  {{votes|1}}  
  
* '''Exported file should identify each peak and cursor position''' {{votes|3}}
+
* '''Pitch Accuracy Analysis:''' add votes [[#pitch_accuracy|below]].
  
* '''Export maximum peak amplitude for each FFT bin rather than the average peak amplitude:''' {{votes|2}} This means that the result will be identical whatever length of absolute silence is included in the selection. This might make a momentary frequency too loud everywhere else if you EQ'd against a such a plot, but if the average and maximum peaks were very different, this could usefully indicate possible faults in the recording.
+
* '''[https://en.wikipedia.org/wiki/Vectorscope Vectorscope]: ''' {{votes|3}} as the example at https://www.youtube.com/watch?v=ZG_Vu32c0ZA, showing X-Y plot for two signals (left and right of stereo track).  
  
* '''Remember window height/width across sessions''' {{votes|5}}
+
* '''Oscilloscope:''' {{votes|1}} showing audio signal(s) converted to voltages over time.
  
* '''More distinctive cursor line''' {{votes|3}} bolder, different color to grid lines or partly transparent  
+
*'''Spectrograms including Pitch (EAC):'''
 +
<ul style="list-style-image: none; list-style-type: none">Also see [[#tddm|Multiple track views]] for votes for a split waveform/spectrogram view.
 +
<ul><li>'''Crosshair''' as in Plot Spectrum {{votes|13}} which enables on-screen measurement of the frequency and dB level. Length of audio should be the minimum interval possible taking the settings of the Fourier transform used in each track, namely the FFT size, window and overlap.
 +
<ul><li> Display low/high/centre of spectral selection on borders of a selection {{votes|6}} </ul>
 +
<li> '''Visual Tool editing of frequency or pitch:''' {{votesdate|11|24Apr17}} - examples [http://chkno.net/softwaretodo.html#spectrogram-paint here].
 +
<ul><li>'''Erase Tool to remove pieces of spectrum:'''  {{votesdate|10}|24Apr17}} e.g. removing harmonics or 'mouth noise' from vocals; brief noises at different pitch). See [http://www.divideframe.com/?p=spectrallayers Spectral layers]
 +
<li> Photoshop-like brush tool {{votesdate|3|24Apr17}} which would apply a chosen effect to an area of the spectrum which you paint it in.  The brush might operate like a dodge/burn tool, making the volume quieter/louder in that frequency, or maybe you would apply a wah-wah just to the low frequency by drawing only in the low area
 +
<li> '''Free shape selection tool'''
 +
<li> '''Pen tool'''
 +
<li> '''Pattern-matched brush tool:''' this would be a brush which attempts to match the area you are painting to pre-selected pattern before it applied the desired effect.
 +
<li> '''Magic wand:''' to click on a color which selects all other pieces of that color
 +
<li> '''Invert selection:''' so that you can select a frequency, invert the selection, delete the selection then be left only with the originally selected frequency. </ul>
 +
<li> '''Export to image file''' (including PNG) {{votes|1}}
 +
<li>  '''Export to image slideshow or video file''' {{votes|1}} 
 +
<li>  '''Export as graph or graphable data:''' {{votes|1}} 
 +
<li>  '''Vary FFT window overlap:''' {{votes|3}} Allow varying the overlap when generating the spectrogram.
 +
<li>  '''Grayscale range of black to white:''' rather than the current "black to gray" range {{votesdate|2|20Jul17}}
 +
{{devcomment|Special consideration of cursor lines would be required, for example to ensure that Timeline Quick Play cursor is visible during (white) track silence.}}
 +
<li>  '''Customize spectrogram colors (foreground and background):''' not just grayscale or not {{votesdate|7|20Jul17}}
 +
{{devcomment|Already works in Audacity 2.2.0 using themes.}}
 +
<li>  '''Export to three-column text file''' (energy/time/frequency)  {{votes|2}}
 +
<li> '''Exchange X (horizontal) and Y (vertical) axis:''' {{votes|1}}
 +
<li>  '''Per-track spectrogram settings:''' {{votes|2}} When exploring the spectrogram, it would be convenient if it were possible to adjust by track the 'FFT Window' and 'Display' settings, which are now set through 'Preferences >Spectrograms'.
 +
<li>  '''3D - Amplitude by Frequency by Time:''' {{votes|2}} 
 +
<li>  '''Scale should have shorter horizontal line for non-integer k values''' {{votes|1}}
 +
<li> '''Display note names in spectrogram view:''' An option to show note names instead of frequencies. {{votesdate|2|22Nov19}}
 +
<li>  See also [[#grid|Grid Lines]] </ul></ul>
  
* '''Alternative plot from cursor point:''' {{votes|2}} like CoolEdit, without having to select a region. Audacity could internally select the region length/position.
+
* '''Frequency band splitter:''' I find this feature in Fscape (an xplatform app similar to Soundhack) http://www.sciss.de/fscape/  -  to be very useful and would like to see it or a Nyquist script written to do something similar: a panel would appear when Band Splitting function is selected and would allow the user to
{{devcomment| Audacity 2.x by default selects "all" on no selection, so an exception would have to be allowed for Plot Spectrum. Also, region selection must still be offered for those analyzing a specific note.}}
+
#define bands as freq/bandwidth -or- crossover freqs
 +
#add new bands/crossovers as needed
 +
# processes the bands or crossover parameters on a soundfile or a selection of a soundfile
 +
# output these as separate files into a selected directory -- similar to splitting soundfiles according to label regions
  
* '''Multiple spectra window:''' {{votes|13}} Plot multiple spectra for different tracks/regions in the same project e.g. Audition has four buttons to hold spectra. Currently different spectra must be in different projects. Multiple plots in different colors in the same window would aid comparing spectra.
 
  
* '''Plot cepstrum, energy, etc. offline:''' {{votes|1}} Plot cepstrum and other indicators at given time intervals.
+
<div id="automate"></div>
  
* '''Plot human frequency response curve (how humans hear frequencies)''' overlaid with the frequency spectrum {{votes|1}}  
+
== Automation ==
** '''Create a negative difference between spectrum and human response curve''' as equalizer preset {{votes|1}}  
+
{{Hint|1=There is a separate [[Automation]] page for detailed discussions about new or advanced methods of workflow automation. For example we are at an early stage of developing the ability to drive Windows versions of Audacity from a perl or other [https://manual.audacityteam.org/man/scripting.html script] via a named pipe. At this stage this feature is suitable for developers only, but you can request the feature by voting below.}}
 +
<div id="scripting"></div>
 +
* {{done}} '''Make Scripting (mod-script-pipe) available after enabling it in Preferences, without having to compile Audacity and the scripting module''' {{votesdate|26|19Mar17}} 
 +
** Normalization/levelling and/or cropping of many files/tracks {{votes|5}}
 +
** Noise removal and other built-in filters or effects {{votes|5}}  
 +
** Create many audio clips from many different audio files {{votes|4}}
 +
** preconfigure exports to a particular format {{votes|4}}
 +
** Repetitive use of effects at different parameters {{votes|2}}
 +
** apply Macros without use of mouse
 +
** for audio analysis
 +
** export files and their label track   
 +
** using information from online music databases such as Discogs
  
* '''Linear option for vertical dB scale:''' {{votes|4}} Use cases:
 
** Demonstrating  primary resonances of different instruments to elementary physics of music students without room noise and other musically insignificant peaks becoming over-prominent
 
** Shows power in peaks as directly proportional to height.
 
  
* '''Cents qualifier for pitch-class/octave''' {{votes|2}}. For example 443 Hz displays as A4+12, meaning "12 cents sharp of A4 in equal temperament (A4 = 440 Hz)".
+
<div id="pedal"></div>
 +
* '''Control Audacity by a foot pedal''' {{votes|25}} attached to the game, serial or USB port so that hands are free for transcription work. Also useful for non-transcription applications, such as recording off a commercial two-way radio with a squelch output signal.
  
=== Other analytical/statistical ability===  
+
===Command line support===
 +
<div id="cls"></div>
 +
* {{done}}{{todo}} Control Audacity from command line {{votes|33}}
 +
{{devcomment|1=See [http://sox.sourceforge.net SoX] for am alternative command line solution.}}
  
* '''Export text file containing amplitude data for each sample''' {{votes|18}} like [http://www.wavosaur.com/ Wavosaur]
+
<div id="chains"></div>
{{devcomment|1=Audacity now has [http://manual.audacityteam.org/man/sample_data_export.html Sample Data Export].}}
+
===Improvements to the "Macro" (batch processing) feature=== 
<ul><ul>
+
* {{done}} '''Include features dependent on selecting regions''' (e.g. trim, fades) {{votes|51}}
<li>'''Import text file containing amplitude data for each sample''' {{votes|2}}
+
{{devcomment|This is partly supported in Audacity 2.0.1 or later by adding to the chain/Macro appropriate [[Download Nyquist Plug-ins|Nyquist plug-ins]] that operate on selections.<br>
<li> '''RMS data wanted not just peak values''' {{votes|1}}  
+
This is fully supported in Audacity 2.3.0 or later which has 'scriptables' for manipulating the current selection.}}
<li> '''Allow selection by seconds as well as samples''' {{votes|1}}  
+
* {{todo}} '''Additional Export format options:'''
</ul></ul>
+
** '''Export FFmpeg formats''' {{votesdate|52|04May17}}
 +
** '''Export sample rate''' {{votesdate|39|22Jul17}} This is important for MP3 and other compressed formats because if a file imported for batch processing switches the project rate to something not supported by the export format, the batch comes to a halt at the resample dialog. Alternatively have a preference to OK the resample dialog automatically at the offered setting. This would not however alter the project rate, which is a separate suggested command
 +
** '''Export format parameters''' {{votesdate|33|04Apr17}} like bit rate, as in the Options button in the file export window. Parameters for Macro-ed and norrmal exports should be stored separately.
 +
** '''Export Other uncompressed''' {{votesdate|28|21Feb17}}
 +
** '''Export 24/32-bit WAV''' {{votesdate|2|22Jul17}}
 +
** '''Export AIFF''' {{votes|2}}
 +
* {{done}} '''Apply Macros to multiple projects''' {{votesdate|23|14Feb19}} instead of giving error messages
 +
* {{todo}} Include '''Export Multiple''' {{votesdate|21|22May18}} with options into Macro commands
 +
* {{done}}{{todo}} '''Support Generate / Analyze effects''' {{votes|15}} both those built into Audacity and user-added ones in any other formats supported by Macros
 +
{{devcomment|1=Some but not all are done for 2.3.0 Macros -but probably not all are suitable}}
 +
* {{todo}} '''Recursive selection of all files in one or more directories:''' {{votesdate|14|19Aug19}}
 +
* {{todo}} '''Export directory''' {{votes|10}}
 +
{{devcomment|1=Planned for 2.3.0}}
 +
* {{todo}} '''Export Labels''' {{votes|1}}
 +
* {{done}} Support Silence Finder {{votes|5}}
 +
{{devcomment|1=Done for 2.3.0 Macros''}}
 +
 
 +
* '''Vamp support''' {{votes|2}}
 +
* '''VST support''' {{votes|8}}
 +
* '''LADSPA support''' {{votes|1}}
 +
* ''' Apply Macros to files listed in LOF''' not mix the content into one file {{votes|3}}
 +
* '''Command to delete the old replaced file''' {{votes|2}}
 +
{{devcomment|1=Planned for 2.3.0 - but differently, we will warn and allow overwriting}}
 +
* '''Specify metadata using Macro command'''
 +
* '''Split Stereo Track:'''
 +
* {{done}} '''Single Macros dialog from which you can edit and apply the Macro''' {{votes|6}} 
 +
{{devcomment|1=Done for 2.3.0 Macros - with the '''Manage Macros''' dialog}}
 +
* '''Permit minimizing Audacity while Macro in progress:''' {{votes|2}} 
 +
* '''Example parameters:''' {{votes|1}} EX 1: (Reduce 4 dB at 2000 Hz with Q shelve 8 dB per Octave). EX 2: De-esser fx ( threshold= -24  above 3800 Hz )
 +
* '''Make parameters configurable for:'''
 +
** SaveHqMaster1 & 2
 +
* '''Beep after a full Macro completes''' {{votes|2}}
 +
** but no beep for individual dialogs in a Macro) {{votes|2}} See https://forum.audacityteam.org/viewtopic.php?p=213546#p213546.
 +
* {{done}} '''Import / Export buttons:''' so users can share Macros more easily {{votes|3}}
 +
{{devcomment|1=Probably planned for 2.3.0 - buttons are in the dialog , but not currently active}}  
 +
* '''Ability to recover Macros applied to files if they crash''' {{votes|1}}
 +
* '''Wider Apply Macro dialog''' so you can see file names with long paths {{votes|2}}
 +
{{devcomment|1='''Peter 30Mar18:''' I have added this one to the [[Macros discussion page]]}}
 +
* '''Apply Macro dialog should be interactive:''' so you can scroll the list vertically or horizontally {{votes|1}}
 +
* '''Include arbitrary Shortcut Key commands''' e.g. CTRL + SHIFT + D to Macros array so that it can auto-task menu-dropdown and other manual mouse-click functions without disrupting batch automation. {{votes|1}}
 +
* '''a shut down program and computer option''' from Macro would be nice for long Macros
 +
* '''call another application''' like a cd burn application
 +
{{devcomment|1=Use Python scripting, then you can do 'anything'}}
 +
* '''Separately pick the mp3 settings''' in the Macros feature
 +
*'''Allow Macros to continue after failure:''' Allow Macros to optionally continue processing the next file after processing a file fails. Currently, when a batch process encounters a problem with one of the files in its list of files-to-process, the entire batch process aborts. For unattended operations this can be inconvenient.
 +
{{devcomment|1=Use Python scripting.}}
 +
**'''Peter:''' for detailed discussion see this archived Forum thread: https://forum.audacityteam.org/viewtopic.php?f=20&t=88413
  
* '''Track sample data:''' headroom to dBFS (audio level), peak minimum and maximum sample, RMS volume, replay gain etc. see SF, Wavelab, Cool Edit etc. over an arbitrary length of audio, even the whole file. {{votes|8}}
+
<div id="macro"></div>
** '''This could go in Status Bar''' {{votes|1}}
 
<ul>{{devcomment|This could work well with the new VAMP analysis plug-ins/}}</ul>
 
  
* '''Find Clicks''' producing labels like "Find Clipping", possibly using sine-wave-curve-fit prediction algorithm and labelling where waveform diverges from prediction. {{votes|2}}
+
{{devcomment|This feature may be underrepresented as many requests on the forum for improved 'macro' type features appear to have been lost or not recorded.}}
 +
* {{done}} '''Support Shortcuts to specific Macros''' {{votesdate|2|23Jul17}} so that 'macro' commands can be applied more conveniently.
 +
* {{done}}{{todo}}'''Support Edit and navigation commands''' {{votesdate|2|23Jul17}} such as paste, duplicate, add new track, move focus to next / previous track, move cursor to selection start / selection end / track start / 
 +
{{devcomment|1=Some are in for 2.3.0: Paste, Duplicate and Move Focus - in 2.4.x all are in except "Add New Track"}}
 +
* {{done}} '''Support Transport commands''' {{votesdate|2|23Jul17}} An example suggested by / for language learners: record 2 seconds then play what has been recorded.
 +
* '''Create macro by recording a sequence of actions''' {{votesdate|2|23Jul17}} Example: The record macro feature in CoolEdit Pro.
 +
{{devcomment|This could be implemented by recording key strokes, possibly with an option to also record mouse events.}}
 +
* '''Automatically apply effects on Import or Export''' Examples: Normalize files on Import, Normalize on Export, Low pass filter on Import. Generally: Apply an arbitrary Nacro of effects to imported or exported files.
  
* [[Suggested Volume Analysis Capabilities]]:
+
=== Fader Automation === 
** [[Suggested Volume Analysis Capabilities#Volume Spectrum analysis tool|Volume Spectrum analysis tool]]: Stepped volume envelope with histograms of volume against channel, and gain against volume steps. {{votes|1}}  
+
* '''Adjust the Mixer Board or Track Control Panel gain sliders while playing then record the slider moves''' so you can render them if desired. {{votes|4}}. Common feature on many other multi-track audio applications. In this way one can build up a mix, adjusting individual tracks and tweaking levels until just right. This would first require changing to linear envelope points.  Could be extended to panning (if we had a pan envelope).
  
* '''Pitch Accuracy Analysis:''' add votes [[#pitch_accuracy|below]].
+
<div id="transcription"></div>
  
* '''[https://en.wikipedia.org/wiki/Vectorscope Vectorscope]: ''' {{votes|3}} as the example at https://www.youtube.com/watch?v=ZG_Vu32c0ZA, showing X-Y plot for two signals (left and right of stereo track).   
+
== Better transcription support ==
  
* '''Oscilloscope:''' {{votes|1}} showing audio signal(s) converted to voltages over time.
+
* '''Extend features/interface of Play-at-Speed Toolbar'''. {{votes|1}}.
  
*'''Spectrograms including Pitch (EAC):'''
+
* '''Label Tracks more suitable for transcription:''' {{votes|10}}
<ul style="list-style-image: none; list-style-type: none">Also see [[#tddm|Multiple track views]] for votes for a split waveform/spectrogram view.
+
** multi-line labels {{votes|4}}
<ul><li>'''Crosshair''' as in Plot Spectrum {{votes|13}} which enables on-screen measurement of the frequency and dB level. Length of audio should be the minimum interval possible taking the settings of the Fourier transform used in each track, namely the FFT size, window and overlap.
+
** so they don't lock when audio track is not zoomed in far enough to create a scroll {{votes|2}}
<ul><li> Display low/high/centre of spectral selection on borders of a selection {{votes|6}} </ul>
+
** Freeform text box/small editing window better then you can copy paste all of it into a text editor when complete {{votes|2}}
<li> '''Visual Tool editing of frequency or pitch:''' {{votes|10}} - examples [http://chkno.net/softwaretodo.html#spectrogram-paint here].
+
** '''Second search method for text in labels other than using [[#labels_editor|Labels Editor]]:'''  {{votesdate|1|26May17}} - this would just be Find Next and Previous with a Replace option. A found occurrence of the text would move focus to the label that has the requested text and highlight that text within the label. Provide option to search in current label track only or in other label tracks.
<ul><li>'''Erase Tool to remove pieces of spectrum:'''  {{votes|9}} e.g. removing harmonics or 'mouth noise' from vocals; brief noises at different pitch). See [http://www.divideframe.com/?p=spectrallayers Spectral layers]
+
** each label should support more than 260 characters (which seems to be the limit on Windows) {{votes|1}}  
<li> Photoshop-like brush tool {{votes|2}} which would apply a chosen effect to an area of the spectrum which you paint it in.  The brush might operate like a dodge/burn tool, making the volume quieter/louder in that frequency, or maybe you would apply a wah-wah just to the low frequency by drawing only in the low area
+
<ul>{{devcomment|Create 30 second tone, zoom out until it half fills screen then type in a label. When label is full, can't add more characters unless you zoom in (zooming allows you to scroll). [[User:James|James]]: If/when we improve transcription we want to support multi-line text and linking with a true text editor.}}</ul>
<li> '''Free shape selection tool'''
+
 
<li> '''Pen tool'''
+
* '''real time loop editing:'''  the fact that Audacity has partial functionality in making loops i.e. allow you to select and play a loop but NOT adjust the loop points in real time seems to me a half baked implementation of loop editingPlease - if you are going to allow someone to select and play a loop then go ALL the way and also allow them to edit it in real time?
<li> '''Pattern-matched brush tool:''' this would be a brush which attempts to match the area you are painting to pre-selected pattern before it applied the desired effect.  
 
<li> '''Magic wand:''' to click on a color which selects all other pieces of that color
 
<li> '''Invert selection:''' so that you can select a frequency, invert the selection, delete the selection then be left only with the originally selected frequency. </ul>
 
<li> '''Export to image file''' (including PNG) {{votes|1}}
 
<li> '''Export to image slideshow or video file''' {{votes|1}} 
 
<li>  '''Export as graph or graphable data:''' {{votes|1}} 
 
<li>  '''Vary FFT window overlap:''' {{votes|3}} Allow varying the overlap when generating the spectrogram.
 
<li>  '''Fully customize background color and spectrum colors''' not just grayscale or not {{votes|2}}
 
<li>  '''Export to three-column text file''' (energy/time/frequency)  {{votes|2}}
 
<li> '''Exchange X (horizontal) and Y (vertical) axis:''' {{votes|1}}
 
<li> '''Per-track spectrogram settings:''' {{votes|2}} When exploring the spectrogram, it would be convenient if it were possible to adjust by track the 'FFT Window' and 'Display' settings, which are now set through 'Preferences >Spectrograms'.
 
<li> '''3D - Amplitude by Frequency by Time:''' {{votes|2}} 
 
<li>  '''Scale should have shorter horizontal line for non-integer k values''' {{votes|1}}
 
<li>  See also [[#grid|Grid Lines]] </ul></ul>
 
  
<div id="automate"></div>
+
*'''Faster Play-at-Speed:''' Currently the transcription toolbar function PlayAtSpeed has a maximum value of 3X. My editing deck allows much higher multiples, I am used to searching raw data for "non-music" (speech etc.) and can recognize the difference at speeds between 7X and 10X.
  
== Automation ==
+
== Effects ==
{{Hint|1=There is a separate [[Automation]] page for detailed discussions about new or advanced methods of workflow automation. For example we are at an early stage of developing the ability to drive Windows versions of Audacity from a perl or other [http://manual.audacityteam.org/man/scripting.html script] via a named pipe. At this stage this feature is suitable for developers only, but you can request the feature by voting below.}}
+
<div id="realtime"></div>
<div id="scripting"></div>
+
* Allow '''[[RealTimeAdjustment|real-time effects]]'''  {{votes|166}}
* '''Make Scripting (mod-script-pipe) available after enabling it in Preferences, without having to compile Audacity and the scripting module''' {{votes|25}}
+
<!-- The first two requests below should total to the same as the root vote for real-time effects-->
** Normalization/levelling and/or cropping of many files/tracks {{votes|5}}  
+
** <font color="gray"><strike>'''Real-time effect preview sufficient as a first step''' {{votes|102}}</strike></font> ''this is now in current Audacity''
** Noise removal and other built-in filters {{votes|4}}  
+
** '''Should include applying effects whenever playing or recording/monitoring''' {{votes|64}}  
** Create many audio clips from many different audio files {{votes|4}}  
+
*** Allow disabling real-time for a selected track as in REAPER.{{votes|5}}  
** preconfigure exports to a particular format {{votes|4}}
+
** Stomp box/guitar effects: {{votes|3}} - one of the most useful features of Diamond Cut 7.
** Repetitive use of effects at different parameters {{votes|2}}
+
** could allow effect intensity/LADSPA plug-in parameters to be varied too?
** apply chains without use of mouse
+
** Panning while recording {{votes|5}}  
** for audio analysis
+
** include something similar to the envelope tool to adjust the effect parameters?
** export files and their label track   
 
** using information from online music databases such as Discogs
 
  
===Command line support===
+
*'''Save a Noise Reduction Profile:'''  save and manage a Noise Reduction Profile for future use in subsequent projects
<div id="cls"></div>
 
* Control Audacity from command line {{votes|33}}
 
{{devcomment|1=See [http://sox.sourceforge.net SoX] for am alternative command line solution.}}
 
  
<div id="chains"></div>
+
===New Effects===
===Improvements to the "Chains" (batch processing) feature=== 
+
<div id="bars_beats">
* '''Include features dependent on selecting regions''' (e.g. trim, fades) {{votes|51}}
+
* '''BPM and beat timecode automatic detection and beat matching''' {{votes|66}}
{{devcomment|This is partly supported in Audacity 2.0.1 or later by adding to the chain appropriate [[Download Nyquist Plug-ins|Nyquist plug-ins]] that operate on selections.}}
 
* '''Export FFmpeg formats''' {{votes|49}}
 
* '''Export sample rate''' {{votes|38}} This is important for MP3 and other compressed formats because if a file imported for batch processing switches the project rate to something not supported by the export format, the batch comes to a halt at the resample dialog. Alternatively have a preference to OK the resample dialog automatically at the offered setting. This would not however alter the project rate, which is a separate suggested command
 
* '''Export format parameters''' {{votes|31}} like bit rate, as in the Options button in the file export window. Parameters for chained and non-chain exports should be stored separately.
 
* '''Export Other uncompressed''' {{votes|27}}
 
* '''Apply Chains to multiple projects''' {{votes|20}} instead of giving error messages
 
* Include '''Export Multiple''' {{votes|19}} with options into Chain commands
 
* '''Support Generate / Analyze effects''' {{votes|15}} both those built into Audacity and user-added ones in any other formats supported by Chains
 
* '''Recursive selection of all files in one or more directories:''' {{votes|11}}
 
* '''Export directory''' {{votes|10}}
 
* '''Export AIFF''' {{votes|2}}
 
* '''Export Labels''' {{votes|1}}
 
** Support Silence Finder {{votes|5}}
 
* '''VAMP support''' {{votes|2}}
 
* '''VST support''' {{votes|8}}
 
* '''LADSPA support''' {{votes|1}}
 
* ''' Apply Chains to files listed in LOF''' not mix the content into one file {{votes|3}}
 
* '''Command to delete the old replaced file''' {{votes|2}}
 
* '''Specify metadata using chain command'''
 
* '''Split Stereo Track:'''
 
* '''Single Chains dialog from which you can edit and apply the Chain''' {{votes|6}} 
 
* '''Permit minimising Audacity while Chain in progress:''' {{votes|2}} 
 
* '''Example parameters:''' {{votes|1}} EX 1: (Reduce 4 dB at 2000 Hz with Q shelve 8 dB per Octave). EX 2: De-esser fx ( threshold= -24  above 3800 Hz )
 
* '''Make parameters configurable for:'''
 
** SaveHqMaster1 & 2
 
* '''Beep after a full Chain completes''' {{votes|2}}
 
** but no beep for individual dialogs in a Chain) {{votes|2}} See http://forum.audacityteam.org/viewtopic.php?p=213546#p213546.
 
* '''Import / Export buttons:''' so users can share Chains more easily {{votes|2}}
 
* '''Ability to recover Chains applied to files if they crash''' {{votes|1}}
 
* '''Wider Apply Chain dialog''' so you can see file names with long paths {{votes|1}}
 
* '''Apply Chain dialog should be interactive:''' so you can scroll the list vertically or horizontally {{votes|1}}
 
* '''Add Shortcut Keys''' e.g. CTRL + SHIFT + D to Chains array so that it can auto-task menu-dropdown and other manual mouse-click functions without disrupting batch automation. {{votes|1}}
 
  
=== Fader Automation === 
+
* '''Vinyl-specific noise removal effects''' such as low level rapid tickiness, groove rasping... (like GramoFile or other specialist [[Audio Restoration|tools]] ) {{votes|12}}
* '''Adjust the Mixer Board or Track Control Panel gain sliders while playing then record the slider moves''' so you can render them if desired. {{votes|4}}. Common feature on many other multi-track audio applications. In this way one can build up a mix, adjusting individual tracks and tweaking levels until just right. This would first require changing to linear envelope points.  Could be extended to panning (if we had a pan envelope).
 
  
== Better transcription support ==
+
* '''Built-in Expander''' (which is often coupled with a noise gate) {{votes|14}}   
 +
** Compressor could include expander function {{votes|1}}
 +
** Presets such as for dbx/HighCom {{votes|1}}
  
* '''Extend features/interface of Transcription Toolbar'''. {{votes|1}}.
+
* '''Filters:'''
 +
** Bandpass {{votes|3}}
  
* '''Label Tracks more suitable for transcription:''' {{votes|10}}
+
* '''DirectX effects''' not just VST {{votesdate|7|28Jan19}}
** multi-line labels {{votes|4}}
 
** so they don't lock when audio track is not zoomed in far enough to create a scroll {{votes|2}}
 
** Freeform text box/small editing window better then you can copy paste all of it into a text editor when complete {{votes|2}} 
 
** each label should support more than 260 characters (which seems to be the limit on Windows) {{votes|1}}  
 
  
<ul>{{devcomment|Create 30 second tone, zoom out until it half fills screen then type in a label. When label is full, can't add more characters unless you zoom in (zooming allows you to scroll). [[User:James|James]]: If/when we improve transcription we want to support multi-line text and linking with a true text editor.}}</ul>
+
<ul><li>'''Pitch correction''' after setting to required key (like Auto-Tune), including T-Pain forced pitch effect {{votes|13}} </ul>
<ul><ul><li>Search for keywords within labels {{votes|1}}</ul></ul>
+
{{Devcomment|1=See open source plug-in called [https://forum.audacityteam.org/viewtopic.php?f=18&t=11520 Autotalent].}}
 +
<div id="pitch_accuracy"></div>
 +
<ul><li>'''Pitch accuracy analysis:''' {{votes|1}} Could be a Nyquist effect that shows the average pitch with cents deviation of labeled notes, or average pitch then on a further run adds a waveform representation of the labeled audio showing pitch deviation over time. See: https://forum.audacityteam.org/viewtopic.php?f=42&t=73796.
 +
<ul><li>'''Better as another View Mode accessed from Track Control Panel instead:''' {{votes|1}}</ul></ul>
  
== Effects ==
+
* '''Room Panning:''' Pan different tracks to different parts of a room for surround sound effect.{{votes|4}}
<div id="realtime"></div>
 
* Allow '''[[RealTimeAdjustment|real-time effects]]''' {{votes|166}}
 
<!-- The first two requests below should total to the same as the root vote for real-time effects-->
 
** '''Real-time effect preview sufficient as a first step''' {{votes|102}} 
 
** '''Should include applying effects whenever playing or recording/monitoring''' {{votes|64}}
 
*** Allow disabling real-time for a selected track as in REAPER.{{votes|5}}  
 
** Stomp box/guitar effects: {{votes|3}} - one of the most useful features of Diamond Cut 7.
 
** could allow effect intensity/LADSPA plug-in parameters to be varied too?
 
** Panning while recording {{votes|5}}
 
** include something similar to the envelope tool to adjust the effect parameters?
 
  
{{Hint|See also [[#Highest-rated|Highest-rated]]}}
+
* '''Channel Mixer (built-in):''' {{votes|1}}  Similar to the Nyquist [https://wiki.audacityteam.org/wiki/Nyquist_Effect_Plug-ins#Channel_Mixer Channel Mixer] but built-in with real-time preview, which would be particularly useful when using the effect for widening or narrowing the stereo field.
 +
** '''Stereo widener''' {{votes|2}}
 +
{{devcomment|Available in the [https://wiki.audacityteam.org/wiki/Nyquist_Effect_Plug-ins#Channel_Mixer Channel Mixer] plug-in, but see above.}}
  
===New Effects===
+
* '''Stereo effect from mono''' {{votes|3}}
<div id="bars_beats">
+
{{devcomment|Available in the [https://wiki.audacityteam.org/wiki/Nyquist_Effect_plug-ins#Pseudo-Stereo Pseudo-Stereo] plug-in.}}
* '''BPM and beat timecode automatic detection and beat matching''' {{votes|66}}
+
<ul><ul><li>use FFT? {{votes|1}}</ul></ul>
 +
 
 +
* '''Smoothen effect''', perhaps using a weighted average (or a better method){{votes|1}}
 +
**I  wonder about a tool to easy removing of noise could be useful in the application. Like the rubber tool in f.ex. photoshop.  The rubber tool should flatten the noise when you touch the noise. It would then be possible to remove noise with less zooming.  And maybe it could be useful to have the possibility to set the pencil to (f.ex. with SHIFT ) only go complete horizontally.
  
<div id="reverb"></div>
+
* '''Specialised Voice effects:'''
<ul><li> '''Better, built-in reverb''' above the divider {{votes|52}} This guarantees a shipped reverb on Linux. The current GVerb has many issues. The built-in reverb should offer:
+
** '''Basic:''' Change gender, Change age, Chipmunks, Zeus {{votes|11}}
{{ednote|'''Peter 30Jan17:''' [[ToDo-1]] We have "retired" Gverb, replacing it with Reverb, so this should be movable to [[Completed Features]] or just simply removed from here. }}
+
::{{devcomment|In the case of a track where the vocals are not solo but mixed in with other audio, how well this works depends how amenable the vocals are to being isolated. See [[Vocal Removal plug-ins]].}}
 +
:* '''Advanced formant tools:''' {{votes|6}} Professional pitch change/tune while retaining the formants, so retaining the characteristics of the original voice
 +
:*'''Advanced filtering/analysis tools:''' like [http://www.fon.hum.uva.nl/praat/ Praat] {{votes|1}}
 +
:* '''Text to speech:''' Possibly by implementing [http://espeak.sourceforge.net/ eSpeak] in Audacity {{votesdate|1|26Sep17}}
  
 +
* '''Dolby B/Dolby C filters''' for converting to/from tape recordings in Dolby) {{votes|4}}
 +
**<I> Will need quite a lot of trial and error by ear, as the Dolby process is recording level dependent. Needs expander and treble cut.</I>
 +
**<I> I agree.  It would be tricky to get it right without straight-up copying the actual process.  This would be a licensing no-no.  Trust me, I work at Dolby.</I>
 +
** <I>There is a Winamp plug-in which simulates Dolby decoding [http://www.hansvanzutphen.com/tape_restore_live/ here]. </I>
  
<div id="extreme stretch"></div>
+
* '''Exciter''' to enhance album or tape recordings. It is actually an easy effect and only needs a high pass and distortion. This is widespread use in recording studios and radio stations.  
* '''Extreme Stretch''' effect - see [[Extreme Stretch Effect]] {{votes|16}}
+
{{devcomment|There are definitely some entries in the Forum for this - I will count votes later}}
{{ednote|'''Peter 31Jan17:''' [[ToDo-1]] Does Paul Nasca's Paulstretch that we ship with Audacity, and reference & link to above, fully address this, looks like this to me?  If so we can remove this from here and move it to Completed Features.}}
 
  
* '''Vinyl-specific noise removal effects''' such as low level rapid tickiness, groove rasping... (like GramoFile or other specialist [[Audio Restoration|tools]] ) {{votes|12}}
+
* '''Deverb/Echo Cancellation:''' Echo Removal Tool/Deverb slider. This could improve back-of-the-room recordings. Sliders are "Liveness," "Room Size," "Room Oblongedness," and "Dirt" (same as sliders in an Echo Generator). {{votes|8}} {{devcomment|Deverb is exceptionally difficult and virtually unknown in audio software except [http://www.hydrogenaudio.org/forums/lofiversion/index.php/t22051.html Postfish].}}<ul><ul><li>Can't both deverb and echo cancellation be implemented by convolving the signal with a modified version of the room's impulse response?</ul></ul><ul><ul><li>No, those operations can't be performed by convolution, this is the case where '''deconvolution''' (aka inverse convolution) has to be used (well, not always).</ul></ul>
  
* '''Noise gate''' (not noise removal, just a simple binary gate) {{votes|14}}
+
* '''De-essing''' {{votes|5}}
{{devcomment|A Nyquist noise gate plug-in is available [[Nyquist_Effect_Plug-ins#Noise_Gate|here]].}}
 
  
* '''Built-in Expander''' (which is often coupled with a noise gate) {{votes|14}}   
+
* '''Re-essing:'''   This is to improve the sound of already low bandwidth voice recordings by adding higher frequencies.
** Compressor could include expander function {{votes|1}}
 
** Presets such as for dbx/HighCom {{votes|1}}
 
  
* '''Filters:'''
+
* '''Multiply two frequencies''' multiply waveforms together as in AM radio
** Bandpass {{votes|3}}
 
  
* '''DirectX effects''' not just VST {{votes|6}}
+
* '''Convolve two audio signals''' {{votes|5}}
 +
** Yes, I realize that there is a lot of difficulty involved in avoiding clipping.  Audio convolution can be used to make very convincing reverb effects. Please don't set limits for the length of the convolution signal. I want to be allowed to convolve much longer "regular audio" signals together.
 +
** Convolution is built into the Nyquist language and is an incredibly powerful feature. If I understand correctly, one could take a simple click, perform any combination of filter/chorus/echo/reverb/equalization/etc. on it, and then apply this pre-calculated set of effects to a long signal. Why wasn't this added long ago, along with multiplying and adding signals? [http://en.wikipedia.org/wiki/Convolution#Fast_convolution_algorithms Implementing convolution]
 +
** Combine this with ''EQ Matching'' proposal?
  
<ul><li>'''Pitch correction''' after setting to required key (like Auto-Tune), including T-Pain forced pitch effect {{votes|13}} </ul>
+
* '''Chorus:''' {{votesdate|10|17Feb17}}
{{Devcomment|1=See open source plug-in called [http://forum.audacityteam.org/viewtopic.php?f=18&t=11520 Autotalent].}}
+
** '''Only needs rate and depth controls''' {{votes|8}}
<div id="pitch_accuracy"></div>
+
** '''Multi-voice Chorus''' {{votes|1}}
<ul><li>'''Pitch accuracy analysis:''' {{votes|1}} Could be a Nyquist effect that shows the average pitch with cents deviation of labeled notes, or average pitch then on a further run adds a waveform representation of the labeled audio showing pitch deviation over time. See: http://forum.audacityteam.org/viewtopic.php?f=42&t=73796.
 
<ul><li>'''Better as another View Mode accessed from Track Control Panel instead:''' {{votes|1}}</ul></ul>
 
<div id="distortion_effect">
 
{{ednote|'''Peter 30Jan17:''' [[ToDo-1]] Does Steve's new Distortion effect meet these requests?  If so we can move this to [[Completed Features]] }}
 
* '''Distortion:''' {{votes|18}} A "tube overdrive" type distortion would probably be useful for a wide range of material (including vocals and guitar). Example choices could include:
 
** Tube Overdrive
 
** Fuzzbox {{votes|5}}
 
** Robots {{votes|8}}
 
** Tube distortion
 
** Walkie-Talkie
 
** Crunch
 
** Harmonic distortion (adds partials to the sound)
 
** Inharmonic distortion (adds frequencies that are not a integer product of the fundamental frequency)
 
** Hard clipping
 
** Soft clipping
 
** Cross-over distortion
 
** Tape saturation 
 
** "Modelled" distortion types - those that emulate specific distortion effects such as modelling a specific brand/model of speaker, microphone, amplifier or effect unit.
 
  
* '''Room Panning:''' Pan different tracks to different parts of a room for surround sound effect.{{votes|4}}
+
* '''Chop with segments of silence:'''  
 
+
** Merely adding in a definable length of silence after a set amount of time from the original stream. This would produce a cutting in and out effect, much more abrupt than a tremolo. It would need only two or three parameters, length of silence and length of audio.
* '''Channel Mixer (built-in):''' {{votes|1}} Similar to the Nyquist [http://wiki.audacityteam.org/wiki/Nyquist_Effect_Plug-ins#Channel_Mixer Channel Mixer] but built-in with real-time preview, which would be particularly useful when using the effect for widening or narrowing the stereo field.
+
* '''Suppress quiet signals'''.  A squelch level suppression to squelch out signals below a adjustable preset level.  (originally this was in the recording enhancements section - but it's better as an effect.).
** '''Stereo widener''' {{votes|2}}  
+
* '''EQ Matching:''' {{votes|4}} SmartEQ function to sample the frequency spectrum of a given piece of audio with a pleasing equalisation, then bring a second piece of audio to the same spectral content. Useful for most cassette recordings and other other medium- and low-fidelity sources. Also usable for sfx. Note: where frequency content falls to the noise floor, this may increase noise level heavily in an attempt to compensate. This is easily addressed afterwards with the Noise Removal, or can be addressed during frequency correction with more coding. Possibly could be incorporated as a third radio button in the current 1.3.x equaliser, with a "Get Frequency Profile" button and ability to add useful profiles as a custom preset.
{{devcomment|Available in the [http://wiki.audacityteam.org/wiki/Nyquist_Effect_plug-ins#Channel_Mixer Channel Mixer] plug-in, but see above.}}
+
* '''Envelope follower:''' {{votes|4}} Dynamically modulate the volume of one track to match the volume of another. Select a waveform, extract its volume changes over time then apply these to another waveform making its envelope behave in exactly the same way.
 +
* '''VCO-Synth:''' Something like a combination of Voltage-Controlled Oscillator and the "Sample and Hold" modules of the old ARP 2600 Synthesizer [analog]
 +
**You could sample another waveform (in another track) at regular time intervals, and the instantaneous level of the sample determines the frequency of a tone generated for the same interval of time. In the real-world Arp 2600, you could patch the output of a VCO (or other audio source) into the input of the S&H module, then patch the S&H output into the control voltage input jack of another VCO. In the Audacity version, the user makes a selection in the track to be sampled (analogous to the first VCO) , and then (in a dialog box) selects the time interval between samples, the minimum and maximum frequency to be generated. The duration of the resulting sequence of tones to be generated in a new track would be the same as the duration of the original selection. Optional - select sine, sawtooth, square, or triangle waveforms for the generated tone. Another option would be to be able to sub-divide the length of the selection into X number of sample intervals, as opposed to specifying the duration of the interval. Typical results would be a sequence of discrete pseudo-random (frequency) tones at regular intervals, like a retro movie sound effect for a computer that's busy thinking. Another example: Sampling a triangle waveform whose period is much longer than the sample interval would result in a series of ascending and descending stepped tones.
 +
* '''Reduce Formant / Boost the fundamental frequency of a signal''' - replace a vocal or instrument signal with the sine wave or square wave of the fundamental frequency of that signal.  Would help identify notes through overly distorted or overlayered signals. [https://forum.audacityteam.org/viewtopic.php?f=12&t=12901 forum post] {{votes|1}}
 +
*'''Transfer Function Effect in time domain:''' {{votes|1}} Drawn with mouse, with presets and import/export.
 +
{{devcomment|[[Nyquist]] has arguably more powerful functionality, but not graphical. So many rules could apply in any one case that the transferability would be very limited and case-specific.}}
 +
<ul><li>'''[https://en.wikipedia.org/wiki/Flanging Flanger]:''' Classic effect, not the [https://wiki.audacityteam.org/wiki/Nyquist_Effect_Plug-ins#Flanger_.28linear.29 linear flanger plugin]. {{votesdate|1|17Feb17}}</ul>
 +
{{devcomment|1=An experimental Flanger plugin (Nyquist) is available at https://forum.audacityteam.org/viewtopic.php?p=323150#p323150.}}
  
* '''Stereo effect from mono''' {{votes|3}}
+
===Other Improvements to Effects===
{{devcomment|Available in the [http://wiki.audacityteam.org/wiki/Nyquist_Effect_plug-ins#Pseudo-Stereo Pseudo-Stereo] plug-in.}}
+
<div id="categorizeeffects"></div>
<ul><ul><li>use FFT? {{votes|1}}</ul></ul>
+
<div id="Effects_Categorisation"></div>
 
+
* '''Effects Categorization:''' Allow the effects dropdown menu capable of sub-folders or categorisation so that the user can organize his plug-ins however he wishes. {{votes|49}}
* '''Smoothen effect''', perhaps using a weighted average (or a better method){{votes|1}}
+
<div id="favorites"></div>
**I  wonder about a tool to easy removing of noise could be useful in the application. Like the rubber tool in f.ex. photoshop. The rubber tool should flatten the noise when you touch the noise. It would then be possible to remove noise with less zoomingAnd maybe it could be useful to have the possibility to set the pencil to (f.ex. with SHIFT ) only go complete horizontally.
+
** '''Include "Favorites" folder at the top for frequently used plug-ins''' (either autogenerated and sorted by number of calls, or user-added) {{votes|21}}
 +
** '''Only two levels deep:''' (Effects > Category), not 3 levels as tried before (Effects > Category > Sub Category). Sub categories are just too fiddly and too much clicking. With just one level of categories, the menu will open by hovering the mouse, making locating a specific effect much quicker and easier. {{votes|7}}
 +
** '''Preference to turn categorisation off''' {{votes|5}}
 +
** '''Fully user-customizable categories and sorting of entries''' {{votes|5}}  
 +
*** '''Ability to assign one effect to multiple categories:''' {{votes|1}} such as a saturation compressor to both Compressor and Distortion categories. 
 +
** '''Detect/display subfolders of the "Plug-Ins" folder as categories:''' {{votes|6}} So if you have a folder called /Plug-Ins/MyEffects/ the menu shows Effects > MyEffects > (effects in the MyEffects folder).
 +
: {{devcomment|How does this work for plug-ins in system folders?}}
 +
* {{done}} '''Must support VST plug-ins''' {{votes|5}}
 +
** '''Must include VST plug-ins in system folders''' {{votes|4}}
 +
* '''Manipulate effects with a dialog box''' that has all plug-ins on the left hand side, an empty box on the right hand side, with "New Group...", "Delete Group", "Rename Group", "OK", "Cancel" buttons below, and arrows ">>" and "<<" in the middle, to move plug-ins between groups. {{votes|2}}
 +
* '''Multiple ''columns'' for different groups of effects''' {{votes|1}}
 +
: {{devcomment|1.3.6 Beta had incomplete categorization of Nyquist and LADSPA plug-ins. Categorisation has a penalty in more difficult navigation, and was withdrawn from 1.3.7 until there is (at least) a way to turn it on and off.}}
  
* '''Specialised Voice effects:'''  
+
* '''General (Effect menu items):'''
** '''Basic:''' Change gender, Change age, Chipmunks, Zeus {{votes|11}}
+
** Mouse scroll the Effect Menu {{votes|8}}
<ul>{{devcomment|In the case of a track where the vocals are not solo but mixed in with other audio, how well this works depends how amenable the vocals are to being isolated. See [[Vocal Removal plug-ins]].}}  
+
*** without scrollbar {{votes|3}}
<ul><li> '''Advanced formant tools:''' {{votes|6}} Professional pitch change/tune while retaining the formants, so retaining the characteristics of the original voice
+
*** with scrollbar if necessary to make it work {{votes|1}}
<li>Advanced filtering/analysis tools like [http://www.fon.hum.uva.nl/praat/ Praat] {{votes|1}}</ul></ul>
+
** Real-time preview effects to have a method to apply and close in one go {{votesdate|6|08Mar18}}
 
+
** '''Effects stay open after processing''' {{votes|5}}. User-added plug-ins (at least, Nyquist) should have this capability too. Use cases:
* '''Dolby B/Dolby C filters''' for converting to/from tape recordings in Dolby) {{votes|4}}
+
*** Multiple pass effects such as Noise Removal
**<I> Will need quite a lot of trial and error by ear, as the Dolby process is recording level dependent. Needs expander and treble cut.</I>
+
*** Facilitates repeating an effect on different selections but using different settings for each
**<I> I agree. It would be tricky to get it right without straight-up copying the actual process. This would be a licensing no-no. Trust me, I work at Dolby.</I>
+
**** An alternative would be a "Re-show last effect" shortcut as per GIMP
** <I>There is a Winamp plug-in which simulates Dolby decoding [http://www.hansvanzutphen.com/tape_restore_live/ here]. </I>
+
*** Useful if an effect is able to change the selection while open
 +
*** Useful if plug-in has displayable help files like some Nyquist plug-ins
 +
** '''Plug-ins can have different number of input and output tracks:''' for example surround encoder in the [http://plugin.org.uk/ plugin.org] package needs four inputs but produces two outputs. {{votes|1}}  
 +
** '''Preview effects for whole duration''' of a selection with option to loop the preview {{votes|3}}
 +
: {{devcomment|Ability to choose preview length has been added to the Audacity 2.x.}}
 +
:* '''Compare original (dry) with new (wet):''' {{votes|9}}
 +
:** '''Dry and Wet Preview buttons''' {{votes|5}}
 +
:** '''Visual comparison''' {{votes|2}}
 +
:** '''Loop dry and wet in succession''' {{votes|1}}
 +
:* '''Curve Editor''' for each effect to adjust how ferociously the effect changes the sample by time (posted on behalf of nitrotrigger on [[Irc|IRC]]) {{votes|3}}
 +
:* '''On-Demand effects:''' {{votes|2}} Effects apply while you continue to work (hear them applied in one part of the track by clicking there)  
 +
:* '''Defaults:'''
 +
::*{{done}} '''"Defaults" button''' {{votes|4}}
 +
:* '''Marker on sliders to indicate default value''' {{votes|2}}
 +
:*more features {{votes|6}}
 +
:*more algorithms especially impulse response convolution reverb {{votes|7}}
 +
:*Very strong opinions to consider [[GVerb#Freeverb3|Freeverb3]] as the "best" benchmark/starting point for reverb types and features (but don't include the whole suite as is) {{votes|14}}
 +
:*sensible presets that do not depend on mixing with a duplicate to sound decent {{votes|6}}
 +
:*Wet/Dry mix control {{votes|2}}
 +
:*stereo output.{{votes|4}}
  
* '''Exciter''' to enhance album or tape recordings. It is actually an easy effect and only needs a high pass and distortion. This is widespread use in recording studios and radio stations. 
+
{{devcomment|1=The [http://www.youtube.com/watch?v=rjYYzNsNqlY&feature=youtu.be Harrison implementation] looks like an example of how to implement GVerb well, but that depends at a minimum on Audacity supporting real-time effects.}}
{{devcomment|There are definitely some entries in the Forum for this - I will count votes later}}
 
  
* '''Deverb/Echo Cancellation:''' Echo Removal Tool/Deverb slider. This could improve back-of-the-room recordings. Sliders are "Liveness," "Room Size," "Room Oblongedness," and "Dirt" (same as sliders in an Echo Generator). {{votes|8}} {{devcomment|Deverb is exceptionally difficult and virtually unknown in audio software except [http://www.hydrogenaudio.org/forums/lofiversion/index.php/t22051.html Postfish].}}<ul><ul><li>Can't both deverb and echo cancellation be implemented by convolving the signal with a modified version of the room's impulse response?</ul></ul><ul><ul><li>No, those operations can't be performed by convolution, this is the case where '''deconvolution''' (aka inverse convolution) has to be used (well, not always).</ul></ul>
 
  
* '''De-essing'''  {{votes|5}}
+
* '''Amplify:'''
 +
** '''Linear "New Peak Amplitude" input:''' less confusing because it matches with default waveform (and the generate effects) {{votes|4}}
 +
** '''Toggle non-destructive clipping''' when in 32-bit float quality {{votes|1}}
 +
** '''Option to launch at last used amplification level:''' {{votes|5}} even if the New Peak Amplitude is different each time. Use case is trying/undoing different amplification amounts to get the one you want, and you want to see quickly what you last tried (or do it again if you think that will give you the desired result. 
 +
** '''Presets in dropdown menu:''' {{votes|2}}  
 +
** '''Default to last used maximum dB level:''' {{votes|1}} Currently it defaults to 0 dB whereas Normalize defaults to last used maximum.
  
* '''Re-essing:'''   This is to improve the sound of already low bandwidth voice recordings by adding higher frequencies.
+
* '''Bass and Treble:'''
 +
** '''Reinstate Bass Boost effect or add Frequency control to Bass and Treble:''' {{votes|7}} 
  
* '''Multiply two frequencies''' multiply waveforms together as in AM radio
+
* '''Change Speed/Tempo/Pitch:'''
 +
** Gradually increasing/decreasing tempo changes (without pitch change) to facilitate DJ-style mixing {{votes|6}}
 +
** Allow changes in tempo/speed to be applied on the fly from the current (and ongoing) playback position. Currently changes in speed forces reverting to the start of cursor.  {{votes|1}}
 +
::: {{devcomment|Edit > Move cursor... > to Selection End?}}
 +
:* '''Change Speed: length of selection control''' like Change Tempo {{votes|19}}
 +
:* '''Change Speed: Use a change factor''' (e.g. 0.5x means half as fast, 2x means twice as fast) so that users are not confused by -50% doubling the length/halving the frequency, while you need +100% to halve the length / double the frequency {{votes9}}
 +
{{devcomment|This is now available with a "Speed Multiplier" control.}}
 +
::*'''Also for "Change Tempo" and "Change Pitch":''' {{votesdate|1|27Jan21}}
 +
:* '''Change Speed: semitone pitch change control'''  {{votes|3}}
 +
{{devcomment|Available with the "[[Nyquist_Effect_Plug-ins#Change_Speed_by_Semitones|Change Speed by Semitones]]" plug-in.}}
 +
:* '''Change Tempo: allow calculation of % change from less than whole BPM values.''' {{votes|3}} At slower tempi a non-integer change in BPM could mean a percentage change of two or three percent. Please notify info_AT_giovannierata_DOT_it if fixed...
 +
:* This also allows this field to be used for any freeform units such as frames per second {{votes|3}}
 +
{{devcomment|This functionality will be available from  Audacity 2.0.4 onwards.}}
 +
:* '''Change Speed/Tempo presets''' {{votes|8}}
 +
:** '''Change Speed presets to/from 16 RPM''' {{votes|1}}</ul> 
 +
:* '''Dynamic Transient sharpening''' in Change Tempo/Pitch as in Sliding Timescale/Pitch Shift (without sliding of course) {{votes|2}}
 +
:* '''Option to use higher quality sbsms algorithm''' from Sliding Timescale/Pitch Shift (or amalgamate the tools so all that can be done in Change Tempo/Pitch can be done in Timescale) {{votes|3}}
 +
:* '''Window size choice''' in Change Pitch to combat FFT artefacts {{votes|1}}
  
* '''Convolve two audio signals''' {{votes|5}}
+
* '''Click Removal:'''  
** Yes, I realize that there is a lot of difficulty involved in avoiding clipping.  Audio convolution can be used to make very convincing reverb effects. Please don't set limits for the length of the convolution signal. I want to be allowed to convolve much longer "regular audio" signals together.
+
** '''Detection for clicks that are of similar level to surrounding audio'''  or generally more reliable detection {{votes|28}}. [https://manual.audacityteam.org/o/man/click_removal.html Click Removal] gives hints for other solutions, but one tool should do the job in most cases, as with other software.
** Convolution is built into the Nyquist language and is an incredibly powerful feature. If I understand correctly, one could take a simple click, perform any combination of filter/chorus/echo/reverb/equalization/etc. on it, and then apply this pre-calculated set of effects to a long signal. Why wasn't this added long ago, along with multiplying and adding signals? [http://en.wikipedia.org/wiki/Convolution#Fast_convolution_algorithms Implementing convolution]
+
** '''Intelligent joining to boundaries''' {{votes|1}} like Repair so that doesn't potentially add artefacts by almost silencing the samples it replaces so leaving abrupt joins with the unchanged audio
** Combine this with ''EQ Matching'' proposal?
 
  
* '''Chorus:''' {{votes|9}}
+
<div id="compressor"></div>
** '''Only needs rate and depth controls''' {{votes|8}}
+
* '''Compressor:'''
** '''Multi-voice Chorus''' {{votes|1}}
+
** '''Multi-band:''' {{votes|8}} so retaining the same frequency distribution.
 
+
*** '''Include a de-esser in this:''' {{votes|1}}  
* '''Repeat with Delay:''' {{votes|2}} Current Repeat effect gives a very dry result compared to creating and playing a loop in software sequencers or drum machines. Some delay could be added after the end of the region to be repeated, then the start of each repeat has this delay mixed in.
+
** '''Process stereo pairs together:''' {{votes|7}} so that the same amount of gain reduction is applied to both channels. The current Compressor applies different gain reduction to each channel which can lead to shifting of stereo image.
 
+
** '''Shorter attack/release times:''' {{votes|5}}
* '''Chop with segments of silence:'''  
+
*** '''Show attack/release times in milliseconds:''' {{votes|1}} 
** Merely adding in a definable length of silence after a set amount of time from the original stream. This would produce a cutting in and out effect, much more abrupt than a tremolo. It would need only two or three parameters, length of silence and length of audio.
+
** '''Text box input:''' {{votes|5}}
* '''Suppress quiet signals'''.  A squelch level suppression to squelch out signals below a adjustable preset level.  (originally this was in the recording enhancements section - but it's better as an effect.).
+
** '''Configurable lookahead in milliseconds:''' {{votes|4}} so pre-emptively apply the compression. Don't just make it the same as the Attack Time as now.
* '''EQ Matching:''' {{votes|4}} SmartEQ function to sample the frequency spectrum of a given piece of audio with a pleasing equalisation, then bring a second piece of audio to the same spectral content. Useful for most cassette recordings and other other medium- and low-fidelity sources. Also usable for sfx. Note: where frequency content falls to the noise floor, this may increase noise level heavily in an attempt to compensate. This is easily addressed afterwards with the Noise Removal, or can be addressed during frequency correction with more coding. Possibly could be incorporated as a third radio button in the current 1.3.x equaliser, with a "Get Frequency Profile" button and ability to add useful profiles as a custom preset.  
+
** '''Choose upward or downwards compression independent of peak or RMS envelope:''' {{votes|2}}
* '''Envelope follower:''' {{votes|4}} Dynamically modulate the volume of one track to match the volume of another. Select a waveform, extract its volume changes over time then apply these to another waveform making its envelope behave in exactly the same way.
+
** '''Choose make-up gain amount''' {{votes|2}}
* '''VCO-Synth:''' Something like a combination of Voltage-Controlled Oscillator and the "Sample and Hold" modules of the old ARP 2600 Synthesizer [analog]. 
+
** '''Built-in Hard limiter/dual slope/tabbed for different settings''' {{votes|2}}
**You could sample another waveform (in another track) at regular time intervals, and the instantaneous level of the sample determines the frequency of a tone generated for the same interval of time. In the real-world Arp 2600, you could patch the output of a VCO (or other audio source) into the input of the S&H module, then patch the S&H output into the control voltage input jack of another VCO. In the Audacity version, the user makes a selection in the track to be sampled (analogous to the first VCO) , and then (in a dialog box) selects the time interval between samples, the minimum and maximum frequency to be generated. The duration of the resulting sequence of tones to be generated in a new track would be the same as the duration of the original selection. Optional - select sine, sawtooth, square, or triangle waveforms for the generated tone. Another option would be to be able to sub-divide the length of the selection into X number of sample intervals, as opposed to specifying the duration of the interval. Typical results would be a sequence of discrete pseudo-random (frequency) tones at regular intervals, like a retro movie sound effect for a computer that's busy thinking. Another example: Sampling a triangle waveform whose period is much longer than the sample interval would result in a series of ascending and descending stepped tones.
+
** '''Presets for common tasks:''' {{votes|2}} such as "Levelling speech", "Maximizing", "Audiobook compression", "Peak limiting". Eliminates the need to install third party compressor plug-ins for casual users.
* '''Reduce Formant / Boost the fundamental frequency of a signal''' - replace a vocal or instrument signal with the sine wave or square wave of the fundamental frequency of that signal.  Would help identify notes through overly distorted or overlayered signals. [http://forum.audacityteam.org/viewtopic.php?f=12&t=12901 forum post] {{votes|1}}
+
** '''Finer Ratio discrimination than .5:''' {{votes|1}}  
*'''Transfer Function Effect in time domain:''' {{votes|1}} Drawn with mouse, with presets and import/export.
+
** '''Envelope-based''' tool that just works by dragging as in Digital Performer {{votes|1}}  
{{devcomment|[[Nyquist]] has arguably more powerful functionality, but not graphical. So many rules could apply in any one case that the transferability would be very limited and case-specific.}}
 
  
===Other Improvements to Effects===
+
<div id="eq"></div>  
<div id="categorizeeffects"></div>
+
* '''Equalization:'''
<div id="Effects_Categorisation"></div>
+
<div id="78curves"></div>
*'''Effects Categorization:''' Allow the effects dropdown menu capable of sub-folders or categorisation so that the user can organize his plug-ins however he wishes. {{votes|49}}
+
:* '''Reinstate 78 RPM EQ curves from Audacity 1.2:''' {{votes|25}}
** '''Include "Favorites" folder at the top for frequently used plug-ins''' (either autogenerated and sorted by number of calls, or user-added) {{votes|21}}
+
: {{devcomment|You can generate a large number of company-specific 78 RPM and pre-RIAA LP curves using the experimental Nyquist plug-in "78 RPM EQ Curve Generator" and the curve tables on [[78rpm playback curves]].}}
** '''Only two levels deep:''' (Effects > Category), not 3 levels as tried before (Effects > Category > Sub Category). Sub categories are just too fiddly and too much clicking. With just one level of categories, the menu will open by hovering the mouse, making locating a specific effect much quicker and easier. {{votes|7}}
+
::* '''Automatic 78 RPM EQ from RIAA-recorded 78's:''' {{votes|9}} Inverts the curve to negate the RIAA EQ then applies the required 78 RPM EQ in one button press. More 78 RPM presets facilitate this (votes as above)
** '''Preference to turn categorisation off''' {{votes|5}}
+
:* '''De-emphasis for early CDs:''' {{votes|2}} using the WaveEmph or other curves (see  http://www.hydrogenaudio.org/forums/index.php?showtopic=65067 )
** '''Fully user-customisable categories and sorting of entries''' {{votes|5}}  
+
:* '''Improve accuracy:'''
*** '''Ability to assign one effect to multiple categories:''' {{votes|1}} such as a saturation compressor to both Compressor and Distortion categories.   
+
:** '''Text input''' {{votes|8}}
** '''Detect/display subfolders of the "Plug-Ins" folder as categories:''' {{votes|6}} So if you have a folder called /Plug-Ins/MyEffects/ the menu shows Effects > MyEffects > (effects in the MyEffects folder).  
+
:*** like Cool Edit's right-click on control point then type the values {{votes|2}}
<ul>{{devcomment|How does this work for plug-ins in system folders?}}</ul>
+
:*** Edit box like Label Editor that would list all the points and allow normal editing functions  like copy and paste {{votes|1}}
<ul><ul><li>'''Must support VST plug-ins''' {{votes|5}}
+
:** Text entry box when double-clicking on Graphic EQ sliders as elsewhere {{votesdate|3|28Nov17}}
<ul><li>'''Must include VST plug-ins in system folders''' {{votes|4}} </ul>
+
:** '''Cursor readout''' {{votesdate|8|28Nov17}}
<li> '''Manipulate effects with a dialog box''' that has all plug-ins on the left hand side, an empty box on the right hand side, with "New Group...", "Delete Group", "Rename Group", "OK", "Cancel" buttons below, and arrows ">>" and "<<" in the middle, to move plug-ins between groups. {{votes|2}}
+
:** '''Zoomable grids''' {{votes|5}}
<li>  '''Multiple ''columns'' for different groups of effects''' {{votes|1}} </ul></ul>
+
:* '''[[Graphic Equalizer - simple|Simpler/more presettable Graphic EQ]]:''' {{votes|3}} Either an alternative interface with current EQ, or an additional built-in effect. 5 - 7 bands would be adequate/quicker for our many casual users. Greater range of general purpose presets needed such as "heavy bass boost", "light treble reduction", "equal loudness"...These should be separated from other e.g. gramophone presets.
<ul>{{devcomment|1.3.6 Beta had incomplete categorisation of Nyquist and LADSPA plug-ins. Categorisation has a penalty in more difficult navigation, and was withdrawn from 1.3.7 until there is (at least) a way to turn it on and off.}}</ul>
+
:* '''Graphic EQ sliders should allow choice of bandwidth''' {{votes|1}}
 +
:* '''Separate built-in Parametric EQ''' {{votes|3}} i.e. where all parameters controlling the tone change have their own control.
 +
:**high pass, low pass and 3 or more bands {{votes|1}}</ul>  
 +
:* '''Add built-in envelope''' so that amount of EQ (% of gain specified in parameters) can be varied over time  {{votes|1}}
 +
:* '''Mini-waveform''' {{votes|2}} (time against amplitude) in which you can click to preview - see [http://www.nch.com.au/wavepad/masters.html Wavepad]
 +
:* '''Incorporate mini-spectrum plot''' {{votes|7}} ideally it should change when you modify the EQ curve
 +
:** '''Include dry (pre-effect) spectrum too''' {{votes|1}} 
 +
:* '''Save Presets without renaming "unnamed"''' {{votes|4}}
 +
:* '''More frequency-specific presets''' like "Very Bright", "Mid-range", "Classical", "Hard Rock", "Soft Rock", "Dr Dre" {{votes|3}}      
 +
:* '''User-saved presets should save filter length and Draw/Graphic mode''' {{votes|1}} e.g. a curve with low frequency control points will require maximum length to be reasonably accurate but this length will slow down processing of other curves un-necessarily.
 +
:* '''Smart Normalize before EQ to safe level for the requested curve''' {{votes|1}}  
 +
:* '''Remember window size and position''' {{votes|3}} 
 +
:* '''FFT Filter''' seems to be missing in 1.3.3 (and in 1.3.5)  
 +
{{devcomment|The linear frequency scale in Equalization provides the same functionality}}
  
<div id="effectsmanager"></div>
+
:* '''Auto Complete Equalizer Graph:'''   I created a simple equalizer graph to get somebody out of trouble recently. I think it was a lot more bother than it needed to be.  Here's an illustration of an Adobe Photoshop tool.  See:  http://audacityteam.org/wiki/index.php?title=Image:Curves2.jpg  Note that there's only one new data point on the right-hand brightness curve, and yet Photoshop automatically produced a graceful, gentle, useful curve typical of a picture whose natural lighting had actually changed. It did not produce two straight lines and depend on me to painstakingly calculate the new points and put the rest of the curve in by hand.  I want the equalizer work window to run like that.
<li> '''Effects manager:''' for all formats. Browse for, add and remove plug-ins from menus, see which require restart/rescan to be visible, add and remove directories where Audacity scans for plug-in types, possibly choose location of plug-ins directory {{votes|22}} </ul>
+
:**SteveTF responds:  Since Audacity does not currently support graphical interfaces for effects (which rules out the "CoolEdit Pro FFT filter" type GUI), could this be done using a bunch of sliders?
{{devcomment|Quite difficult if extended to plug-ins outside the Audacity installation folder, where plug-ins can be in system folders. Also VST plug-ins in Audacity 2.x are managed by a "scan on restart" preference}}
+
:**Koz responds:  It could, but to figure out where the sliders go, I'd be curled up on the living room floor with my Toshiba adding machine, my Terman's book of six place log tables, number two lead pencil, and nice legal pad. If only we could make a machine to do these laborious calculations for us....
{{ednote|'''Peter 02Feb17:''' [[ToDo-1]] Surely plug-in manager was implemented by Leland for 2.1.2 (or maybe 2.1.1) ? }}
+
:* '''Display curve name in [https://manual.audacityteam.org/man/filter_curve_eq.html Filter Curve EQ]:''' {{votesdate|2|27Dec20}} Only when unmodified preset is in use.
  
* '''General (Effect menu items):'''
+
* '''Generate:'''
** Mouse scroll the Effect Menu {{votes|8}} 
+
<!-- ** '''All generators should remember their parameters across sessions.''' {{votes|5}} Currently only DTMF and Noise do so, stored in audacity.cfg FIXED -->
*** without scrollbar {{votes|3}}
+
** '''Provide way to default selection format to other than seconds.''' Either store the format in .cfg or let it default to the current Selection Toolbar format {{votesdate|36|09Aug17}}
*** with scrollbar if necessary to make it work {{votes|1}}
+
*** "last used" is better {{votes|14}}
** Real-time preview effects should have a method to apply and close in one go {{votes|5}}
+
*** "same as Selection Toolbar format" is better {{votes|6}}
** '''Effects stay open after processing''' {{votes|5}}. User-added plug-ins (at least, Nyquist) should have this capability too. Use cases:
+
*** Possibly generation at a region should always default to hh:mm:ss + samples, but still allow different choice to be saved in Preferences {{votes|6}}  
*** Multiple pass effects such as Noise Removal
+
** '''List notes for tone generation:''' {{votes|4}} e.g.middle C (264 Hz) etc.
*** Facilitates repeating an effect on different selections but using different settings for each
+
** '''Applause''' {{votes|1}}  
**** An alternative would be a "Re-show last effect" shortcut as per GIMP
+
** (2.x) '''Text box input''' as in 1.2, because much simpler to overtype irrespective of the format, and allows copy and paste {{votes|8}}  
*** Useful if an effect is able to change the selection while open
+
** '''Choice of overtones to include:''' (within the limitations of the waveform chosen) {{votes|1}}.
*** Useful if plug-in has displayable help files like some Nyquist plug-ins
+
* '''Generate follows Recording Channels:''' Generate should give me stereo tone if Recording Channels is set to stereo in Device Toolbar {{votes|1}}.
<ul><ul><li>'''Plug-ins can have different number of input and output tracks:''' for example surround encoder in the [http://plugin.org.uk/ plugin.org] package needs four inputs but produces two outputs.  {{votes|1}}
 
<li> '''Preview effects for whole duration''' of a selection with option to loop the preview {{votes|3}}</ul>
 
{{devcomment|Ability to choose preview length has been added to the Audacity 2.x.}}  
 
<ul><li>'''Compare original (dry) with new (wet):''' {{votes|9}}
 
<ul><li>'''Dry and Wet Preview buttons''' {{votes|5}}
 
<li> '''Visual comparison''' {{votes|2}}  
 
<li> '''Loop dry and wet in succession''' {{votes|1}}</ul>
 
<li> '''Curve Editor''' for each effect to adjust how ferociously the effect changes the sample by time (posted on behalf of nitrotrigger on [[Irc|IRC]]) {{votes|3}}
 
<li> '''Recallable presets''' {{votes|13}}
 
<ul><li>'''Or as a minimum, all effects should remember settings on exit''' {{votes|12}} 
 
<li> Should apply to effects under the divider too {{votes|6}}</ul>
 
{{devcomment|Currently only Equalization has presets.}}
 
<li>'''On-Demand effects:''' {{votes|2}} Effects apply while you continue to work (hear them applied in one part of the track by clicking there)
 
<li> '''Defaults:'''
 
<ul><li>'''"Defaults" button'''  {{votes|4}}  
 
<li>'''Marker on sliders to indicate default value''' {{votes|2}} </ul>
 
<ul><li>more features {{votes|6}}
 
<li>more algorithms especially impulse response convolution reverb {{votes|7}}
 
<li>Very strong opinions to consider [[GVerb#Freeverb3|Freeverb3]] as the "best" benchmark/starting point for reverb types and features (but don't include the whole suite as is) {{votes|14}}
 
<li>sensible presets that do not depend on mixing with a duplicate to sound decent {{votes|6}}
 
<li>Wet/Dry mix control {{votes|2}}
 
<li>stereo output.{{votes|4}}
 
</ul>
 
{{devcomment|1=The [http://www.youtube.com/watch?v=rjYYzNsNqlY&feature=youtu.be Harrison implementation] looks like an example of how to implement GVerb well, but that depends at a minimum on Audacity supporting real-time effects.}} 
 
</ul></ul>
 
  
* '''Amplify:'''
+
* '''Noise Removal:'''
** '''Linear "New Peak Amplitude" input:''' less confusing because it matches with default waveform (and the generate effects) {{votes|4}}
+
** '''Save Noise Profile for re-use in another session''' such as the previous method in Audacity 2.x where enabling CleanSpeech mode loaded a saved noise profile).{{votes|9}}
** '''Toggle non-destructive clipping''' when in 32-bit float quality {{votes|1}}
+
** '''Import/export noise profile as text file'''
** '''Option to launch at last used amplification level:''' {{votes|5}} even if the New Peak Amplitude is different each time. Use case is trying/undoing different amplification amounts to get the one you want, and you want to see quickly what you last tried (or do it again if you think that will give you the desired result.  
+
** '''Profile graphs''' showing an FFT of the noise profile at capture and graphs before and after removal step
** '''Presets in dropdown menu:''' {{votes|2}}
+
** '''Reset to Defaults''' {{votes|2}}
** '''Default to last used maximum dB level:''' {{votes|1}} Currently it defaults to 0 dB whereas Normalize defaults to last used maximum.  
+
** '''Modeless window:''' {{votes|5}} like Analyze > Contrast that lets you modify the selection with the window open. Clicking "Get Noise Profile" could then grab the profile but leave the window open while you select the audio to be noise-removed.
 +
** '''Presets (including user-addable)''' such as "light hiss", "60Hz hum" {{votes|2}}  
 +
** '''Leave Only Noise''' option as in Adobe Audition. When user performs  this on a duplicated track which is then inverted and mixed with the original, it allows noise to be removed by pure cancel-by-inversion. 
 +
** '''Implement as a plug-in''' DX or VST, so people could use it in other applications. To filter noise out of mic input in real time, for example {{votes|1}}
 +
** '''Better noise removal without fiddling with sliders:''' {{votes|2}}
 +
 
 +
<div id="normalizationrms"></div>
 +
* '''Normalize:'''
 +
:* {{done}} '''[http://en.wikipedia.org/wiki/Replay_Gain Replay Gain] or RMS:''' {{votes|20}} The current peak value normalization is far from what human ears perceive. If hard to implement, we can normalize to RMS (light blue in waveform) values instead 
 +
:** {{done}} '''Or use [http://tech.ebu.ch/loudness/ EBU Loudness Recommendation R128]''' {{votesdate|3|02Jun18}}
 +
:*** '''Display a momentary loudness curve that could adjust the normalization:''' {{votes|1}}
 +
:* '''Percentages:''' as an alternative to decibels. Many people have problems with decibels. {{votes|3}}
 +
:* '''Smarter Normalize when isolated peaks much higher than others:''' {{votes|5}}
 +
:** '''Ignore isolated peaks:''' {{votes|3}} An adjustable percentage of the highest peaks are ignored for purposes of calculation, simply being left at the original level 
 +
:** '''Sacrifice quality in isolated peaks:''' {{votes|1}} Create histogram of levels that lets user choose normalisation dB or percentage and a percentage (or per thousand/million/billion) of peaks allowed to exceed the normalisation level
 +
:** '''Choose whether to ignore any peaks over 0 dB or not:''' {{votes|1}} (some intersample peaks may be deliberate). 
 +
:* '''Option to calculate track gains together to avoid changing stereo balance:''' When multiple stereo tracks are selected, only the highest peak level of ALL tracks should be considered to adjust each track by the same amount so that the volume of each track relative to each other will stay the same.  {{votes|6}}
 +
: {{devcomment|This is what Effect > Amplify does. Some people would argue "Amplify" should be called "Normalize". 2/0.x has an option to "Normalize stereo channels independently". If unchecked, this retains the channel balance in stereo tracks while still letting all '''tracks''' be normalized '''independently'''. It does not replicate Amplify by only calculating the amplification needed to bring the loudest channel or track to the required New Peak Amplitude, then amplifying all tracks by that amount. Some people do want Amplify and Normalize to be merged - see the vote below - but care is needed so that too many options are not provided which could make a single effect too complex.}}
 +
:* '''Normalize should be merged with Amplify''' {{votes|5}}
 +
:* '''Display the current absolute peak level:''' {{votes|1}}
  
* '''Bass and Treble:'''
 
** '''Reinstate Bass Boost effect or add Frequency control to Bass and Treble:''' {{votes|7}} 
 
  
* '''Change Speed/Tempo/Pitch:'''  
+
* '''Nyquist plug-ins:'''
** Gradually increasing/decreasing tempo changes (without pitch change) to facilitate DJ-style mixing {{votes|6}}
+
** '''Preview Button:''' {{votes|2}}
** Allow changes in tempo/speed to be applied on the fly from the current (and ongoing) playback position. Currently changes in speed forces reverting to the start of cursor.  {{votes|1}}
+
** '''Bundle as one large zip file:''' {{votes|2}}  
<ul>{{devcomment|Edit > Move cursor... > to Selection End?}}
+
** '''Tabbed Interface:''' {{votes|3}} Could allow a simple interface on one tab and an advanced on the other, or help on the other tab
<ul><li>'''Change Speed: length of selection control''' like Change Tempo {{votes|19}}
+
** '''Remember settings post-session:''' {{votes|3}}   
<li>'''Change Speed: Use a change factor''' (e.g. 0.5x means half as fast, 2x means twice as fast) so that users are not confused by -50% doubling the length/halving the frequency, while you need +100% to halve the length / double the frequency {{votes|9}}</ul>
 
{{devcomment|This is now available with a "Speed Multiplier" control.}}
 
<ul><li>'''Change Speed: semitone pitch change control''' {{votes|3}}</ul>
 
{{devcomment|Available with the "[[Nyquist_Effect_Plug-ins#Change_Speed_by_Semitones|Change Speed by Semitones]]" plug-in.}}
 
<ul><li>'''Change Tempo: allow calculation of % change from less than whole BPM values.''' {{votes|3}} At slower tempi a non-integer change in BPM could mean a percentage change of two or three percent. Please notify info_AT_giovannierata_DOT_it if fixed...
 
<ul><li> This also allows this field to be used for any freeform units such as frames per second {{votes|3}}</ul>
 
{{devcomment|This functionality will be available from  Audacity 2.0.4 onwards.}}
 
<li> '''Change Speed/Tempo presets''' {{votes|8}}
 
<ul><li> '''Change Speed presets to/from 16 RPM''' {{votes|1}}</ul>    
 
<li> '''Dynamic Transient sharpening''' in Change Tempo/Pitch as in Sliding Timescale/Pitch Shift (without sliding of course) {{votes|2}}
 
<li> '''Option to use higher quality sbsms algorithm''' from Sliding Timescale/Pitch Shift (or amalgamate the tools so all that can be done in Change Tempo/Pitch can be done in Timescale) {{votes|3}}
 
  
<li> '''Window size choice''' in Change Pitch to combat FFT artefacts {{votes|1}}</ul></ul>
+
* '''Nyquist Prompt:'''
 +
** '''Parenthesis matching:''' {{votes|1}} Highlight [http://en.wikipedia.org/wiki/Brace_matching matching open/close brackets] when one or the other is selected.
  
* '''Click Removal:'''  
+
<div id="paulstretch"></div>
** '''Detection for clicks that are of similar level to surrounding audio''' or generally more reliable detection {{votes|28}}. [http://manual.audacityteam.org/o/man/click_removal.html Click Removal] gives hints for other solutions, but one tool should do the job in most cases, as with other software.
+
* '''Paulstretch:'''
** '''Intelligent joining to boundaries''' {{votes|1}} like Repair so that doesn't potentially add artefacts by almost silencing the samples it replaces so leaving abrupt joins with the unchanged audio
+
** '''Add''' '''''"Shorten"''''' '''mode:''' {{votesdate|1|21Aug17}} As in the standalone version of [http://hypermammut.sourceforge.net/paulstretch/ Paul's Extreme Sound Stretch] effect.
  
<div id="compressor"></div>
+
<div id="repair"></div>
* '''Compressor:'''
+
* '''Repair:'''
** '''Multi-band:''' {{votes|8}} so retaining the same frequency distribution.
+
** '''Vastly increased length of track to be worked on/works when zoomed out:''' {{votes|37}}  
*** '''Include a de-esser in this:''' {{votes|1}}
+
: {{devcomment|1=See [http://audacity.238276.n2.nabble.com/Patch-Repair-Clipping-Plugin-td2623796.html here] and [http://audacity.homerow.net/index.php?dir=modules%2F&download=fixclipping.zip this zip] for attempts to integrate Repair with Find Clipping}}
** '''Process stereo pairs together:''' {{votes|7}} so that the same amount of gain reduction is applied to both channels. The current Compressor applies different gain reduction to each channel which can lead to shifting of stereo image.
+
***If selection made is too long, truncate it to maximum possible, but still let user drag the selection in either direction retaining the maximum length {{votes|4}}    
** '''Shorter attack/release times:''' {{votes|5}}
+
***Show the length that can be processed in current Selection Format, not samples {{votes|2}}
*** '''Show attack/release times in milliseconds:''' {{votes|1}}
+
***Show an approximate processing time for long selections. {{votes|1}}
** '''Text box input:''' {{votes|5}}
 
** '''Configurable lookahead in milliseconds:''' {{votes|4}} so pre-emptively apply the compression. Don't just make it the same as the Attack Time as now. 
 
** '''Choose upward or downwards compression independent of peak or RMS envelope:''' {{votes|2}}
 
** '''Choose make-up gain amount''' {{votes|2}}
 
** '''Built-in Hard limiter/dual slope/tabbed for different settings''' {{votes|2}}
 
** '''Presets for common tasks:''' {{votes|2}} such as "Levelling speech", "Maximizing", "Audiobook compression", "Peak limiting". Eliminates the need to install third party compressor plug-ins for casual users. 
 
** '''Finer Ratio discrimination than .5:''' {{votes|1}} 
 
** '''Envelope-based''' tool that just works by dragging as in Digital Performer {{votes|1}}  
 
  
<div id="eq"></div>
+
* '''Repeat:'''  
* '''Equalization:'''
+
** '''Add Delay''' so as to merge each repeat smoothly {{votes|5}}:  Current Repeat effect gives a very dry result compared to creating and playing a loop in software sequencers or drum machines. Some delay could be added after the end of the region to be repeated, then the start of each repeat has this delay mixed in.  
<div id="78curves"></div>
+
** '''Checkbox for "do not create split lines":''' {{votes|4}} visually very distracting when fitting project to window.
** '''Reinstate 78 RPM EQ curves from Audacity 1.2:''' {{votes|25}}  
+
** '''Insert Silence between repeats:''' {{votesdate|1|15Mar17}}
<ul>{{devcomment|You can generate a large number of company-specific 78 RPM and pre-RIAA LP curves using the experimental Nyquist plug-in "78 RPM EQ Curve Generator" and the curve tables on [[78rpm playback curves]].}}
 
<ul><ul><li> '''Automatic 78 RPM EQ from RIAA-recorded 78's:''' {{votes|9}} Inverts the curve to negate the RIAA EQ then applies the required 78 RPM EQ in one button press. More 78 RPM presets facilitate this (votes as above) </ul>
 
<li> '''De-emphasis for early CDs:''' {{votes|2}} using the WaveEmph or other curves (see  http://www.hydrogenaudio.org/forums/index.php?showtopic=65067 )
 
<li> '''Improve accuracy:'''
 
<ul><li> '''Text input''' {{votes|8}}
 
<ul><li> like Cool Edit's right-click on control point then type the values {{votes|2}}
 
<li> Edit box like Label Editor that would list all the points and allow normal editing functions  like copy and paste {{votes|1}}</ul>
 
<li> Text entry box when double-clicking on Graphic EQ sliders as elsewhere {{votes|2}}
 
<li> '''Cursor readout''' {{votes|7}}
 
<li> '''Zoomable grids''' {{votes|5}}</ul>
 
<li>'''[[Graphic Equalizer - simple|Simpler/more presettable Graphic EQ]]:''' {{votes|3}} Either an alternative interface with current EQ, or an additional built-in effect. 5 - 7 bands would be adequate/quicker for our many casual users. Greater range of general purpose presets needed such as "heavy bass boost", "light treble reduction", "equal loudness"....  These should be separated from other e.g. gramophone presets.
 
<li> '''Graphic EQ sliders should allow choice of bandwidth''' {{votes|1}}
 
<li> '''Separate built-in Parametric EQ''' {{votes|3}} i.e. where all parameters controlling the tone change have their own control.
 
<ul><li>high pass, low pass and 3 or more bands {{votes|1}}</ul>
 
<li> '''Add built-in envelope''' so that amount of EQ (% of gain specified in parameters) can be varied over time  {{votes|1}}
 
<li> '''Mini-waveform''' {{votes|2}} (time against amplitude) in which you can click to preview - see [http://www.nch.com.au/wavepad/masters.html Wavepad]
 
<li> '''Incorporate mini-spectrum plot''' {{votes|7}} ideally it should change when you modify the EQ curve
 
<ul><li>'''Include dry (pre-effect) spectrum too''' {{votes|1}}  </ul>
 
<li> '''Save Presets without renaming "unnamed"''' {{votes|4}}  
 
<li> '''More frequency-specific presets''' like "Very Bright", "Mid-range", "Classical", "Hard Rock", "Soft Rock", "Dr Dre" {{votes|3}}     
 
<li> '''User-saved presets should save filter length and Draw/Graphic mode''' {{votes|1}} e.g. a curve with low frequency control points will require maximum length to be reasonably accurate but this length will slow down processing of other curves un-necessarily.
 
<li> '''Smart Normalize before EQ to safe level for the requested curve''' {{votes|1}}
 
<li> '''Remember window size and position''' {{votes|3}} 
 
<li> '''FFT Filter''' seems to be missing in 1.3.3 (and in 1.3.5) </ul>
 
{{devcomment|The linear frequency scale in Equalization provides the same functionality}}</ul>
 
  
<div id="fadeinout"></div>
+
* '''Sliding Time Scale/Pitch Shift:'''  
<ul><li> '''Fade In/Fade Out:'''
+
** '''Percentage control for pitch''' {{votes|2}} so that conversions into semitone changes are avoided
<ul><li> '''New controls for choosing the start and end amplitude gain''' - quick linear fade, much simpler and quicker than the Envelope Tool (and VI-accessible)  {{votes|27}}
+
** '''Envelope GUI''' {{votes|2}}  
{{ednote|1=<p>
 
*'''Steve 12Nov12:''' Does there need to be a note that linear scale gain is not acceptable?
 
**'''Gale:''' One more person has requested both "target" and "% gain", so I added the votes. OK, I've now sifted through as many of these original requests for "start and end amplitude" as I could find (20). 14 of them say "%", four say "0.something", and two just say "partial linear fade" (but they mean the shape, I think). I've generalised the first order request and applied that ratio of those who wanted "%" and other features to the second order bullets. I think it's up to you and I if we allow linear scale of 0 - 1, but I'd still argue that it would confuse some users because of the similarity with the horizontal scale.
 
** '''Gale:''' If you add devcomments, please look at the result and fix the bullet points :=) </p>}}
 
<ul><ul><ul><li>'''Should be from % of original amplitude to another % of original amplitude''' {{votes|19}}
 
{{ednote|'''Peter 01Feb17:''' [[ToDo-1]] Doesn't Steve's Adjustable Fade do just this % change?  If so we can mark this as completed.  }}
 
<li> '''Additional Choice of fade to a target dB''', not by an amount {{votes|17}}</ul>
 
{{devcomment|As it stands, this feature could not be practicably realized for signals that have varying amplitude without a time period being specified within which the target amplitude should be attained. However there is still the possible choice of hiding the length issue from the user - the "help" would say what it actually does. See [[Talk:Feature Requests#target|discussion on Talk page.]]}}</ul>
 
<ul><ul><li>'''Choices for dB or linear units, and/or linear or logarithmic shape'''  {{votes|9}}</ul></ul>
 
<ul><li> '''Should include multiple envelope points''' {{votes|4}}
 
<li> '''Fade out according to freqency spectrum:''' fade bass more slowly like professional fader hardware to provide smooth fade and maintain depth right to the end </ul>
 
{{devcomment|1=This is implemented in the Nyquist plug-in [http://forum.audacityteam.org/viewtopic.php?f=42&t=66654 "Professional Fade Out"]}}</ul></ul>
 
  
* '''Generate:'''
+
* '''Truncate Silence:'''  
<!-- ** '''All generators should remember their parameters across sessions.''' {{votes|5}} Currently only DTMF and Noise do so, stored in audacity.cfg FIXED -->
+
** '''New option to work on each track separately not on mix''' {{votes|8}}    
** '''Provide way to default selection format to other than seconds.''' Either store the format in .cfg or let it default to the current Selection Toolbar format {{votes|35}}
+
** '''New option to truncate only leading and trailing silence''' {{votes|2}}
*** "last used" is better {{votes|14}}
 
*** "same as Selection Toolbar format" is better {{votes|6}}
 
*** Possibly generation at a region should always default to hh:mm:ss + samples, but still allow different choice to be saved in Preferences {{votes|6}}
 
** '''List notes for tone generation:''' {{votes|4}} e.g.middle C (264 Hz) etc.
 
** '''Triangle option for Tone''' {{votes|7}}
 
*** with no alias option {{votes|2}}
 
** '''Applause''' {{votes|1}} 
 
** (2.x) '''Text box input''' as in 1.2, because much simpler to overtype irrespective of the format, and allows copy and paste {{votes|8}} 
 
** '''Choice of overtones to include:''' (within the limitations of the waveform chosen) {{votes|1}}.
 
  
* '''Noise Removal:'''
+
* '''VST Plug-ins:'''
** '''Save Noise Profile for re-use in another session''' such as the previous method in Audacity 2.x where enabling CleanSpeech mode loaded a saved noise profile).{{votes|9}}
+
** '''Option for rescan on each launch''' plus "once-only" checkbox to restart on OK'ing Preferences {{votes|9}}
** '''Import/export noise profile as text file'''
+
** '''Rescan without restart''' {{votes|5}}
** '''Profile graphs''' showing an FFT of the noise profile at capture and graphs before and after removal step
+
<!--** '''Load when using the effect, not on launch''' {{votes|3}} for greater stability and fewer licensing and other notices from third-party plug-ins -->
** '''Reset to Defaults''' {{votes|2}}
+
** '''Install VST Effects dialog:''' Sort Name and Path separately {{votes|3}}
** '''Modeless window:''' {{votes|5}} like Analyze > Contrast that lets you modify the selection with the window open. Clicking "Get Noise Profile" could then grab the profile but leave the window open while you select the audio to be noise-removed.
+
** '''Put the name of the effect first''' in the menu or omit manufacturer {{votes|6}}
** '''Presets (including user-addable)''' such as "light hiss", "60Hz hum" {{votes|2}}  
+
: {{devcomment|You can quit Audacity, open Audacity's [https://manual.audacityteam.org/o/man/preferences.html#stored folder for application data], then open pluginsregistry.cfg and carefully exchange the Name with the Vendor information and the Vendor with the Name information. Your change will only persist until you rescan plug-ins, of course.}}
** '''Leave Only Noise''' option as in Adobe Audition. When user performs  this on a duplicated track which is then inverted and mixed with the original, it allows noise to be removed by pure cancel-by-inversion. 
 
** '''Implement as a plug-in''' DX or VST, so people could use it in other applications. To filter noise out of mic input in real time, for example {{votes|1}}
 
** '''Better noise removal without fiddling with sliders:''' {{votes|2}}  
 
  
* '''Normalization:'''
 
<div id="normalizationrms"></div>
 
** '''[http://en.wikipedia.org/wiki/Replay_Gain Replay Gain] or RMS:''' {{votes|20}} The current peak value normalization is far from what human ears perceive. If hard to implement, we can normalize to RMS (light blue in waveform) values instead 
 
*** '''Or use [http://tech.ebu.ch/loudness/ EBU Loudness Recommendation R128]''' {{votes|2}}
 
**** '''Display a momentary loudness curve that could adjust the normalization:''' {{votes|1}}
 
** '''Percentages:''' as an alternative to decibels. Many people have problems with decibels. {{votes|3}}
 
  
** '''Smarter Normalize when isolated peaks much higher than others:''' {{votes|5}}
+
<div id="install"></div>
*** '''Ignore isolated peaks:''' {{votes|3}} An adjustable percentage of the highest peaks are ignored for purposes of calculation, simply being left at the original level 
 
*** '''Sacrifice quality in isolated peaks:''' {{votes|1}} Create histogram of levels that lets user choose normalisation dB or percentage and a percentage (or per thousand/million/billion) of peaks allowed to exceed the normalisation level
 
*** '''Choose whether to ignore any peaks over 0 dB or not:''' {{votes|1}} (some intersample peaks may be deliberate). 
 
** '''Option to calculate track gains together to avoid changing stereo balance:''' When multiple stereo tracks are selected, only the highest peak level of ALL tracks should be considered to adjust each track by the same amount so that the volume of each track relative to each other will stay the same.  {{votes|6}}
 
<ul>{{devcomment|This is what Effect > Amplify does. Some people would argue "Amplify" should be called "Normalize". 2/0.x has an option to "Normalize stereo channels independently". If unchecked, this retains the channel balance in stereo tracks while still letting all '''tracks''' be normalized '''independently'''. It does not replicate Amplify by only calculating the amplification needed to bring the loudest channel or track to the required New Peak Amplitude, then amplifying all tracks by that amount. Some people do want Amplify and Normalize to be merged - see the vote below - but care is needed so that too many options are not provided which could make a single effect too complex.}}
 
<ul><li>'''Normalize should be merged with Amplify''' {{votes|5}}
 
<li> '''Display the current absolute peak level:''' {{votes|1}}
 
</ul></ul>
 
  
* '''Nyquist plug-ins:'''
+
== Installation/first run, deployment and uninstallation ==
**'''Preview Button:''' {{votes|2}}
+
* ''(Windows)'' '''Choose English language:''' {{votes|14}}  
**'''Bundle as one large zip file:''' {{votes|2}}
 
**'''Tabbed Interface:''' {{votes|3}} Could allow a simple interface on one tab and an advanced on the other, or help on the other tab
 
**'''Remember settings post-session:''' {{votes|3}}  
 
  
* '''Nyquist Prompt:'''
+
* ''(Windows)'' '''MSI installer for multiple installation on networked computers''' {{votes|9}} {{devcomment|There is a script [[Group Policy Installation|here]] that allows multiple installation via Group Policy or a tool to make an MSI installer [http://dennisbareis.com/makemsi.htm here].}}
** '''Parenthesis matching:''' {{votes|1}} Highlight [http://en.wikipedia.org/wiki/Brace_matching matching open/close brackets] when one or the other is selected.  
 
  
* '''Make [[Nyquist Plug-ins Reference#Nyquist Workbench|Nyquist workbench]] an installable feature''' without having to compile Audacity from [http://web.audacityteam.org/community/developers#svn HEAD] as now.
+
* ''(Windows)'' '''User-customizable location for Start Menu shortcut''' {{votes|2}}
** Add syntax highlighting
 
** "Insert plug-in Header" command
 
  
<div id="repair"></div>
+
* '''Complete uninstallation''' including removal of Audacity settings and temp folder {{votes|5}}  
* '''Repair:'''
+
{{devcomment|Not very clear how this could be done outside of Windows installers unless there was a separate executable to remove settings. Where there was an uninstaller, it could include a "repair" option to reset settings instead of having a separate executable to repair or remove them.}}
** '''Vastly increased length of track to be worked on/works when zoomed out:''' {{votes|37}}  
+
<ul>{{devcomment|1=See [http://audacity.238276.n2.nabble.com/Patch-Repair-Clipping-Plugin-td2623796.html here] and [http://audacity.homerow.net/index.php?dir=modules%2F&download=fixclipping.zip this zip] for attempts to integrate Repair with Find Clipping}}</ul>
+
* '''All-users settings, not per-user:''' {{votes|11}} This frees new users in a multi-user environment such as a college or audio lab from having to configure paths or features that have to be chosen on first use, such as language (in 1.2), LAME or FFmpeg (in Audacity 2.x).
::*If selection made is too long, truncate it to maximum possible, but still let user drag the selection in either direction retaining the maximum length {{votes|4}}    
+
{{devcomment|You could run a script the first time a user logs on or otherwise pre-load
::*Show the length that can be processed in current Selection Format, not samples {{votes|2}}
+
their account with the settings wanted for Audacity.}}
::*Show an approximate processing time for long selections. {{votes|1}}
 
  
* '''Repeat:'''
+
* '''"Plug-ins" and "Modules" folders in Audacity's data folder''' {{votes|2}} (where audacity.cfg is). On Linux this means root access is no longer needed to modify these folders, and custom plug-ins aren't lost when updating from a package manager. OTOH "Plug-ins" and "Modules" would be hidden. This would be a drawback for Windows users which might outweigh the benefit of per-user plug-ins and modules.  
** '''Checkbox for "do not create split lines":''' {{votes|4}} visually very distracting when fitting project to window.
+
** '''Let user choose folder location''' {{votes|2}} could be done via an  AUDACITY_PATH environment variable for all platforms, or via an "Effects Manager" (doesn't matter then if folder is hidden), or via Preferences.
** '''Add Delay''' so as to merge each repeat smoothly {{votes|3}}  
 
  
* '''Sliding Time Scale/Pitch Shift:'''  
+
== Improved Resource or Project Management  ==
** '''Percentage control for pitch''' {{votes|2}} so that conversions into semitone changes are avoided
+
* '''Additional options for saving "[http://manual.audacityteam.org/man/file_menu_save_other.html#Save_Compressed_Copy_of_Project... Compressed Copy]":'''
** '''Envelope GUI''' {{votes|2}}  
+
** '''Lossless:''' {{votesdate|3|21Feb18}} Option to use FLAC (and / or other lossless compressed format) rather than Ogg.
 +
** '''One file per clip:''' {{votesdate|1|24Nov17}} rather than one file per track.
 +
* '''Priority:'''  
 +
** '''Set overall Audacity priority:''' {{votes|6}} Raising Audacity priority can reduce risk of recording skips. Reducing might make it easier to work in other applications while exporting or running long effects. Could be a Preference but better to set on the fly with a button, its value stored in audacity.cfg and used on launch. Otherwise you need hacks such as computer's Task Manager to change priority after launch, or a shortcut to do so at launch using some external software.
 +
** '''Per-thread or per task priority:''' {{votes|3}} Useful when Audacity projects and processes are separable and threadsafe.
 +
* '''Progress bar for waveform drawing:''' When I do a control-f (zoom to fit in window) in audacity on a 2 hour recording it takes a while before the waveform is displayed. Some busy indicator, maybe even progress bar might help.  Same for moving around in a file, which can take time. (even on striped disks) This also affects re-drawing of the waveform after applying pretty much any Effect.  {{votes|6}}
  
* '''Truncate Silence:'''
+
* '''Disk space check before exporting:''' {{votes|16}} - including indication of expected size of export, and choice to export partial file or cancel if insufficient space available. Would stop user exporting WAV files over the 2/4 GB limit, MP3s in excess of ringtone limits etc.
** '''New option to work on each track separately not on mix''' {{votes|8}}    
+
{{devcomment|Could only indicate that space was available at time of checking, could never guarantee the file would be completed if other disk events occurred. However Audacity 2.x does now have a warning if WAV/AIFF exports are not completed.}}
** '''New option to truncate only leading and trailing silence''' {{votes|2}}
 
  
* '''Vocal Remover:'''
+
* '''Capability Hints in GUI:''' Search and recognize existing hardware capabilities. Specifically, note limits on quality achievable due to RAM configuration, DAC bit counts, soundboard specifics such as dB gain at recording levels (41, 44, 96), and other software installed on the machine (iTunes, other popular players / organizers). Then customize recommendations by what is doable on that machine, but still allow anyone to get extreme if they wish. {{votes|1}}
** '''Removal of other than center-panned content, and isolation of content''' {{votes|10}}  
+
* '''Detection of operating system with warning if Audacity version inappropriate:''' {{votes|1}} Suggestion made primarily due to problems with Mac users having the wrong version of Audacity 1.2 for their architecture then the correct LAME binary is not recognised, though most of this particular problem will disappear when 2.0 comes out as a universal binary. Maybe useful when 2.0 is mainstream and does not support OS X 10.3?  
** '''Stereo output''' {{votes|3}}
 
<ul>{{devcomment|See [[Vocal Removal Plug-ins]] for the issues involved in doing this and alternative tools already available. The main ways of improving such tools is by working on frequency/cepstrum rather than just spatial characteristics, plus (in the future) [[Source Separation Notes|source separation]].}}
 
<ul><li> '''Option to place original audio in one channel and ouput in the other:''' {{votes|1}} -  solves main problem of recording karaoke - when to sing according to the original timings </li></ul></ul>  
 
  
* '''VST Plug-ins:'''
+
<div id="undo"></div>
** '''Option for rescan on each launch''' plus "once-only" checkbox to restart on OK'ing Preferences {{votes|9}}
+
<ul><li> '''Undo History''':
** '''Rescan without restart''' {{votes|5}}
+
<ul><li> '''Compress undo buffers''' {{votes|2}}
<!--** '''Load when using the effect, not on launch''' {{votes|3}} for greater stability and fewer licensing and other notices from third-party plug-ins -->
+
<ul><li> (You can already clear the Undo buffers by opening the Undo History dialog box, and compressing will take lots of CPU and have little space gain unless you use a lossy compressor, which kind of defeats the point of undo...)</ul>
** '''Install VST Effects dialog:''' Sort Name and Path separately {{votes|3}}
+
<div id="history"></div>
** '''Put the name of the effect first''' in the menu or omit manufacturer {{votes|6}}
+
<li>'''Make Undo history viewable (but not actionable) after close project:''' {{votes|17|14Oct18}} just so you can see what those actions were. Can be done by:
<ul>{{devcomment|You can quit Audacity, open Audacity's [http://manual.audacityteam.org/o/man/preferences.html#stored folder for application data], then open pluginsregistry.cfg and carefully exchange the Name with the Vendor information and the Vendor with the Name information. Your change will only persist until you rescan plug-ins, of course.}}</ul>
+
<ul><li> '''Export undo history or complete commands history''' as a .txt file {{votesdate|10|14Oct18}} or
 
+
<li> '''Store Undo history in the AUP file:''' {{votes|9|14Oct18}} then you could look at the items (grayed out) in View > History.
<div id="install"></div>
+
<ul><li> '''Combine with feature to periodically save multiple timestamped AUP files as a backup''' {{votes|1}} </ul></ul>
 +
<li>'''Make Undo active across sessions:''' {{votesdate|8|18Aug20}} Useful when projects are shared between users and you may want to undo the last thing(s) that someone else did. This saves the much larger space requirements as now of saving multiple backup projects at different stages of project progress. </ul> 
 +
{{devcomment|This could potentially require vast amounts of disk space, so could never be default.}}
 +
<ul><li>'''Autosave history, so it can be restored after a crash:''' {{votes|1}} </ul>  
 +
{{devcomment|Autosave is currently inefficient in long projects, scanning the entire data. As of 2.0.6-alpha there are many actions that appear in history that are not autosaved. It may or may not be possible to periodically "export" the history list every N minutes to the AUP file, bypassing the data scan.}}
 +
<ul><li> '''More detailed/organised:''' {{votes|3}}
 +
<ul><li> includes EQ Parameters applied {{votes|1}} 
 +
<li> includes which tracks items were applied to {{votes|3}}
 +
<li> should have separate entries for each track {{votes|1}} </ul>
 +
<li> '''Add mute/solo state to history ''' {{votes|1}}</ul></ul>
  
== Installation/first run, deployment and uninstallation ==
+
* '''Project manager utility:''' {{votes|6}} Could include:
* ''(Windows)'' '''Choose English language:''' {{votes|14}}  
+
** Safe renaming/moving/deleting of projects
 +
** Choose multiple projects to export from/import into at one go (including export multiple ability from each project)
 +
*** "Project Jukebox" to play selected projects in sequence {{votes|1}}  
  
* ''(Windows)'' '''MSI installer for multiple installation on networked computers''' {{votes|9}} {{devcomment|There is a script [[Group Policy Installation|here]] that allows multiple installation via Group Policy or a tool to make an MSI installer [http://dennisbareis.com/makemsi.htm here].}}
+
* '''Project integrity''':
 +
** <font color=gray><strike>'''Make copy-in default:''' Only this will completely avoid danger of user deleting dependent files. {{votes|5}}</strike></font> - ''this is now the default in current Audacity
 +
** '''Store ''copy'' of .aup or autosave file as a backup''' {{votes|8}} Could be a vital recovery feature if a crash or error on saving causes the file to be corrupted or destroyed.
 +
** '''Incremental version check on audio file data''' (a la Volume Shadow Copy) because as of now, it seems to save anything it can and wants {{votes|1}}
 +
** '''Provide official MD5 and/or SHA1 sum''' {{votes|1}}
 +
** '''Save timeline/track position metadata in each .au file''' to allow recovery if .aup file missing or damaged {{votes|2}}
 +
<ul>{{devcomment|Could have a significant performance impact as editing may require continual resaving of all the .au files}} </ul>
  
* ''(Windows)'' '''User-customisable location for Start Menu shortcut''' {{votes|2}}
+
* '''Better multi-threading/multi-processing support:''' {{votes|18}} to use full potential of Dual-Core/multi-processor machines when exporting/editing the audio. Use Lisp process delegation for multi-core processing and (harder) multi-threaded operation. (Think: divide and conquer, process pools that operate on portions of the waveform and joining the result, and you will arrive at a solution)
 +
** '''Better thread separation''' {{votes|9}} to allow safe execution of simultaneous tasks to improve workflow. It should be possible on a modern machine to do things like simultaneously record in separate projects; record in one project while editing or exporting from another etc.
 +
<ul>{{devcomment|'''LRN wrote:''' Multi-threading means two different things. 1: "Do two things simultaneously". This requires Audacity redesign to be more threaded. [https://en.wikipedia.org/wiki/OpenCL OpenCL] wouldn't help here. [https://manual.audacityteam.org/o/man/on_demand_loading.html On-Demand Loading] is an example of threaded design. 2: "Do one thing in two threads, which makes it go about two times faster". This requires special implementation and OpenCL would help. But it's not cost-effective to rewrite everything in
 +
[https://en.wikipedia.org/wiki/Symmetric_multiprocessing symmetric multi-processing] style. Only costly operations should be made parallel, everything else would benefit more from threaded design.}}</ul>
  
* ''(Windows)'' '''Support Windows 7 [http://windows.microsoft.com/en-US/windows7/products/features/jump-lists Jump Lists]''' {{votes|3}}  
+
* '''Additions to AUP project file:'''
** At least allow Audacity to support [http://code.google.com/p/jumplist-extender/downloads/detail?name=JumplistExtender_v0.4.exe&can=2 Jump List Extender] {{votes|1}}  
+
**'''Current View Mode of each track:''' {{votes|3}} "Default View Mode" in Tracks preferences will then affect only newly created tracks. View mode changes alone, like other view changes, may still not be sufficient to prompt for save of the project when closing.
 +
** '''Window sizes and x/y positions:'''  {{votes|3}}
  
* '''Complete uninstallation''' including removal of Audacity settings and temp folder {{votes|5}}  
+
* '''Take advantage of unused GPU cycles:''' Graphics processing units have the processing power to run 3D image but Audacity doesn't use hi-res 3D. This unused power could potentially be harnessed to speed up audio processing.  {{votes|4}}
{{devcomment|Not very clear how this could be done outside of Windows installers unless there was a separate executable to remove settings. Where there was an uninstaller, it could include a "repair" option to reset settings instead of having a separate executable to repair or remove them.}}
+
** '''Use Nvidia's freeware [http://en.wikipedia.org/wiki/CUDA CUDA] parallel computing engine''' {{votes|1}}
+
 
* '''All-users settings, not per-user:''' {{votes|11}} This frees new users in a multi-user environment such as a college or audio lab from having to configure paths or features that have to be chosen on first use, such as language (in 1.2), LAME or FFmpeg (in Audacity 2.x).
+
* '''Improvements to audacity.cfg:'''
{{devcomment|You could run a script the first time a user logs on or otherwise pre-load
+
** '''Export and Import''' {{votes|1}}
their account with the settings wanted for Audacity.}}
+
*** '''Immediate application of changes like modifying xml files:''' {{votes|1}}  
  
* '''"Plug-ins" and "Modules" folders in Audacity's data folder''' {{votes|2}} (where audacity.cfg is). On Linux this means root access is no longer needed to modify these folders, and custom plug-ins aren't lost when updating from a package manager. OTOH "Plug-ins" and "Modules" would be hidden. This would be a drawback for Windows users which might outweigh the benefit of per-user plug-ins and modules.  
+
* '''Audio clip library manager (built in):''' Many audio editors / DAWs have some sort of "library manager" that allows quick and convenient access to audio clips for use in the current project. {{votesdate|28Aug18|3}}
** '''Let user choose folder location''' {{votes|2}} could be done via an  AUDACITY_PATH environment variable for all platforms, or via an "Effects Manager" (doesn't matter then if folder is hidden), or via Preferences.
 
  
== Improved Resource or Project Management  ==
+
== Imports and Exports ==
<div id="unitaryproject"></div>
 
* '''Smaller-sized and/or more unified project storage:''' {{votes|29}}
 
**See this proposal:  [[Proposal Unitary Project]]
 
** '''Single file, compressed audio (lossy or not)''' {{votes|18}} Uncompressed data not essential for sending to others if they are not editing it. The dual concept of the _data folder and .aup file is confusing and too interdependent.
 
*** '''Option to zip project on save:''' Reduces size losslessly and minimises recipient confusion  {{votes|5}}
 
*** '''Must be a lossless option''', single file more important than compression {{votes|5}}
 
<ul><ul>{{devcomment|Audacity 2.x now has ability to save a compressed project, one OGG file per track, but still with a separate .aup file.}}
 
<li>'''Each track as one file''' {{votes|3}} This is how commercial multitrack apps like Logic, Cubase, Pro Tools etc usually handles multitrack audio.
 
<li> '''Keep .aup file and _data folder together in one folder.''' {{votes|3}}
 
<li> '''Compatible with version control software''' (e.g. unchanged tracks or chunks always appear the same in binary form) --[[User:Skorpion|Skorpion]] 11:04, 11 March 2010 (CST)
 
</ul></ul>
 
  
* '''Priority:'''
 
** '''Set overall Audacity priority:''' {{votes|6}} Raising Audacity priority can reduce risk of recording skips. Reducing might make it easier to work in other applications while exporting or running long effects. Could be a Preference but better to set on the fly with a button, its value stored in audacity.cfg and used on launch. Otherwise you need hacks such as computer's Task Manager to change priority after launch, or a shortcut to do so at launch using some external software.
 
** '''Per-thread or per task priority:''' {{votes|3}} Useful when Audacity projects and processes are separable and threadsafe.
 
* '''Progress bar for waveform drawing:''' When I do a control-f (zoom to fit in window) in audacity on a 2 hour recording it takes a while before the waveform is displayed. Some busy indicator, maybe even progress bar might help.  Same for moving around in a file, which can take time. (even on striped disks) This also affects re-drawing of the waveform after applying pretty much any Effect.  {{votes|6}}
 
  
* '''Disk use limit for recording''' {{votes|11}}
+
<div id="importappended"></div>
** '''Option to Disable''' {{votes|1}}
+
'''Import Appended:''' {{votes|39}} Import multiple files end-to-end in a single track. Would allow re-assembly/re-processing of LP/tape recordings for which no Audacity project exists. Also allows to import multiple tracks for CD assembly <p>Possible Enhancements:</p>
 +
* with labels containing their file names
 +
:{{devcomment|1=If not labeled, it will be important for many use cases that the imported files remain as separate audio clips.}}
 +
* Import multiple files (or even a single file) at cursor position:
 +
:{{devcomment|1=You can always Project > Import Audio and SHIFT + click or CTRL + click to select and import multiple files into a project as separate tracks. There is no automated process beyond that. No players can read the labels in the joined track other than Audacity - they aren't bookmarks in that sense, as there is no agreed standard for reading divisions within files. The labels can be exported to form the basis of a cue sheet.<p>A [https://forum.audacityteam.org/viewtopic.php?f=42&t=59528 Nyquist plug-in] is available to test which can import multiple WAV or AIFF files end-to-end from a directory or from a list of files, starting from either time zero or from the cursor position.</p>}}
 +
*Import one new file at cursor position: simpler/more important {{votes|3}}
  
* '''Disk space check before exporting:''' {{votes|16}} - including indication of expected size of export, and choice to export partial file or cancel if insufficient space available. Would stop user exporting WAV files over the 2/4 GB limit, MP3s in excess of ringtone limits etc.
+
'''Import below current track:''' This would be useful when working with projects that have a lot of tracks. Much easier than having to manually move a track after it has been imported at the bottom of the project. {{votesdate|2|21May19}}
{{devcomment|Could only indicate that space was available at time of checking, could never guarantee the file would be completed if other disk events occurred. However Audacity 2.x does now have a warning if WAV/AIFF exports are not completed.}}
+
* See: [[Proposal: Rationalizing where new tracks are created to aid usability and consistency]]
 +
:{{devcomment|1=This feature was first requested years ago, but appears to have been lost over time. A possible workaround would be a Nyquist Macro that moves the bottom track to immediately below the first selected track.}}
  
* '''Capability Hints in GUI:''' Search and recognize existing hardware capabilities. Specifically, note limits on quality achievable due to RAM configuration, DAC bit counts, soundboard specifics such as dB gain at recording levels (41, 44, 96), and other software installed on the machine (iTunes, other popular players / organizers). Then customize recommendations by what is doable on that machine, but still allow anyone to get extreme if they wish. {{votes|1}}
+
*'''Previewing audio:''' A way to preview audio before importing it as a new track like with Adobe Audition?  {{votes|3}}
* '''Detection of operating system with warning if Audacity version inappropriate:''' {{votes|1}} Suggestion made primarily due to problems with Mac users having the wrong version of Audacity 1.2 for their architecture then the correct LAME binary is not recognised, though most of this particular problem will disappear when 2.0 comes out as a universal binary. Maybe useful when 2.0 is mainstream and does not support OS X 10.3? 
 
  
<div id="undo"></div>
 
<ul><li> '''Undo History''':
 
<ul><li> '''Compress undo buffers''' {{votes|2}}
 
<ul><li> (You can already clear the Undo buffers by opening the Undo History dialog box, and compressing will take lots of CPU and have little space gain unless you use a lossy compressor, which kind of defeats the point of undo...)</ul>
 
<li>'''Make Undo history viewable (but not actionable) after close project:''' {{votes|14}} just so you can see what those actions were. Can be done by:
 
<ul><li> '''Export undo history or complete commands history''' as a .txt file {{votes|7}} or
 
<li> '''Store Undo history in the AUP file:''' {{votes|7}} then you could look at the items (grayed out) in View > History.
 
<ul><li> '''Combine with feature to periodically save multiple timestamped AUP files as a backup''' {{votes|1}} </ul></ul>
 
<li>'''Make Undo active across sessions:''' {{votes|7}} Useful when projects are shared between users and you may want to undo the last thing(s) that someone else did. This saves the much larger space requirements as now of saving multiple backup projects at different stages of project progress. </ul> 
 
{{devcomment|This could potentially require vast amounts of disk space, so could never be default.}}
 
<ul><li>'''Autosave history, so it can be restored after a crash:''' {{votes|1}} </ul>
 
{{devcomment|Autosave is currently inefficient in long projects, scanning the entire data. As of 2.0.6-alpha there are many actions that appear in history that are not autosaved. It may or may not be possible to periodically "export" the history list every N minutes to the AUP file, bypassing the data scan.}}
 
<ul><li> '''More detailed/organised:''' {{votes|3}}
 
<ul><li> includes EQ Parameters applied {{votes|1}} 
 
<li> includes which tracks items were applied to {{votes|3}}
 
<li> should have separate entries for each track {{votes|1}} </ul>
 
<li> '''Add mute/solo state to history ''' {{votes|1}}</ul></ul>
 
  
* '''Project manager utility:''' {{votes|6}} Could include:
+
<div id="newformats"></div>
** Safe renaming/moving/deleting of projects
+
===New Import/Export Formats===
** Choose multiple projects to export from/import into at one go (including export multiple ability from each project)
 
*** "Project Jukebox" to play selected projects in sequence {{votes|1}}
 
  
* '''Ability to open an AUP file by dragging in''' - it should just open a new project window {{votes|3}}
+
{{Hint|There are some file formats and effect interfaces we can't support for commercial reasons. Please check our [[Features We Can't Implement]] page before adding features to the list below.}}
  
* '''Project integrity''':
+
<div id="soundtrack"></div>
** '''Make copy-in default:''' Only this will completely avoid danger of user deleting dependent files. {{votes|5}}
+
*'''Import/play video for synchronized soundtrack editing''' {{votesdate|49|20Nov21}} No need for Audacity to edit the video. Alternatively, Audacity could send/receive SMPTE or MTC timecode data e.g. to VLC or mplayer.
** '''Store ''copy'' of .aup or autosave file as a backup''' {{votes|8}} Could be a vital recovery feature if a crash or error on saving causes the file to be corrupted or destroyed.
+
:Logged as an Ehancement Request on GitHub:  https://github.com/audacity/audacity/issues/2167
** '''Incremental version check on audio file data''' (a la Volume Shadow Copy) because as of now, it seems to save anything it can and wants {{votes|1}}
+
** '''Standalone SMPTE reader useful in own right''' {{votes|1}} e.g. for reading time track on an analog tape deck. 
** '''Provide official MD5 and/or SHA1 sum''' {{votes|1}}
+
** '''Existing Timeline must show audio behind zero''' {{votes|1}}
** '''Save timeline/track position metadata in each .au file''' to allow recovery if .aup file missing or damaged {{votes|2}}
+
** '''Video window should have video timeline''' but Audacity window should not need separate video timeline {{votes|1}}  
<ul>{{devcomment|Could have a significant performance impact as editing may require continual resaving of all the .au files}} </ul>
 
  
* '''Better multi-threading/multi-processing support:''' {{votes|18}} to use full potential of Dual-Core/multi-processor machines when exporting/editing the audio. Use Lisp process delegation for multi-core processing and (harder) multi-threaded operation. (Think: divide and conquer, process pools that operate on portions of the waveform and joining the result, and you will arrive at a solution)
+
<div id="omf"></div>
** '''Better thread separation''' {{votes|9}} to allow safe execution of simultaneous tasks to improve workflow. It should be possible on a modern machine to do things like simultaneously record in separate projects; record in one project while editing or exporting from another etc.
+
* '''[https://en.wikipedia.org/wiki/Open_Media_Framework_Interchange Open Media Framework Interchange]''' {{votesdate|7|15Apr18}}
<ul>{{devcomment|'''LRN wrote:''' Multi-threading means two different things. 1: "Do two things simultaneously". This requires Audacity redesign to be more threaded. [https://en.wikipedia.org/wiki/OpenCL OpenCL] wouldn't help here. [http://manual.audacityteam.org/o/man/on_demand_loading.html On-Demand Loading] is an example of threaded design. 2: "Do one thing in two threads, which makes it go about two times faster". This requires special implementation and OpenCL would help. But it's not cost-effective to rewrite everything in
+
** Open Media Framework Interchange (OMFI) is a platform-independent file format intended for transfer of digital media between different software applications. Example: multi-track to/from Audition/ProTools/Cakewalk, etc.
[https://en.wikipedia.org/wiki/Symmetric_multiprocessing symmetric multi-processing] style. Only costly operations should be made parallel, everything else would benefit more from threaded design.}}</ul>
 
  
* '''Additions to AUP project file:'''
+
*Import/Export:
**'''Current View Mode of each track:''' {{votes|3}} "Default View Mode" in Tracks preferences will then affect only newly created tracks. View mode changes alone, like other view changes, may still not be sufficient to prompt for save of the project when closing.
+
** '''Speex'''.  Codec similar to Ogg Vorbis but optimized for voice. {{votes|11}}
** '''Window sizes and x/y positions:'''   {{votes|3}}
+
** '''WV''' WavPack {{votes|4}}
 +
** '''DSS''' {{votes|3}}
 +
** '''OFR''' files: (OptimFROG files, a lossless audio format that's smaller than FLAC).{{votesdate|2|24Nov17}}
 +
**'''MBWF''' (new multichannel extension for Broadcast WAV format) {{votes|2}}
 +
** '''MPC''' files (Windows) {{votes|2}}
 +
** '''DSD''' 1-bit Pulse Density Modulation (PDM) audio e.g. used in top-end portable recorders or for storage on SACD's. {{votes|2}}
 +
** [http://www.rowetel.com/?page_id=452 '''C2''' (Codec 2)] is an open source speech codec designed for communications quality speech between 700 and 3200 bit/s.{{votesdate|1|16Aug18}}
 +
** '''[http://www.cybercom.net/~dcoffin/rca/ RCA-VOC G.729a]''' compression codec for RCA Digital Voice Recorders {{votes|2}}
 +
** '''Aud-X (mp3 5.1)''' files  {{votes|1}}
 +
** '''[http://en.wikipedia.org/wiki/Internet_Low_Bit_Rate_Codec iLBC]''' as defined in RFC 3951. Free/Open Source. One of the codecs used by Google Talk, Yahoo! Messenger etc. Often wrapped in [http://en.wikipedia.org/wiki/Core_Audio_Format CAF] container {{votes|1}}
 +
:* '''Uncompressed FLAC''' {{votesdate|1|20Aug17}}
 +
{{devcomment|Although this option is supported by dBpoweramp, it offers no benefits over AIFF and may encourage belief in snake oil.}}
 +
** '''BIN''' sound files.{{votes|1}}
  
* '''Take advantage of unused GPU cycles:'''  Graphics processing units have the processing power to run 3D image but Audacity doesn't use hi-res 3D. This unused power could potentially be harnessed to speed up audio processing.  {{votes|4}}
 
** '''Use Nvidia's freeware [http://en.wikipedia.org/wiki/CUDA CUDA] parallel computing engine''' {{votes|1}}
 
  
* '''Improvements to audacity.cfg:'''
+
<div id="video"></div>
** '''Export and Import''' {{votes|1}}
+
* '''Import audio from video files/transport streams:''' such as AVI/MPEG/Ogg Theora e.g. by demuxing {{votes|14}}
*** '''Immediate application of changes like modifying xml files:''' {{votes|1}}
+
**Extracting Vorbis from multiplexed Ogg files should be an easy changeover.  Also note [http://wiki.xiph.org/MIME_Types_and_File_Extensions new specifications] on file names (e.g., <tt>.ogv</tt> for Ogg Video, <tt>.oga</tt> for Ogg Vorbis)
  
* '''64-bit version of Audacity for faster processing''' addressing more than 4 GB RAM and support for 64-bit plug-ins{{votes|15}}
+
* Ability to extract and import '''Vorbis portion of Ogg files''' encoded with non-audio tracks, such as Theora.  Currently gives an error "unknown format", straightforward modifications should do the trick.  {{votes|2}}
* '''Documentation more integrated with GUI:''' {{votes|6}}
 
** '''Links/buttons go to relevant help in the Manual''' {{votes|4}}
 
** '''Tooltips for extra help''' {{votes|3}}  
 
** '''Right-click context menu with list of all Wiki/docs entries'''
 
  
== Imports and Exports ==
+
===Other Import/Exports===
 +
<div id="multi-channel-import"></div>
 +
* '''Multi-channel import'''
 +
** Import multi-channel  files as all mono tracks {{votesdate|2|18Apr19}}
 +
:: Currently, the first two channels are one stereo track, which may be split to mono, but then the track numbering is incorrect.
 +
<div id="timestamp"></div>
 +
* '''Timestamp metadata'''
 +
**'''[http://cartchunk.org:8080/introduc.htm CART]''' metadata as used by radio stations There are several thousand users of Audacity who would find it convenient to have all the labeling of tracks done at the production stage rather then the 2 stages required now {{votes|4}}
 +
**'''Option to not write [https://code.google.com/archive/p/awesome-wav/wikis/WAVFormat.wiki PEAK] chunk''' or at least not write time in this chunk when exporting as 32/64 bit float WAV. {{votesdate|1|04Dec20}}
 +
*'''BWF:''' Support reading/exporting metadata, (including embedded timestamp information) in Broadcast WAV files ([http://en.wikipedia.org/wiki/Broadcast_Wave_Format BWF]) {{votesdate|43|09Oct19}}
 +
::See:
 +
:::* https://tech.ebu.ch/docs/tech/tech3285.pdf
 +
:::* http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/wave.htm
 +
:::* http://www.sonicspot.com/guide/wavefiles.html
 +
::* cue chunks {{votes|6}}
 +
::* smpl chunks {{votes|4}}
 +
::* levl chunk for quick waveform visualisation (new addition to BWF as per http://tech.ebu.ch/docs/tech/tech3285s3.pdf) {{votes|3}} 
 +
::* plst chunks {{votes|2}}
 +
::* Origination time {{votes|2}}
 +
::* One reason Audacity fails to support important metadata is that it does not support export of an [http://digitalcontentproducer.com/mag/video_aes_standard AES-31] compliant Audio Decision List (ADL)<ul><ul>{{devcomment|It's about priorities and to what extent mainline Audacity should support features the majority of users would not avail themselves of (even if they are "standards"). An equal case could be made for adding support for the [http://cartchunk.org:8080/introduc.htm CART] metadata chunk required by radio stations.}}</ul></ul>
 +
<ul><ul><ul><li> Timestamp metadata is e55ssential for working on projects of longer duration (interviews, news gathering, live recording, podcasts, etc). There are dozens of digital recorders that support BWF timestamp metadata. Leaving such features out of Audacity effectively excludes a large potential audience from using Audacity.</li>
 +
<li>As a workaround, I have just written a [[Importing Timestamp Information|python program]] that reads the WAV file in BWF format produced by the M-Audio Microtrack recorder, and generates a text file that can be imported as a label track into Audacity via Tracks > Edit Labels.(The hardest part was to search for the information on WAV chunk formats.[[User:Guenterrote|Guenterrote]] 21:53, 9 March 2010 (CST)
 +
<li>Also for recording directly with Audacity this feature would be helpful. In the [http://wiki.librivox.org/index.php/Alternative_Editing_Method Librivox wiki] they recommend to click (with tongue or so) after each error so you can find back easily these "auditive markers" while editing. This idea is very handy, but clumsy. Better would be that you could press a key which then sets a marker on the soundtrack.</ul>
 +
{{devcomment|If you have a finger free to press a key (or a foot if you have a foot pedal that delivers mouse clicks) then just change the Audacity shortcut for "Add Label at Playback Position" to some key that's easy to hit The comment is only relevant if you want to export an audio file with embedded markers.}} </li></ul></ul>
  
{{Hint|There are some file formats and effect interfaces we can't support for commercial reasons. Please check our [[Features We Can't Implement]] page before adding features to the list below.}}
+
* '''Read/write embedded cue points in WAV files''' like CoolEdit {{votes|5}} 
 +
** and let them contain information from Audacity labels {{votes|1}}
 +
** and have them act as snap points (e.g. marking bar or beat boundaries on rhythm samples) {{votes|1}}
 +
* '''Read/write embedded loop points in WAV files''' like Wavosaur. {{votes|3}}
 +
* '''Export File window:'''
 +
** New checkbox “Export at current Play-at-speed". {{votes|2}} by Penguin on 19 July 2008
 +
** '''Timestamp button''' to add a string for current system date/time in the file name {{votes|2}}
 +
* '''Templated Command Line Export:''' Add variables to the Command Line Export Options that reference the contents of the various Metadata fields. These would be similar to the %f variable for Filename already available, allowing totally automated export of files to applications that support writing Metadata to files/understand the variables being passed.  {{votes|3}}
 +
{{devcomment|Until then, a workaround to get the metadata exported when using the command line would be to disable Metadata Editor in Preferences and enter the metadata in the command line options using the relevant tag switches (for example in MP3s with LAME, --tt <title>) as described on the [http://lame.cvs.sourceforge.net/*checkout*/lame/lame/USAGE LAME usage page]}}
 +
* '''Command line presets''' in an .ini or .xml file rather than retype over for different formats. {{votes|1}}
 +
* '''Command line pipes:''' For example [sox -t wav - -r 44100 -t wav - polyphase | lame -V6 --vbr-new - "%f"]  
 +
* '''Set sample rate for export in export options:''' {{votes|5}}
 +
** Default could be the project rate, but if a single track is exported and has a different rate, use that rate.
 +
* '''Set bit rate for export options for all formats:''' {{votes|1}}
 +
{{devcomment|Bitrate would be very confusing for most users where WAV/AIFF are concerned - it's (<bit format> * <number of channels> * <sample rate>) so 1411 kbps for a stereo, 16 bit 44100 Hz sample rate WAV.}}
 +
* '''Invalid sample rate dialog:''' Add checkbox "Apply this rate to any remaining conflicts" (checkbox state is stored in .cfg) and/or add checkbox linked to Warnings Preferences "Don't warn again and always use highest rate". {{votes|7}}  
  
===New Import/Export Formats===
+
* '''Easier file selection:'''
 +
** Allow multiple import from different directories by specifying in a list box {{votes|1}} 
  
<div id="soundtrack"></div>
+
* '''Automatic snap-to CDDA boundaries when exporting multiple with labels:''' Avoids small gaps when burning CDs, saves changing selection format and turning snap-to on manually. The FLAC encode actually has an option to do this. {{votes|2}}
*'''Import/play video for synchronized soundtrack editing''' {{votes|44}} No need for Audacity to edit the video. Alternatively, Audacity could send/receive SMPTE or MTC timecode data e.g. to VLC or mplayer.
 
** '''Standalone SMPTE reader useful in own right''' {{votes|1}} e.g. for reading time track on an analog tape deck.  
 
** '''Existing Timeline must show audio behind zero''' {{votes|1}}
 
** '''Video window should have video timeline''' but Audacity window should not need separate video timeline {{votes|1}}  
 
  
<div id="importappended"></div>
+
* '''Import/Export of envelope points:''' as XML file {{votes|4}}  
* '''Import Appended:''' {{votes|39}} Import multiple files end-to-end in a single track. Would allow re-assembly/re-processing of LP/tape recordings for which no Audacity project exists. Also allows to import multiple tracks for CD assembly <p>Possible Enhancements:</p>
 
** with labels containing their file names
 
<ul>{{devcomment|1=If not labeled, it will be important for many use cases that the imported files remain as separate audio clips.}}</ul>
 
<ul><ul><li> ability to import the multiple files (or even a single file) at cursor position</ul>
 
{{devcomment|1=You can always Project > Import Audio and SHIFT + click or CTRL + click to select and import multiple files into a project as separate tracks. There is no automated process beyond that. No players can read the labels in the joined track other than Audacity - they aren't bookmarks in that sense, as there is no agreed standard for reading divisions within files. The labels can be exported to form the basis of a cue sheet.<p>A [http://forum.audacityteam.org/viewtopic.php?f=42&t=59528 Nyquist plug-in] is available to test which can import multiple WAV or AIFF files end-to-end from a directory or from a list of files, starting from either time zero or from the cursor position.</p>}}
 
<ul><li>'''Import new track at cursor position simpler/more important''' {{votes|3}}</ul></ul>
 
  
 +
* '''Label Export'''
 +
** '''Include project name in exported file name:'''  for example: projectname_labels.txt {{votes|2}}
 +
** '''XML/SMIL Label Export''' for using Audacity to analyze interviews or to generate Audio-Picture-Slideshows e.g. for educational use). Nodes: "trackname" with Nodes "start, end, label" or using [http://www.w3.org/AudioVideo/ SMIL]. {{votes|3}}
 +
** '''ODF Label Export''' with the timecode of each label in an ODF document. {{votes|1}} <ul>{{devcomment|[[User:James|James]]: We already have CSV.  Already easy to get ODF.}}</ul>
  
*Import/Export:
+
* '''Import/Export playlist file like M3U/PLS'''. Playlist is 'converted' to a track with separate clips, each clip being loaded from the specified file {{votes|2}} {{devcomment|You can as a workround edit playlist files into a .lof "list of files" format as per instructions [[How to import playlists|here]]. Audacity will then import the listed files, albeit into separate tracks}}
** '''Speex'''.  Codec similar to Ogg Vorbis but optimized for voice. {{votes|11}}
+
* '''Hierarchical Projects''' Importing a project into another project: Could highly facilitate the development of big projects, because one can maintain the different parts separated {{votes|2}}
**'''Native [http://en.wikipedia.org/wiki/Opus_%28audio_format%29 Ogg Opus] support:''' {{votes|19}} - replaces Speex
 
*** Support Opus info {{votes|1}} - diagnostic tool giving technical information about the Opus file.  
 
** '''OMF''' multi-track to/from ProTools/Cakewalk, etc. {{votes|5}}
 
** '''Aud-X (mp3 5.1)''' files  {{votes|1}}
 
**'''MBWF''' (new multichannel extension for Broadcast WAV format) {{votes|2}}
 
** '''MPC''' files (Windows) {{votes|2}}
 
** '''DSS''' {{votes|3}}
 
** '''OFR''' files: (OptimFROG files, a lossless audio format that's smaller than FLAC).
 
** '''DSD''' 1-bit Pulse Density Modulation (PDM) audio e.g. used in top-end portable recorders or for storage on SACD's. {{votes|2}}
 
** '''[http://www.cybercom.net/~dcoffin/rca/ RCA-VOC G.729a]''' compression codec for RCA Digital Voice Recorders {{votes|2}}
 
** '''BIN''' sound files.
 
** '''WV''' WavPack {{votes|4}}
 
** '''[http://en.wikipedia.org/wiki/Internet_Low_Bit_Rate_Codec iLBC]''' as defined in RFC 3951. Free/Open Source. One of the codecs used by Google Talk, Yahoo! Messenger etc. Often wrapped in [http://en.wikipedia.org/wiki/Core_Audio_Format CAF] container {{votes|1}}
 
** '''[[QuickTime]]'''  files on Windows/Mac {{votes|6}} <ul>{{devcomment|Support for importing QuickTime based formats has been reintroduced in 1.3.3 for users on OS X}}</ul>
 
  
<div id="video"></div>
+
<ul> '''Metadata tags:'''
* '''Import audio from video files/transport streams:''' such as AVI/MPEG/Ogg Theora e.g. by demuxing {{votes|14}}
+
<ul id="per_track_meta"><li>'''Separate tags for each imported file''' not have Metadata Editor take the tags from the last imported file {{votesdate|20|14May17}}  </ul>
**Extracting Vorbis from multiplexed Ogg files should be an easy changeoverAlso note [http://wiki.xiph.org/MIME_Types_and_File_Extensions new specifications] on file names (e.g., <tt>.ogv</tt> for Ogg Video, <tt>.oga</tt> for Ogg Vorbis)
+
{{devcomment|Separate metadata for each file can be achieved by using File > Open... to import each file into a separate project, or by using a [https://manual.audacityteam.org/man/chains_for_batch_processing_and_effects_automation.html Chain] applied to files. The requested feature needs much thought to be intuitive, given Audacity is a multi-track editor and can move audio data between tracks or mix tracks together. }}   
 +
<ul><li> '''Track Number tag should have two fields "n" of "nn"''' (for example, 3 of 12) {{votes|1}} 
 +
<div id="albumart"></div>
 +
<li> '''Support lyrics and album art in metadata tags''' where the format supports this, so that you can add these, or at the least so that these are not discarded when you import and export the file {{votesdate|62|28Nov20}} 
 +
<li> '''Support ID3v1:''' {{votes|6}}. Some MP3 players and specialised software or hardware require it e.g. BWF WidgetPro and some hard disc recorders can only identify MP3 timecode in ID3V1.
 +
<li> '''CR/LF in metadata:''' {{votes|1}} a way to enter Carriage Returns/Line feeds into the 'Comments Tag' field in the Metadata Editor. Audacity now truncates pasted text at the first CR/LF but more advanced tag editors support multi-line comments. Could be handled by a single-line edit box with "expansion" button. The single-line edit box displays the multi-line data without breaks; clicking the "expansion" button opens a new dialog with a multiline editor.  
 +
<li> '''Connect to MySQL metadata database:''' {{votes|1}} so can select a song from the database and "push a button" to fill in the data for a recording in Audacity.
 +
<li> '''Support common ID3 tags that are not included in Audacity defaults, such as "Album Artist" (TPE2), "Composer" (TCOM) and "BPM" (TBPM)''' {{votes|13}} rather than write them as user-specified TXXX tags that some tag editors cannot see ( [https://bugzilla.audacityteam.org/show_bug.cgi?id=541 Bug 541]).  
 +
<li> '''Support FMPS:''' [https://gitorious.org/xdg-specs/xdg-specs/trees/master/specifications/FMPSpecs?p=xdg-specs:xdg-specs.git;a=tree;f=specifications/FMPSpecs;hb=HEAD Free Media Player Specifications] {{votesdate|1|18Nov19}}
 +
<ul><li>Sufficient to only add "FMPS_RATING". {{votesdate|1|22Jan19}}
 +
</ul></ul>
  
* Ability to extract and import '''Vorbis portion of Ogg files''' encoded with non-audio tracks, such as Theora. Currently gives an error "unknown format", straightforward modifications should do the trick. {{votes|2}}
+
<ul><li> '''Import RAW data:'''
 +
<ul><li> '''Save and load Presets''' {{votes|6}}
 +
<li> '''Remove hardcoding to maximum 100000 Hz''' {{votes|12}}  as per [https://bugzilla.audacityteam.org/show_bug.cgi?id=192 bug 192]
 +
<li> '''Remove hardcoding to maximum 16 channels''' {{votes|4}}
 +
<li> '''Command line options''' specifying channels, format, rate, etc. {{votesdate|2|06Feb18}}
 +
<li>'''Parse file names or extensions:'''  {{votes|2}} for example "audio_16b_44100Hz_6c" or similar pre-fills the dialog</ul>
 +
{{devcomment|1=There is a [https://bugzilla.audacityteam.org/show_bug.cgi?id=145 patch] submitted which automatically imports U-Law files as mono 8000 Hz via Import > Raw data based on their .ulaw file extension.}}
 +
<ul><li>'''Link or button to open Import Raw from Error importing dialog''' when error suggests using raw import {{votes|3}}
 +
<li>'''Option to disable format guessing and use last used setting''' saved in audacity.cfg {{votesdate|6|10Mar20}}   
 +
<li>'''Retain format guessing but remember sample rate across sessions''' {{votes|2}}</ul>
 +
<li>'''Import/Export Project to Advanced Authoring Format (AAF)''': Or use AFF instead of .aup.  Makes Audacity projects compatible with many other audio (and video) editing applications. AAF supersedes OMF. See [http://en.wikipedia.org/wiki/Advanced_Authoring_Format AAF on Wikipedia] and [http://sourceforge.net/projects/aaf/ AAF framework on SF].
 +
<ul><li> '''Keep import/export libraries up-to-date:''' {{votes|2}} for example libogg is several years out of date as at July 2010
 +
<li>'''Default MP3 export setting halves the bit-rate if the track is mono:''' {{votes|15}} When you invoke LAME from the command-line using the default command without parameters, it detects if the track is mono and produces a 64 kbps file (as opposed to producing a 128 kbps file if the track is stereo). With Audacity GUI MP3 export, the default export to MP3 always produces a 128 kbps file even if the track is mono.
 +
{{devcomment|1=When you invoke LAME from the command-line using the -b option then the specified bit rate applies. In Audacity's MP3 export GUI, the bit rate is always specified for CBR (and ABR) and is applied just as for command line export. What Audacity does not have is an option to leave the bit rate unspecified.}}
 +
<li>'''MP3 export option to use default LAME sample rate for the bit rate''' rather than use the Audacity project rate {{votes|1}}. Use case: import 44100 Hz MP3, export as 32 kbps MP3. Using -b 32 in (external program) export sets output sample rate to 22050 Hz (for mono) and often produces a better sounding file than leaving project rate at 44100 Hz.
 +
<li> '''Allow use of pre-existing system libraries:''' for example [http://ffdshow-tryout.sourceforge.net/ ffdshow tryout] on Windows instead of both LAME and FFmpeg.
  
===Other Import/Exports===
+
{{devcomment|[[User:Galeandrews|Gale]] There is no way to do that now, except by Custom FFmepg export or command-line export. The reason I disagree with the suggestion is that there would be no way to force an extension other than the allowed ones for the format. To workaround it, add the intended extension manually (for example, "dot.com.mp3"), then there will be no warning.}}
<div id="timestamp"></div>
+
{{devcomment|[[User:Bertyhell|Bertyhell]] I see your point but i disagree. what do you think about this: when you want no extension you choose "all files" from the extension menu, when you already have a point, check if its 3 or less chars behind the point and not only numbers, then you don't have to add extension, else you autoadd.}} 
* '''Timestamp metadata'''
+
{{devcomment|[[User:Galeandrews|Gale]] "All files" would not let you specify the format unless there was a huge dialog behind the "Options" button. Your rule would still not let me write "dot.com" to export "dot.com.mp3". There are 3 cases 1) force no extension 2) force non-standard extension 3) add format-appropriate extension even if file name has dot. I suppose 1) and 2) could be covered by a "Verbatim" checkbox which then never produces a warning and 3) by an "Always add extension" checkbox. I don't think any single rule will cover all cases. What does someone typing "music.mpg" want to produce - "music.mpg" or music.mpg.mp3"?}}  
**'''[http://cartchunk.org:8080/introduc.htm CART]''' metadata as used by radio stations There are several thousand users of Audacity who would find it convenient to have all the labeling of tracks done at the production stage rather then the 2 stages required now {{votes|4}}
+
<li>'''Keep FFmpeg dynamic library support updated to latest FFmpeg:''' {{votes|3}}
**'''BWF:''' Support reading/exporting embedded timestamp information in Broadcast WAV files ([http://en.wikipedia.org/wiki/Broadcast_Wave_Format BWF]) {{votes|42}} See http://www.blitter.com/~russtopia/MIDI/~jglatt/tech/wave.htm and http://www.sonicspot.com/guide/wavefiles.html for general information 
+
<li> '''Add 'Honour solo state' checkboxes to the 'Export' and 'Export Multiple' dialog boxes:''' {{votes|1}} There's [http://audacity.238276.n2.nabble.com/behaviour-of-mute-and-solo-td2414351.html#none some disagreement and user confusion] over whether the 'solo' buttons should affect exports.  Adding this option to the export dialogs will (a) allow the users to select the behaviour they prefer, (b) inform them
*** cue chunks {{votes|6}}
+
the the default behaviour doesn't honour the solo state, and (c) reassure them that this isn't a bug.
*** smpl chunks {{votes|4}}
+
<li> '''Handle channel-position count data from imported files when exporting:''' {{votes|1}} Currently FLAC export leaves the number of reported positions unchanged even when removing channels before export, and WAV export (either with libsndfile or FFmpeg) removes the position count completely.   See https://bugzilla.audacityteam.org/show_bug.cgi?id=1589.
*** levl chunk for quick waveform visualisation (new addition to BWF as per http://tech.ebu.ch/docs/tech/tech3285s3.pdf) {{votes|3}}
+
<li> '''Allow export selected audio and/or Export Multiple to name files with start and length (or end) of the selection''' {{votesdate|1|02May17}}. See [https://forum.audacityteam.org/viewtopic.php?p=321925#p321925 this archived Forum response] for a script that can be run in Nyquist Prompt to label the selections with the requested information.  
*** plst chunks {{votes|2}}
+
</ul>
*** Origination time {{votes|2}}
+
* '''Need longer file names:''' I would like for Audacity to be able to use long (up to 255 characters) file names
*** One reason Audacity fails to support important metadata is that it does not support export of an [http://digitalcontentproducer.com/mag/video_aes_standard AES-31] compliant Audio Decision List (ADL)<ul><ul>{{devcomment|It's about priorities and to what extent mainline Audacity should support features the majority of users would not avail themselves of (even if they are "standards"). An equal case could be made for adding support for the [http://cartchunk.org:8080/introduc.htm CART] metadata chunk required by radio stations.}}</ul></ul>
+
without adding in its own arbitrary codes. I also checked it on a file name that
<ul><ul><ul><li> Timestamp metadata is essential for working on projects of longer duration (interviews, news gathering, live recording, podcasts, etc). There are dozens of digital recorders that support BWF timestamp metadata. Leaving such features out of Audacity effectively excludes a large potential audience from using Audacity.</li>
+
doesn't contain parenthesis, and the same problem still occurs.  I start up Audacity and it has a blank project window. Then I import my first audio.  file. The name of the input file is "RAH 08 Out On the Edge (itunes)".  However, once it's done importing, both the project window and the tracks
<li>As a workaround, I have just written a [[Importing Timestamp Information|python program]] that reads the WAV file in BWF format produced by the M-Audio Microtrack recorder, and generates a text file that can be imported as a label track into Audacity via Tracks > Edit Labels.(The hardest part was to search for the information on WAV chunk formats.[[User:Guenterrote|Guenterrote]] 21:53, 9 March 2010 (CST)
+
within it are named something like "RAH 08 Out On the Ed#4330D7"Currently using Audacity 1.2.5 on Mac OS X (10.4), with Intel processor.
<li>Also for recording directly with Audacity this feature would be helpful. In the [http://wiki.librivox.org/index.php/Alternative_Editing_Method Librivox wiki] they recommend to click (with tongue or so) after each error so you can find back easily these "auditive markers" while editing. This idea is very handy, but clumsy. Better would be that you could press a key which then sets a marker on the soundtrack.</ul>
 
{{devcomment|If you have a finger free to press a key (or a foot if you have a foot pedal that delivers mouse clicks) then just change the Audacity shortcut for "Add Label at Playback Position" to some key that's easy to hit The comment is only relevant if you want to export an audio file with embedded markers.}} </li></ul></ul>
 
<div id="autoextension"></div>
 
* '''Provide way to automatically add extension for chosen export format after file name when file name contains a dot:''' {{votes|22}} Audacity adds the chosen extension when there is no dot in the file name, but if you add a dot as part of the file name, it prompts if you want to save as the file name typed in.  - [[User:Bertyhell|Bertyhell]]
 
{{devcomment|[[User:James|James]] If we did this there would be no way for a user to save the file without an extensionSome users may want to do that.}}
 
  
* '''Quick Export:''' the essential feature is that the Export button saves the file - no dialogs, questions, or clicks after that. Paths/file names/formats are configured beforehand, probably in Preferences (these could include to use the path/file name the original file comes from, or a fixed location) {{votes|8}}
+
*'''Option to select/de-select dither on export:''' Usually it is best to have dither enabled for high quality resampling, but in some situations it is preferable to disable dither. Having to go into Preferences to disable dither, and then go back into Preferences again to re-enable it (and remembering to do so as there is no visual indication in Audacity other than in Preferences whether dither is enabled or not) is very inconvenient. {{votes|2}}
** This feature is especially useful if combined with the request below for a timestamp included in the file name, especially for wildlife recording where you want to make frequent short recordings without having to divert too much time or attention from the actual subject.
 
**[[User:Edgar|Edgar]] I put code on the forum which stores the Import directory and uses that to seed the Export dialog: [http://forum.audacityteam.org/viewtopic.php?f=20&t=53568 forum topic]
 
<ul>{{devcomment|See [[Proposal Menu Reorganisation#File Menu|Proposal Menu Reorganisation]] for some ideas that are being discussed for project save and file export. There are also some [[#pref|votes]] to have preferences for file name and/or path, but still having to go through a file save window to give the ability to change format on the fly.}}</ul>
 
  
* '''Read/write embedded cue points in WAV files''' like CoolEdit {{votes|5}} 
+
==Interface Modifications==
** and let them contain information from Audacity labels {{votes|1}}
 
** and have them act as snap points (e.g. marking bar or beat boundaries on rhythm samples) {{votes|1}}
 
* '''Read/write embedded loop points in WAV files''' like Wavosaur. {{votes|3}}
 
* '''Export File window:'''
 
** '''Checkbox here and in Export Multiple window for exporting leading white space as silence''' {{votes|14}}. Could be a preference or a render option rather than only export. See also http://forum.audacityteam.org/viewtopic.php?f=20&t=80408.
 
** New checkbox “Export at current Play-at-speed". {{votes|2}} by Penguin on 19 July 2008
 
** (2.x) '''Options too undiscoverable/hard to remember/fiddly to access''' {{votes|11}} Ideas:
 
*** Dynamic text shows current settings for those formats with options {{votes|3}}
 
*** Tooltip {{votes|3}}
 
*** Fly-out dialog when you select the format {{votes|2}}
 
*** Go back to individual <export format> items in File menu {{votes|3}} 
 
** '''Timestamp button''' to add a string for current system date/time in the file name {{votes|2}}
 
* '''Templated Command Line Export:''' Add variables to the Command Line Export Options that reference the contents of the various Metadata fields. These would be similar to the %f variable for Filename already available, allowing totally automated export of files to applications that support writing Metadata to files/understand the variables being passed.  {{votes|3}}
 
{{devcomment|Until then, a workaround to get the metadata exported when using the command line would be to disable Metadata Editor in Preferences and enter the metadata in the command line options using the relevant tag switches (for example in MP3s with LAME, --tt <title>) as described on the [http://lame.cvs.sourceforge.net/*checkout*/lame/lame/USAGE LAME usage page]}}
 
*  '''Cross-platform project files''' - somebody on Mac got burned by being given Audacity Project files from a PC. Audacity doesn't warn you that you should export WAV instead and there’s nothing in the instructions.
 
{{devcomment|Projects saved by Audacity 1.2.2 and later are cross-platform, but you have to supply the other user with the _data folder as well. See [http://manual.audacityteam.org/o/man/sending_your_work_to_others.html Sending your work to others].}}
 
* '''Command line presets''' in an .ini or .xml file rather than retype over for different formats. {{votes|1}}
 
* '''Command line pipes:''' For example [sox -t wav - -r 44100 -t wav - polyphase | lame -V6 --vbr-new - "%f"]
 
* '''VBR as Default:''' Export MP3 should use by default variable bitrate to efficiently allow best quality, probably also with a low-pass filter enabled. It appears to me the available bitranges are still too narrow in the current (1.3.4) version. Please see {{external|http://jthz.com/mp3}}  {{votes|1}} {{devcomment|The MP3 export options dialog does have to balance offering more advanced options with being usable by the majority of users. All you need to do if you want more exotic options such as those allowing the exported VBR MP3 to contain a wider range of bitrates, is to put LAME.exe in the Audacity installation folder then select "external program" instead of "MP3 files". Then enter your command string. For example, for the highest quality command  that page suggests, you'd enter:<br>lame -V1 --vbr-new -b112 --lowpass 21 -q0 - "%f"'' }}
 
* '''Set sample rate for export in export options:''' {{votes|5}}
 
** Default could be the project rate, but if a single track is exported and has a different rate, use that rate.
 
* '''Set bit rate for export options for all formats:''' {{votes|1}}
 
{{devcomment|Bitrate would be very confusing for most users where WAV/AIFF are concerned - it's (<bit format> * <number of channels> * <sample rate>) so 1411 kbps for a stereo, 16 bit 44100 Hz sample rate WAV.}}
 
* '''Invalid sample rate dialog:''' Add checkbox "Apply this rate to any remaining conflicts" (checkbox state is stored in .cfg) and/or add checkbox linked to Warnings Preferences "Don't warn again and always use highest rate". {{votes|7}}   
 
  
* '''Easier file selection:'''
+
{{Hint|In some cases requests for modifications are differences in user preferences, and are best entered as a request for a modification to [[#pref|Preferences]].}}
** Allow multiple import from different directories by specifying in a list box {{votes|1}}
 
  
* '''Automatic snap-to CDDA boundaries when exporting multiple with labels:''' Avoids small gaps when burning CDs, saves changing selection format and turning snap-to on manually. The FLAC encode actually has an option to do this. {{votes|2}}
+
<div id="monitoring"></div>
 +
* '''Preference for monitoring on by default''' {{votesdate|23|10Sep21}}
 +
** See [[Proposal Monitoring On]]
 +
{{devcomment|We initially didn't do this because of concerns about performance on lower powered machines.  We've since had feedback on this that is works fine and that not having monitoring "on" is causing a bigger problem - especially with new users. This however is not such an easy change as it appears - handling the situation when a device is changed/swapped out for example but Audacity is still looking for an input to read - it may not be fixed quickly}}
 +
 
 +
 
 +
===New/Modified Toolbars or Menus ===
  
* '''Import/Export of envelope points:''' as XML file {{votes|4}}  
+
* '''Customizable Toolbar:''' {{votes|7}} add/remove/move items from/between toolbars (similar to customising the toolbars in Firefox) and create a personal toolbar with just the icons you use heavily yourself (then you can hide all the other toolbars to save space)
 +
** '''Customizable Menus:''' add/remove/move items from/between menus {{votes|1}}
  
* '''Label Export'''
+
* '''Lock Toolbars:''' {{votesdate|3|04Mar21}} prevent accidental moving of toolbars by locking the layout. Unlock the toolbars to customize the layout. See also: [[Proposal:_GUI_Custom_Resets_for_Toolbar_Layouts|Proposal: GUI Custom Resets for Toolbar]]
** '''Include name of label track''' in the file fields so this displays in the label name upon import {{votes|3}}  
 
** '''Include project name in exported file name:'''  for example: projectname_labels.txt {{votes|2}}
 
** '''XML/SMIL Label Export''' for using Audacity to analyze interviews or to generate Audio-Picture-Slideshows e.g. for educational use). Nodes: "trackname" with Nodes "start, end, label" or using [http://www.w3.org/AudioVideo/ SMIL]. {{votes|3}}
 
** '''ODF Label Export''' with the timecode of each label in an ODF document. {{votes|1}} <ul>{{devcomment|[[User:James|James]]: We already have CSV.  Already easy to get ODF.}}</ul>
 
  
* '''Import/Export playlist file like M3U/PLS'''.  Playlist is 'converted' to a track with separate clips, each clip being loaded from the specified file {{votes|2}} {{devcomment|You can as a workround edit playlist files into a .lof "list of files" format as per instructions [[How to import playlists|here]]. Audacity will then import the listed files, albeit into separate tracks}}
+
* '''Ribbon toolbars''' or dropdown icons to help declutter the GUI {{votes|3}}
* '''Hierarchical Projects''' Importing a project into another project:  Could highly facilitate the development of big projects, because one can maintain the different parts separated {{votes|2}}
 
  
* '''Metadata tags:'''
+
* '''Effects Toolbar''' {{votes|9}} Should be able to be dragged to any area of the screen and dockable. Organize the visible buttons, organise the Effect menu and create favorites list.  
** '''Separate tags for each imported file''' not have Metadata Editor take the tags from the last imported file {{votes|16}}
 
<ul>{{devcomment|Separate metadata for each file can be achieved by using File > Open... to import each file into a separate project, or by using a [http://manual.audacityteam.org/man/chains_for_batch_processing_and_effects_automation.html Chain] applied to files. The requested feature needs much thought to be intuitive, given Audacity is a multi-track editor and can move audio data between tracks or mix tracks together. }}   
 
<ul><li> '''Track Number tag should have two fields "n" of "nn"''' (for example, 3 of 12) {{votes|1}} 
 
<div id="albumart"></div>
 
<li> '''Support lyrics and album art in metadata tags''' where the format supports this, so that you can add these, or at the least so that these are not discarded when you import and export the file {{votes|52}} 
 
<li> '''Support ID3v1:''' {{votes|6}}. Some MP3 players and specialised software or hardware require it e.g. BWF WidgetPro and some hard disc recorders can only identify MP3 timecode in ID3V1.
 
<li> '''CR/LF in metadata:''' {{votes|1}} a way to enter Carriage Returns/Line feeds into the 'Comments Tag' field in the Metadata Editor. Audacity now truncates pasted text at the first CR/LF but more advanced tag editors support multi-line comments. Could be handled by a single-line edit box with "expansion" button. The single-line edit box displays the multi-line data without breaks; clicking the "expansion" button opens a new dialog with a multiline editor.
 
<li> '''Connect to MySQL metadata database:''' {{votes|1}} so can select a song from the database and "push a button" to fill in the data for a recording in Audacity.
 
<li> '''Support common ID3 tags that are not included in Audacity defaults, such as "Album Artist" (TPE2), "Composer" (TCOM) and  "BPM" (TBPM)''' {{votes|13}} rather than write them as user-specified TXXX tags that some tag editors cannot see ( [http://bugzilla.audacityteam.org/show_bug.cgi?id=541 Bug 541]). </ul></ul>
 
  
<ul><li> '''Import RAW data:'''
+
* '''Repair Toolbar''' {{votes|1}} containing (left to right) Zoom In/Repair/Zoom Out buttons. Both Zoom buttons zoom by (say) factor of 10 if Control key depressed. Breaks monotony of using the keyboard all the time and holding and releasing the mouse to highlight the repair area.
<ul><li> '''Save and load Presets''' {{votes|6}}
 
<li> '''Remove hardcoding to maximum 100000 Hz''' {{votes|12}}  as per [http://bugzilla.audacityteam.org/show_bug.cgi?id=192 bug 192]
 
<li> '''Remove hardcoding to maximum 16 channels''' {{votes|4}}
 
<li>'''Parse file names or extensions:'''  {{votes|2}} for example "audio_16b_44100Hz_6c" or similar pre-fills the dialog</ul>
 
{{devcomment|1=There is a [http://bugzilla.audacityteam.org/show_bug.cgi?id=145 patch] submitted which automatically imports U-Law files as mono 8000 Hz via Import > Raw data based on their .ulaw file extension.}}  
 
<ul><li>'''Link or button to open Import Raw from Error importing dialog''' when error suggests using raw import {{votes|3}}
 
<li>'''Option to disable format guessing and use last used setting''' saved in audacity.cfg {{votes|4}}   
 
<li>'''Retain format guessing but remember sample rate across sessions''' {{votes|2}}</ul>
 
<li>'''Import/Export Project to Advanced Authoring Format (AAF)''': Or use AFF instead of .aup.  Makes Audacity projects compatible with many other audio (and video) editing applications. AAF supersedes OMF. See [http://en.wikipedia.org/wiki/Advanced_Authoring_Format AAF on Wikipedia] and [http://sourceforge.net/projects/aaf/ AAF framework on SF].
 
<li> '''Easier Lame:''' Rewrite the Lame selection panel so non-techies can understand it. </ul>{{devcomment|We now have an .exe LAME installer for Windows users. Just download and run it.}}
 
<ul><li> '''Keep import/export libraries up-to-date:''' {{votes|2}} for example libogg is several years out of date as at July 2010
 
<li>'''Default MP3 export setting halves the bit-rate if the track is mono:''' {{votes|15}} When you invoke LAME from the command-line using the default command without parameters, it detects if the track is mono and produces a 64 kbps file (as opposed to producing a 128 kbps file if the track is stereo). With Audacity GUI MP3 export, the default export to MP3 always produces a 128 kbps file even if the track is mono.
 
{{devcomment|1=When you invoke LAME from the command-line using the -b option then the specified bit rate applies. In Audacity's MP3 export GUI, the bit rate is always specified for CBR (and ABR) and is applied just as for command line export. What Audacity does not have is an option to leave the bit rate unspecified.}}
 
<li>'''MP3 export option to use default LAME sample rate for the bit rate''' rather than use the Audacity project rate {{votes|1}}. Use case: import 44100 Hz MP3, export as 32 kbps MP3. Using -b 32 in (external program) export sets output sample rate to 22050 Hz (for mono) and often produces a better sounding file than leaving project rate at 44100 Hz.
 
<li> '''Allow use of pre-existing system libraries:''' for example [http://ffdshow-tryout.sourceforge.net/ ffdshow tryout] on Windows instead of both LAME and FFmpeg.
 
  
{{devcomment|[[User:Galeandrews|Gale]] There is no way to do that now, except by Custom FFmepg export or command-line export. The reason I disagree with the suggestion is that there would be no way to force an extension other than the allowed ones for the format. To workaround it, add the intended extension manually (for example, "dot.com.mp3"), then there will be no warning.}}
+
* '''Global "hide/show toolbars" switch''' {{votes|1}} retains the same toolbar positions when unhid - preferably keyboard accessible too.
{{devcomment|[[User:Bertyhell|Bertyhell]] I see your point but i disagree. what do you think about this: when you want no extension you choose "all files" from the extension menu, when you already have a point, check if its 3 or less chars behind the point and not only numbers, then you don't have to add extension, else you autoadd.}} 
 
{{devcomment|[[User:Galeandrews|Gale]] "All files" would not let you specify the format unless there was a huge dialog behind the "Options" button. Your rule would still not let me write "dot.com" to export "dot.com.mp3". There are 3 cases 1) force no extension 2) force non-standard extension 3) add format-appropriate extension even if file name has dot. I suppose 1) and 2) could be covered by a "Verbatim" checkbox which then never produces a warning and 3) by an "Always add extension" checkbox. I don't think any single rule will cover all cases. What does someone typing "music.mpg" want to produce - "music.mpg" or music.mpg.mp3"?}}   
 
<li> '''Use FFmpeg for MP3 export''' so that maximum external libraries to install is one {{votes|4}} 
 
<li>'''Keep FFmpeg dynamic library support updated to latest FFmpeg:''' {{votes|3}}
 
<li> '''Add 'Honour solo state' checkboxes to the 'Export' and 'Export Multiple' dialog boxes:''' {{votes|1}} There's [http://audacity.238276.n2.nabble.com/behaviour-of-mute-and-solo-td2414351.html#none some disagreement and user confusion] over whether the 'solo' buttons should affect exports.  Adding this option to the export dialogs will (a) allow the users to select the behaviour they prefer, (b) inform them the the default behaviour doesn't honour the solo state, and (c) reassure them that this isn't a bug.
 
</ul>
 
  
==Interface Modifications==
+
* (macOS) '''When applying a shortcut for a command that is in the menus, make that root menu item flash in the menu bar, like Apple apps do.'''  {{votes|1}}
 +
{{devcomment|FileZilla which uses a slightly later version of wxWidgets (3.0.3) than we do (3.0.2) shows this flash, so possibly Audacity might show that too when we upgrade wxWidgets again.}}
  
{{Hint|In some cases requests for modifications are differences in user preferences, and are best entered as a request for a modification to [[#pref|Preferences]].}}
+
* '''Analyze Menu:'''
 +
** '''Real-time Tuner:''' like Tuning Fork in [http://en.wikipedia.org/wiki/GarageBand GarageBand]  {{votes|1}}
 +
<ul>{{devcomment|See [[Instrument tuners|here]] for some free instrument tuner applications and a possible method to tune instruments in Audacity using a pre-recorded track and [https://manual.audacityteam.org/o/man/plot_spectrum.html Plot Spectrum].}}</ul>
 +
<ul><ul><li> '''Repeat last used analyzer:''' {{votesdate|7|05Jan21}}  Like "Repeat <effect> CTRL + R" but for Analyzers.
 +
<ul><li> '''Allow users to give it a keyboard shortcut so that it is separate from CTRL + R.''' {{votesdate|1|07Mar17}} </ul></ul></ul>
  
===New/Modified Toolbars or Menus ===
+
<div id="paste"></div>
 
+
* '''Edit Menu:'''
* '''Customisable Toolbar:''' {{votes|7}} add/remove/move items from/between toolbars (similar to customising the toolbars in Firefox) and create a personal toolbar with just the icons you use heavily yourself (then you can hide all the other toolbars to save space)
+
** '''Insert File:''' {{votes|5}}  
** '''Customizable Menus:''' add/remove/move items from/between menus {{votes|1}}
 
 
 
* '''Ribbon toolbars''' or dropdown icons to help declutter the GUI {{votes|3}}
 
 
 
* '''Effects Toolbar''' {{votes|9}} Should be able to be dragged to any area of the screen and dockable. Organize the visible buttons, organise the Effect menu and create favorites list.
 
 
 
* '''Repair Toolbar''' {{votes|1}} containing (left to right) Zoom In/Repair/Zoom Out buttons. Both Zoom buttons zoom by (say) factor of 10 if Control key depressed. Breaks monotony of using the keyboard all the time and holding and releasing the mouse to highlight the repair area.
 
 
 
* '''Global "hide/show toolbars" switch''' {{votes|1}} retains the same toolbar positions when unhid - preferably keyboard accessible too.
 
 
 
* (macOS) '''When applying a shortcut for a command that is in the menus, make that root menu item flash in the menu bar, like Apple apps do.'''  {{votes|1}}
 
{{devcomment|FileZilla which uses a slightly later version of wxWidgets (3.0.3) than we do (3.0.2) shows this flash, so possibly Audacity might show that too when we upgrade wxWidgets again.}}
 
 
 
* '''Analyze Menu:'''
 
** '''Real-time Tuner:''' like Tuning Fork in [http://en.wikipedia.org/wiki/GarageBand GarageBand]  {{votes|1}}
 
<ul>{{devcomment|See [[Other Specific Tasks#Instrument tuners|here]] for some free instrument tuner applications and a possible method to tune instruments in Audacity using a pre-recorded track and [http://manual.audacityteam.org/o/man/plot_spectrum.html Plot Spectrum].}}</ul>
 
 
 
<div id="paste"></div>
 
* '''Edit Menu:'''
 
** '''Insert File:''' {{votes|5}}  
 
 
*** '''Dialog allows insertion of multiple files, each at specified cursor positions''' not just insertion of one file at wherever the current position is {{votes|1}}
 
*** '''Dialog allows insertion of multiple files, each at specified cursor positions''' not just insertion of one file at wherever the current position is {{votes|1}}
 
** '''Paste Special:''' More commands including "Replace", "Mix" and "Insert Before" as well as the standard "Paste" for "Insert After."  {{votes|13}}
 
** '''Paste Special:''' More commands including "Replace", "Mix" and "Insert Before" as well as the standard "Paste" for "Insert After."  {{votes|13}}
Line 1,085: Line 1,066:
 
*** '''Save multiple regions''' {{votes|2}}
 
*** '''Save multiple regions''' {{votes|2}}
 
*** '''Restore last used:''' {{votes|2}} so you don't have to remember to save. If user repeated the command, we would need to decide if it alternated between the last two regions or carried on going back in time (or provide a choice for those).  
 
*** '''Restore last used:''' {{votes|2}} so you don't have to remember to save. If user repeated the command, we would need to decide if it alternated between the last two regions or carried on going back in time (or provide a choice for those).  
** '''Reset Preferences:''' {{votes|15}} An easier way is needed to enable *and advertise* reset of Preferences (rather than have users mistakenly think uninstalling/reinstalling Audacity will correct a problem). Could instead/also be an executable to repair or remove settings in the install folder (see [[#install|first run, deployment and uninstallation]]). It could be an item *in* Preferences but that creates confusion as you could both change preferences and negate the changes by enabling a reset. It could be a key-modified click when launching the Audacity executable.
+
 
<ul>{{devcomment|From version 2.0.1, the Windows installer for Audacity has an option to reset Preferences on next launch of Audacity.}}
+
* '''Make "Silence Audio" non-destructive so it could be undone at any time.''' {{votesdate|3|25Sep17}} Could be a feature of Envelope Tool or it could work like an "automation control" for the Mute button. </ul>
* '''Make "Silence Audio" non-destructive so it could be undone at any time.''' {{votes|1}} Could be a feature of Envelope Tool or it could work like an "automation control" for the Mute button. </ul>
 
 
* '''Edit Toolbar:'''
 
* '''Edit Toolbar:'''
 
** '''Delete selection:''' Cut (scissors) also too easily used for this in error  
 
** '''Delete selection:''' Cut (scissors) also too easily used for this in error  
Line 1,111: Line 1,091:
  
 
* '''Effect Menu:'''
 
* '''Effect Menu:'''
** '''Reopen <last effect>:''' {{votes|5}} without running it, with a new shortcut CTRL+SHIFT+R. Useful to apply the same effect several times with different settings, for example if applying Equalization, Compression or filters. Would also be an easier way to re-access Noise Removal after grabbing the Noise Profile.  
+
** '''Reopen <last effect>:''' {{votesdate|7|07Mar21}} without running it, with a new shortcut CTRL+SHIFT+R. Useful to apply the same effect several times with different settings, for example if applying Equalization, Compression or filters. Would also be an easier way to re-access Noise Removal after grabbing the Noise Profile.  
  
 
* '''File Menu:'''
 
* '''File Menu:'''
** '''Overwrite:''' {{votes|17}} Just overwrite the imported file without any questions asked about name, format or options  
+
** '''Overwrite:''' {{votesdate|22|31Mar21}} Just overwrite the imported file without any questions asked about name, format or options  
 
*** See also requests for a [[#New/Modified Preferences|preference]] to "Export to same format as imported file" and "File > Overwrite on Exit".
 
*** See also requests for a [[#New/Modified Preferences|preference]] to "Export to same format as imported file" and "File > Overwrite on Exit".
 
** '''Preview file within file open dialog'''  {{votes|8}}   
 
** '''Preview file within file open dialog'''  {{votes|8}}   
Line 1,127: Line 1,107:
 
<li>'''Only have Export item, not Export Selection:''' {{votes|1}} The problem is now that if you select audio then press Export thinking that exports the selection as in some other applications, it actually exports all. </ul>
 
<li>'''Only have Export item, not Export Selection:''' {{votes|1}} The problem is now that if you select audio then press Export thinking that exports the selection as in some other applications, it actually exports all. </ul>
 
{{devcomment|A couple of people have objected that you can't then export all while retaining the selection, or you may forget to remove the selection.}}</ul>
 
{{devcomment|A couple of people have objected that you can't then export all while retaining the selection, or you may forget to remove the selection.}}</ul>
 +
 +
 +
* '''Generate Menu'''
 +
** '''Repeat last used generator:''' {{votesdate|4|05Jan21}}  Like "Repeat <effect> CTRL + R" but for Generators.
  
 
* '''Help Menu'''
 
* '''Help Menu'''
Line 1,146: Line 1,130:
 
** '''Ability to remove default fields''' {{votes|1}}  
 
** '''Ability to remove default fields''' {{votes|1}}  
 
<ul>{{devcomment|There would also have to be a way to restore the default fields, or make it so that removing them would only work while the Metadata Editor was open, so that a Template or Default could be saved with fields removed.}} </ul>  
 
<ul>{{devcomment|There would also have to be a way to restore the default fields, or make it so that removing them would only work while the Metadata Editor was open, so that a Template or Default could be saved with fields removed.}} </ul>  
 +
:* '''Load template without overwriting current data''' so that only empty fields are overwritten. {{votesdate|26Aug18|1}}
  
 
<div id="meter"></div>
 
<div id="meter"></div>
Line 1,164: Line 1,149:
 
** '''Control for Meter/Waveform (dB) display range''' on the fly instead of in global preferences {{votes|2}} Cascading menu item "Meter/Waveform dB range > " in the right-click meter menu?  
 
** '''Control for Meter/Waveform (dB) display range''' on the fly instead of in global preferences {{votes|2}} Cascading menu item "Meter/Waveform dB range > " in the right-click meter menu?  
 
** '''Display/name the input being monitored''' {{votes|1}} I understand that this info would have to initially come from the drivers and that it might be named poorly. I'd like to change the name of each of these inputs myself. For instance, I have a card with 8 analog inputs, and 5 different input names, multi (for access to all the inputs), and 1/2, 3/4, 5/6, 7/8. In the Edit -> Preferences menu these all have the words "M-Audio Delta 1010LT" in front, but I don't need to see that.
 
** '''Display/name the input being monitored''' {{votes|1}} I understand that this info would have to initially come from the drivers and that it might be named poorly. I'd like to change the name of each of these inputs myself. For instance, I have a card with 8 analog inputs, and 5 different input names, multi (for access to all the inputs), and 1/2, 3/4, 5/6, 7/8. In the Edit -> Preferences menu these all have the words "M-Audio Delta 1010LT" in front, but I don't need to see that.
 +
** '''"Peak Hold" for RMS level:''' Similar to the vertical bar that displays the highest peak of the last 3 seconds, but for the RMS level when "RMS" is selected as the meter style. {{votesdate|1|03Jul19}}
  
 
* '''Options Toolbar: a new toolbar''' {{votes|1}} for easy access to Envelope/Fade/and possibly other options
 
* '''Options Toolbar: a new toolbar''' {{votes|1}} for easy access to Envelope/Fade/and possibly other options
Line 1,212: Line 1,198:
 
** Linear or Exponential Envelopes (Envelope Tool Options)
 
** Linear or Exponential Envelopes (Envelope Tool Options)
 
** Fade In/Out options  
 
** Fade In/Out options  
** Nyquist Workbench
 
 
** New "Utility" type Nyquist plug-ins that do not generate, process or analyze.  
 
** New "Utility" type Nyquist plug-ins that do not generate, process or analyze.  
 +
** '''Repeat last used Tool:''' {{votesdate|4|05Jan21}}  Like "Repeat <effect> CTRL + R" but for Tools.
  
 
* '''Tools Toolbar:'''
 
* '''Tools Toolbar:'''
Line 1,235: Line 1,221:
 
<div id="transport_toolbar"></div>
 
<div id="transport_toolbar"></div>
 
* '''Transport Toolbar:'''
 
* '''Transport Toolbar:'''
** '''Separate loop-play button''' {{votes|9}}  
+
** '''Separate loop-play button''' {{votesdate|10|23Nov17}}  
 
*** '''Arguably we need an alternative optional Transport Toolbar with smaller buttons''' to accommodate this - until then the extra button could be seen as "clutter" {{votes|2}}  
 
*** '''Arguably we need an alternative optional Transport Toolbar with smaller buttons''' to accommodate this - until then the extra button could be seen as "clutter" {{votes|2}}  
 
*** '''Loop button to loop whole track even if selection''' {{votes|1}}   
 
*** '''Loop button to loop whole track even if selection''' {{votes|1}}   
Line 1,270: Line 1,256:
 
** '''Move in or duplicate "Show track name in waveform display" from Interface Preferences''' to View Menu {{votes|5}} Could be called "Show Track Name in Display" or "Show Track Name" (slightly ambiguous)
 
** '''Move in or duplicate "Show track name in waveform display" from Interface Preferences''' to View Menu {{votes|5}} Could be called "Show Track Name in Display" or "Show Track Name" (slightly ambiguous)
 
** '''"Show Clipping": configure number of consecutive samples required to trigger'''  {{votes|3}}
 
** '''"Show Clipping": configure number of consecutive samples required to trigger'''  {{votes|3}}
** '''Karaoke multiple label track support:''' {{votes|1}} Play multiple label tracks at once and assign which track gets the bouncing ball. Use case is three separate label tracks, one for the sections (verses, choruses and bridges), another for the rhythm changes and another for the lyrics parsed as individual words.  
+
** '''Go to Selection Start/End items should center the cursor too:''' {{votesdate|3|13May17}}. This would let you center the cursor even if it is on screen (in which case {{shortcut|Left}} {{shortcut|Right}} is not a workaround) and even when "Select entire project" autoselection is on (rather than destroy the cursor position as now). 
** '''"Mixer Board" misnamed:''' the main interface is about mixing as well. The point about Mixer Board is the multi-metering so the menu item should be "Multi-Meters" or "Per Track Meters" {{votes|3}}
+
** '''Karaoke multiple label track support:''' {{votes|1}} Play multiple label tracks at once and assign which track gets the bouncing ball. Use case is three separate label tracks, one for the sections (verses, choruses and bridges), another for the rhythm changes and another for the lyrics parsed as individual words.
*** I disagree, the "Mixer-Board" is much more than just a set of multi-meters, it carries a full set of mixing controls too (much like a hardware mixing board that many would be familiar with) [[User:PeterSampson|PeterSampson]]
 
<ul><ul>{{devcomment|I've seen a number of comments pointing out "you can mix without Mixer Board, so why call it that?" sent off the email link in the Manual, but this user wanted to explicitly vote for a wording change. I think the point is that the "extra" meters are what catch the eye and what really make Mixer Board "different". Mixer Board has an extra image too, but the "full set" of controls is only otherwise the same controls that all the tracks have. I wouldn't say it's "misnamed" but I perfectly understand the comments. - Gale}}
 
<ul>{{devcomment|This is a <em>silly</em> idea. "Multi-meters" is a non-standard, uninformative name. Misleading even, as it describes only the meters (as Peter commented). Mixer Board has had that name for about 4 years, so only one user complaining about it actually speaks to the appropriateness of the name. It <em>looks</em> like a hardware mixer board and is modeled after one. Yes, you can mix in the TrackPanel class, but you can also, for example, see the waveform as you record, and many other things that you cannot in Mixer Board. Mixer Board's sole and special purpose is mixing. The name is totally appropriate and I veto this "request." Can we just remove it, as this page generates a warning about its large size already? - Vaughan}}
 
<ul><ul>{{devcomment|No, votes can't be removed in a democracy, you can only refuse to implement the idea. I think the other people who made similar comments as an aside are "almost" voting that they find the Mixer Board concept confusing. Possibly their unfamiliarity with hardware mixers is the reason, and they are the same type of person who expect mute/solo to be interdependent. I think if it were possible to have a wider background behind the Mixer Board track strips it "might" help get it across better as an alternate view? - Gale}}</ul></ul></ul></ul></ul>
 
  
 
===New/Modified other GUI elements===
 
===New/Modified other GUI elements===
Line 1,282: Line 1,264:
 
* '''Markers on Waveform''' {{votes|36}} Add with one keystroke a vertical mark that stays on the waveform and can be labeled. Common in audio editors. Should be draggable but attached to the audio segment. Select between any two markers easily e.g. with double click. Snap a region to the markers. Should be implemented in addition to split lines. Very necessary for long-form documentary editing, where you are identifying and then going back and handling many different selections from a long file. Also important if recordings are edited afterwards by others.  
 
* '''Markers on Waveform''' {{votes|36}} Add with one keystroke a vertical mark that stays on the waveform and can be labeled. Common in audio editors. Should be draggable but attached to the audio segment. Select between any two markers easily e.g. with double click. Snap a region to the markers. Should be implemented in addition to split lines. Very necessary for long-form documentary editing, where you are identifying and then going back and handling many different selections from a long file. Also important if recordings are edited afterwards by others.  
  
* '''Buttons on dialogs (general):'''
+
<div id="signature"></div>
** ''(OS X)'' '''Support OS X dual defaults''' which differentiate between preselected (hit ENTER) and bordered (hit spacebar)  {{votes|1}}
+
* '''Let the Timeline display time signature and bars/beats''' {{votesdate|39|08May21}}. This is a useful feature in its own right, even if user had to identify the BPM manually. It could also be the means of displaying automatically detected beats if/when that is implemented. It would mean we could align to beats - see: "Snap To: Beats".
 
+
<ul><ul>
* '''Waveform and clip colors:'''
+
<li>'''Must show complete grid with all beats having vertical line:''' {{votes|2}}
<div id="coloredtracks"></div>
+
<li>'''[http://en.wikipedia.org/wiki/Quantization_(music) Quantize] to a grid like [http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=EditingMIDI.38.html Sonar]:''' {{votesdate|16|02Jan21}} This corrects timing errors in MIDI or audio where you record slightly before or after the beat or hold some notes shorter or longer than intended.
** '''Assign different colors to individual tracks, clips or regions''' {{votes|42}} For example different colors for different participants in an interview
+
<ul><li>Do this by dragging clip boundaries to grid lines {{votes|3}}</ul>
*** ''' A border around the clip is sufficient''' {{votes|1}}
+
<li>'''Identify BPM manually''' by tapping in an interface as in web applications {{votes|7}}  
*** ''' Changing the track background is sufficient, not the waveform colors''' {{votes|1}}
+
<ul><li> with option to show the true tempo of the song even if I play it back at different speed {{votes|1}} </ul>
*** ''' Allow different names for each clip as well as different colors''' {{votes|2}}
+
<li>'''BPM Calculator''' that shows BPM based on a selection. {{votes|1}}. </ul>
<div id="customwave"></div>
+
{{devcomment|1=See also this BPM calculator plugin https://forum.audacityteam.org/viewtopic.php?f=42&t=69028.}}
** '''User-customised waveform colors for RMS and background to improve contrast''' {{votes|31}}  
+
</ul>
*** '''Do this ''without'' need for Theme downloads''' {{votes|3}}
+
 
<ul>{{devcomment|This will be added in a future Audacity along with other interface customisations. Average value (RMS) already is light blue. Another issue is that the selection color is behind the waveform. Other editors e.g. GoldWave, CoolEdit just use different colors for selected and non-selected waveform.}}</ul>
+
<div id="contextmenu"></div>
 
+
* '''More Context Menu (right-click or CTRL-click) functionality''' {{votes|23}}
* '''[[:File:Effect track.png|Effect track]]:''' {{votes|1}}
+
** '''Right-click over selection region''' - ideas:
** An envelope with control points like Time Track. Dropdown menu lets you choose the effect to be applied and whether the effect track applies to the audio track below, above or to all audio tracks. The Track Control Panel has buttons to select each parameter. Control points are set against the parameter levels shown on the vertical scale. The envelope line starts flat, implying the default parameter is applied to all of the track(s) it applies to.
+
***'''Cut; copy; paste; delete; Undo''' {{votes|5}}
 
+
***'''Apply effects:''' Workflow and reduced mousing benefits {{votes|2}}
<div id="envelope"></div> 
+
***'''Zoom in/out on selection (horizontally)''' {{votes|2}}
*'''Envelope Tool''':
+
***'''Select all; Select in all tracks''' {{votes|2}}
** '''Choice of linear envelope editing:''' e.g. as in Pro Tools {{votes|16}} Current fades are logarithmic, if you switch the track view mode to Waveform (dB) the fades will show as "straight" lines. To make linear fade, need to create multiple small fades to create an envelope that approximates to a straight line. 
+
***'''Silence'''
*** '''Too fiddly/unintuitive to fade out to zero''' {{votes|3}}. Pinching the point hard to the zero line makes volume fade to zero almost after the beginning of the fade.
+
***'''Set start/end of selection:''' {{votes|1}} like Goldwave
*** "SHIFT + drag" for linear envelopes and "CTRL" + drag for logarithmic envelopes
+
***'''Split off a selection of a clip'''
**** Fading to 0 is possible: in normal Waveform view, click the top point and drag down below the center line. Easier seen in Waveform (dB) mode or after rendering.
+
***'''Duplicate a selection of a clip'''
<ul><ul><ul>{{devcomment|The last point is not quite correct. Waveform dB view does not show fading to 0. The lower limit of the Waveform dB view is set in Interface Preferences and any signal below this lower limit will appear to be silent. The envelope tool performs a logarithmic fade out down to -145 dB and then steps down from -145 dB to -inf dB.}}</ul>
+
***'''Send to new track:''' or to a labelled position in an existing track.
<li> '''Tooltip or Status Bar message when mouse holds control point:''' {{votes|9}} to show gain amount, final dB level and position in the Timeline.
+
***'''Set Envelope Points:''' creates start and end points on the envelope automatically.
<ul><li> '''Tooltip preferred:''' {{votes|2}}</ul>
+
** '''Right-click over waveform''' - ideas, some for features that don't yet exist yet (from [[Proposal Woozle's Interface Tweaks]]): 
<li>'''Apply to regions''' {{votes|9}} e.g. hold down ALT key and drag between envelope points to move only that section up or down (handy for changing the volume of a section of audio without having to drag individual points around). </ul>{{devcomment|This would seem to imply that regions create temporary envelope points as split lines do.}}
+
***'''Delete track''' {{votes|2}}
<ul><li>'''CTRL or ALT + click creates a control point but doesn't alter the envelope:''' {{votes|4}} (it currently starts dragging the envelope straight away which isn't very helpful). If you are far from a control point and want to tweak the envelope, but don't want to add a new control point, you need to go back to the control point.
+
***'''Insert track below/above current'''
<li>'''Text input for accuracy of control point placement''' {{votes|6}} 
+
***'''Mute individual clips''' (new feature)  
<ul><li>Should allow specifying timeline position at frame resolution, as well as movement in the vertical axis on a percent or dB scale) {{votes|1}}</ul>
+
***'''Time-lock individual clips''' (Tracks Preferences can globally prevent clips moving with edits) 
<li>'''More intelligent/automatic rendering:''' {{votes|4}} Could be a switch or a preference, off by default. Could render after each point drawn, or after switching from Envelope Tool. Reason: it's too easy to switch back to Selection Tool, forget you have not rendered the envelope then apply some effect that causes clipping after you render. It must confuse novices too to look in Amplify after using Envelope Tool and see the "wrong" values. 
+
***'''Duplicate an entire clip'''
<li>'''Cut and paste of envelope points:''' {{votes|5}} - especially useful to paste between different tracks or projects. Ideally, should permit pasting from mono track envelope to stereo (copying both envelopes from a stereo track to a mono track would be more problematic).
+
***'''Delete clip'''
<li>'''Per-track envelope accessed from button in Track Control Panel''' {{votes|2}}
+
***'''Insert a split point at the cursor'''
<li>'''Lock to prevent drag creating clipping''' {{votes|1}}
+
***'''Edit start time, offset and length of a clip''' (new feature)
<li>'''Modifier keys for horizontal drag only/ vertical drag only''' {{votes|4}}
+
***'''Zoom in/out vertically''' {{votes|2}}
<li>'''Horizontal bar to change volume of all envelope points together''' {{votes|5}}
+
***'''Turn envelope view on/off''' (preferably per clip, which is a new feature)
<ul><li>Perhaps alt-drag on a master fader could do that {{votes|1}}</ul>
+
 
<li>'''Method to shift all envelope points left/right:''' {{votes|1}}
+
* '''Buttons on dialogs (general):'''
<li>'''Non-destructive:''' Draw lines and curves on top of audio events for accurate, graphically-based audio mixing like Cakewalk {{votes|1}}</ul></ul>
+
** ''(OS X)'' '''Support OS X dual defaults''' which differentiate between preselected (hit ENTER) and bordered (hit spacebar)  {{votes|1}}
 +
 
 +
* '''[[:File:Effect track.png|Effect track]]:''' {{votes|1}}
 +
** An envelope with control points like Time Track. Dropdown menu lets you choose the effect to be applied and whether the effect track applies to the audio track below, above or to all audio tracks. The Track Control Panel has buttons to select each parameter. Control points are set against the parameter levels shown on the vertical scale. The envelope line starts flat, implying the default parameter is applied to all of the track(s) it applies to.
 +
 
 +
<div id="envelope"></div> 
 +
*'''Envelope Tool''':
 +
** '''Choice of linear envelope editing:''' e.g. as in Pro Tools {{votesdate|17|10Mar19}} Current fades are logarithmic, if you switch the track view mode to Waveform (dB) the fades will show as "straight" lines. To make linear fade, need to create multiple small fades to create an envelope that approximates to a straight line.
 +
*** '''Too fiddly/unintuitive to fade out to zero''' {{votes|3}}. Pinching the point hard to the zero line makes volume fade to zero almost after the beginning of the fade.
 +
*** "SHIFT + drag" for linear envelopes and "CTRL" + drag for logarithmic envelopes  
 +
**** Fading to 0 is possible: in normal Waveform view, click the top point and drag down below the center line. Easier seen in Waveform (dB) mode or after rendering.
 +
:::{{devcomment|The last point is not quite correct. Waveform dB view does not show fading to 0. The lower limit of the Waveform dB view is set in Interface Preferences and any signal below this lower limit will appear to be silent. The envelope tool performs a logarithmic fade out down to -145 dB and then steps down from -145 dB to -inf dB.}}
 +
:::{{devcomment|Update: In Audacity 3.0.0 we are back to it being impossible to fade to zero.}}
 +
:* '''Tooltip or Status Bar message when mouse holds control point:''' {{votes|9}} to show gain amount, final dB level and position in the Timeline.
 +
::* '''Tooltip preferred:''' {{votes|2}}
 +
:*'''Apply to regions''' {{votes|9}} e.g. hold down ALT key and drag between envelope points to move only that section up or down (handy for changing the volume of a section of audio without having to drag individual points around). </ul>{{devcomment|This would seem to imply that regions create temporary envelope points as split lines do.}}
 +
:*'''CTRL or ALT + click creates a control point but doesn't alter the envelope:''' {{votes|4}} (it currently starts dragging the envelope straight away which isn't very helpful). If you are far from a control point and want to tweak the envelope, but don't want to add a new control point, you need to go back to the control point.
 +
:*'''Text input for accuracy of control point placement''' {{votes|6}} 
 +
::*Should allow specifying timeline position at frame resolution, as well as movement in the vertical axis on a percent or dB scale) {{votes|1}}</ul>
 +
:*'''More intelligent/automatic rendering:''' {{votes|4}} Could be a switch or a preference, off by default. Could render after each point drawn, or after switching from Envelope Tool. Reason: it's too easy to switch back to Selection Tool, forget you have not rendered the envelope then apply some effect that causes clipping after you render. It must confuse novices too to look in Amplify after using Envelope Tool and see the "wrong" values. 
 +
:*'''Cut and paste of envelope points:''' {{votesdate|8|02Apr17}} - especially useful to paste between different tracks or projects. Ideally, should permit pasting from mono track envelope to stereo (copying both envelopes from a stereo track to a mono track would be more problematic).
 +
:*'''Per-track envelope accessed from button in Track Control Panel''' {{votes|2}}
 +
:*'''Lock to prevent drag creating clipping''' {{votes|1}}
 +
:*'''Modifier keys for horizontal drag only/ vertical drag only''' {{votes|4}}
 +
:*'''Horizontal bar to change volume of all envelope points together''' {{votes|5}}
 +
::*Perhaps alt-drag on a master fader could do that {{votes|1}}</ul>
 +
:*'''Method to shift all envelope points left/right:''' {{votes|1}}
 +
:*'''Non-destructive:''' Draw lines and curves on top of audio events for accurate, graphically-based audio mixing like Cakewalk {{votes|1}}
 +
 
  
 
* '''FTP/RSS/online distribution''' support for podcasters, bands etc.  {{votes|19}} {{devcomment|1=Experimental FTP support was previously available in Audacity 1.3.3 Beta. FTP is not supported in current Audacity releases, but copies of 1.3.3 are still downloadable from our [http://sourceforge.net/project/showfiles.php?group_id=6235 file archive]}}
 
* '''FTP/RSS/online distribution''' support for podcasters, bands etc.  {{votes|19}} {{devcomment|1=Experimental FTP support was previously available in Audacity 1.3.3 Beta. FTP is not supported in current Audacity releases, but copies of 1.3.3 are still downloadable from our [http://sourceforge.net/project/showfiles.php?group_id=6235 file archive]}}
Line 1,327: Line 1,337:
 
* '''Hand Tool to Cut/Drag and Copy/Drag selection region:''' While dragging, the END of the selection range would be a dotted line and START a regular vertical line to know where to drop it. Selection Bar shows the START/END values {{votes|1}}
 
* '''Hand Tool to Cut/Drag and Copy/Drag selection region:''' While dragging, the END of the selection range would be a dotted line and START a regular vertical line to know where to drop it. Selection Bar shows the START/END values {{votes|1}}
  
* '''Label Track'''
+
<div id="labels_editor"></div>
** '''Double Click Label Edit''': have one click on a label select the labelled area, e.g. for »shift-space« playback; have double-click open the label itself for text-editing {{votes|1}}
+
* '''Labels Editor'''
<ul> {{devcomment|The reason we don't do this, which was discussed at the time, is to allow creation of a label by typing in a label track (either at a cursor or inside a region) without use of a shortcut to do so. Once you have single-clicked in the label to select it, use up arrow, ESC or ENTER to use a shortcut without affecting the label contents.}}</ul>
+
 
 +
** '''Built-in Play function for previewing label:''' {{votesdate|6|12Jan17}}
 +
** '''Make the editor modeless so for example Transport shortcuts can be used:''' {{votesdate|3|11Mar17}}
 +
** '''Ability to select multiple labels for action:''' {{votesdate|6|11Mar17}} such as moving or removing labels (as a separate action from  giving focus to a cell in a label row to move to that label in the track)
 +
** '''Search for keywords within labels''' {{votesdate|4|25May17}}
 +
** '''Add "Distance from preceding label" field:''' {{votesdate|1|03Feb17}} Could be editable, so modifying the time position of that label and the distance value for the succeeding label. Maybe option to edit the distance from two labels only and have all succeeding labels shifted by this amount.
 +
** '''Apply button to save changes without closing:''' {{votesdate|1|26Dec12}}
 +
** '''More intuitive way to change a label's track than double-click:''' {{votesdate|1|26Dec12}}
 +
** '''Remember size and position:''' {{votesdate|2|24Jun17}}  
  
 
* '''Message boxes:'''  
 
* '''Message boxes:'''  
Line 1,340: Line 1,358:
 
      
 
      
 
* '''Mixer Board:'''  
 
* '''Mixer Board:'''  
** '''Needs to stay on top with main window.''' {{votes|19}} Although it gets in the way if you have a lot of tracks, you can resize it horizontally. Making it disappear when you use the main window is not the answer. That means shortcuts don't work when it has focus (or developers have to add separate shortcuts for it). Tiling doesn't help if you want to work with maximised windows.
+
:*'''Button (and shortcut) to roll it up and down in situ:''' {{votes|1}}  
*** Shortcut to switch focus and on top state between main Audacity window and Mixer Board window.
+
::* or embed Mixer board into Meter toolbar {{votes|1}}
*** Or try the [http://www.goldwave.com/ Goldwave] solution for its Control Window. It floats on top when main window is maximised, or sticks to side/bottom of main window when that is restored down. If minimised, it sits on top of the Taskbar as a Title bar with buttons and can be moved anywhere.         
 
<ul><ul>{{devcomment|On Windows you can use right-click over Taskbar > Tile Windows ("Side-by-Side" or "Stacked" on Vista or later) or select the windows to tile in Task Manager. Alternatively try [http://www.hyperionics.com/files/index.asp FileBox eXtender] or [http://www.abstractpath.com/powermenu/ PowerMenu]. On Mac, try [http://infinite-labs.net/afloat/ Afloat]. Most Linux window managers include an "always on top" option for each window.}} 
 
<li>'''Button (and shortcut) to roll it up and down in situ:''' {{votes|1}}  
 
<li>'''Allow it to be vertically resized:'''  {{votes|1}}
 
<li>'''Include Recording meter as well as playback meter''' {{votes|3}} Allows per-channel metering for multi-channel sound cards.
 
<ul><li> or embed Mixer board into Meter toolbar {{votes|1}}</ul>
 
 
{{devcomment|See also requests for per-track meters in [[#meter|Meter Toobar]].}}
 
{{devcomment|See also requests for per-track meters in [[#meter|Meter Toobar]].}}
<li>'''More like Kristal's mixing window''' {{votes|2}}
+
:*'''More like Kristal's mixing window''' {{votes|2}}
<li>'''Include 2 or 3 band EQ''' {{votes|1}}
+
:*'''Include 2 or 3 band EQ''' {{votes|1}}
<li> '''Save open/closed Mixer Board state in audacity.cfg''' so new projects respect that  {{votes|1}}  
+
:* '''Save open/closed Mixer Board state in audacity.cfg''' so new projects respect that  {{votes|1}}  
<li> '''Save open/closed Mixer Board state in .aup file''' {{votes|1}}</ul></ul>
+
:* '''Save open/closed Mixer Board state in .aup file''' {{votes|1}}
 +
:* '''Show post-envelope level (option):''' Allow the Mixer Board to show the actual level in the project when envelopes are present. {{votesdate|2|14Jan21}}
  
 
* '''Quick Play Region:'''
 
* '''Quick Play Region:'''
Line 1,374: Line 1,387:
 
** '''Secondary horizontal scrollbar''' {{votes|1}} (above the existing standard horizontal scrollbar) that scrolls only the extent of selection. When you've highlighted one bar of a song, then want to zoom in to the sample level you want to scroll back and forth in your selection, but the standard project-wide horizontal scrollbar isn't granular enough and you whiz way out of your selection.  
 
** '''Secondary horizontal scrollbar''' {{votes|1}} (above the existing standard horizontal scrollbar) that scrolls only the extent of selection. When you've highlighted one bar of a song, then want to zoom in to the sample level you want to scroll back and forth in your selection, but the standard project-wide horizontal scrollbar isn't granular enough and you whiz way out of your selection.  
  
* '''Selection Viewer (draggable):'''  {{votes|11}} Useful for previewing loops, to see how well the ends match. Could incorporate zooming like the Windows magnifier. Could have option to duplicate a region into viewer as transparent different colored waveform for easy comparison over the top of another region.  
+
* '''Selection Viewer (draggable):'''  {{votesdate|12|02Dec19}} Useful for previewing loops, to see how well the ends match. Could incorporate zooming like the Windows magnifier. Could have option to duplicate a region into viewer as transparent different colored waveform for easy comparison over the top of another region.  
** Also see proof of concept for a [http://audacity.238276.n2.nabble.com/Focus-Plus-Context-Audacity-Demo-screencast-td257863.html Focus-Plus-Context Audacity interface] {{votes|2}}  
+
** Also see proof of concept for a [http://audacity.238276.n2.nabble.com/Focus-Plus-Context-Audacity-Demo-screencast-td257863.html Focus-Plus-Context Audacity interface] {{votes|2}}
 +
** '''Overview Map:''' as a navigation aid (not requiring additional features described in main point), as found in applications such as SoundForge and Sibelius. Example of how it might look: https://forum.audacityteam.org/download/file.php?id=25268 {{votesdate|2|02Dec19}}
  
 
* '''Sliders:'''  
 
* '''Sliders:'''  
 
** '''More discoverable precise adjustment'''
 
** '''More discoverable precise adjustment'''
 
** '''Add "double-click for precise adjustment" message to tooltips''' {{votes|1}}
 
** '''Add "double-click for precise adjustment" message to tooltips''' {{votes|1}}
<ul>{{devcomment|1=A downward pointing widget may be a better idea because there is a fairly definite [http://bugzilla.audacityteam.org/show_bug.cgi?id=74 intention] to use the tooltip to display the current setting}} </ul>   
+
<ul>{{devcomment|1=A downward pointing widget may be a better idea because there is a fairly definite [https://bugzilla.audacityteam.org/show_bug.cgi?id=74 intention] to use the tooltip to display the current setting}} </ul>   
  
 
* '''Status Bar:'''
 
* '''Status Bar:'''
Line 1,387: Line 1,401:
  
 
* '''Tabs for individual projects, not separate windows:''' {{votes|9}} Far easier to manipulate and understand  
 
* '''Tabs for individual projects, not separate windows:''' {{votes|9}} Far easier to manipulate and understand  
 +
 +
* '''Taskbar Icon:'''
 +
** Show progress bar in the taskbar button on Windows and the dock icon on OS X for long processes. {{votesdate|3|27Oct18}}
 +
:: {{devcomment|As of wxWidgets 3.1 there is [[https://docs.wxwidgets.org/3.1/classwx_app_progress_indicator.html wxAppProgressIndicator]].}}
  
 
* '''Timeline:'''
 
* '''Timeline:'''
 
** '''Option to display in current Selection Format''' such as film frames, not just in seconds. {{votes|7}}   
 
** '''Option to display in current Selection Format''' such as film frames, not just in seconds. {{votes|7}}   
** '''Timeline settable to HH:MM:SS:''' {{votes|7}} for easier calculation of times at which recording events occurred  
+
** '''Timeline settable to HH:MM:SS:''' {{votesdate|9|07Mar17}} for easier calculation of times at which recording events occurred  
*** Should be an extra timeline, not just an option for existing Timeline {{votes|4}}
+
*** Should be an extra timeline, not just an option for existing Timeline {{votesdate|5|07Mar17}}
 +
**** '''The separate Clock Timeline could be a strip having the length of the original recording, capable of showing labels.'''  {{votesdate|1|07Mar17}} If we change the length of the audio for example by inserting or deleting, the labels show the actual clock time of the audio. The labels could extend to right of the strip or come to an end inside the strip, according to whatever the length change was.
 
*** Cutting or pasting audio should adjust displayed time {{votes|1}}   
 
*** Cutting or pasting audio should adjust displayed time {{votes|1}}   
 
** '''Draggable Timeline that could dock between or at bottom of tracks:''' {{votes|3}}'''
 
** '''Draggable Timeline that could dock between or at bottom of tracks:''' {{votes|3}}'''
Line 1,402: Line 1,421:
 
** '''One per track''' not one per window {{votes|1}}
 
** '''One per track''' not one per window {{votes|1}}
 
** '''Vertical scale shows speed change percentages''' {{votes|1}}
 
** '''Vertical scale shows speed change percentages''' {{votes|1}}
** '''Tooltip on hover over envelope point''' showing corrected time line position and speed percentage {{votes|1}}  
+
** '''Grid with horizontal and vertical lines:''' {{votesdate|1|07Mar17}}
 +
** '''Tooltip on hover over envelope point''' showing updated time line position and speed percentage {{votesdate|2|07Mar17}}  
  
 
* '''Title Bar:'''  
 
* '''Title Bar:'''  
Line 1,419: Line 1,439:
 
<ul><li> '''Make it into a normal combo menu box''' that everyone understands and accept it will widen the Track Control Panel. As a variant, track name could be a slide-out (with a tooltip) where you enter the name. Dropdown menu itself could be a spanner icon to right of sample rate/format, or maybe even a button that says "menu"  {{votes|4}}</ul>
 
<ul><li> '''Make it into a normal combo menu box''' that everyone understands and accept it will widen the Track Control Panel. As a variant, track name could be a slide-out (with a tooltip) where you enter the name. Dropdown menu itself could be a spanner icon to right of sample rate/format, or maybe even a button that says "menu"  {{votes|4}}</ul>
 
<li>'''Move track to specific place in track table''' {{votes|6}}  
 
<li>'''Move track to specific place in track table''' {{votes|6}}  
<ul><li>'''"Move Track to Top" and "Move Track to Bottom"''' are most important {{votes|2}}</ul>   
+
<ul><li> {{done}} '''"Move Track to Top" and "Move Track to Bottom"''' are most important {{votes|2}}</ul>   
<li> '''Make it easier to read long track names:''' {{votes|9}}
+
<li>'''Hover tooltip for the trackname''' {{votesdate|9|07Jan21}}</ul>
<ul><li>'''Hover tooltip for the name''' {{votes|7}}</ul>
+
:* Or greater transparency of name overlay, becoming opaque on mouse over {{votesdate|2|07Jan21}}
{{note|'''Peter 30Jan17:''' With current Audacity you can superimpose a long track name, for audio tracks, on the waveform winw.  Use Preferences>Tracks and set the entry for '''Shoaw audio track name as overlay''' to be '''on'''.
 
{{ednote|'''Peter 30Jan17:''' [[ToDo-1]] does this satisfy this FR sufficiently so we can mark it as completed>}} }}
 
 
<li> '''Pitch view should show intelligible pitch estimates'''  of simple piano, guitar or vocal selections with a piano labelled diagram [[user yanky5cool]]  {{votes|3}}
 
<li> '''Pitch view should show intelligible pitch estimates'''  of simple piano, guitar or vocal selections with a piano labelled diagram [[user yanky5cool]]  {{votes|3}}
 
<ul><li> Should also be a real time tool with a graph and movable points that change the pitch as the track plays </ul>
 
<ul><li> Should also be a real time tool with a graph and movable points that change the pitch as the track plays </ul>
 
<li> '''Add scaling for negative samples in Waveform (dB) view''' {{votes|9}} (the obvious issue is how to present that when the scale values themselves are mostly negative) </ul>  
 
<li> '''Add scaling for negative samples in Waveform (dB) view''' {{votes|9}} (the obvious issue is how to present that when the scale values themselves are mostly negative) </ul>  
 
{{devcomment|That is not a problem at all (beyond indicating the samples in the lower half are negative). The numbers on the lower side of "-inf" are a direct reflection of those above. See any other audio editor for an example.}}
 
{{devcomment|That is not a problem at all (beyond indicating the samples in the lower half are negative). The numbers on the lower side of "-inf" are a direct reflection of those above. See any other audio editor for an example.}}
<ul><li> '''Zoom the vertical scale with magnify icon to much finer resolution''' {{votes|7}} not just to integer or a bit less.  
+
<ul><li> {{done}} '''Zoom the vertical scale with magnify icon to much finer resolution''' {{votes|7}} not just to integer or a bit less.  
 
<ul><li>'''Should show samples e.g. -32768 to 32767''' {{votes|2}}</ul>{{devcomment|If you drag the track down at the bottom of the waveform you will get more resolution}} </ul>
 
<ul><li>'''Should show samples e.g. -32768 to 32767''' {{votes|2}}</ul>{{devcomment|If you drag the track down at the bottom of the waveform you will get more resolution}} </ul>
<ul><li> '''New "Waveform (Linear)" view with Logarithmic Scale''' then one can look at a sine wave without distortion. Also Audacity effects and filters all work in dB!  {{votes|3}}
+
<ul><li> '''New "Waveform (Linear)" view with Logarithmic Scale''' then one can look at a sine wave without distortion. Also Audacity effects and filters all work in dB!  {{votesdate|8|10Nov19}}
 
<li> '''New "Waveform dB" view with Logarithmic scale''' {{votes|8}} not linear spacing of increments as now  
 
<li> '''New "Waveform dB" view with Logarithmic scale''' {{votes|8}} not linear spacing of increments as now  
 
<li>'''New "Waveform dB" view with linear interpolation''' (sine wave looks like sine) {{votes|2}}
 
<li>'''New "Waveform dB" view with linear interpolation''' (sine wave looks like sine) {{votes|2}}
Line 1,436: Line 1,454:
 
<li> '''Additional vertical scale at right hand end of waveform'''  {{votes|1}}
 
<li> '''Additional vertical scale at right hand end of waveform'''  {{votes|1}}
 
<li>'''Swap stereo channels''' for upper track of stereo pair  {{votes|1}}
 
<li>'''Swap stereo channels''' for upper track of stereo pair  {{votes|1}}
 +
<div id="mtv"></div>
 
<li> '''Multiple track views''': {{votes|7}}  
 
<li> '''Multiple track views''': {{votes|7}}  
<ul><li> '''Waveform/Spectrogram split view for each track:''' {{votes|9}} upper track has a waveform view, lower a spectrogram view of the same audio, like the [http://www.thinklabsmedical.com/electronic-stethoscope/products/thinklabs-phonocardiography-software-161.html Thinklabs] variant of Audacity  
+
<ul><li> {{done}} '''Waveform/Spectrogram split view for each track:''' {{votesdate|10|04Apr17}} upper track has a waveform view, lower a spectrogram view of the same audio, like the [http://www.thinklabsmedical.com/electronic-stethoscope/products/thinklabs-phonocardiography-software-161.html Thinklabs] variant of Audacity  
 
<ul><li>Split stereo track into waveform left channel, spectrogram right channel: {{votes|1}} Use case is bat recorder hardware where left and right have different content for different purposes. </ul>  
 
<ul><li>Split stereo track into waveform left channel, spectrogram right channel: {{votes|1}} Use case is bat recorder hardware where left and right have different content for different purposes. </ul>  
 
<li> '''Multi-View:''' upper track in waveform view, then linked views of the same track below in waveform (dB) view then (read only) spectrum and pitch views: {{votes|2}} Editing or horizontal zooming either waveform view changes the other views. Makes it easier to isolate and analyze a specific micro sound and see all "the big picture". Should also be accessible via Analyze Menu. </ul>
 
<li> '''Multi-View:''' upper track in waveform view, then linked views of the same track below in waveform (dB) view then (read only) spectrum and pitch views: {{votes|2}} Editing or horizontal zooming either waveform view changes the other views. Makes it easier to isolate and analyze a specific micro sound and see all "the big picture". Should also be accessible via Analyze Menu. </ul>
Line 1,443: Line 1,462:
 
<li> '''New 3D track view:''' Amplitude *and* Frequency against Time to complement Analyze > Plot Spectrum {{votes|2}}
 
<li> '''New 3D track view:''' Amplitude *and* Frequency against Time to complement Analyze > Plot Spectrum {{votes|2}}
 
<li> '''Solo and Mute choices''' {{votes|1}} so easier to operate these with shortcuts in multi-track projects  
 
<li> '''Solo and Mute choices''' {{votes|1}} so easier to operate these with shortcuts in multi-track projects  
</ul></ul>
+
</ul>
  
 
<ul><li>'''Track Control Panel  (TrackInfo class):'''
 
<ul><li>'''Track Control Panel  (TrackInfo class):'''
Line 1,451: Line 1,470:
 
{{devcomment|see [[Space Savers]] for some more ideas}}   
 
{{devcomment|see [[Space Savers]] for some more ideas}}   
 
<li> '''Add per track Equalizer:''' Fairly coarse control OK, or (better) put it on pop-up panel {{votes|3}}
 
<li> '''Add per track Equalizer:''' Fairly coarse control OK, or (better) put it on pop-up panel {{votes|3}}
<li> ''''Allow Track Control Panel to be resized horizontally''' {{votes|8}}  
+
<li> ''''Allow Track Control Panel to be resized horizontally''' {{votes|9}}  
 
<li> '''Additional Priority Solo Button:''' {{votes|4}} Pressing this unsolos any soloed tracks and releasing it re-solos the previously soloed tracks.
 
<li> '''Additional Priority Solo Button:''' {{votes|4}} Pressing this unsolos any soloed tracks and releasing it re-solos the previously soloed tracks.
 
<li> '''Delete track with [X] when playing or recording''' {{votes|1}}
 
<li> '''Delete track with [X] when playing or recording''' {{votes|1}}
Line 1,463: Line 1,482:
  
 
<div id="grid"></div>
 
<div id="grid"></div>
* '''Grid lines:'''
+
* '''Grid lines:''' {{votesdate|29|09Nov20}}
**'''Horizontal: and also in spectrogram view''' {{votes|25}}
+
**'''Horizontal: and also in spectrogram view'''
 
*** '''Helps alignment with a specific level or frequency on the vertical scale''' when working at the other end of the track {{votes|12}}   
 
*** '''Helps alignment with a specific level or frequency on the vertical scale''' when working at the other end of the track {{votes|12}}   
 
*** '''Headroom lines at user-specified dB below and above 0dB FS'''. {{votes|1}} Gives compliance with SMPTE and EBU standards calling for specified amount of headroom before full-scale clipping.
 
*** '''Headroom lines at user-specified dB below and above 0dB FS'''. {{votes|1}} Gives compliance with SMPTE and EBU standards calling for specified amount of headroom before full-scale clipping.
Line 1,482: Line 1,501:
 
<ul><li> '''Close all open projects without individual dialog for each''' {{votes|1}}  
 
<ul><li> '''Close all open projects without individual dialog for each''' {{votes|1}}  
 
<li> '''Automatically refit project after dragging out window''' rather than user having to CTRL + F manually afterwards.</ul></ul>
 
<li> '''Automatically refit project after dragging out window''' rather than user having to CTRL + F manually afterwards.</ul></ul>
 
* '''Windows 7 features:'''
 
** '''Use Windows 7 Explorer-style open and save dialogs:''' {{votes|7}} like 1.2.6 does. These have extra functionality like search.
 
<ul>{{devcomment|This is probably a legacy from when we supported Windows 2000 or earlier. On those systems the newer Windows file open dialogue with search would not work properly in Audacity 1.3.Beta.}}
 
<ul><li> '''Use Taskbar button overlay icons/progress bars''' {{votes|1}} See [http://windowsteamblog.com/windows/b/developers/archive/2009/07/28/windows-7-taskbar-dynamic-overlay-icons-and-progress-bars.aspx developer information].</ul></ul>
 
  
 
===Keyboard Shortcuts/Modifiers===
 
===Keyboard Shortcuts/Modifiers===
 
 
{{Hint|Also see [[Use Cases]] for a number of ideas for shortcuts that would be used during playback or recording.}}
 
{{Hint|Also see [[Use Cases]] for a number of ideas for shortcuts that would be used during playback or recording.}}
 
<div id="parameterbinding"></div>
 
* '''Bind particular parameters of effects to buttons or keyboard shortcuts:''' e.g. one for amplify + 3 dB, another -3 dB, another to Compress with -6 dB threshold {{votes|50}}
 
** Effects for which this has been requested: Amplify; Change Speed; Fade In/Out; Generate Tone; Insert Silence; Noise Removal; Normalize; Repair; DC removal ; Chris' Compressor
 
<ul>{{devcomment|To avoid running out of shortcuts/frequently changing parameters, one of the shortcuts should be to use the last used setting. Perhaps now that we have effects presets, the dialogue would actually use or create presets.}}</ul>
 
  
 
* '''New Shortcuts''':
 
* '''New Shortcuts''':
** '''Effects''' - see [[#Highest-rated|Highest-rated]] 
+
** '''Effects'''  
 
** '''Export formats''' {{votes|2}}  
 
** '''Export formats''' {{votes|2}}  
 
** '''File > Export Selected Audio''' {{votes|1}}
 
** '''File > Export Selected Audio''' {{votes|1}}
Line 1,505: Line 1,513:
 
*** '''Open text box to enter exact speed''' for VI users, like gain/pan sliders  {{votes|1}}  
 
*** '''Open text box to enter exact speed''' for VI users, like gain/pan sliders  {{votes|1}}  
 
** '''Navigation and align:'''
 
** '''Navigation and align:'''
*** '''Scroll project horizontally:''' {{votes|8}}  See [http://bugzilla.audacityteam.org/show_bug.cgi?id=187 Bug 187].
+
*** '''Scroll project horizontally by less than screen width:''' {{votesdate|4|07Mar17}}   
 +
**** '''Should simulate mouse click on the horizontal scroll bar arrows:''' {{votesdate|1|07Mar17}}
 
<!---**** '''Reinstate Page Up/Page Down from 1.2''' to scroll forwards/back through the project by the screen width. {{votes|5}} FIXED -->
 
<!---**** '''Reinstate Page Up/Page Down from 1.2''' to scroll forwards/back through the project by the screen width. {{votes|5}} FIXED -->
 
**** '''CTRL + Left and CTRL + Right:''' {{votes|3}} The first press of these could centre on the cursor (or if there was a selection, on left or right edge of selection). Useful for adjusting loop positions.  
 
**** '''CTRL + Left and CTRL + Right:''' {{votes|3}} The first press of these could centre on the cursor (or if there was a selection, on left or right edge of selection). Useful for adjusting loop positions.  
Line 1,519: Line 1,528:
 
<li> '''Edit > Clip boundaries > Align together''' {{votes|1}} align clip boundaries together that are in the middle of a track </ul></ul></ul>
 
<li> '''Edit > Clip boundaries > Align together''' {{votes|1}} align clip boundaries together that are in the middle of a track </ul></ul></ul>
 
* '''Add icons for all shortcuts:''' {{votes|4}} would complement possible new feature for customisable toolbars  
 
* '''Add icons for all shortcuts:''' {{votes|4}} would complement possible new feature for customisable toolbars  
* '''Better default shortcuts''':
+
* '''Zoom:''' CTRL+ + to zoom in, CTRL+ - to zoom out, CTRL+ 0 for zoom normal as per almost every other app {{votes|4}}  
** '''Zoom:''' CTRL+ + to zoom in, CTRL+ - to zoom out, CTRL+ 0 for zoom normal as per almost every other app {{votes|4}}  
+
* '''Time Track Control Points:'''  {{votesdate|1|07Mar17}}
 +
** Set a control point to exactly 100
 +
** Store the value of a control point
 +
** Set a control point to the stored value
 +
 
 
* '''Keyboard Modifiers:'''  
 
* '''Keyboard Modifiers:'''  
 
** '''CTRL + click for selecting multiple objects''' such as tracks, instead of SHIFT + click which is not standard practice {{votes|4}}
 
** '''CTRL + click for selecting multiple objects''' such as tracks, instead of SHIFT + click which is not standard practice {{votes|4}}
Line 1,527: Line 1,540:
 
** '''Add more modifiers to speed up working''' {{votes|1}} for example Sound Forge has shift modifier to move a selection without changing the duration
 
** '''Add more modifiers to speed up working''' {{votes|1}} for example Sound Forge has shift modifier to move a selection without changing the duration
 
<div id="globalshortcuts"></div>
 
<div id="globalshortcuts"></div>
* '''Global shortcuts''' {{votes|43}} that operate Audacity if it does not have focus but don't return focus to Audacity. Not just useful for correcting recording mistakes while in another application (see below). For example, control recording and labelling while working on unrelated tasks.
+
* '''Global shortcuts''' {{votesdate|46|16Jun20}} that operate Audacity if it does not have focus but don't return focus to Audacity. Not just useful for correcting recording mistakes while in another application (see below). For example, control recording and labelling while working on unrelated tasks.
 
{{devcomment|This feature is available cross-platform in wx 3.x (http://trac.wxwidgets.org/ticket/12354).}}
 
{{devcomment|This feature is available cross-platform in wx 3.x (http://trac.wxwidgets.org/ticket/12354).}}
 
<ul><ul><li>'''Multimedia key support''' {{votes|5}}
 
<ul><ul><li>'''Multimedia key support''' {{votes|5}}
Line 1,536: Line 1,549:
 
{{devcomment|Gamers would not be able to start the recording quickly enough.}}   
 
{{devcomment|Gamers would not be able to start the recording quickly enough.}}   
 
<li> '''Shortcuts for buttons more discoverable''' e.g. by Status Bar message or dynamic Tooltip {{votes|5}}</ul>
 
<li> '''Shortcuts for buttons more discoverable''' e.g. by Status Bar message or dynamic Tooltip {{votes|5}}</ul>
 +
 +
*'''Ability to add custom shortcuts to drop down menus:''' Need some kind of ability to add additional shortcuts to drop down menus that can point to the actual menu item for plug-ins.
  
 
<div id="pref"></div>
 
<div id="pref"></div>
Line 1,546: Line 1,561:
 
* '''Devices:'''  
 
* '''Devices:'''  
 
** '''Store separate buffer and latency values per host and device:''' {{votes|3}} Need to decide if necessary to store for separate sample rates too. Need to handle different devices that display with same name such as "USB Audio CODEC".  
 
** '''Store separate buffer and latency values per host and device:''' {{votes|3}} Need to decide if necessary to store for separate sample rates too. Need to handle different devices that display with same name such as "USB Audio CODEC".  
*** '''Extend the not yet implemented idea of [http://forum.audacityteam.org/viewtopic.php?f=56&t=71178 Recording Profiles for multi-channel track allocation]''' to include devices and their settings. {{votes|1}}
+
*** '''Extend the not yet implemented idea of [https://forum.audacityteam.org/viewtopic.php?f=56&t=71178 Recording Profiles for multi-channel track allocation]''' to include devices and their settings. {{votes|1}}
  
 
* '''Directories:'''  
 
* '''Directories:'''  
Line 1,566: Line 1,581:
 
** '''dB level Checkbox for "Normalize all tracks in project" on import:''' {{votes|3}} to be independent of the current level applied via the Normalize effect dialog.  
 
** '''dB level Checkbox for "Normalize all tracks in project" on import:''' {{votes|3}} to be independent of the current level applied via the Normalize effect dialog.  
 
** '''Normalize on export:''' {{votes|3}}   
 
** '''Normalize on export:''' {{votes|3}}   
** '''Reliable MP3 encoding without changing the peak level:''' {{votes|7}} as per [http://bugzilla.audacityteam.org/show_bug.cgi?id=23 bug 23]
+
** '''Reliable MP3 encoding without changing the peak level:''' {{votes|7}} as per [https://bugzilla.audacityteam.org/show_bug.cgi?id=23 bug 23]
 
** '''Explorer integration:'''
 
** '''Explorer integration:'''
 
*** '''Multiple files import into same project''' {{votes|5}}  
 
*** '''Multiple files import into same project''' {{votes|5}}  
 
*** '''Associate with chosen file extensions''' {{votes|5}}
 
*** '''Associate with chosen file extensions''' {{votes|5}}
 
*** '''All open and import are into same project:''' {{votes|2}} less confusing - if you want a file to open a new window, open the window first   
 
*** '''All open and import are into same project:''' {{votes|2}} less confusing - if you want a file to open a new window, open the window first   
** '''Default Open/Import folder and Default Export/Save Folder'''  {{votes|13}} These are always accessed when opening the file dialog.
+
** '''Default Open/Import folder and Default Export/Save Folder'''  {{votesdate|17|08Apr20}} These are always accessed when opening the file dialog.
 
<ul>{{devcomment|If you only ever use one directory Audacity would always open it as it already remembers the last used.}} </ul>
 
<ul>{{devcomment|If you only ever use one directory Audacity would always open it as it already remembers the last used.}} </ul>
 
<ul><ul><li>  '''Default XML import/export directory:''' {{votes|3}} e.g. for Load/Save Metadata templates and Import/Export of EQ curves, rather than use Audacity's data directory. Could remember last directory instead, but shouldn't simply use the same directory as import/export of audio files.   
 
<ul><ul><li>  '''Default XML import/export directory:''' {{votes|3}} e.g. for Load/Save Metadata templates and Import/Export of EQ curves, rather than use Audacity's data directory. Could remember last directory instead, but shouldn't simply use the same directory as import/export of audio files.   
 
<div id="exportsame"></div>  
 
<div id="exportsame"></div>  
<li> '''Export to directory from which original .aup or audio file loaded:''' (like Save Project does). Should apply to all export options (including labels, which should use name of the file, not "labels.txt") and fall back to "last used" directory otherwise. {{votes|36}}
+
<li> '''Export to directory from which original .aup or audio file loaded:''' (like Save Project does). Should apply to all export options (including labels, which should use name of the file, not "labels.txt") and fall back to "last used" directory otherwise. {{votesdate|41|14Mar18}}
 
<li>  '''Export to current directory:''' Much easier for command line users  {{votes|3}}
 
<li>  '''Export to current directory:''' Much easier for command line users  {{votes|3}}
 
<div id="exportsame"></div>
 
<div id="exportsame"></div>
Line 1,589: Line 1,604:
 
<li>  '''Generate/suggest on basis of current metadata''' {{votes|1}}  
 
<li>  '''Generate/suggest on basis of current metadata''' {{votes|1}}  
 
<li>  '''Preserve start-time relative to time zero when exporting''' {{votes|19}} This is needed for exporting offset tracks for multi-track mixing elsewhere.</ul>
 
<li>  '''Preserve start-time relative to time zero when exporting''' {{votes|19}} This is needed for exporting offset tracks for multi-track mixing elsewhere.</ul>
<ul>{{devcomment|This can now be done by generating silence between time zero and the start of the audio, or by exporting a multi-channel file (choose "Use custom mix..." in [http://manual.audacityteam.org/o/man/import_export_preferences.html Import / Export Preferences]).}} </ul>
+
<ul>{{devcomment|This can now be done by generating silence between time zero and the start of the audio, or by exporting a multi-channel file (choose "Use custom mix..." in [https://manual.audacityteam.org/o/man/import_export_preferences.html Import / Export Preferences]).}} </ul>
 
<ul><ul><li>'''Better instead as a checkbox in export dialog''' {{votes|4}}</ul></ul></ul>
 
<ul><ul><li>'''Better instead as a checkbox in export dialog''' {{votes|4}}</ul></ul></ul>
 
<ul><ul>
 
<ul><ul>
Line 1,600: Line 1,615:
 
** '''Placement of new tracks:''' {{votes|13}}  
 
** '''Placement of new tracks:''' {{votes|13}}  
 
*** '''At top''' {{votes|6}}
 
*** '''At top''' {{votes|6}}
*** '''Underneath selected track(s)''' {{votes|7}}
+
*** {{todo}} '''Underneath selected track(s)''' {{votes|7}}
** '''Mixed and Rendered tracks placed at top of project''' {{votes|8}}
+
**** See [[Proposal: Rationalizing where new tracks are created to aid usability and consistency]]
** '''Every new audio track creates its own label track underneath''' {{votes|1}} - requirement for [http://en.wikipedia.org/wiki/DAISY DAISY Books]
+
** <strike>Mixed and Rendered tracks placed at top of project {{votes|8}} </strike>
 +
** <strike> Every new audio track creates its own label track underneath {{votes|1}} - requirement for [http://en.wikipedia.org/wiki/DAISY DAISY Books]</strike>
 
** '''Global font for GUI display''' {{votes|4}}  
 
** '''Global font for GUI display''' {{votes|4}}  
 
** '''"Zoom Normal" level'''. Default 10 seconds too restrictive  {{votes|3}}   
 
** '''"Zoom Normal" level'''. Default 10 seconds too restrictive  {{votes|3}}   
Line 1,614: Line 1,630:
 
* '''Keyboard'''
 
* '''Keyboard'''
 
** '''Click "Command" to sort alphabetically''' {{votes|4}}
 
** '''Click "Command" to sort alphabetically''' {{votes|4}}
** '''Alert User about Keyboard Shortcut conflict''' if the shortcut is already taken, and what is currently set to it. {{votes|1}}
+
** {{done}} '''Alert User about Keyboard Shortcut conflict''' if the shortcut is already taken, and what is currently set to it. {{votes|1}}
<ul>{{devcomment|1=This should already happen - if it doesn't it's [http://bugzilla.audacityteam.org/show_bug.cgi?id=229 Bug 229] - in that case make changes in the "All" category to receive the alert.}}</ul>  
+
<ul>{{devcomment|1=This should already happen - if it doesn't it's [https://bugzilla.audacityteam.org/show_bug.cgi?id=229 Bug 229] - in that case make changes in the "All" category to receive the alert.}}</ul>  
  
 
* '''Meters:'''
 
* '''Meters:'''
 
** '''Reset delay for Recent Peak''' {{votes|1}} so it can fall back sooner than a few seconds after the peak
 
** '''Reset delay for Recent Peak''' {{votes|1}} so it can fall back sooner than a few seconds after the peak
  
 +
 +
<div id="mouse"></div>
 
* '''Mouse:'''
 
* '''Mouse:'''
** '''Configurable bindings'''  {{votes|17}}  
+
** '''Configurable bindings'''  {{votesdate|20|14Sep21}}  
 
** '''Zoom by holding mouse button''' not by continual click
 
** '''Zoom by holding mouse button''' not by continual click
 
** '''Zoom by hovering mouse over pre-defined part of a region''' such as bottom-left {{votes|1}}   
 
** '''Zoom by hovering mouse over pre-defined part of a region''' such as bottom-left {{votes|1}}   
Line 1,648: Line 1,666:
 
** '''Set Timeline zero to system clock time when starting recordings:''' not just for Sound Activated Recording {{votes|7}}
 
** '''Set Timeline zero to system clock time when starting recordings:''' not just for Sound Activated Recording {{votes|7}}
 
** '''Spectrogram Monitoring Before record:'''  {{votes|1}} to monitor the real-time spectrogram display before hitting record and after hitting stop. Especially useful for wildlife recording.
 
** '''Spectrogram Monitoring Before record:'''  {{votes|1}} to monitor the real-time spectrogram display before hitting record and after hitting stop. Especially useful for wildlife recording.
** '''Timer Record Duration''' {{votes|3}} - although Timer Record now remembers its last duration across sessions, a "use default/use last value" preference would allow flexibility to change duration in Timer Record for specific purposes but still have it initialise back to the most commonly required default.
 
 
** '''Default input source''' to be always loaded when Audacity launches irrespective of current system setting {{votes|7}}   
 
** '''Default input source''' to be always loaded when Audacity launches irrespective of current system setting {{votes|7}}   
 
<ul>{{devcomment|would have to apply to Mixer Toolbar or Recording Preferences according to where the OS puts them, and assumes the OS is set to enable the required default.}}</ul>
 
<ul>{{devcomment|would have to apply to Mixer Toolbar or Recording Preferences according to where the OS puts them, and assumes the OS is set to enable the required default.}}</ul>
Line 1,668: Line 1,685:
 
</ul></ul>
 
</ul></ul>
  
=== Non-preference behaviours and other interface modifications===
+
*'''Sync-lock as project stored state:'''  Track linking is well developed and seems stable. Currently its menu item refers to Sync-Lock and its state is ON or OFF. This is stored as a global preference and ON/OFFness affects all projects. Thus, if you work on project A with sync ON and save it then work on project B with sync OFF (and even if you DO NOT save project B) then exit Audacity. then open project A, sync will be OFF even though the last time you worked on project A sync was ON.  I propose that (at a minimum) Sync-Lock state be stored with a project. keep the global state and use it in the absence of a project's having a sync state and for new empty projects. otherwise toggle sync to match the project's stored state when a project is opened (maybe if doing so changes the application-wide sync state an info dialog could open (but that should be defeatable via prefs).  In addition, currently if one has multiple projects open and toggles Sync-Lock in one project ALL project's sync is toggled. It might be a lot of work to implement, but I think it would be nice to have per-project sync. {{votes|5}}
 +
 
 +
*'''Editing audacity.cfg:''' Proposed Feature:  An "advanced" option - possibly hidden away in Preferences - providing quick access to the audacity.cfg for manual editing.  Possible implementations could be:  1) to open the audacity.cfg file in the default text editor,  2) to open the audacity.cfg file with an option to "open with ...",  3) to open the containing folder in a browser window.  This feature could also include "reset" and "backup" options.
  
 +
=== Non-preference behaviors and other interface modifications===
 
* '''Play selected tracks''' rather than choosing tracks to play by mute/solo. If allied with buffering changes might help smooth playback of a few tracks out of many (muting the others only helps playback marginally). Also avoids danger in 2.x of unintentionally muting tracks at export.  {{votes|1}}     
 
* '''Play selected tracks''' rather than choosing tracks to play by mute/solo. If allied with buffering changes might help smooth playback of a few tracks out of many (muting the others only helps playback marginally). Also avoids danger in 2.x of unintentionally muting tracks at export.  {{votes|1}}     
  
 
* '''Cut Preview:'''
 
* '''Cut Preview:'''
 
** '''Plays all selected or Sync-Lock Selected tracks''' ignoring mute/solo {{votes|4}}  
 
** '''Plays all selected or Sync-Lock Selected tracks''' ignoring mute/solo {{votes|4}}  
** '''Previews the mix''' respecting Mute and Solo, and ignoring track selectedness {{votes|2}}  
+
** '''Previews the mix''' respecting Mute and Solo, and ignoring track selectedness {{votesdate|3|20Aug18}}  
 
** '''If no selection, play centered on the cursor position''' (and rename feature if needed) {{votes|3}}  
 
** '''If no selection, play centered on the cursor position''' (and rename feature if needed) {{votes|3}}  
  
Line 1,694: Line 1,714:
 
* '''Allow minimize/maximize/restore/move of window during operations (import, export, effects, etc.)'''{{votes|1}}
 
* '''Allow minimize/maximize/restore/move of window during operations (import, export, effects, etc.)'''{{votes|1}}
  
* (OS X) '''Support for Macs with [http://en.wikipedia.org/wiki/Retina_Display Retina Display]:''' {{votes|16}} Believed to be a lack of support in wxWidgets. You can apply [http://retinizer.mikelpr.com/ Retinizer] to Audacity but this makes it impossible to change the export format inside Audacity.
 
 
<div id="noclipping"></div>
 
<div id="noclipping"></div>
 
* '''One-step way to avoid clipping on multiple tracks:''' {{votes|30}}
 
* '''One-step way to avoid clipping on multiple tracks:''' {{votes|30}}
** '''Master Fader ability:''' {{votes|26}}  
+
** '''Master Fader ability:''' {{votesdate|27|29Jul18}}  
 
*** '''Separate mixing window (like Mixer Board but with a "Master-Fader" control):'''  {{votes|7}}
 
*** '''Separate mixing window (like Mixer Board but with a "Master-Fader" control):'''  {{votes|7}}
 
*** '''Shortcut that moves all gain sliders by same amount''' {{votes|8}}
 
*** '''Shortcut that moves all gain sliders by same amount''' {{votes|8}}
Line 1,706: Line 1,725:
 
<ul><ul><li> The target level should be calculated from all unmuted tracks but applied to all tracks. {{votes|1}}
 
<ul><ul><li> The target level should be calculated from all unmuted tracks but applied to all tracks. {{votes|1}}
 
<li>'''Must be non-destructive''', that is not modify the waveform data or its visible height {{votes|2}}</ul></ul></ul>
 
<li>'''Must be non-destructive''', that is not modify the waveform data or its visible height {{votes|2}}</ul></ul></ul>
 
<div id="betterupdate"></div>
 
* '''Better ability to update''' {{votes|45}}
 
** '''Automatic push of updated versions at launch''' {{votes|15}}
 
** '''User-initiated menu item to advise if version is current''' but '''not''' automatic updates {{votes|30}}
 
<ul>{{devcomment|Feel free to vote. The developers are currently [http://n2.nabble.com/LAME-Installer-for-Windows-td256060i20.html#a256068 not keen] on Audacity querying servers directly due to the complexity and especially security, especially in a cross-platform application. However a Windows feature to go to a web page giving user's version and current version is [[Proposal Update Checking|under consideration]]. }}</ul>
 
  
 
<div id="appearance"></div>
 
<div id="appearance"></div>
 
* '''Too utilitarian/outdated/generic in appearance/hard to customise'''. {{votes|51}} (generalised comments only) {{devcomment|1=See [http://audacityteam.org/forum/viewtopic.php?f=21&t=657 this Forum topic] for some suggested new skins/logo}}
 
* '''Too utilitarian/outdated/generic in appearance/hard to customise'''. {{votes|51}} (generalised comments only) {{devcomment|1=See [http://audacityteam.org/forum/viewtopic.php?f=21&t=657 this Forum topic] for some suggested new skins/logo}}
 
<ul><ul><li> As with Windows, there should be an easy way to revert to the "Audacity Classic" look
 
<ul><ul><li> As with Windows, there should be an easy way to revert to the "Audacity Classic" look
<li>'''Mac version should look more like Mac software:''' {{votes|6}} important for Mac users that our software is unified. All the knobs, buttons, sliders should use the standard Aqua interface instead of the current Windows 95 look. If it has to be done with Themes, then do it
 
 
<li>'''Audacity should look completely native on all platforms''' {{votes|1}}  
 
<li>'''Audacity should look completely native on all platforms''' {{votes|1}}  
 
<li>Icon too low resolution: looks poor at 32 x 32 or higher  {{votes|4}}  </ul></ul>
 
<li>Icon too low resolution: looks poor at 32 x 32 or higher  {{votes|4}}  </ul></ul>
 
<div id="smoothscrolling"></div>
 
* '''Smoother Track scrolling on Playback:''' {{votes|31}}  Keep the cursor in one place but move the track - gives smooth visual playback without continual cursor back and forth
 
** '''As selectable option which is on by default in case of slower systems.''' {{votes|2}}
 
** '''Or still allow cursor to move, but scroll smoothly when it reaches about 15% from the right and place cursor 15% from left''' {{votes|1}}.
 
** '''Also during recording.''' {{votes|1}}
 
{{note|We have implemented (optional and switchable) Fixed-head playback and recording for 2.1.3
 
{{ednote|'''Peter 01Feb17:''' [[ToDo-1]] which means that we should be able to move this to [[Completed Features]] }} }}
 
  
 
* '''Proper support for Windows [http://en.wikipedia.org/wiki/Remote_Desktop_Protocol Remote Desktop Protocol]''' including audio transfer. {{votes|9}} Other audio applications like CoolEditPro (as was) handle playback audio over RDP. Use case is examining the files, or chopping into smaller ones for local use without bringing the whole file over from the host.  
 
* '''Proper support for Windows [http://en.wikipedia.org/wiki/Remote_Desktop_Protocol Remote Desktop Protocol]''' including audio transfer. {{votes|9}} Other audio applications like CoolEditPro (as was) handle playback audio over RDP. Use case is examining the files, or chopping into smaller ones for local use without bringing the whole file over from the host.  
Line 1,732: Line 1,736:
 
* '''Automatic Crossfading''' {{votes|15}}  
 
* '''Automatic Crossfading''' {{votes|15}}  
 
** see [[Proposal Crossfade]] for how the developers think it might work
 
** see [[Proposal Crossfade]] for how the developers think it might work
** Might this may lack something in flexibility? If the above does not let you choose the overlap region, define it by dragging, then apply cross-fade. Include ability to find an achieved cross fade again and stretch/contract or move the region.
+
** Might this may lack something in flexibility? If the above does not let you choose the overlap region, define it by dragging, then apply crossfade. Include ability to find an achieved cross fade again and stretch/contract or move the region.
 
** Needs more subtle automation for an already beat-matched mix - you don't want to slide it around again. Suggest using a separate crossfade track that preserves beat matching and lets you play with the best place to do the crossfade. The crossfade track would show graphically what percentage of each of two tracks were contributing to the playback, and simple controls would allow the user to set the levels in straight-line segments and slide those segments around.  So, in my case, I would have 100% track 1 for a while, then a short ramp to 100% track 2, and the ramp could be slid in time. You could even have some pre-defined crossfade tracks as a starting point.
 
** Needs more subtle automation for an already beat-matched mix - you don't want to slide it around again. Suggest using a separate crossfade track that preserves beat matching and lets you play with the best place to do the crossfade. The crossfade track would show graphically what percentage of each of two tracks were contributing to the playback, and simple controls would allow the user to set the levels in straight-line segments and slide those segments around.  So, in my case, I would have 100% track 1 for a while, then a short ramp to 100% track 2, and the ramp could be slid in time. You could even have some pre-defined crossfade tracks as a starting point.
{{ednote|'''Peter 30Jan17:''' [[ToDo-1]] Do Steve's Crossfade Tracks and Crossfade Clips satisfy this FRs for auto-fade? }}
 
  
 
* '''Clarify distinction between Save Project and Export audio file'''  {{votes|6}}
 
* '''Clarify distinction between Save Project and Export audio file'''  {{votes|6}}
Line 1,771: Line 1,774:
 
*  '''Scroll with the Mac Mighty Mouse or [http://en.wikipedia.org/wiki/Scrolling_TrackPad TrackPad]:''' (including two-finger TrackPad scroll left/right, up/down and pinch in/out zoom gestures, as recently added to Finale). {{votes|26}}  
 
*  '''Scroll with the Mac Mighty Mouse or [http://en.wikipedia.org/wiki/Scrolling_TrackPad TrackPad]:''' (including two-finger TrackPad scroll left/right, up/down and pinch in/out zoom gestures, as recently added to Finale). {{votes|26}}  
 
** '''Allow to scroll left/right with mouse ball/wheel without SHIFT on Windows too''' {{votes|5}}  
 
** '''Allow to scroll left/right with mouse ball/wheel without SHIFT on Windows too''' {{votes|5}}  
<ul>{{devcomment|1=This "may" or may not be possible when Audacity updates to wxWidgets 2.9 - see this [http://forum.audacityteam.org/viewtopic.php?f=17&t=12139#p47616 Forum thread].}}</ul>
+
<ul>{{devcomment|1=This "may" or may not be possible when Audacity updates to wxWidgets 2.9 - see this [https://forum.audacityteam.org/viewtopic.php?f=17&t=12139#p47616 Forum thread].}}</ul>
  
* '''Scroll with the middle-mouse button''': {{votes|1}} This should work like panning with the middle mouse button in Gimp, or panning in Google Maps, to make it easier to scroll in small amounts when working with long tracks.
+
* '''Scroll with the middle-mouse button''': {{votesdate|14|08Feb19}} This should work like panning with the middle mouse button in Gimp, or panning in Google Maps, to make it easier to scroll in small amounts when working with long tracks.
  
 
* '''Drag windows by bottom bar as on OS X''' {{votes|1}}   
 
* '''Drag windows by bottom bar as on OS X''' {{votes|1}}   
Line 1,792: Line 1,795:
  
 
* '''Use GTK+ for GUI''' for more "native" colors/icons/controls. Could use GTK+ [http://library.gnome.org/devel/gtk/2.21/gtk-Stock-Items.html stock items] or ask them for custom widgets {{votes|2}}
 
* '''Use GTK+ for GUI''' for more "native" colors/icons/controls. Could use GTK+ [http://library.gnome.org/devel/gtk/2.21/gtk-Stock-Items.html stock items] or ask them for custom widgets {{votes|2}}
 +
 +
*'''Track name with tooltip:'''  Invariably my track names display only the least significant bits – the first few letters – usually it's the trailing letters that are unique. Wouldn't it be nice if when one hovers the mouse over the track name a tooltip bubble would open displaying the entire track name.
 +
 +
===Selections===
 +
*'''Change color of waveform when selected, not just the waveform background.''' This would improve the visibility of the selected region, especially when editing high amplitude, highly compressed audio and full scale test tones. ([https://forum.audacityteam.org/viewtopic.php?f=20&t=104325 forum discussion]) {{votesdate|4|27Oct19}}
 +
*'''Under Edit > Select, I would like to see more choices than just 'All' or everything fore or aft of the cursor.''' It would be neat if in that same area a list of all my markers came up so I could also choose something like 'Cursor to Markername'. And/or select Cursor to ... then flyouts to Label Track(s) > Markername(s). This would really help when recording albums and you now want to split the songs quickly. Other selection features maybe cursor to allow more than one cursor? Or something like 'splices'. Splices could be set in just like markers? Then a script could run for batch exports. I'm just thinking I could set all these splice markers, then click Export > Splices, then either one dialog for batch naming the files (I would edit the tags later individually later) or the dialog comes up with each splice and I edit all names and tags as processes.
 +
*'''Add Select All to label text context dropdown menu:'''Since ctrl+a does not work to select all the text in a label (it selects everything in the project) and since we are ready have Cut, Copy and Paste in the context menu
  
 
==Recording Enhancements==
 
==Recording Enhancements==
 +
<div id="punch"></div>
 
===Punch-in===
 
===Punch-in===
<div id="punch"></div>
+
* '''Non-destructive punch:''' {{votes|20}} some idea like Audition punch in that allows you to store multiple punch-in takes, or ProTools Non-Destructive Record.
* '''"Punch-in and punch-out" recording:''' {{votes|79}} - one of
+
{{ednote|1= '''Steve:''' We need to distinguish between "destructive" and "non-destructive" punch-in recording. New users often mean destructive punch-in recording (like with a tape recorder), but this is '''''an extraordinarily bad idea'''''. More advanced users generally mean non-destructive punch-in (like other DAW applications). Non-destructive punch-in recording would be very much harder to implement as it requires building in the concepts of "virtual tracks" and "track groups" into Audacity, which do not currently exist. I would be very much in favour of non-destructive punch-in recording but very strongly opposed to destructive punch-in.}}
** '''Not further specified or "destructive":''' {{votes|59}}  - a quick destructive punch that changes the existing audio data in the track, usually overwriting a section of it, but can also refer to inserting a new recording after the cursor rather than replacing any of the existing recording.
 
<ul>{{devcomment|While convenient, this is not as flexible as recording on another track, which lets you adjust the timeline position of the new recording precisely (once made) then cross-fade it so it sounds seamless.}}
 
<ul><li> '''Non-destructive punch:''' {{votes|20}} some idea like Audition punch in that allows you to store multiple punch-in takes, or ProTools Non-Destructive Record.
 
<ul><li> '''Punch-in needs pre-roll:''' {{votes|11}} "With punch and roll, I would pause the recording when I made an error, use the mouse to select an insertion point.  Then I would hit a shortcut key that automatically gave me 3-5 seconds of pre-roll playback to hear my lead in, then shifts to record mode at the insertion point. This is just three commands: pause, insert point, function key. The fewer keystrokes, the more efficient."
 
<ul><li> '''Pre-roll only needed when overdubbing''' {{votes|7}}</ul></ul></ul>
 
{{ednote|1= '''Steve:''' We need to distinguish between "destructive" and "non-destructive" punch-in recording. New users often mean destructive punch-in recording (like with a tape recorder), but this is '''''an extraordinarily bad idea'''''. More advanced users generally mean non-destructive punch-in (like other DAW applications). Non-destructive punch-in recording would be very much harder to implement as it requires building in the concepts of "virtual tracks" and "track groups" into Audacity, which do not currently exist. I would be very much in favour of non-destructive punch-in recording but very strongly opposed to destructive punch-in.
 
*'''Gale:''' Thanks, Steve. I have now split the votes as I can best determine and added yours and Koz's vote for "non-destructive". I'd still like to be clearer why user could not undo the punch-in if it was bad; and if they re-recorded into the same selection repeatedly, they can then cycle through the undo stack to pick the "best" take. Of course they have more potential hassle with the transitions. Why is append-record or generating at the cursor point in the middle of a track not bad? Can we force the recording cursor to start from a zero crossing? Of course another (easier to implement) approach might to leave the recording in its own track and have a one-click cross fade.
 
**'''Steve:''' Append Record in not a problem because it is single ended. If the "join" does not match up exactly then it's a simple matter to edit it. On the other hand a punch-in recording needs to fit precisely into a pre-defined "hole". I have posted a more comprehensive reply on the forum. http://forum.audacityteam.org/viewtopic.php?p=199384#p199384
 
}}
 
  
 
===Multi-channel/multi-device issues===
 
===Multi-channel/multi-device issues===
 +
<div id="nonconsecutiveinput"></div>
 +
* '''Choose which of multiple channels to record'''. {{votesdate|+54|29Dec18}}.
 +
** Allows not to waste space/time recording and closing unwanted channels e.g. S/PDIF which is often only on the highest numbered channels.
 +
** Allows flexibility to use mixed non-consecutive channels for special purposes. For example, Alesis MultiMix-8 returns its mixed outputs, which is the only outlet for its on-board effects, on channels 9 and 10. It would be useful to record low-numbered  channels for instruments or and mics, while mixing in onboard effects.
 +
{{Hint|Some suggestions for applying effects 'as you record' have been moved to the effects section.}}
 +
 
<div id="multisound"></div>
 
<div id="multisound"></div>
 
* '''Record from multiple sound devices at once''' {{votes|39}}  
 
* '''Record from multiple sound devices at once''' {{votes|39}}  
Line 1,818: Line 1,826:
 
<li> '''Allow multiple input devices with broad definitions''' that would each be added to device toolbar and each individually defined.  One could be from a PCI card's input mic port, another from that same card's output speaker port, and another from a USB card's input mic port. Thus eliminating the need to rely on expensive professional multichannel hardware / drivers or stereo mix drivers. {{votes|2}}</ul></ul>
 
<li> '''Allow multiple input devices with broad definitions''' that would each be added to device toolbar and each individually defined.  One could be from a PCI card's input mic port, another from that same card's output speaker port, and another from a USB card's input mic port. Thus eliminating the need to rely on expensive professional multichannel hardware / drivers or stereo mix drivers. {{votes|2}}</ul></ul>
  
<div id="nonconsecutiveinput"></div>
+
* '''Allocate specific recording channels to specific Audacity tracks:''' {{votes|18}}
* Allow '''nonconsecutive set of input channels''' to be selected e.g. to deal with devices that send special outputs on the higher numbered channels. For example, Alesis's MultiMix-8 returns its mixed outputs, which is the only outlet for its on-board effects, on channels 9 and 10. A common setup for me is to use channels 1-3 for instruments and mics, and mix in some effects from the Alesis unit; I'd like to have Audacity record channels 1,2,3,9,10 instead of 1 through 10.{{votes|23}}
 
 
 
{{Hint|See also [[#Highest-rated|Highest-rated]] (not cross referenced).
 
:Find "Record from multiple sound devices at once"}}
 
{{Hint|Some suggestions for applying effects 'as you record' have been moved to the effects section.}}
 
 
 
* '''Allocate specific channels to specific Audacity tracks:''' {{votes|18}}
 
  
 
* '''Detect newly added or removed device automatically:''' {{votes|5}}  
 
* '''Detect newly added or removed device automatically:''' {{votes|5}}  
  
 +
* '''Template with any number of stacked NAMED tracks:''' dropdown menu should allow us to choose any of the N-channels of the attached device (e.g., 16 for a Mackie 1640i). Once template is created and saved, RECORD should launch an instance of this template and record those channels. Each time RECORD is invoked, another instance of the template would start below those already done. In this way the user interface would look mostly as now, but would add the multitrack capability. {{votes|3}}
  
** '''Template with any number of stacked NAMED tracks:''' dropdown menu should allow us to choose any of the N-channels of the attached device (e.g., 16 for a Mackie 1640i). Once template is created and saved, RECORD should launch an instance of this template and record those channels. Each time RECORD is invoked, another instance of the template would start below those already done. In this way the user interface would look mostly as now, but would add the multitrack capability. {{votes|3}}
+
* '''Per-channel recording metering:''' {{votesdate|16|13Mar21}} - Multi-channel recording requires one meter channel for each channel being recorded. Also waveform display while recording is lagged and arrives in steps rather than being continuous.  
 
 
* '''Per-channel recording metering:''' {{votes|13}} - Multi-channel recording requires one meter channel for each channel being recorded. Also waveform display while recording is lagged and arrives in steps rather than being continuous.  
 
 
 
 
** Must be a reasonable length as in other multi-channel recording apps.  Could use Mixer Board metering for record as well as playback, with main recording meter showing levels for "mix" of all channels. As second best, the main meters could be switchable from channels 1+2 / 3+4 / 5+6 / 7+8 (up to the number of channels set in Preferences). A problem is that Mixer Board is a separate window that takes focus from the main window, so does not accept shortcuts. If meters are vertical, that makes Mixer Board wider so encourages keeping it as a separate window  {{votes|1}}
 
** Must be a reasonable length as in other multi-channel recording apps.  Could use Mixer Board metering for record as well as playback, with main recording meter showing levels for "mix" of all channels. As second best, the main meters could be switchable from channels 1+2 / 3+4 / 5+6 / 7+8 (up to the number of channels set in Preferences). A problem is that Mixer Board is a separate window that takes focus from the main window, so does not accept shortcuts. If meters are vertical, that makes Mixer Board wider so encourages keeping it as a separate window  {{votes|1}}
  
Line 1,839: Line 1,838:
 
<div id="sar"></div>
 
<div id="sar"></div>
 
* '''Sound Activated Recording (SAR)'''
 
* '''Sound Activated Recording (SAR)'''
** '''Pre- and post-roll duration:''' {{votes|50}}  define a duration to be recorded before the threshold-level sound occurs, and similarly a duration to be recorded after the input falls back below the threshold. Requires buffering of the recording for pre-roll, but is expected behaviour for this type of tool.  
+
** '''Pre- and post-roll duration:''' {{votesdate|56|22Jul20}}  define a duration to be recorded before the threshold-level sound occurs, and similarly a duration to be recorded after the input falls back below the threshold. Requires buffering of the recording for pre-roll, but is expected behaviour for this type of tool.  
** '''Post-roll (say 4 seconds) on its own:''' {{votes|6}} For example this would allow realistic recording of dialog - it may be sufficient or easier to implement  
+
** '''Post-roll (say 4 seconds) on its own:''' {{votesdate|10|19Apr20}} For example this would allow realistic recording of dialog - it may be sufficient or easier to implement  
 
** '''Post roll of up to 5 minutes on its own for radio recording''' {{votes|2}}  
 
** '''Post roll of up to 5 minutes on its own for radio recording''' {{votes|2}}  
 
** '''Ignore silent periods''' option with configurable interval {{votes|4}} (Use cases: archiving tapes in their entirety complete with inter-track gaps; starting a recording on sound detection then recording until manually stopped irrespective of level)  
 
** '''Ignore silent periods''' option with configurable interval {{votes|4}} (Use cases: archiving tapes in their entirety complete with inter-track gaps; starting a recording on sound detection then recording until manually stopped irrespective of level)  
 
<ul>{{devcomment|Probably can be done in the post-roll? If the post-roll period was active when the level rose above the threshold again, recording would resume.}}   
 
<ul>{{devcomment|Probably can be done in the post-roll? If the post-roll period was active when the level rose above the threshold again, recording would resume.}}   
 
<ul><li> '''Continue to record silence where input falls below the Sound Activation Level''' {{votes|1}} This makes the recording continuous (e.g. keeping it synced with video that was being recorded at the same time) but makes cleanly separated segments where recording was above the threshold.  
 
<ul><li> '''Continue to record silence where input falls below the Sound Activation Level''' {{votes|1}} This makes the recording continuous (e.g. keeping it synced with video that was being recorded at the same time) but makes cleanly separated segments where recording was above the threshold.  
<li> '''Segment each recording event''' {{votes|20}}
+
<li> '''Segment each recording event''' {{votesdate|21|14Mar17}}
<ul><li> with labels {{votes|15}} - labels could contain either the length of preceding pause, or date and time when recording started/resumed  
+
<ul><li> with labels {{votesdate|16|14Mar17}} - labels could contain either the length of preceding pause, or date and time when recording started/resumed  
 
<li> with clip lines {{votes|1}}</ul>
 
<li> with clip lines {{votes|1}}</ul>
 
<li> '''Report system clock times for each recording event (other than in labels):''' {{votes|9}}  
 
<li> '''Report system clock times for each recording event (other than in labels):''' {{votes|9}}  
Line 1,859: Line 1,858:
  
 
* '''Off-Tape Monitor:''' True off-Tape Monitor while recording or 'What you Hear is What you've got'. When Recording the playback is taken from the data stored on the Hard drive and passed through the entire audio chain with a suitable delay (say 100+ ms) so it's obvious you're not listening to the input. This is ideal for high quality spoken word recordings.
 
* '''Off-Tape Monitor:''' True off-Tape Monitor while recording or 'What you Hear is What you've got'. When Recording the playback is taken from the data stored on the Hard drive and passed through the entire audio chain with a suitable delay (say 100+ ms) so it's obvious you're not listening to the input. This is ideal for high quality spoken word recordings.
 
<div id="timer_record"></div>
 
<ul><li>'''Timer Record:'''<br/>Many of the below requests could be implemented (I think) by enabling automation support for [[Automation#Scriptability|tcp/unix sockets]]
 
<div id="multievent"></div>
 
<ul><li> '''Multi-event scheduler''' {{votes|29}} for future recordings (like a VCR), not just scheduling a single recording for now
 
<ul><li> '''Record multiple streams at once if desired recordings overlap''' {{votes|2}}
 
</ul>
 
<li> '''Access to progress or record controls:'''
 
<ul><li> '''Both dialogs should be modeless for current project, allowing access to same controls available during standard recording''' {{votes|16}} This lets you change levels, pause manually, drop a label, zoom in/out or resize tracks, plus it lets Audacity on Windows be minimised while Timer Record is in progress.   
 
<li> '''Waiting for Start dialog should be modeless for all (or at least, other) projects:''' {{votes|5}} allowing to work normally until recording starts </ul>
 
{{devcomment|This raises all manner of issues about what happens if user is in the middle of playing / exporting when recording is due to start.<p>'''Peter 15Mar16:''' My PVR deals with this by giving me a ten and five minute warning of a scheduled recording or channel change. If I ignore it the recording or channel change takes precedence at the prescribed time.</p>}}
 
<ul><li> '''Change/extend recording stop time during record or waiting to record''' {{votes|4}}
 
<li> '''Stop a manually started recording automatically''' {{votes|2}} by extending recording stop time in Timer Record - use case "something unexpected makes me have to go out" </ul>
 
{{devcomment|Could be considered user error not to have started Timer Record in the first place, though lack of access during Timer Record might be discouraging its use. However this requires more menu access than is currently allowed during recording. Can be achieved if user scripts a scheduled task before leaving, or it "would" be possible with [http://sourceforge.net/projects/audaremote/ Audaremote] on Windows except it does not recognise the Audacity 2.x window title.}} 
 
<ul><li> '''Some method to close the timer''' without stopping it - Cancel? {{votes|2}} </ul>
 
<li>'''More intuitive/simpler timer controls:''' {{votes|18}}:
 
<ul><li>'''Type any hour before present time to stop timer/advance date:''' {{votes|5}} instead of input before present time being unintuitively ignored.
 
<li> '''Recall last used date/times''' to start recording on a daily basis {{votes|8}}
 
<li>'''Simple set of independent combo boxes for start and end''' {{votes|2}} having month, day (both pre-selected), hour, minute and seconds.
 
<li>'''More like a hardware timer:''' {{votes|3}} Get rid of "Duration" and "Dates" as editable controls and get rid of interlinking of start and end time </ul>
 
{{devcomment|Needs thought - the basic suggestion of "type an hour before present to advance date" (applied on top of current implementation) would only work well for advancing date by one day and moving only one of either Start Date or End Date. Maybe disallow typing in spinboxes to make it more obvious that incrementing already works like a hardware timer. This may imply not using TimeText spinboxes at all or modifying how they work.}}
 
<li> '''Perform system shutdown after recording''' {{votes|9}}
 
<li> '''Schedule computer to turn on for recording from within Audacity, as well as shutdown:''' {{votes|5}}
 
<li> '''Save/export on completion:'''
 
<ul><li> to a pre-defined project name/location set in an in-situ dialog {{votes|6}}
 
<li> to a pre-defined audio file name/format and location set in an in-situ dialog {{votes|8}}
 
<li> export file name in date and time form {{votes|3}}
 
<li> option '''not''' to autosave {{votes|5}}
 
<li> export at given periods during the scheduled recording {{votes|3}}
 
<li>also close the track or project on completion {{votes|1}}
 
</ul>
 
<li> '''"Waiting for Start" dialog enhancements:'''
 
<ul><li>'''Add duration and scheduled stop time''' {{votes|2}}
 
<li> '''Rename "Remaining Time"''' to "Recording will commence in: hh:mm:ss" {{votes|2}}
 
<li> '''Remove "Elapsed Time" and Progress Bar''' {{votes|2}}</ul>
 
<li> (Windows) '''Minimise Audacity while Timer Record in progress''' {{votes|7}}
 
<li> '''Disconnect internet stream as well as stop the recording'''  {{votes|2}}
 
<li> '''Pick URL to record from:''' {{votes|2}} 
 
</ul></ul>
 
  
 
* '''New Loop Record''' feature: records while loop-playing a selection region in other tracks.    {{votes|1}}     
 
* '''New Loop Record''' feature: records while loop-playing a selection region in other tracks.    {{votes|1}}     
Line 1,949: Line 1,909:
 
** '''Audacity should block DC at source''' because of the problems it causes. DC is not sound, and passing DC should only be a fringe purpose for scientists/researchers.  {{votes|2}}  
 
** '''Audacity should block DC at source''' because of the problems it causes. DC is not sound, and passing DC should only be a fringe purpose for scientists/researchers.  {{votes|2}}  
 
<ul>{{devcomment|Blocking DC at source raises technical issues which we may well not want to address.}}</ul>
 
<ul>{{devcomment|Blocking DC at source raises technical issues which we may well not want to address.}}</ul>
 +
 +
===Timer Record enhancements===
 +
<div id="timer_record"></div>
 +
Many of the below requests could be implemented (I think) by enabling automation support for [[Automation#Scriptability|tcp/unix sockets]]
 +
<div id="multievent"></div>
 +
*'''Multi-event scheduler''' {{votesdate|32|27Mar20}} for future recordings (like a VCR), not just scheduling a single recording for now
 +
 +
*'''More intuitive/simpler timer controls:''' {{votes|18}}:
 +
**'''Type any hour before present time to stop timer/advance date:''' {{votes|5}} instead of input before present time being unintuitively ignored.
 +
** '''Recall last used date/times''' to start recording on a daily basis {{votes|8}}
 +
**'''Simple set of independent combo boxes for start and end''' {{votes|2}} having month, day (both pre-selected), hour, minute and seconds.
 +
**'''More like a hardware timer:''' {{votes|3}} Get rid of "Duration" and "Dates" as editable controls and get rid of interlinking of start and end time
 +
{{devcomment|Needs thought - the basic suggestion of "type an hour before present to advance date" (applied on top of current implementation) would only work well for advancing date by one day and moving only one of either Start Date or End Date. Maybe disallow typing in spinboxes to make it more obvious that incrementing already works like a hardware timer. This may imply not using TimeText spinboxes at all or modifying how they work.}}
 +
 +
* '''Access to progress or record controls:''' {{votesdate|18|27Mar20}}
 +
** '''Both dialogs should be modeless for current project, allowing access to same controls available during standard recording''' {{votes|16}} This lets you change levels, pause manually, drop a label, zoom in/out or resize tracks, plus it lets Audacity on Windows be minimised while Timer Record is in progress.   
 +
** '''Waiting for Start dialog should be modeless for all (or at least, other) projects:''' {{votes|5}} allowing to work normally until recording starts
 +
{{devcomment|This raises all manner of issues about what happens if user is in the middle of playing / exporting when recording is due to start.<p>'''Peter 15Mar16:''' My PVR deals with this by giving me a ten and five minute warning of a scheduled recording or channel change. If I ignore it the recording or channel change takes precedence at the prescribed time.</p><p>'''Peter 04Feb17:'''Mark Young has dealt with this in 2.1.3 by ensuring that for Timer Record the user must have that sole project open.  No other projects can be open when setting up a Timer Record - and none can be opened after the Timer Record is set up.</p> }}
 +
 +
* '''Change/extend recording stop time during record or waiting to record''' {{votes|4}}
 +
* '''Stop a manually started recording automatically''' {{votes|2}} by extending recording stop time in Timer Record - use case "something unexpected makes me have to go out" </ul>
 +
{{devcomment|Could be considered user error not to have started Timer Record in the first place, though lack of access during Timer Record might be discouraging its use. However this requires more menu access than is currently allowed during recording. Can be achieved if user scripts a scheduled task before leaving, or it "would" be possible with [http://sourceforge.net/projects/audaremote/ Audaremote] on Windows except it does not recognise the Audacity 2.x window title.}} 
 +
* '''Some method to close the timer''' without stopping it - Cancel? {{votes|2}}
 +
* '''Record multiple streams at once if desired recordings overlap''' {{votes|2}}
 +
 +
<ul><li> '''Perform system shutdown after recording''' {{votes|9}}
 +
<li> (Windows) '''Minimise Audacity while Timer Record in progress''' {{votes|7}}
 +
<li>  '''Schedule computer to turn on for recording from within Audacity, as well as shutdown:''' {{votes|5}}
 +
<li>  '''Timer Record Duration''' {{votes|3}} - although Timer Record now remembers its last duration across sessions, a "use default/use last value" preference would allow flexibility to change duration in Timer Record for specific purposes but still have it initialise back to the most commonly required default.
 +
<li>  '''Pick URL to record from:''' {{votes|2}}
 +
<li>  '''On completion, disconnect the  internet stream as well as stop the recording'''  {{votes|2}}
 +
 +
 +
<li> <font color=gray><strike>'''Save/export on completion:''' </strike></font> - ''these are implemented for Audacity 2.1.3''
 +
<ul><li> <font color=gray><strike>to a pre-defined project name/location set in an in-situ dialog {{votes|6}}</strike></font>
 +
<li> <font color=gray><strike>to a pre-defined audio file name/format and location set in an in-situ dialog {{votes|8}}</strike></font>
 +
<li> <font color=gray><strike>export file name in date and time form {{votes|3}}</strike></font>
 +
<li> <font color=gray><strike>option '''not''' to autosave {{votes|5}} </strike></font>
 +
<li> <font color=gray><strike>export at given periods during the scheduled recording {{votes|3}} </strike></font>
 +
<li> <font color=gray><strike>also close the track or project on completion {{votes|1}}</strike></font>
 +
 +
</ul>
 +
<li> <font color=gray><strike>'''"Waiting for Start" dialog enhancements:'''</strike></font> ''these are implemented for Audacity 2.1.3, with the exception that the progess bar remains and will remain''
 +
<ul><li><font color=gray><strike>'''Add duration and scheduled stop time''' {{votes|2}}</strike></font>
 +
<li> <font color=gray><strike>'''Rename "Remaining Time"''' to "Recording will commence in: hh:mm:ss" {{votes|2}}</strike></font>
 +
<li> <font color=gray><strike>'''Remove "Elapsed Time" and Progress Bar''' {{votes|2}}</ul></strike></font> 
 +
</ul></ul>
  
 
== Playback Enhancements ==
 
== Playback Enhancements ==
 
<div id="autosync"></div>
 
<div id="autosync"></div>
 
* '''Synchronize recorded/played back tracks automatically''' without Time Shift tool or Preferences adjustment, for example using MTC/SMPTE with Audacity either as Master or Slave {{votes|71}}
 
* '''Synchronize recorded/played back tracks automatically''' without Time Shift tool or Preferences adjustment, for example using MTC/SMPTE with Audacity either as Master or Slave {{votes|71}}
 +
  
 
<div id="multi"></div>
 
<div id="multi"></div>
* '''Multi-channel playback''' {{votes|77}}
+
* '''Multi-channel playback''' {{votesdate|84|08July17}}
 
** mix down to '''Dolby''' 5.1, 7.1, 10.2, 64.4 etc. or standard old-fashioned electroacoustic 4 and 8 channel circular arrays){{votes|2}}
 
** mix down to '''Dolby''' 5.1, 7.1, 10.2, 64.4 etc. or standard old-fashioned electroacoustic 4 and 8 channel circular arrays){{votes|2}}
** Should include a patch panel to define routing of multi-channel audio to specific channels of a multi-channel device.{{votes|5}}
+
** Should include a patch panel to define routing of multi-channel audio to specific channels of a multi-channel device.{{votes|6}}
 
** allows adding an extra output channel for timecode sync when editing audio of a video.
 
** allows adding an extra output channel for timecode sync when editing audio of a video.
 
** could allow routing of inputs to outputs  
 
** could allow routing of inputs to outputs  
** '''Playback to multiple devices simultaneously''' {{votes|2}}
+
** '''Show channel mapping of multi-channel files''' {{votes|6}}
 +
<ul>{{devcomment|Audacity doesn't do what you ask now, but could only do so on the assumption there is a standard mapping for the format or the information is in the file somewhere. Some files may have this information in the file but this assumes the application writing the file has provided it. Audacity doesn't write or understand such information.}}
 +
<ul><li>'''Playback to multiple devices simultaneously''' {{votes|2}}</ul>
  
<div id="scrub"></div>
 
{{note|1=
 
'''Scrubbing:''' {{votes|74}} - one of:
 
* '''Basic functionality:''' Drag playback position left/right while playing (no effect until drop), or just click a position bar to skip to new position. {{votes|29}} Common in audio players, for example Foobar. Allows to judge the end of (long) selections without having to play repeatedly. it would be nice to see it implemented how sony soundforge has it implemented with Keyboard Shortcuts to Toggle Timeline Scrub Mode JKL shuttle.
 
*'''Audio reproduction while dragging/playing:''' {{votes|45}} Drag cursor back and forth across a particular point and hear the audio as a function of the direction and speed of the cursor. Allows to zero in on the beginning of a plosive syllable or other distinctive sound as an edit point. Precisely analogous to rocking the tape back and forth on the playback head of a recorder. Could also have a preset speed using Fast Forward/Rewind buttons.
 
*Here is a demonstration of Paul L's experimental implementation:  https://www.youtube.com/watch?v=9rrDOhj_4GY
 
<ul>{{devcomment|There is a hotkey B for play to selection and various alternative means of playback navigation in Audacity 2.x, such as CTRL + click to skip playback position. Also, rapidly using repeated left or right arrow presses sound quite like reproduction while dragging, even though audio stops between arrow presses - see [http://manual.audacityteam.org/o/man/navigation_tips.html Navigation Tips].}}</ul>
 
{{ednote|'''Peter 30Jan17:''' Experimenting here with enrobing this entry in a coloured div, a note div for now, but we may want a specialized template.<p>[[ToDo-1]] Surely we can remove this from here and move it to Completed Features?</p>}}
 
}}
 
  
* "Play-at-speed" button/slider:
+
* '''Play-at-speed Toolbar:'''
** '''Remember Play-at-speed slider setting:''' ([http://bugzilla.audacityteam.org/show_bug.cgi?id=711 Bug 711)] {{votes|10}} The setting should not be reset to 1x at the start of each new project or session. It should work as the Selection Toolbar format does from Audacity 2.0.6:
+
** '''Remember Play-at-speed slider setting:''' ([https://bugzilla.audacityteam.org/show_bug.cgi?id=711 Bug 711)] {{votes|10}} The setting should not be reset to 1x at the start of each new project or session. It should work as the Selection Toolbar format does from Audacity 2.0.6:
 
*** A new project window takes its Play-at-Speed slider setting from the audacity.cfg settings file
 
*** A new project window takes its Play-at-Speed slider setting from the audacity.cfg settings file
 
*** If you move the slider in the new project window, the slider in the previous project window should remain at its current setting  
 
*** If you move the slider in the new project window, the slider in the previous project window should remain at its current setting  
Line 1,988: Line 1,989:
 
<li> '''Pre-set speeds''' e.g. 50% slower or faster as in [http://www.cowonamerica.com/download/ Jet Audio Basic] plus a "Reset" for 1x speed {{votes|7}}  
 
<li> '''Pre-set speeds''' e.g. 50% slower or faster as in [http://www.cowonamerica.com/download/ Jet Audio Basic] plus a "Reset" for 1x speed {{votes|7}}  
 
<li> '''Change speed while playing''' 22.47, 10 May 2007 (GMT+10) - Nickdella {{votes|2}}  
 
<li> '''Change speed while playing''' 22.47, 10 May 2007 (GMT+10) - Nickdella {{votes|2}}  
<li> '''Play at tempo (without changing pitch):''' Very useful for editing spoken word vocals. --[[User:Jongalloway|Jongalloway]] 13:42, 18 January 2009 (PST) {{votes|12}}
+
<li> '''Play at tempo (without changing pitch):''' Very useful for editing spoken word, ear training or music transcription {{votesdate|14|17Jul20}}
<li> '''Play at pitch without changing tempo:''' {{votes|4}}  
+
<li> '''Play at pitch without changing tempo:''' {{votesdate|5|17Mar20}}  
 
<li> '''Ability to resize:''' {{votes|2}}  
 
<li> '''Ability to resize:''' {{votes|2}}  
 
</ul></ul>
 
</ul></ul>
  
*Loop:
+
 
** '''Dynamically adjust loop playback when selection boundaries move''' {{votes|17}}     
+
*'''Loop:'''
*** '''A short part of the original selection start or end should be played''' while and just after the boundary is moved. {{votes|1}}
+
<div id="dynamic_loop"></div>
*** '''Must be able to move boundary with keyboard while playing''' {{votes|1}} Currently, SHIFT + ARROW to move the selection merely moves the playhead backwards.  
+
<ul><ul><li> '''Dynamically adjust loop playback when selection boundaries move''' {{votesdate|36|08Jul17}}     
** '''Timed track loop as an alternative to repeat''', to potentially help increased ram efficiency. With adjustable time it would be easier for matching tempo. In the render it would repeat the desired sound and have silent intervals when repeat time exceeds the time of the sound.
+
<ul><li> '''A short part of the original selection start or end should be played while and just after the boundary is moved.''' {{votes|3}}
** '''Gapless MP3 playback:''' e.g. using [http://www.mpg123.de/faq.shtml libmpg123] ([http://www.gnu.org/licenses/lgpl.html LGPL]) instead of [http://www.underbit.com/products/mad/ libmad] {{votes|1}}  
+
<li> '''Must be able to move boundary with keyboard while playing''' {{votes|1}} Currently, SHIFT + ARROW to move the selection merely moves the playhead backwards. </ul>
** '''Looping tool''': play a '''metronome click''' (ideally of your own choice) on beat divisions of your selection. This would help to be sure that the loop to be cut is syncopated. ''(see SoundForge's Acid looping tools and Wavosaur's selection gridlines''). {{votes|1}}
+
<ul><li> '''Timed track loop as an alternative to repeat''' {{votes|1}} to potentially help increased ram efficiency. With adjustable time it would be easier for matching tempo. In the render it would repeat the desired sound and have silent intervals when repeat time exceeds the time of the sound.</ul>
** '''Batch-looping tool with auto loop finder and slice marker''' like fl-studio. {{votes|1}}
+
<li> '''Gapless MP3 playback:''' e.g. using [http://www.mpg123.de/faq.shtml libmpg123] ([http://www.gnu.org/licenses/lgpl.html LGPL]) instead of [http://www.underbit.com/products/mad/ libmad] {{votes|1}}  
* '''Fade in/out playback volume automatically when pressing Play/Stop''' {{votes|2}}
+
<li> '''Looping tool''': play a '''metronome click''' (ideally of your own choice) on beat divisions of your selection. This would help to be sure that the loop to be cut is syncopated. ''(see SoundForge's Acid looping tools and Wavosaur's selection gridlines''). {{votes|1}}  
* '''Streaming server''' {{votes|3}} to broadcast playback or recording, stream it over internet, send it to Skype...
+
<li> '''Batch-looping tool with auto loop finder and slice marker''' like fl-studio. {{votes|1}}
 +
<li>'''Fade in/out playback volume automatically when pressing Play/Stop''' {{votes|2}}
 +
<li>'''Streaming server''' {{votes|3}} to broadcast playback or recording, stream it over internet, send it to Skype... </ul></ul>
  
 
== Editing Enhancements ==
 
== Editing Enhancements ==
Line 2,009: Line 2,012:
  
 
<div id="nondestructiveedit"></div>
 
<div id="nondestructiveedit"></div>
* '''Non-destructive (non-linear) editing:''' {{votes|21}} Especially useful for effects e.g. put some echo on a file, then realise a click needs to be edited out, I now have to edit out the echoes of the click as well as the click itself.  
+
* '''Non-destructive (non-linear) editing:''' {{votesdate|22|24Mar17}} Especially useful for effects e.g. put some echo on a file, then realise a click needs to be edited out, I now have to edit out the echoes of the click as well as the click itself.  
** '''Project-wide is sufficient:''' {{votes|16}}  
+
** '''Project-wide is sufficient:''' {{votes|17}}  
 
** '''Should be per-track:''' {{votes|5}} so you don't have to undo a bunch of changes you DO want on some tracks to get rid of something you did a while ago to another track. The history would then be viewable per track.
 
** '''Should be per-track:''' {{votes|5}} so you don't have to undo a bunch of changes you DO want on some tracks to get rid of something you did a while ago to another track. The history would then be viewable per track.
 
{{devcomment|See also a -devel list [http://audacity.238276.n2.nabble.com/Re-Non-destructive-effects-stacks-td258866.html discussion] about a proof-of-concept patch for non-destructive effects stacks.}}
 
{{devcomment|See also a -devel list [http://audacity.238276.n2.nabble.com/Re-Non-destructive-effects-stacks-td258866.html discussion] about a proof-of-concept patch for non-destructive effects stacks.}}
Line 2,016: Line 2,019:
 
* '''Delete/move regions/clips/tracks without having to press Stop first:''' {{votes|13}} Playback carries on (from end of deletion region if needs be) so saving stop and restart of playback every time. Truncate Silence a possible alternative, but only if near silences are what you want to delete.   
 
* '''Delete/move regions/clips/tracks without having to press Stop first:''' {{votes|13}} Playback carries on (from end of deletion region if needs be) so saving stop and restart of playback every time. Truncate Silence a possible alternative, but only if near silences are what you want to delete.   
  
* '''Select multiple regions''', e.g. in Word programs etc. you can use the control key to select multiple but separate areas of a file so several areas to processed at the same time. {{votes|4}}
+
* '''Select multiple regions''', e.g. in Word programs etc. you can use the control key to select multiple but separate areas of a file so several areas to processed at the same time. {{votesdate|5|23May18}}
  
 
* '''Audio pattern matching:''' In a recording, remove the same 20 second tag scattered throughout. I want to identify the same piece of sound and remove it from a number of files.    {{votes|6}}
 
* '''Audio pattern matching:''' In a recording, remove the same 20 second tag scattered throughout. I want to identify the same piece of sound and remove it from a number of files.    {{votes|6}}
Line 2,026: Line 2,029:
 
** '''Should work when further zoomed out:''' {{votes|3}} SoundForge allows pencil tool to be used at a zoom ratio of 1:32 or lower, without seeing individual samples.
 
** '''Should work when further zoomed out:''' {{votes|3}} SoundForge allows pencil tool to be used at a zoom ratio of 1:32 or lower, without seeing individual samples.
 
** '''Should work in "Waveform (dB)" mode''' {{votes|3}}
 
** '''Should work in "Waveform (dB)" mode''' {{votes|3}}
** '''Horizontal [http://forum.audacityteam.org/download/file.php?id=3435 Guideline]''' to follow amplitude position of the pointer. Possibly with numerical readout in Status Bar {{votes|2}}
+
 
 +
*'''Ability to use Audacity as a simple WAV editor, or other imported format:'''  Given that 4 out of the 5 primary features of audacity[1] involve editing a single file, would it not be worth making that process easier? e.g. if you load a file, modify something, and press control-S, it should save the file, instead of prompting you to create a project?
 +
**PS notes:  this led to a discussion between Kozikowski and the original poster - and largely revolves round the previously much-discussed issue of Save versus Export.  For more details see this thread in the forum:  http://audacityteam.org/forum/viewtopic.php?f=11&t=7816&p=34759#p31137
 +
** '''Horizontal [https://forum.audacityteam.org/download/file.php?id=3435 Guideline]''' to follow amplitude position of the pointer. Possibly with numerical readout in Status Bar {{votes|2}}
 
*** And/or a ruler that you move manually to snap to the ticks on the vertical scale. The guideline would change color when snapping to the ruler. {{votes|1}}  
 
*** And/or a ruler that you move manually to snap to the ticks on the vertical scale. The guideline would change color when snapping to the ruler. {{votes|1}}  
  
Line 2,032: Line 2,038:
 
** '''Adjust trim:''' by dragging corners of clip boundary. Allows to recover original audio easily if you trim too much, rather than as now, having to undo a cut and redo it. See Audition, Cubase, Vegas... {{votes|12}}
 
** '''Adjust trim:''' by dragging corners of clip boundary. Allows to recover original audio easily if you trim too much, rather than as now, having to undo a cut and redo it. See Audition, Cubase, Vegas... {{votes|12}}
 
*** Very useful for chopping sound bites into separate tracks where you may need to grab a second or two before or after the sound bite. Currently you must search out the source material in the original track.  
 
*** Very useful for chopping sound bites into separate tracks where you may need to grab a second or two before or after the sound bite. Currently you must search out the source material in the original track.  
<ul><ul>{{devcomment|Audacity does have [http://manual.audacityteam.org/man/Tracks_Preferences#behaviors cut lines] allowing you to restore cuts at any time, but you can only restore all the cut.}}
+
<ul><ul>{{devcomment|Audacity does have [https://manual.audacityteam.org/man/Tracks_Preferences#behaviors cut lines] allowing you to restore cuts at any time, but you can only restore all the cut.}}
<li>'''Time Stretching:''' {{votes|7}} mouse tools for both pitch-variable and pitch-constant time stretching.  Adobe Audition has this and it's vital for the production of sample-based music.  
+
<li>'''Time Stretching:''' {{votesdate|8|09Jun17}} mouse tools for both pitch-variable and pitch-constant time stretching.  Adobe Audition has this and it's vital for the production of sample-based music.  
 
</ul></ul>
 
</ul></ul>
 +
 +
* '''Mouse Drag Time Stretching:'''  Right now my procedure for resampling a particular guitar sample is:
 +
# Cut it into little bite size pieces in Audacity, where pretty much each and every strum has it's own file
 +
# Make each piece into a track in FL Studio, and use the mouse to stretch/shrink these pieces until they fit the BPM / rhythm I'm lookin for
 +
# Drag these samples back out of rhythm so that there is silence at any place where they overlap, keeping the newly stretched tempo of each individual piece
 +
# Bring the resulting wave back into Audacity, where I again separate all these into separate tracks, and shift and trim until they match up with a click track in my new desired BPM.
  
 
* '''When dragging to create a selection spanning multiple tracks, be able to stop selecting a previously-selected track''': for example, if I press somewhere on track A and drag down onto track B, then down onto track C, I now have a selection spanning tracks A, B, and C. It would be helpful to (while continuing to hold down the mouse) drag back up to track B and no longer be selecting track C (so that the selection now only spans tracks A and B).
 
* '''When dragging to create a selection spanning multiple tracks, be able to stop selecting a previously-selected track''': for example, if I press somewhere on track A and drag down onto track B, then down onto track C, I now have a selection spanning tracks A, B, and C. It would be helpful to (while continuing to hold down the mouse) drag back up to track B and no longer be selecting track C (so that the selection now only spans tracks A and B).
Line 2,040: Line 2,052:
 
==MIDI==
 
==MIDI==
 
<div id="midi"></div>
 
<div id="midi"></div>
 +
* '''Display bar lines''' {{votesdate|2|27Feb18}}
 +
** Could be shown as heavier beat lines, and/or a [https://wiki.audacityteam.org/wiki/Feature_Requests#signature scale under the Timeline].
 +
 
* Allow direct '''MIDI editing/playback''' and incorporate '''midi sequencer''' {{votes|60}}
 
* Allow direct '''MIDI editing/playback''' and incorporate '''midi sequencer''' {{votes|60}}
** It doesn't make a lot of sense to add support for MIDI files if Audacity can't also be used as a sequencer. Obviously this would take some time, but if sufficiently developed would make Audacity competitive even with ProTools and Sonar!
+
{{devcomment|Audacity now has MIDI playback, and basic cut/paste editing}}
 
** If MIDI tracks are eventually supported, it would be neat to include a piano roll and notation window in the future.
 
** If MIDI tracks are eventually supported, it would be neat to include a piano roll and notation window in the future.
  
Line 2,077: Line 2,092:
  
 
==Unclassified Feature Requests==
 
==Unclassified Feature Requests==
None
+
 
 +
<div id="backward compatibility"></div>
 +
* '''Backward compatibility from AUP3 to AUP:''' {{votesdate|1|08Dec20}}
 +
: Support saving projects from Audacity 3.0 or later as Audacity 2.x "AUP" project. A separate format conversion utility would be adequate.
 +
{{devcomment|Multi-channel WAV files may provide a workaround.}}
 +
 
 +
 
 +
<div id="rip&burn"></div>
 +
* '''CD Rip and Burn''' {{votes|22}}
 +
{{devcomment|There is experimental code for CD Import/Export in progress.  Help welcome.}}
  
  
 
[[Category:Feature Planning]][[Category:Participation]] [[Category:For Developers]]
 
[[Category:Feature Planning]][[Category:Participation]] [[Category:For Developers]]
 +
</noinclude>

Revision as of 10:00, 20 November 2021

This is our Feature Requests page where suggestions from users to enhance or add new features to Audacity are logged.
To vote for a feature or suggest a new enhancement, please post to the "Adding Features" section of the Audacity forum.
Quick Links:


Highest-rated Feature Requests

All Feature Requests with a vote count of 20 or more qualify for a listing in the Highest Rated index here.
  • Tip: To sort by Category and have each Category ordered by number of votes, click the "Category" column then SHIFT-click the "Votes" column.
This is how we get from ideas to new releases of Audacity
Feature Requests   -->   Proposals   -->   Projects   -->   Releases
Feature Votes Category Status
Improvements to the "Macros" (batch processing) feature - many high-rated requests, total as shown 224 Automation Done.png Some enhancements (Automation Project) ToDo.png Many more possibilities.
Real-time effects 166 Effects Done.png Basics (Effect-Preview button). ToDo.png Full feature.
Multi-channel playback 84 Playback Enhancements
PDF version of Manual 82 Interface Modifications Done.png Draft Experimental PDF for 2.2.0 available. Offers of help to improve on this are welcome!
Synchronize recorded/played back tracks automatically 71 Playback Enhancements
BPM and beat timecode automatic detection and beat matching 66 Effects
Support lyrics and album art in metadata tags 62 Imports and Exports
Allow direct MIDI editing/playback and incorporate MIDI sequencer 60 MIDI Done.png Playback. It's in 2.2.0. ToDo.png Sequencer.
Sound Activated Recording pre- and post-roll: 56 Recording Enhancements
Choose which of multiple channels to record 54 Recording Enhancements
Too utilitarian/outdated/generic in appearance/hard to customise 51 Interface Modifications Done.png Themes and Custom Theming available in 2.2.0. More ongoing work on appearance at Dark Audacity.
Bind particular parameters of effects to buttons or keyboard shortcuts 51 Interface Modifications Done.png Achievable via Macros now. ToDo.png could be slicker.
Effects Categorization 49 Effects ToDo.png Work started on blocks-based interface for configuring effects menu.
Import/play video for synchronized soundtrack editing 49 Imports and Exports
Include Audacity's own virtual driver to record stereo mix 46 Recording Enhancements
Global shortcuts that operate Audacity if it does not have focus 46 Interface Modifications
Timestamp metadata 44 Imports and Exports
Panning envelope editing 42 Editing Enhancements
Export to directory from which original .aup or audio file loaded 41 Imports and Exports
Import Appended 39 Imports and Exports
Let the Timeline display time signature and bars/beats 39 Interface Modifications
Record from multiple sound devices at once 39 Recording Enhancements
Repair: vastly increased length of track to be worked on/works when zoomed out 37 Effects
Dynamically adjust loop playback when selection boundaries move 36 Playback Enhancements
Markers on Waveform 36 Interface Modifications
Control Audacity from command line 33 Automation Done.png Was part of the Automation Project, for Audacity 2.3.0.
Disable "Save Changes?" on exit - Simple option, even if the file has been edited. 32 Interface Modifications
Timer Record Multi-event scheduler 32 Recording Enhancements
One-step way to avoid clipping on multiple tracks 30 Interface Modifications
Grid lines: Horizontal- and also in spectrogram view 29 Interface Modifications
Selection Toolbar: Microseconds [µs] 26 Imports and Exports
Control Audacity by a foot pedal 25 Automation
Make Scripting (mod-script-pipe) available after enabling it in Preferences 26 Automation
Reinstate 78 RPM EQ curves from Audacity 1.2 25 Effects
More Context Menu (right-click or CTRL-click) functionality 23 Interface Modifications
Preference for monitoring on by default 23 Interface Modifications
Non-destructive (non-linear) editing 22 Editing Enhancements
CD Rip and Burn 22 Unclassified Feature Requests
Sound Activated Recording: segment each recording event: 21 Recording Enhancements
Include "Favorites" folder at the top for frequently used plug-ins 21 Effects (either autogenerated and sorted by number of calls, or user-added)
Normalization Replay Gain (RMS) 20 Effects
Store metadata for each imported file 20 Other Import/Exports
Non-destructive Punch-in recording 20 Recording Enhancements
Configurable mouse bindings 20 Preferences


Segmenting Tracks

  • Automatic segmentation during Record: (10 votes) Automatically segments the audio being recorded into another track upon meeting the user defined settings for "silence" length, threshold level and number of track to be split.
      The best way to do this might be to add labels at the track splits, which fits in with other requests to label points where Sound Activated Recording pauses when the audio falls below the specified threshold.
  • Beat Finder Improvements:
    • See "BPM Detection" in Highest-rated
    • Search for periodicities, let user refine and add time measures, then redo with probability/interpolation bases on added information. Use the corrected beats and a dynamics analysis to detect musical structures like verse, refrain. See Beat Finder Improvements for details.
    • Create regions encompassing each beat by inputting a BPM (maybe include auto-dedection of the BPM), see image. The region can then be moved, duplicated etc. as normal to create loops or re-mixes easily.
  • Clips:
    • Allow left-click in track to snap to or retain split line not delete it: (12 votes) For example, right-click to remove the split-line, as is done to remove the cut line.
  • Snap to editing cursor and show Boundary Snap Guide (2 votes)
  • Export Multiple:
    • Done.png (version 2.4.2) Checkbox in dialog to pass metadata through to all exported files automatically: if identical tags wanted for all files, saves having to (remember to) File > Open Metadata Editor to add tags before export. (59 votes)
    • File name prefix should have leading zeros for operating systems which don't have natural number sort (otherwise track 10 comes before track 2 etc). (3 votes)
    • Choice of minimum number of digits for numbering (2 votes)
    • Store last used state of "Include audio before first label" as for "Name files" buttons (2 votes)
    • Done.png Checkbox "Do not export audio before zero" as per straight export: (4 votes) If unechecked, exports audio before zero and includes any trailing white space before zero as silence.
    • Checkbox "Normalize on export" (1 votes) Use case is for e.g. live concert destined for individual files
    • Enumerate files in single progress dialog to say "exporting 1 of 5", "2 of 5...", not string of "exporting entire Project" dialogs. Still needed, even though 2.x now gives the name of the file currently being exported (12 votes)
    • Support "Use Custom Mix" (6 votes)
    • Remaining time for entire process, not (just) for each file (4 votes)
    • Done.png "Overwrite existing files" off by default: (3 votes)
      • Done.png but remembers previous state (2 votes)
    • "Success" dialog should not have same title as main Export Multiple dialog (2 votes) Use case is this makes it possible to script actions based on the unique window title (and it "could" be argued as bad design to have two identically titled dialogs).
        Possible title could be "Export Multiple (Results)" - the title must include the phrase "Export Multiple" IMO - Gale
    • Skip export of selected labels (1 votes)
    • Button to export to current project location (1 votes)
  • Labels:
    • Multi-Label-Select: Ability to select multiple (not necessarily adjacent) labels (such as with control-click or shift-click) (11 votes 23May18)
      • Should work on point labels, too, thereby selecting regions between labels. (5 votes)
      • Also there could be commands to select multiple label regions or to ignore specified labels. See extra detail here.
      • Play Labels Only: Play clipped in or labelled regions only - standard feature on professional audio editing systems. skipping the non-selected regions. This feature would be useful for comparing two regions of an audio file without delay between their playback.(5 votes)
      • Change font size/color for selected text in labels (7 votes 02Nov17)
      • Multiple select must work in Edit Labels too (1 votes)
    • Invert labels: (2 votes) Replace current labels with new labels that start from the end of the previous label to the start of the next label. If two of the original labels touch (but don't overlap), they will be replaced with a point label at the point where they meet.
    • Snap labels to:
      • Other labels (11 votes)
      • Editing cursor (7 votes)
      • Clips (5 votes)
      • Selection boundary (3 votes)
    • Mark-in and mark-out points: As per video editors, "I" sets Edit In Point and "O" sets Edit Out Point. Should use zero-crossing accuracy. Doesn't matter what you do between those two actions; once you press "O", everything between "I" and "O" is selected. (12 votes)
    • Easy way to select a region between labels (9 votes)
        Would the interface changes required be worth it when there is an easy solution now? Click where you want to "mark in" (can be in an existing point-label) and hold SHIFT while clicking where you want to "mark out"; a region is drawn between the click points. Currently, the SHIFT-click can't be in a label, it has to be in the waveform, but shift-clicking between labels could be added. Also see Marking cut regions or points.
    • Moving a label draws original and current edge(s) in waveform without having to select the label (7 votes)
    • Right-click functionality: (3 votes)
      • Add label (2 votes)
    • Moving a label moves the audio: (2 votes)
    • Done.png More distinction between region and point labels when zoomed out: (4 votes) so that Export Multiple does not produce a few milliseconds of audio if you accidentally drag a point label when zoomed in.
        There already is the distinction that zoomed out and selected, the minimal region label will show no vertical line in the waveform and a double arrowhead in the Timeline, versus vertical line and single arrowhead for a point label. Still, it seems a reasonable addition for a point label to have a different-colored vertical line in label track and waveform.
    • Labels include metadata (6 votes) - not a request for cue sheet support, instead this gives a way in compilation albums to pass other than track Title and Track Number to Metadata Editor
    • Automatic label text during playback/recording: (3 votes) When using Add Label at Playback Position, provide an option to populate labels automatically with pre-defined text then close the label. Provide an option to increment the entered numbers or letters.
    • Import label by simply drag-and-drop label file (1 votes)
    • Expand-to-silence: (2 votes) expand selection command expands the selection leftwards and rightwards until silence between songs or beginning/end of track is found
    • Expand-to-non-silence: (3 votes) Double-click any point in a "silence" to automatically select the complete silence - useful for voice editing.
        In Audacity 2.x, Analyze > Silence Finder labels silence, and Effect > Truncate Silence can remove these silences.
    • Minimum distance between labels (6 votes) similar to Nero Wave Editor it can be very handy when handling large amount of spoken audio
        There is an experimental modification to Silence Finder here
    • Count the number of silences produced to cross-check with number of tracks on an LP or cassette (1 votes)
    • New Label Track name defaults to Current Track name (1 votes 30Mar17) When a new label track is created then its name should default to that of the currently selected (audio?) track to which the labels relate. The currently selected track is the most likely to be relevant to the label track. If there are multiple unnamed Audio Tracks, then it doesn't matter what name the label track defaults to since, if the name is of any concern anyway, then it will need to be renamed anyway. It is just as easy to rename it from 'Audio Track' as it is to rename it from 'Label Track' - both are equally un-useful.
        If there is more than one audio track, it may not be obvious which to choose for the label name. If all the audio tracks are called the default "Audio Track" then Label Track should not be called "Audio Track".
  • Time Shift Tool
    • Move Cursor Too! Cursor within the track being moved should move with the track, not stay at same time point. (1 votes) Additionally, if this cursor extended over other visible tracks, it would make it much easier to line up one track with the others.
          You can extend the cursor through all tracks by holding down SHIFT then clicking in the Track Control Panels of the other tracks.
      • Allow overlapping clips as in CoolEdit, but give overlap a different color (1 votes)
      • Lock-beyond: (2 votes) Set a lock point beyond which tracks cannot be dragged. Could be set in current direction of travel or by right-click menu. Use Case: Set maximum length in a project with many overlapping tracks where you may not be able to see the end (bottom) of the project.
      • An individual track locking capability to prevent inadvertent time shifting or changes to previously edited tracks
      • Allow shifting by less than distance between samples (1 votes)
      • Allow shifting while audio playing (1 votes) as in Cool Edit Pro
      • Export cue sheets from labels e.g. for CD burning (and/or text file compatible with shntool) (16 votes 06May17)
        • MP3 cue sheets (1 votes) for example compatible with MP3Cue
          There is a Java-based tool called label2cue that converts Audacity's exported text files containing label information to cue information. Instructions for use of label2cue and details of other similar tools are here.
      • Import cue sheets to labels e.g. to add internet database information to files. (5 votes 27Sep19)
      • Export lrc files from label track to be able to create song lyric files from inside audacity. (1 votes)
      • Split to multiple projects: Split the project into smaller multiple projects by labels, similar to the "Export Multiple" command. Each project retains the per-track labels of the original single project. (10 votes)
        • Save selection as new project: (3 votes)

      Frequency Analysis Capabilities

      Plot Spectrum

      There are many additional single-vote suggestions at Suggested Frequency Analysis Capabilities. If any there especially appeal to you, please cut and paste them below and include your own vote for them.
      • User-defined minimum dB level, but not via meter/waveform dB preference: (14 votes) This is too inflexible, and non-obvious to the user. Also given the (generally better) normalization compared to 1.2, this leaves you with an empty plot when looking at low level audio, e.g white noise at -75 dB is not visible with Preferences set at -96 dB. Set a default minimum that can never leave user with an empty plot, but let user move the minimum if they wish.
        • Text box input for lowest visible level (6 votes)
      • Real time plot when playing audio: (13 votes 07Mar17) Or, in view of the CPU demands of calculating the spectrum, have Audacity do plot spectrum at given time intervals.
          Plotting spectrum while recording would likely be impractical due to the risk of errors writing the recording data.
      • Option to turn off auto-scaling: which sets the top and bottom of the dB scale according to the "significant" level measured (7 votes). User can then save their own maximum and minimum by text box in Plot Spectrum, a preference or sliders. Use case is easy comparison of different plots.
      • Zoomable/pannable sliders (13 votes)
        • Absolute minimum dB could still be set by Meter/Waveform dB Preference, but use slider to set minimum within that. (1 votes)
      • Select any area on the grid and release mouse to zoom in on it (1 votes)
      • Normalization presets (10 votes) Understandable default called e.g. "music" that gives a result like 1.2 plot, so that a section with most samples close to 0 dB peaks near to 0 dB in the spectrum, not at -20 dB
      • User-defined frequency bands: (13 votes) CoolEdit/Audition allow this. Use case: the most relevant region for music is 20 to 8000 Hz. Could be done by:
        • Zoomable/pannable frequency axis (10 votes)
        • Text box for frequency cutoff point (4 votes) For example the user could type in 1000 to see the frequency range of the spectrum from 0 to 1000 Hz. That parallels with the choice in Spectrograms preferences.
      • Export spectrum graph as an image (7 votes)
      • Exported plot file should have metadata: (5 votes) giving current plot window settings and a timestamp.
        • Should also include path to project file (1 votes)
      • Manage plot files: (2 votes) import or edit the files within Plot Spectrum window.
      • Longer analyzable length than 10485760 samples: (3 votes)
        • Preference or option for analyzable length: (1 votes)
      • Overwrite or append choice for exported plot file: (3 votes)
      • Exported file should identify each peak and cursor position (3 votes)
      • Export maximum peak amplitude for each FFT bin rather than the average peak amplitude: (2 votes) This means that the result will be identical whatever length of absolute silence is included in the selection. This might make a momentary frequency too loud everywhere else if you EQ'd against a such a plot, but if the average and maximum peaks were very different, this could usefully indicate possible faults in the recording.
      • Remember window height/width across sessions (5 votes)
      • More distinctive cursor line (3 votes) bolder, different color to grid lines or partly transparent
      • Alternative plot from cursor point: (2 votes) like CoolEdit, without having to select a region. Audacity could internally select the region length/position.
          Audacity 2.x by default selects "all" on no selection, so an exception would have to be allowed for Plot Spectrum. Also, region selection must still be offered for those analyzing a specific note.
      • Multiple spectra window: (13 votes) Plot multiple spectra for different tracks/regions in the same project e.g. Audition has four buttons to hold spectra. Currently different spectra must be in different projects. Multiple plots in different colors in the same window would aid comparing spectra.
      • Plot cepstrum, energy, etc. offline: (1 votes) Plot cepstrum and other indicators at given time intervals.
      • Plot human frequency response curve (how humans hear frequencies) overlaid with the frequency spectrum (1 votes)
        • Create a negative difference between spectrum and human response curve as equalizer preset (1 votes)
      • Linear option for vertical dB scale: (4 votes) Use cases:
        • Demonstrating primary resonances of different instruments to elementary physics of music students without room noise and other musically insignificant peaks becoming over-prominent
        • Shows power in peaks as directly proportional to height.
      • Cents qualifier for pitch-class/octave (2 votes). For example 443 Hz displays as A4+12, meaning "12 cents sharp of A4 in equal temperament (A4 = 440 Hz)".
      • Make Plot Spectrum "WINDOW" a real window: The problem:
        • Switching between one screen and another is a pain because:
          1. The Spectrum Window is always on top of the main window
          2. The Spectrum window can not be minimized
          3. It can not be reduced in size below a fairly large size
          4. The Spectrum Window does not appear on the Desktop Task Bar
        • Ideally I would like.
          1. The Spectrum window to be a real window (with a minimize button)
          2. To be able to resize the window like other windows (with scroll bars when reduced below the minimum size)
          3. To see the Spectrum Window on the Desktop Task Bar
          4. A tick box on the Spectrum Window for "always on top"

      Other analytical/statistical ability

      • Export text file containing amplitude data for each sample (18 votes) like Wavosaur
        • Import text file containing amplitude data for each sample (2 votes)
        • RMS data wanted not just peak values (1 votes)
        • Allow selection by seconds as well as samples (1 votes)
      • Track sample data: headroom to dBFS (audio level), peak minimum and maximum sample, RMS volume, replay gain etc. see SF, Wavelab, Cool Edit etc. over an arbitrary length of audio, even the whole file. (8 votes)
        • This could go in Status Bar (1 votes)
            This could work well with the new Vamp analysis plug-ins/
      • Find Clicks producing labels like "Find Clipping", possibly using sine-wave-curve-fit prediction algorithm and labelling where waveform diverges from prediction. (2 votes)
      • Pitch Accuracy Analysis: add votes below.
      • Oscilloscope: (1 votes) showing audio signal(s) converted to voltages over time.
      • Spectrograms including Pitch (EAC):
        Also see Multiple track views for votes for a split waveform/spectrogram view.
        • Crosshair as in Plot Spectrum (13 votes) which enables on-screen measurement of the frequency and dB level. Length of audio should be the minimum interval possible taking the settings of the Fourier transform used in each track, namely the FFT size, window and overlap.
          • Display low/high/centre of spectral selection on borders of a selection (6 votes)
        • Visual Tool editing of frequency or pitch: (11 votes 24Apr17) - examples here.
          • Erase Tool to remove pieces of spectrum: (10} votes 24Apr17) e.g. removing harmonics or 'mouth noise' from vocals; brief noises at different pitch). See Spectral layers
          • Photoshop-like brush tool (3 votes 24Apr17) which would apply a chosen effect to an area of the spectrum which you paint it in. The brush might operate like a dodge/burn tool, making the volume quieter/louder in that frequency, or maybe you would apply a wah-wah just to the low frequency by drawing only in the low area
          • Free shape selection tool
          • Pen tool
          • Pattern-matched brush tool: this would be a brush which attempts to match the area you are painting to pre-selected pattern before it applied the desired effect.
          • Magic wand: to click on a color which selects all other pieces of that color
          • Invert selection: so that you can select a frequency, invert the selection, delete the selection then be left only with the originally selected frequency.
        • Export to image file (including PNG) (1 votes)
        • Export to image slideshow or video file (1 votes)
        • Export as graph or graphable data: (1 votes)
        • Vary FFT window overlap: (3 votes) Allow varying the overlap when generating the spectrogram.
        • Grayscale range of black to white: rather than the current "black to gray" range (2 votes 20Jul17)
              Special consideration of cursor lines would be required, for example to ensure that Timeline Quick Play cursor is visible during (white) track silence.
        • Customize spectrogram colors (foreground and background): not just grayscale or not (7 votes 20Jul17)
              Already works in Audacity 2.2.0 using themes.
        • Export to three-column text file (energy/time/frequency) (2 votes)
        • Exchange X (horizontal) and Y (vertical) axis: (1 votes)
        • Per-track spectrogram settings: (2 votes) When exploring the spectrogram, it would be convenient if it were possible to adjust by track the 'FFT Window' and 'Display' settings, which are now set through 'Preferences >Spectrograms'.
        • 3D - Amplitude by Frequency by Time: (2 votes)
        • Scale should have shorter horizontal line for non-integer k values (1 votes)
        • Display note names in spectrogram view: An option to show note names instead of frequencies. (2 votes 22Nov19)
        • See also Grid Lines
      • Frequency band splitter: I find this feature in Fscape (an xplatform app similar to Soundhack) http://www.sciss.de/fscape/ - to be very useful and would like to see it or a Nyquist script written to do something similar: a panel would appear when Band Splitting function is selected and would allow the user to
      1. define bands as freq/bandwidth -or- crossover freqs
      2. add new bands/crossovers as needed
      3. processes the bands or crossover parameters on a soundfile or a selection of a soundfile
      4. output these as separate files into a selected directory -- similar to splitting soundfiles according to label regions


      Automation

      There is a separate Automation page for detailed discussions about new or advanced methods of workflow automation. For example we are at an early stage of developing the ability to drive Windows versions of Audacity from a perl or other script via a named pipe. At this stage this feature is suitable for developers only, but you can request the feature by voting below.
      • Done.png Make Scripting (mod-script-pipe) available after enabling it in Preferences, without having to compile Audacity and the scripting module (26 votes 19Mar17)
        • Normalization/levelling and/or cropping of many files/tracks (5 votes)
        • Noise removal and other built-in filters or effects (5 votes)
        • Create many audio clips from many different audio files (4 votes)
        • preconfigure exports to a particular format (4 votes)
        • Repetitive use of effects at different parameters (2 votes)
        • apply Macros without use of mouse
        • for audio analysis
        • export files and their label track
        • using information from online music databases such as Discogs


      • Control Audacity by a foot pedal (25 votes) attached to the game, serial or USB port so that hands are free for transcription work. Also useful for non-transcription applications, such as recording off a commercial two-way radio with a squelch output signal.

      Command line support

      • Done.pngToDo.png Control Audacity from command line (33 votes)
          See SoX for am alternative command line solution.

      Improvements to the "Macro" (batch processing) feature

      • Done.png Include features dependent on selecting regions (e.g. trim, fades) (51 votes)
          This is partly supported in Audacity 2.0.1 or later by adding to the chain/Macro appropriate Nyquist plug-ins that operate on selections.
          This is fully supported in Audacity 2.3.0 or later which has 'scriptables' for manipulating the current selection.
      • ToDo.png Additional Export format options:
        • Export FFmpeg formats (52 votes 04May17)
        • Export sample rate (39 votes 22Jul17) This is important for MP3 and other compressed formats because if a file imported for batch processing switches the project rate to something not supported by the export format, the batch comes to a halt at the resample dialog. Alternatively have a preference to OK the resample dialog automatically at the offered setting. This would not however alter the project rate, which is a separate suggested command
        • Export format parameters (33 votes 04Apr17) like bit rate, as in the Options button in the file export window. Parameters for Macro-ed and norrmal exports should be stored separately.
        • Export Other uncompressed (28 votes 21Feb17)
        • Export 24/32-bit WAV (2 votes 22Jul17)
        • Export AIFF (2 votes)
      • Done.png Apply Macros to multiple projects (23 votes 14Feb19) instead of giving error messages
      • ToDo.png Include Export Multiple (21 votes 22May18) with options into Macro commands
      • Done.pngToDo.png Support Generate / Analyze effects (15 votes) both those built into Audacity and user-added ones in any other formats supported by Macros
          Some but not all are done for 2.3.0 Macros -but probably not all are suitable
      • ToDo.png Recursive selection of all files in one or more directories: (14 votes 19Aug19)
      • ToDo.png Export directory (10 votes)
          Planned for 2.3.0
      • ToDo.png Export Labels (1 votes)
      • Done.png Support Silence Finder (5 votes)
          Done for 2.3.0 Macros
      • Vamp support (2 votes)
      • VST support (8 votes)
      • LADSPA support (1 votes)
      • Apply Macros to files listed in LOF not mix the content into one file (3 votes)
      • Command to delete the old replaced file (2 votes)
          Planned for 2.3.0 - but differently, we will warn and allow overwriting
      • Specify metadata using Macro command
      • Split Stereo Track:
      • Done.png Single Macros dialog from which you can edit and apply the Macro (6 votes)
          Done for 2.3.0 Macros - with the Manage Macros dialog
      • Permit minimizing Audacity while Macro in progress: (2 votes)
      • Example parameters: (1 votes) EX 1: (Reduce 4 dB at 2000 Hz with Q shelve 8 dB per Octave). EX 2: De-esser fx ( threshold= -24 above 3800 Hz )
      • Make parameters configurable for:
        • SaveHqMaster1 & 2
      • Beep after a full Macro completes (2 votes)
      • Done.png Import / Export buttons: so users can share Macros more easily (3 votes)
          Probably planned for 2.3.0 - buttons are in the dialog , but not currently active
      • Ability to recover Macros applied to files if they crash (1 votes)
      • Wider Apply Macro dialog so you can see file names with long paths (2 votes)
      • Apply Macro dialog should be interactive: so you can scroll the list vertically or horizontally (1 votes)
      • Include arbitrary Shortcut Key commands e.g. CTRL + SHIFT + D to Macros array so that it can auto-task menu-dropdown and other manual mouse-click functions without disrupting batch automation. (1 votes)
      • a shut down program and computer option from Macro would be nice for long Macros
      • call another application like a cd burn application
          Use Python scripting, then you can do 'anything'
      • Separately pick the mp3 settings in the Macros feature
      • Allow Macros to continue after failure: Allow Macros to optionally continue processing the next file after processing a file fails. Currently, when a batch process encounters a problem with one of the files in its list of files-to-process, the entire batch process aborts. For unattended operations this can be inconvenient.
          Use Python scripting.


          This feature may be underrepresented as many requests on the forum for improved 'macro' type features appear to have been lost or not recorded.
      • Done.png Support Shortcuts to specific Macros (2 votes 23Jul17) so that 'macro' commands can be applied more conveniently.
      • Done.pngToDo.pngSupport Edit and navigation commands (2 votes 23Jul17) such as paste, duplicate, add new track, move focus to next / previous track, move cursor to selection start / selection end / track start /
          Some are in for 2.3.0: Paste, Duplicate and Move Focus - in 2.4.x all are in except "Add New Track"
      • Done.png Support Transport commands (2 votes 23Jul17) An example suggested by / for language learners: record 2 seconds then play what has been recorded.
      • Create macro by recording a sequence of actions (2 votes 23Jul17) Example: The record macro feature in CoolEdit Pro.
          This could be implemented by recording key strokes, possibly with an option to also record mouse events.
      • Automatically apply effects on Import or Export Examples: Normalize files on Import, Normalize on Export, Low pass filter on Import. Generally: Apply an arbitrary Nacro of effects to imported or exported files.

      Fader Automation

      • Adjust the Mixer Board or Track Control Panel gain sliders while playing then record the slider moves so you can render them if desired. (4 votes). Common feature on many other multi-track audio applications. In this way one can build up a mix, adjusting individual tracks and tweaking levels until just right. This would first require changing to linear envelope points. Could be extended to panning (if we had a pan envelope).

      Better transcription support

      • Extend features/interface of Play-at-Speed Toolbar. (1 votes).
      • Label Tracks more suitable for transcription: (10 votes)
        • multi-line labels (4 votes)
        • so they don't lock when audio track is not zoomed in far enough to create a scroll (2 votes)
        • Freeform text box/small editing window better then you can copy paste all of it into a text editor when complete (2 votes)
        • Second search method for text in labels other than using Labels Editor: (1 votes 26May17) - this would just be Find Next and Previous with a Replace option. A found occurrence of the text would move focus to the label that has the requested text and highlight that text within the label. Provide option to search in current label track only or in other label tracks.
        • each label should support more than 260 characters (which seems to be the limit on Windows) (1 votes)
            Create 30 second tone, zoom out until it half fills screen then type in a label. When label is full, can't add more characters unless you zoom in (zooming allows you to scroll). James: If/when we improve transcription we want to support multi-line text and linking with a true text editor.
      • real time loop editing: the fact that Audacity has partial functionality in making loops i.e. allow you to select and play a loop but NOT adjust the loop points in real time seems to me a half baked implementation of loop editing. Please - if you are going to allow someone to select and play a loop then go ALL the way and also allow them to edit it in real time?
      • Faster Play-at-Speed: Currently the transcription toolbar function PlayAtSpeed has a maximum value of 3X. My editing deck allows much higher multiples, I am used to searching raw data for "non-music" (speech etc.) and can recognize the difference at speeds between 7X and 10X.

      Effects

      • Allow real-time effects (166 votes)
        • Real-time effect preview sufficient as a first step (102 votes) this is now in current Audacity
        • Should include applying effects whenever playing or recording/monitoring (64 votes)
          • Allow disabling real-time for a selected track as in REAPER.(5 votes)
        • Stomp box/guitar effects: (3 votes) - one of the most useful features of Diamond Cut 7.
        • could allow effect intensity/LADSPA plug-in parameters to be varied too?
        • Panning while recording (5 votes)
        • include something similar to the envelope tool to adjust the effect parameters?
      • Save a Noise Reduction Profile: save and manage a Noise Reduction Profile for future use in subsequent projects

      New Effects

      • BPM and beat timecode automatic detection and beat matching (66 votes)
      • Vinyl-specific noise removal effects such as low level rapid tickiness, groove rasping... (like GramoFile or other specialist tools ) (12 votes)
      • Built-in Expander (which is often coupled with a noise gate) (14 votes)
        • Compressor could include expander function (1 votes)
        • Presets such as for dbx/HighCom (1 votes)
      • Filters:
        • Bandpass (3 votes)
      • DirectX effects not just VST (7 votes 28Jan19)
      • Pitch correction after setting to required key (like Auto-Tune), including T-Pain forced pitch effect (13 votes)
      • Pitch accuracy analysis: (1 votes) Could be a Nyquist effect that shows the average pitch with cents deviation of labeled notes, or average pitch then on a further run adds a waveform representation of the labeled audio showing pitch deviation over time. See: https://forum.audacityteam.org/viewtopic.php?f=42&t=73796.
        • Better as another View Mode accessed from Track Control Panel instead: (1 votes)
      • Room Panning: Pan different tracks to different parts of a room for surround sound effect.(4 votes)
      • Channel Mixer (built-in): (1 votes) Similar to the Nyquist Channel Mixer but built-in with real-time preview, which would be particularly useful when using the effect for widening or narrowing the stereo field.
        • Stereo widener (2 votes)
      • Stereo effect from mono (3 votes)
        • use FFT? (1 votes)
      • Smoothen effect, perhaps using a weighted average (or a better method)(1 votes)
        • I wonder about a tool to easy removing of noise could be useful in the application. Like the rubber tool in f.ex. photoshop. The rubber tool should flatten the noise when you touch the noise. It would then be possible to remove noise with less zooming. And maybe it could be useful to have the possibility to set the pencil to (f.ex. with SHIFT ) only go complete horizontally.
      • Specialised Voice effects:
        • Basic: Change gender, Change age, Chipmunks, Zeus (11 votes)
          In the case of a track where the vocals are not solo but mixed in with other audio, how well this works depends how amenable the vocals are to being isolated. See Vocal Removal plug-ins.
      • Advanced formant tools: (6 votes) Professional pitch change/tune while retaining the formants, so retaining the characteristics of the original voice
      • Advanced filtering/analysis tools: like Praat (1 votes)
      • Text to speech: Possibly by implementing eSpeak in Audacity (1 votes 26Sep17)
      • Dolby B/Dolby C filters for converting to/from tape recordings in Dolby) (4 votes)
        • Will need quite a lot of trial and error by ear, as the Dolby process is recording level dependent. Needs expander and treble cut.
        • I agree. It would be tricky to get it right without straight-up copying the actual process. This would be a licensing no-no. Trust me, I work at Dolby.
        • There is a Winamp plug-in which simulates Dolby decoding here.
      • Exciter to enhance album or tape recordings. It is actually an easy effect and only needs a high pass and distortion. This is widespread use in recording studios and radio stations.
          There are definitely some entries in the Forum for this - I will count votes later
      • Deverb/Echo Cancellation: Echo Removal Tool/Deverb slider. This could improve back-of-the-room recordings. Sliders are "Liveness," "Room Size," "Room Oblongedness," and "Dirt" (same as sliders in an Echo Generator). (8 votes)
          Deverb is exceptionally difficult and virtually unknown in audio software except Postfish.
        • Can't both deverb and echo cancellation be implemented by convolving the signal with a modified version of the room's impulse response?
        • No, those operations can't be performed by convolution, this is the case where deconvolution (aka inverse convolution) has to be used (well, not always).
      • De-essing (5 votes)
      • Re-essing: This is to improve the sound of already low bandwidth voice recordings by adding higher frequencies.
      • Multiply two frequencies multiply waveforms together as in AM radio
      • Convolve two audio signals (5 votes)
        • Yes, I realize that there is a lot of difficulty involved in avoiding clipping. Audio convolution can be used to make very convincing reverb effects. Please don't set limits for the length of the convolution signal. I want to be allowed to convolve much longer "regular audio" signals together.
        • Convolution is built into the Nyquist language and is an incredibly powerful feature. If I understand correctly, one could take a simple click, perform any combination of filter/chorus/echo/reverb/equalization/etc. on it, and then apply this pre-calculated set of effects to a long signal. Why wasn't this added long ago, along with multiplying and adding signals? Implementing convolution
        • Combine this with EQ Matching proposal?
      • Chorus: (10 votes 17Feb17)
        • Only needs rate and depth controls (8 votes)
        • Multi-voice Chorus (1 votes)
      • Chop with segments of silence:
        • Merely adding in a definable length of silence after a set amount of time from the original stream. This would produce a cutting in and out effect, much more abrupt than a tremolo. It would need only two or three parameters, length of silence and length of audio.
      • Suppress quiet signals. A squelch level suppression to squelch out signals below a adjustable preset level. (originally this was in the recording enhancements section - but it's better as an effect.).
      • EQ Matching: (4 votes) SmartEQ function to sample the frequency spectrum of a given piece of audio with a pleasing equalisation, then bring a second piece of audio to the same spectral content. Useful for most cassette recordings and other other medium- and low-fidelity sources. Also usable for sfx. Note: where frequency content falls to the noise floor, this may increase noise level heavily in an attempt to compensate. This is easily addressed afterwards with the Noise Removal, or can be addressed during frequency correction with more coding. Possibly could be incorporated as a third radio button in the current 1.3.x equaliser, with a "Get Frequency Profile" button and ability to add useful profiles as a custom preset.
      • Envelope follower: (4 votes) Dynamically modulate the volume of one track to match the volume of another. Select a waveform, extract its volume changes over time then apply these to another waveform making its envelope behave in exactly the same way.
      • VCO-Synth: Something like a combination of Voltage-Controlled Oscillator and the "Sample and Hold" modules of the old ARP 2600 Synthesizer [analog].
        • You could sample another waveform (in another track) at regular time intervals, and the instantaneous level of the sample determines the frequency of a tone generated for the same interval of time. In the real-world Arp 2600, you could patch the output of a VCO (or other audio source) into the input of the S&H module, then patch the S&H output into the control voltage input jack of another VCO. In the Audacity version, the user makes a selection in the track to be sampled (analogous to the first VCO) , and then (in a dialog box) selects the time interval between samples, the minimum and maximum frequency to be generated. The duration of the resulting sequence of tones to be generated in a new track would be the same as the duration of the original selection. Optional - select sine, sawtooth, square, or triangle waveforms for the generated tone. Another option would be to be able to sub-divide the length of the selection into X number of sample intervals, as opposed to specifying the duration of the interval. Typical results would be a sequence of discrete pseudo-random (frequency) tones at regular intervals, like a retro movie sound effect for a computer that's busy thinking. Another example: Sampling a triangle waveform whose period is much longer than the sample interval would result in a series of ascending and descending stepped tones.
      • Reduce Formant / Boost the fundamental frequency of a signal - replace a vocal or instrument signal with the sine wave or square wave of the fundamental frequency of that signal. Would help identify notes through overly distorted or overlayered signals. forum post (1 votes)
      • Transfer Function Effect in time domain: (1 votes) Drawn with mouse, with presets and import/export.
          Nyquist has arguably more powerful functionality, but not graphical. So many rules could apply in any one case that the transferability would be very limited and case-specific.

      Other Improvements to Effects

      • Effects Categorization: Allow the effects dropdown menu capable of sub-folders or categorisation so that the user can organize his plug-ins however he wishes. (49 votes)
        • Include "Favorites" folder at the top for frequently used plug-ins (either autogenerated and sorted by number of calls, or user-added) (21 votes)
        • Only two levels deep: (Effects > Category), not 3 levels as tried before (Effects > Category > Sub Category). Sub categories are just too fiddly and too much clicking. With just one level of categories, the menu will open by hovering the mouse, making locating a specific effect much quicker and easier. (7 votes)
        • Preference to turn categorisation off (5 votes)
        • Fully user-customizable categories and sorting of entries (5 votes)
          • Ability to assign one effect to multiple categories: (1 votes) such as a saturation compressor to both Compressor and Distortion categories.
        • Detect/display subfolders of the "Plug-Ins" folder as categories: (6 votes) So if you have a folder called /Plug-Ins/MyEffects/ the menu shows Effects > MyEffects > (effects in the MyEffects folder).
          How does this work for plug-ins in system folders?
      • Done.png Must support VST plug-ins (5 votes)
        • Must include VST plug-ins in system folders (4 votes)
      • Manipulate effects with a dialog box that has all plug-ins on the left hand side, an empty box on the right hand side, with "New Group...", "Delete Group", "Rename Group", "OK", "Cancel" buttons below, and arrows ">>" and "<<" in the middle, to move plug-ins between groups. (2 votes)
      • Multiple columns for different groups of effects (1 votes)
          1.3.6 Beta had incomplete categorization of Nyquist and LADSPA plug-ins. Categorisation has a penalty in more difficult navigation, and was withdrawn from 1.3.7 until there is (at least) a way to turn it on and off.
      • General (Effect menu items):
        • Mouse scroll the Effect Menu (8 votes)
          • without scrollbar (3 votes)
          • with scrollbar if necessary to make it work (1 votes)
        • Real-time preview effects to have a method to apply and close in one go (6 votes 08Mar18)
        • Effects stay open after processing (5 votes). User-added plug-ins (at least, Nyquist) should have this capability too. Use cases:
          • Multiple pass effects such as Noise Removal
          • Facilitates repeating an effect on different selections but using different settings for each
            • An alternative would be a "Re-show last effect" shortcut as per GIMP
          • Useful if an effect is able to change the selection while open
          • Useful if plug-in has displayable help files like some Nyquist plug-ins
        • Plug-ins can have different number of input and output tracks: for example surround encoder in the plugin.org package needs four inputs but produces two outputs. (1 votes)
        • Preview effects for whole duration of a selection with option to loop the preview (3 votes)
          Ability to choose preview length has been added to the Audacity 2.x.
      • Compare original (dry) with new (wet): (9 votes)
        • Dry and Wet Preview buttons (5 votes)
        • Visual comparison (2 votes)
        • Loop dry and wet in succession (1 votes)
      • Curve Editor for each effect to adjust how ferociously the effect changes the sample by time (posted on behalf of nitrotrigger on IRC) (3 votes)
      • On-Demand effects: (2 votes) Effects apply while you continue to work (hear them applied in one part of the track by clicking there)
      • Defaults:
      • Done.png "Defaults" button (4 votes)
      • Marker on sliders to indicate default value (2 votes)
      • more features (6 votes)
      • more algorithms especially impulse response convolution reverb (7 votes)
      • Very strong opinions to consider Freeverb3 as the "best" benchmark/starting point for reverb types and features (but don't include the whole suite as is) (14 votes)
      • sensible presets that do not depend on mixing with a duplicate to sound decent (6 votes)
      • Wet/Dry mix control (2 votes)
      • stereo output.(4 votes)


          The Harrison implementation looks like an example of how to implement GVerb well, but that depends at a minimum on Audacity supporting real-time effects.


      • Amplify:
        • Linear "New Peak Amplitude" input: less confusing because it matches with default waveform (and the generate effects) (4 votes)
        • Toggle non-destructive clipping when in 32-bit float quality (1 votes)
        • Option to launch at last used amplification level: (5 votes) even if the New Peak Amplitude is different each time. Use case is trying/undoing different amplification amounts to get the one you want, and you want to see quickly what you last tried (or do it again if you think that will give you the desired result.
        • Presets in dropdown menu: (2 votes)
        • Default to last used maximum dB level: (1 votes) Currently it defaults to 0 dB whereas Normalize defaults to last used maximum.
      • Bass and Treble:
        • Reinstate Bass Boost effect or add Frequency control to Bass and Treble: (7 votes)
      • Change Speed/Tempo/Pitch:
        • Gradually increasing/decreasing tempo changes (without pitch change) to facilitate DJ-style mixing (6 votes)
        • Allow changes in tempo/speed to be applied on the fly from the current (and ongoing) playback position. Currently changes in speed forces reverting to the start of cursor. (1 votes)
          Edit > Move cursor... > to Selection End?
      • Change Speed: length of selection control like Change Tempo (19 votes)
      • Change Speed: Use a change factor (e.g. 0.5x means half as fast, 2x means twice as fast) so that users are not confused by -50% doubling the length/halving the frequency, while you need +100% to halve the length / double the frequency Template:Votes9
          This is now available with a "Speed Multiplier" control.
      • Also for "Change Tempo" and "Change Pitch": (1 votes 27Jan21)
      • Change Speed: semitone pitch change control (3 votes)
      • Change Tempo: allow calculation of % change from less than whole BPM values. (3 votes) At slower tempi a non-integer change in BPM could mean a percentage change of two or three percent. Please notify info_AT_giovannierata_DOT_it if fixed...
      • This also allows this field to be used for any freeform units such as frames per second (3 votes)
          This functionality will be available from Audacity 2.0.4 onwards.
      • Change Speed/Tempo presets (8 votes)
        • Change Speed presets to/from 16 RPM (1 votes)</ul>
      • Dynamic Transient sharpening in Change Tempo/Pitch as in Sliding Timescale/Pitch Shift (without sliding of course) (2 votes)
      • Option to use higher quality sbsms algorithm from Sliding Timescale/Pitch Shift (or amalgamate the tools so all that can be done in Change Tempo/Pitch can be done in Timescale) (3 votes)
      • Window size choice in Change Pitch to combat FFT artefacts (1 votes)
      • Click Removal:
        • Detection for clicks that are of similar level to surrounding audio or generally more reliable detection (28 votes). Click Removal gives hints for other solutions, but one tool should do the job in most cases, as with other software.
        • Intelligent joining to boundaries (1 votes) like Repair so that doesn't potentially add artefacts by almost silencing the samples it replaces so leaving abrupt joins with the unchanged audio
      • Compressor:
        • Multi-band: (8 votes) so retaining the same frequency distribution.
          • Include a de-esser in this: (1 votes)
        • Process stereo pairs together: (7 votes) so that the same amount of gain reduction is applied to both channels. The current Compressor applies different gain reduction to each channel which can lead to shifting of stereo image.
        • Shorter attack/release times: (5 votes)
          • Show attack/release times in milliseconds: (1 votes)
        • Text box input: (5 votes)
        • Configurable lookahead in milliseconds: (4 votes) so pre-emptively apply the compression. Don't just make it the same as the Attack Time as now.
        • Choose upward or downwards compression independent of peak or RMS envelope: (2 votes)
        • Choose make-up gain amount (2 votes)
        • Built-in Hard limiter/dual slope/tabbed for different settings (2 votes)
        • Presets for common tasks: (2 votes) such as "Levelling speech", "Maximizing", "Audiobook compression", "Peak limiting". Eliminates the need to install third party compressor plug-ins for casual users.
        • Finer Ratio discrimination than .5: (1 votes)
        • Envelope-based tool that just works by dragging as in Digital Performer (1 votes)
      • Equalization:
      • Reinstate 78 RPM EQ curves from Audacity 1.2: (25 votes)
          You can generate a large number of company-specific 78 RPM and pre-RIAA LP curves using the experimental Nyquist plug-in "78 RPM EQ Curve Generator" and the curve tables on 78rpm playback curves.
      • Automatic 78 RPM EQ from RIAA-recorded 78's: (9 votes) Inverts the curve to negate the RIAA EQ then applies the required 78 RPM EQ in one button press. More 78 RPM presets facilitate this (votes as above)
      • De-emphasis for early CDs: (2 votes) using the WaveEmph or other curves (see http://www.hydrogenaudio.org/forums/index.php?showtopic=65067 )
      • Improve accuracy:
        • Text input (8 votes)
          • like Cool Edit's right-click on control point then type the values (2 votes)
          • Edit box like Label Editor that would list all the points and allow normal editing functions like copy and paste (1 votes)
        • Text entry box when double-clicking on Graphic EQ sliders as elsewhere (3 votes 28Nov17)
        • Cursor readout (8 votes 28Nov17)
        • Zoomable grids (5 votes)
      • Simpler/more presettable Graphic EQ: (3 votes) Either an alternative interface with current EQ, or an additional built-in effect. 5 - 7 bands would be adequate/quicker for our many casual users. Greater range of general purpose presets needed such as "heavy bass boost", "light treble reduction", "equal loudness".... These should be separated from other e.g. gramophone presets.
      • Graphic EQ sliders should allow choice of bandwidth (1 votes)
      • Separate built-in Parametric EQ (3 votes) i.e. where all parameters controlling the tone change have their own control.
        • high pass, low pass and 3 or more bands (1 votes)</ul>
      • Add built-in envelope so that amount of EQ (% of gain specified in parameters) can be varied over time (1 votes)
      • Mini-waveform (2 votes) (time against amplitude) in which you can click to preview - see Wavepad
      • Incorporate mini-spectrum plot (7 votes) ideally it should change when you modify the EQ curve
        • Include dry (pre-effect) spectrum too (1 votes)
      • Save Presets without renaming "unnamed" (4 votes)
      • More frequency-specific presets like "Very Bright", "Mid-range", "Classical", "Hard Rock", "Soft Rock", "Dr Dre" (3 votes)
      • User-saved presets should save filter length and Draw/Graphic mode (1 votes) e.g. a curve with low frequency control points will require maximum length to be reasonably accurate but this length will slow down processing of other curves un-necessarily.
      • Smart Normalize before EQ to safe level for the requested curve (1 votes)
      • Remember window size and position (3 votes)
      • FFT Filter seems to be missing in 1.3.3 (and in 1.3.5)
          The linear frequency scale in Equalization provides the same functionality
      • Auto Complete Equalizer Graph: I created a simple equalizer graph to get somebody out of trouble recently. I think it was a lot more bother than it needed to be. Here's an illustration of an Adobe Photoshop tool. See: http://audacityteam.org/wiki/index.php?title=Image:Curves2.jpg Note that there's only one new data point on the right-hand brightness curve, and yet Photoshop automatically produced a graceful, gentle, useful curve typical of a picture whose natural lighting had actually changed. It did not produce two straight lines and depend on me to painstakingly calculate the new points and put the rest of the curve in by hand. I want the equalizer work window to run like that.
        • SteveTF responds: Since Audacity does not currently support graphical interfaces for effects (which rules out the "CoolEdit Pro FFT filter" type GUI), could this be done using a bunch of sliders?
        • Koz responds: It could, but to figure out where the sliders go, I'd be curled up on the living room floor with my Toshiba adding machine, my Terman's book of six place log tables, number two lead pencil, and nice legal pad. If only we could make a machine to do these laborious calculations for us....
      • Display curve name in Filter Curve EQ: (2 votes 27Dec20) Only when unmodified preset is in use.
      • Generate:
        • Provide way to default selection format to other than seconds. Either store the format in .cfg or let it default to the current Selection Toolbar format (36 votes 09Aug17)
          • "last used" is better (14 votes)
          • "same as Selection Toolbar format" is better (6 votes)
          • Possibly generation at a region should always default to hh:mm:ss + samples, but still allow different choice to be saved in Preferences (6 votes)
        • List notes for tone generation: (4 votes) e.g.middle C (264 Hz) etc.
        • Applause (1 votes)
        • (2.x) Text box input as in 1.2, because much simpler to overtype irrespective of the format, and allows copy and paste (8 votes)
        • Choice of overtones to include: (within the limitations of the waveform chosen) (1 votes).
      • Generate follows Recording Channels: Generate should give me stereo tone if Recording Channels is set to stereo in Device Toolbar (1 votes).
      • Noise Removal:
        • Save Noise Profile for re-use in another session such as the previous method in Audacity 2.x where enabling CleanSpeech mode loaded a saved noise profile).(9 votes)
        • Import/export noise profile as text file
        • Profile graphs showing an FFT of the noise profile at capture and graphs before and after removal step
        • Reset to Defaults (2 votes)
        • Modeless window: (5 votes) like Analyze > Contrast that lets you modify the selection with the window open. Clicking "Get Noise Profile" could then grab the profile but leave the window open while you select the audio to be noise-removed.
        • Presets (including user-addable) such as "light hiss", "60Hz hum" (2 votes)
        • Leave Only Noise option as in Adobe Audition. When user performs this on a duplicated track which is then inverted and mixed with the original, it allows noise to be removed by pure cancel-by-inversion.
        • Implement as a plug-in DX or VST, so people could use it in other applications. To filter noise out of mic input in real time, for example (1 votes)
        • Better noise removal without fiddling with sliders: (2 votes)
      • Normalize:
      • Done.png Replay Gain or RMS: (20 votes) The current peak value normalization is far from what human ears perceive. If hard to implement, we can normalize to RMS (light blue in waveform) values instead
      • Percentages: as an alternative to decibels. Many people have problems with decibels. (3 votes)
      • Smarter Normalize when isolated peaks much higher than others: (5 votes)
        • Ignore isolated peaks: (3 votes) An adjustable percentage of the highest peaks are ignored for purposes of calculation, simply being left at the original level
        • Sacrifice quality in isolated peaks: (1 votes) Create histogram of levels that lets user choose normalisation dB or percentage and a percentage (or per thousand/million/billion) of peaks allowed to exceed the normalisation level
        • Choose whether to ignore any peaks over 0 dB or not: (1 votes) (some intersample peaks may be deliberate).
      • Option to calculate track gains together to avoid changing stereo balance: When multiple stereo tracks are selected, only the highest peak level of ALL tracks should be considered to adjust each track by the same amount so that the volume of each track relative to each other will stay the same. (6 votes)
          This is what Effect > Amplify does. Some people would argue "Amplify" should be called "Normalize". 2/0.x has an option to "Normalize stereo channels independently". If unchecked, this retains the channel balance in stereo tracks while still letting all tracks be normalized independently. It does not replicate Amplify by only calculating the amplification needed to bring the loudest channel or track to the required New Peak Amplitude, then amplifying all tracks by that amount. Some people do want Amplify and Normalize to be merged - see the vote below - but care is needed so that too many options are not provided which could make a single effect too complex.
      • Normalize should be merged with Amplify (5 votes)
      • Display the current absolute peak level: (1 votes)


      • Nyquist plug-ins:
        • Preview Button: (2 votes)
        • Bundle as one large zip file: (2 votes)
        • Tabbed Interface: (3 votes) Could allow a simple interface on one tab and an advanced on the other, or help on the other tab
        • Remember settings post-session: (3 votes)
      • Repair:
        • Vastly increased length of track to be worked on/works when zoomed out: (37 votes)
          See here and this zip for attempts to integrate Repair with Find Clipping
          • If selection made is too long, truncate it to maximum possible, but still let user drag the selection in either direction retaining the maximum length (4 votes)
          • Show the length that can be processed in current Selection Format, not samples (2 votes)
          • Show an approximate processing time for long selections. (1 votes)
      • Repeat:
        • Add Delay so as to merge each repeat smoothly (5 votes): Current Repeat effect gives a very dry result compared to creating and playing a loop in software sequencers or drum machines. Some delay could be added after the end of the region to be repeated, then the start of each repeat has this delay mixed in.
        • Checkbox for "do not create split lines": (4 votes) visually very distracting when fitting project to window.
        • Insert Silence between repeats: (1 votes 15Mar17)
      • Sliding Time Scale/Pitch Shift:
        • Percentage control for pitch (2 votes) so that conversions into semitone changes are avoided
        • Envelope GUI (2 votes)
      • Truncate Silence:
        • New option to work on each track separately not on mix (8 votes)
        • New option to truncate only leading and trailing silence (2 votes)
      • VST Plug-ins:
        • Option for rescan on each launch plus "once-only" checkbox to restart on OK'ing Preferences (9 votes)
        • Rescan without restart (5 votes)
        • Install VST Effects dialog: Sort Name and Path separately (3 votes)
        • Put the name of the effect first in the menu or omit manufacturer (6 votes)
          You can quit Audacity, open Audacity's folder for application data, then open pluginsregistry.cfg and carefully exchange the Name with the Vendor information and the Vendor with the Name information. Your change will only persist until you rescan plug-ins, of course.


      Installation/first run, deployment and uninstallation

      • (Windows) Choose English language: (14 votes)
      • (Windows) MSI installer for multiple installation on networked computers (9 votes)
          There is a script here that allows multiple installation via Group Policy or a tool to make an MSI installer here.
      • (Windows) User-customizable location for Start Menu shortcut (2 votes)
      • Complete uninstallation including removal of Audacity settings and temp folder (5 votes)
          Not very clear how this could be done outside of Windows installers unless there was a separate executable to remove settings. Where there was an uninstaller, it could include a "repair" option to reset settings instead of having a separate executable to repair or remove them.
      • All-users settings, not per-user: (11 votes) This frees new users in a multi-user environment such as a college or audio lab from having to configure paths or features that have to be chosen on first use, such as language (in 1.2), LAME or FFmpeg (in Audacity 2.x).
          You could run a script the first time a user logs on or otherwise pre-load their account with the settings wanted for Audacity.
      • "Plug-ins" and "Modules" folders in Audacity's data folder (2 votes) (where audacity.cfg is). On Linux this means root access is no longer needed to modify these folders, and custom plug-ins aren't lost when updating from a package manager. OTOH "Plug-ins" and "Modules" would be hidden. This would be a drawback for Windows users which might outweigh the benefit of per-user plug-ins and modules.
        • Let user choose folder location (2 votes) could be done via an AUDACITY_PATH environment variable for all platforms, or via an "Effects Manager" (doesn't matter then if folder is hidden), or via Preferences.

      Improved Resource or Project Management

      • Additional options for saving "Compressed Copy":
        • Lossless: (3 votes 21Feb18) Option to use FLAC (and / or other lossless compressed format) rather than Ogg.
        • One file per clip: (1 votes 24Nov17) rather than one file per track.
      • Priority:
        • Set overall Audacity priority: (6 votes) Raising Audacity priority can reduce risk of recording skips. Reducing might make it easier to work in other applications while exporting or running long effects. Could be a Preference but better to set on the fly with a button, its value stored in audacity.cfg and used on launch. Otherwise you need hacks such as computer's Task Manager to change priority after launch, or a shortcut to do so at launch using some external software.
        • Per-thread or per task priority: (3 votes) Useful when Audacity projects and processes are separable and threadsafe.
      • Progress bar for waveform drawing: When I do a control-f (zoom to fit in window) in audacity on a 2 hour recording it takes a while before the waveform is displayed. Some busy indicator, maybe even progress bar might help. Same for moving around in a file, which can take time. (even on striped disks) This also affects re-drawing of the waveform after applying pretty much any Effect. (6 votes)
      • Disk space check before exporting: (16 votes) - including indication of expected size of export, and choice to export partial file or cancel if insufficient space available. Would stop user exporting WAV files over the 2/4 GB limit, MP3s in excess of ringtone limits etc.
          Could only indicate that space was available at time of checking, could never guarantee the file would be completed if other disk events occurred. However Audacity 2.x does now have a warning if WAV/AIFF exports are not completed.
      • Capability Hints in GUI: Search and recognize existing hardware capabilities. Specifically, note limits on quality achievable due to RAM configuration, DAC bit counts, soundboard specifics such as dB gain at recording levels (41, 44, 96), and other software installed on the machine (iTunes, other popular players / organizers). Then customize recommendations by what is doable on that machine, but still allow anyone to get extreme if they wish. (1 votes)
      • Detection of operating system with warning if Audacity version inappropriate: (1 votes) Suggestion made primarily due to problems with Mac users having the wrong version of Audacity 1.2 for their architecture then the correct LAME binary is not recognised, though most of this particular problem will disappear when 2.0 comes out as a universal binary. Maybe useful when 2.0 is mainstream and does not support OS X 10.3?
      • Undo History:
        • Compress undo buffers (2 votes)
          • (You can already clear the Undo buffers by opening the Undo History dialog box, and compressing will take lots of CPU and have little space gain unless you use a lossy compressor, which kind of defeats the point of undo...)
        • Make Undo history viewable (but not actionable) after close project: (17 votes) just so you can see what those actions were. Can be done by:
          • Export undo history or complete commands history as a .txt file (10 votes 14Oct18) or
          • Store Undo history in the AUP file: (9 votes) then you could look at the items (grayed out) in View > History.
            • Combine with feature to periodically save multiple timestamped AUP files as a backup (1 votes)
        • Make Undo active across sessions: (8 votes 18Aug20) Useful when projects are shared between users and you may want to undo the last thing(s) that someone else did. This saves the much larger space requirements as now of saving multiple backup projects at different stages of project progress.
            This could potentially require vast amounts of disk space, so could never be default.
        • Autosave history, so it can be restored after a crash: (1 votes)
            Autosave is currently inefficient in long projects, scanning the entire data. As of 2.0.6-alpha there are many actions that appear in history that are not autosaved. It may or may not be possible to periodically "export" the history list every N minutes to the AUP file, bypassing the data scan.
        • More detailed/organised: (3 votes)
          • includes EQ Parameters applied (1 votes)
          • includes which tracks items were applied to (3 votes)
          • should have separate entries for each track (1 votes)
        • Add mute/solo state to history (1 votes)
      • Project manager utility: (6 votes) Could include:
        • Safe renaming/moving/deleting of projects
        • Choose multiple projects to export from/import into at one go (including export multiple ability from each project)
          • "Project Jukebox" to play selected projects in sequence (1 votes)
      • Project integrity:
        • Make copy-in default: Only this will completely avoid danger of user deleting dependent files. (5 votes) - this is now the default in current Audacity
        • Store copy of .aup or autosave file as a backup (8 votes) Could be a vital recovery feature if a crash or error on saving causes the file to be corrupted or destroyed.
        • Incremental version check on audio file data (a la Volume Shadow Copy) because as of now, it seems to save anything it can and wants (1 votes)
        • Provide official MD5 and/or SHA1 sum (1 votes)
        • Save timeline/track position metadata in each .au file to allow recovery if .aup file missing or damaged (2 votes)
            Could have a significant performance impact as editing may require continual resaving of all the .au files
      • Better multi-threading/multi-processing support: (18 votes) to use full potential of Dual-Core/multi-processor machines when exporting/editing the audio. Use Lisp process delegation for multi-core processing and (harder) multi-threaded operation. (Think: divide and conquer, process pools that operate on portions of the waveform and joining the result, and you will arrive at a solution)
        • Better thread separation (9 votes) to allow safe execution of simultaneous tasks to improve workflow. It should be possible on a modern machine to do things like simultaneously record in separate projects; record in one project while editing or exporting from another etc.
            LRN wrote: Multi-threading means two different things. 1: "Do two things simultaneously". This requires Audacity redesign to be more threaded. OpenCL wouldn't help here. On-Demand Loading is an example of threaded design. 2: "Do one thing in two threads, which makes it go about two times faster". This requires special implementation and OpenCL would help. But it's not cost-effective to rewrite everything in symmetric multi-processing style. Only costly operations should be made parallel, everything else would benefit more from threaded design.
      • Additions to AUP project file:
        • Current View Mode of each track: (3 votes) "Default View Mode" in Tracks preferences will then affect only newly created tracks. View mode changes alone, like other view changes, may still not be sufficient to prompt for save of the project when closing.
        • Window sizes and x/y positions: (3 votes)
      • Take advantage of unused GPU cycles: Graphics processing units have the processing power to run 3D image but Audacity doesn't use hi-res 3D. This unused power could potentially be harnessed to speed up audio processing. (4 votes)
        • Use Nvidia's freeware CUDA parallel computing engine (1 votes)
      • Improvements to audacity.cfg:
        • Export and Import (1 votes)
          • Immediate application of changes like modifying xml files: (1 votes)
      • Audio clip library manager (built in): Many audio editors / DAWs have some sort of "library manager" that allows quick and convenient access to audio clips for use in the current project. (28Aug18 votes 3)

      Imports and Exports

      Import Appended: (39 votes) Import multiple files end-to-end in a single track. Would allow re-assembly/re-processing of LP/tape recordings for which no Audacity project exists. Also allows to import multiple tracks for CD assembly

      Possible Enhancements:

      • with labels containing their file names
          If not labeled, it will be important for many use cases that the imported files remain as separate audio clips.
      • Import multiple files (or even a single file) at cursor position:
          You can always Project > Import Audio and SHIFT + click or CTRL + click to select and import multiple files into a project as separate tracks. There is no automated process beyond that. No players can read the labels in the joined track other than Audacity - they aren't bookmarks in that sense, as there is no agreed standard for reading divisions within files. The labels can be exported to form the basis of a cue sheet.

          A Nyquist plug-in is available to test which can import multiple WAV or AIFF files end-to-end from a directory or from a list of files, starting from either time zero or from the cursor position.

      • Import one new file at cursor position: simpler/more important (3 votes)

      Import below current track: This would be useful when working with projects that have a lot of tracks. Much easier than having to manually move a track after it has been imported at the bottom of the project. (2 votes 21May19)

          This feature was first requested years ago, but appears to have been lost over time. A possible workaround would be a Nyquist Macro that moves the bottom track to immediately below the first selected track.
      • Previewing audio: A way to preview audio before importing it as a new track like with Adobe Audition? (3 votes)


      New Import/Export Formats

      There are some file formats and effect interfaces we can't support for commercial reasons. Please check our Features We Can't Implement page before adding features to the list below.
      • Import/play video for synchronized soundtrack editing (49 votes 20Nov21) No need for Audacity to edit the video. Alternatively, Audacity could send/receive SMPTE or MTC timecode data e.g. to VLC or mplayer.
      Logged as an Ehancement Request on GitHub: https://github.com/audacity/audacity/issues/2167
        • Standalone SMPTE reader useful in own right (1 votes) e.g. for reading time track on an analog tape deck.
        • Existing Timeline must show audio behind zero (1 votes)
        • Video window should have video timeline but Audacity window should not need separate video timeline (1 votes)
      • Open Media Framework Interchange (7 votes 15Apr18)
        • Open Media Framework Interchange (OMFI) is a platform-independent file format intended for transfer of digital media between different software applications. Example: multi-track to/from Audition/ProTools/Cakewalk, etc.
      • Import/Export:
        • Speex. Codec similar to Ogg Vorbis but optimized for voice. (11 votes)
        • WV WavPack (4 votes)
        • DSS (3 votes)
        • OFR files: (OptimFROG files, a lossless audio format that's smaller than FLAC).(2 votes 24Nov17)
        • MBWF (new multichannel extension for Broadcast WAV format) (2 votes)
        • MPC files (Windows) (2 votes)
        • DSD 1-bit Pulse Density Modulation (PDM) audio e.g. used in top-end portable recorders or for storage on SACD's. (2 votes)
        • C2 (Codec 2) is an open source speech codec designed for communications quality speech between 700 and 3200 bit/s.(1 votes 16Aug18)
        • RCA-VOC G.729a compression codec for RCA Digital Voice Recorders (2 votes)
        • Aud-X (mp3 5.1) files (1 votes)
        • iLBC as defined in RFC 3951. Free/Open Source. One of the codecs used by Google Talk, Yahoo! Messenger etc. Often wrapped in CAF container (1 votes)
      • Uncompressed FLAC (1 votes 20Aug17)
          Although this option is supported by dBpoweramp, it offers no benefits over AIFF and may encourage belief in snake oil.
        • BIN sound files.(1 votes)


      • Import audio from video files/transport streams: such as AVI/MPEG/Ogg Theora e.g. by demuxing (14 votes)
        • Extracting Vorbis from multiplexed Ogg files should be an easy changeover. Also note new specifications on file names (e.g., .ogv for Ogg Video, .oga for Ogg Vorbis)
      • Ability to extract and import Vorbis portion of Ogg files encoded with non-audio tracks, such as Theora. Currently gives an error "unknown format", straightforward modifications should do the trick. (2 votes)

      Other Import/Exports

      • Multi-channel import
        • Import multi-channel files as all mono tracks (2 votes 18Apr19)
      Currently, the first two channels are one stereo track, which may be split to mono, but then the track numbering is incorrect.
      • Timestamp metadata
        • CART metadata as used by radio stations There are several thousand users of Audacity who would find it convenient to have all the labeling of tracks done at the production stage rather then the 2 stages required now (4 votes)
        • Option to not write PEAK chunk or at least not write time in this chunk when exporting as 32/64 bit float WAV. (1 votes 04Dec20)
      • BWF: Support reading/exporting metadata, (including embedded timestamp information) in Broadcast WAV files (BWF) (43 votes 09Oct19)
      See:
      • cue chunks (6 votes)
      • smpl chunks (4 votes)
      • levl chunk for quick waveform visualisation (new addition to BWF as per http://tech.ebu.ch/docs/tech/tech3285s3.pdf) (3 votes)
      • plst chunks (2 votes)
      • Origination time (2 votes)
      • One reason Audacity fails to support important metadata is that it does not support export of an AES-31 compliant Audio Decision List (ADL)
            It's about priorities and to what extent mainline Audacity should support features the majority of users would not avail themselves of (even if they are "standards"). An equal case could be made for adding support for the CART metadata chunk required by radio stations.
          • Timestamp metadata is e55ssential for working on projects of longer duration (interviews, news gathering, live recording, podcasts, etc). There are dozens of digital recorders that support BWF timestamp metadata. Leaving such features out of Audacity effectively excludes a large potential audience from using Audacity.
          • As a workaround, I have just written a python program that reads the WAV file in BWF format produced by the M-Audio Microtrack recorder, and generates a text file that can be imported as a label track into Audacity via Tracks > Edit Labels.(The hardest part was to search for the information on WAV chunk formats.Guenterrote 21:53, 9 March 2010 (CST)
          • Also for recording directly with Audacity this feature would be helpful. In the Librivox wiki they recommend to click (with tongue or so) after each error so you can find back easily these "auditive markers" while editing. This idea is very handy, but clumsy. Better would be that you could press a key which then sets a marker on the soundtrack.
              If you have a finger free to press a key (or a foot if you have a foot pedal that delivers mouse clicks) then just change the Audacity shortcut for "Add Label at Playback Position" to some key that's easy to hit The comment is only relevant if you want to export an audio file with embedded markers.
      • Read/write embedded cue points in WAV files like CoolEdit (5 votes)
        • and let them contain information from Audacity labels (1 votes)
        • and have them act as snap points (e.g. marking bar or beat boundaries on rhythm samples) (1 votes)
      • Read/write embedded loop points in WAV files like Wavosaur. (3 votes)
      • Export File window:
        • New checkbox “Export at current Play-at-speed". (2 votes) by Penguin on 19 July 2008
        • Timestamp button to add a string for current system date/time in the file name (2 votes)
      • Templated Command Line Export: Add variables to the Command Line Export Options that reference the contents of the various Metadata fields. These would be similar to the %f variable for Filename already available, allowing totally automated export of files to applications that support writing Metadata to files/understand the variables being passed. (3 votes)
          Until then, a workaround to get the metadata exported when using the command line would be to disable Metadata Editor in Preferences and enter the metadata in the command line options using the relevant tag switches (for example in MP3s with LAME, --tt <title>) as described on the LAME usage page
      • Command line presets in an .ini or .xml file rather than retype over for different formats. (1 votes)
      • Command line pipes: For example [sox -t wav - -r 44100 -t wav - polyphase | lame -V6 --vbr-new - "%f"]
      • Set sample rate for export in export options: (5 votes)
        • Default could be the project rate, but if a single track is exported and has a different rate, use that rate.
      • Set bit rate for export options for all formats: (1 votes)
          Bitrate would be very confusing for most users where WAV/AIFF are concerned - it's (<bit format> * <number of channels> * <sample rate>) so 1411 kbps for a stereo, 16 bit 44100 Hz sample rate WAV.
      • Invalid sample rate dialog: Add checkbox "Apply this rate to any remaining conflicts" (checkbox state is stored in .cfg) and/or add checkbox linked to Warnings Preferences "Don't warn again and always use highest rate". (7 votes)
      • Easier file selection:
        • Allow multiple import from different directories by specifying in a list box (1 votes)
      • Automatic snap-to CDDA boundaries when exporting multiple with labels: Avoids small gaps when burning CDs, saves changing selection format and turning snap-to on manually. The FLAC encode actually has an opt