Difference between revisions of "Proposal: Rationalizing where new tracks are created to aid usability and consistency"

From Audacity Wiki
Jump to: navigation, search
(Details: M&R already done)
(Details: Recording based on selection not focus)
Line 58: Line 58:
 
* {{menu|Edit > Duplicate}}
 
* {{menu|Edit > Duplicate}}
 
* {{menu|Edit > Clip Boundaries > Split New}}
 
* {{menu|Edit > Clip Boundaries > Split New}}
 +
* {{menu|Transport > Recording > Record New Track}}
 +
* {{menu|Transport > Recording > Timer Record}}
 
In cases where there is no track selected then the new track should be added at the bottom of the track.
 
In cases where there is no track selected then the new track should be added at the bottom of the track.
 
{{note|the selected track need not be an audio track, it could be a label track.}}
 
{{note|the selected track need not be an audio track, it could be a label track.}}
Line 71: Line 73:
 
* {{menu|Analyze > ...}} when no label track is selected
 
* {{menu|Analyze > ...}} when no label track is selected
 
* {{menu|Transport > Recording > Record}} - Append record when there are insufficient track channels selected
 
* {{menu|Transport > Recording > Record}} - Append record when there are insufficient track channels selected
* {{menu|Transport > Recording > Record New Track}}
 
* {{menu|Transport > Recording > Timer Record}}
 
 
* {{menu|Tools > Detect Upstream Dropouts}}
 
* {{menu|Tools > Detect Upstream Dropouts}}
 
but would NOT apply to actions that require a track selection.  
 
but would NOT apply to actions that require a track selection.  

Revision as of 12:07, 3 June 2020

Proposal pages help us get from feature requests into actual plans. This page is a proposal to rationalize where new tracks are created to aid usability and consistency.
Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.


  • Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.


The Problem

Where new tracks are created has mostly been out of the control of the user. Mostly these are placed at the end (bottom) of the project, which may not be ideal particularly for users with large multi-track projects.

We have received Feature Requests from users who would like to control where new tracks are placed in their project.

We fixed this a while back for a) Mix and Render where the new track replaces the last selected track b) Mix and Render to New Track where the new track goes below the last selected track

Since we have changed this to be based on selection (and not on focus) it makes sense for consistency, that other commands that create new tracks should also position the new track: 1) based on selection - i.e. normally below last selected track, 2) IF no selection is present THEN at the bottom of the project.

Proposed Feature

We should allow greater user control of where new tracks are created in Audacity by whatever means.

We should aim for consistency in our approach in doing this. Vnd thus since we chose "Selection" as the basis for Mix & Render we should continue in that vein.


Developer/QA Backing

  • Peter


Use Cases

From User CharlieSummers on the Forum

Is there any way to coerce Audacity to create a new track under the currently-selected/working track instead of at the bottom? My workflow is such that after importing the tracks for the weekly show, I need to create tracks (mono and label, mostly) for copy/paste from other windows (voice tracking, interstitials, etc.). They show up at the bottom, and need to be dragged upwards to the currently-working area past all the imported tracks, fixed ending tracks, and such; which is...awkward with a lot of over-under-shooting, especially when I'm tired or in a hurry. (Deadlines? DEADLINES???)

Is there some secret key combination I don't know about that will create the track (regardless of type) directly below the currently-focused track instead of way down there?

See P3 ENH: Bug #2219 - ENH: Add new track places the track at the bottom of the project - should be under user control


Details

The behavior varies depending on the command used and whether or not a selection exists.

These commands should create the new track after the last (bottom-most) selected track

In these cases the commands act on the selection and not focus, so the new tracks will be relative to the selection.

  • Tracks > Add New > Mono Track
  • Tracks > Add New > Stereo Track
  • Tracks > Add New > Label Track
    • also applies when a label track is created as a result of adding a label when no Label Track exists
  • Edit > Duplicate
  • Edit > Clip Boundaries > Split New
  • Transport > Recording > Record New Track
  • Transport > Recording > Timer Record

In cases where there is no track selected then the new track should be added at the bottom of the track.

the selected track need not be an audio track, it could be a label track.

Already done:

  • Tracks > Mix and Render
  • Tracks > Mix and Render to New Track


These commands should create the new track after the currently focused track

The behaviour would thus be the same for:

  • Generate > ... when there is no selection
  • Analyze > ... when no label track is selected
  • Transport > Recording > Record - Append record when there are insufficient track channels selected
  • Tools > Detect Upstream Dropouts

but would NOT apply to actions that require a track selection.



This command always goes at the top of the Project

  • Tracks > Add New > Time Track

Focus

In all cases (bar the exception below) Focus should be transferred to the new track.

Exception:

There is at least one case where this should not be the case. If the Use dialog for name of new label option is checked in Tracks Behaviors preferences, and creating a label causes a new Label Track to be created, then when the new label dialog closes, focus is returned to the original track. This is for the benefit of keyboard users.


GUI Examples

Not needed.


Previous Feature Requests relating to this proposal

Resolved Fixed

  • P2 Bug #2214 - Rendering a single track unnecessarily moves the track to project bottom