[Known Bug] Cmd-1 broken after numeric range edit
Forum rules
This forum is for Audacity on macOS 10.4 and later.
Please state which version of macOS you are using,
and the exact three-section version number of Audacity from "Audacity menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Please state which version of macOS you are using,
and the exact three-section version number of Audacity from "Audacity menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
[Known Bug] Cmd-1 broken after numeric range edit
When trying to clip out a segment of a music bed to shorten it, I found I was having trouble as follows:
1) Set start point with mouse
2) Set end point with mouse
3) Play around cut with 'C'
4) Adjust start and end points by clicking in the number fields in the footer and adjusting
5) Play again with C; still not happy
6) Hit Cmd-[ to zoom to start
7) Hit Cmd-1 to zoom in to adjust by eye
Expected behavior:
Window zooms in horizontally with start point of selection staying centered.
Observed behavior:
The digit 1 replaces whatever digit was next in the selection position field in the footer, as many times as I hit it.
There is, at that point, no way I can see to pull focus *out* of that field because everything I try loses my selection -- that's a separate issue (is there a way to mark a fixed named selection range which won't fall off as I navigate around or click in the track to preview part of it, that I'm missing?).
The "my 1's go into the text field instead of being interpreted as commands" thing seems like a bug to me; can anyone repro it?
[ billw58 confirms below it's a known bug; Cmd-F6 will break you out of those fields, presumably without losing your selection range. ]
1) Set start point with mouse
2) Set end point with mouse
3) Play around cut with 'C'
4) Adjust start and end points by clicking in the number fields in the footer and adjusting
5) Play again with C; still not happy
6) Hit Cmd-[ to zoom to start
7) Hit Cmd-1 to zoom in to adjust by eye
Expected behavior:
Window zooms in horizontally with start point of selection staying centered.
Observed behavior:
The digit 1 replaces whatever digit was next in the selection position field in the footer, as many times as I hit it.
There is, at that point, no way I can see to pull focus *out* of that field because everything I try loses my selection -- that's a separate issue (is there a way to mark a fixed named selection range which won't fall off as I navigate around or click in the track to preview part of it, that I'm missing?).
The "my 1's go into the text field instead of being interpreted as commands" thing seems like a bug to me; can anyone repro it?
[ billw58 confirms below it's a known bug; Cmd-F6 will break you out of those fields, presumably without losing your selection range. ]
Last edited by Baylink on Thu Feb 05, 2015 4:57 pm, edited 2 times in total.
-
kozikowski
- Forum Staff
- Posts: 69373
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
Re: [Possible Bug] Cmd-1 broken after numeric range edit
Audacity doesn't have Edit Markers like a video editor. The best you can do is set labels at the two edit points. You can move and tune them as needed.
http://manual.audacityteam.org/o/man/label_tracks.html
Labels are sticky and you can drag-select your clip and work on that. You can also use the "region" tools.
Koz
http://manual.audacityteam.org/o/man/label_tracks.html
Labels are sticky and you can drag-select your clip and work on that. You can also use the "region" tools.
Koz
Re: [Possible Bug] Cmd-1 broken after numeric range edit
I assume drag-select will snap to the labels, and that'll be good enough. I'll give that a try, thanks.
I still gotta think, though, that if my primary report is reproducible, that it's a bug. Or "there's no way to get the focus out of those number fields" is, take your pick. :-}
I still gotta think, though, that if my primary report is reproducible, that it's a bug. Or "there's no way to get the focus out of those number fields" is, take your pick. :-}
Re: [Possible Bug] Cmd-1 broken after numeric range edit
Are you talking about the numerical "Selection and Audio Position Boxes" in the Selection Toolbar?Baylink wrote:There is, at that point, no way I can see to pull focus *out* of that field because everything I try loses my selection
If you are, you can move out of the "Selection Start" box into the (Selection) "End/Length" box using the Tab key.
The "Tab" key is the standard way to move from one control to the next within a window or panel. On Windows and Linux it is "Shift + Tab" to rotate through the controls in the opposite direction - probably the same on Mac but I don't use Mac.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
-
billw58
- Forum Staff
- Posts: 5600
- Joined: Wed Aug 12, 2009 2:10 am
- Operating System: macOS 10.15 Catalina or later
Re: [Possible Bug] Cmd-1 broken after numeric range edit
Yes, it's a bug. Tabbing through the selection toolbar controls doesn't help. You can get trapped in the project rate box and then any Cmd-<number> does nothing. The bug is that Cmd-<number> when in any control in the selection toolbar ignores the Cmd modifier and instead types the number. As you noted, Cmd-[ works, as does Cmd-F and Cmd-E.Baylink wrote: I still gotta think, though, that if my primary report is reproducible, that it's a bug. Or "there's no way to get the focus out of those number fields" is, take your pick. :-}
The way to get out of the selection toolbar boxes is Cmd-F6. I admit that's not easy to find in the manual.
-- Bill
Re: [Possible Bug] Cmd-1 broken after numeric range edit
Sorry: "out of those fields".steve wrote:Are you talking about the numerical "Selection and Audio Position Boxes" in the Selection Toolbar?Baylink wrote:There is, at that point, no way I can see to pull focus *out* of that field because everything I try loses my selection
If you are, you can move out of the "Selection Start" box into the (Selection) "End/Length" box using the Tab key.
The "Tab" key is the standard way to move from one control to the next within a window or panel. On Windows and Linux it is "Shift + Tab" to rotate through the controls in the opposite direction - probably the same on Mac but I don't use Mac.
Yes, I know that Tab is *supposed* to move your focus from one control to another, but it didn't seem to be able to escape that controlset for me. [And, as billw confirms in the next post I hadn't read yet, it's a known bug.]
Last edited by Baylink on Thu Feb 05, 2015 4:58 pm, edited 1 time in total.
Re: [Possible Bug] Cmd-1 broken after numeric range edit
I'll make a note of it. Thanks. :-)billw58 wrote:Yes, it's a bug. Tabbing through the selection toolbar controls doesn't help. You can get trapped in the project rate box and then any Cmd-<number> does nothing. The bug is that Cmd-<number> when in any control in the selection toolbar ignores the Cmd modifier and instead types the number. As you noted, Cmd-[ works, as does Cmd-F and Cmd-E.Baylink wrote: I still gotta think, though, that if my primary report is reproducible, that it's a bug. Or "there's no way to get the focus out of those number fields" is, take your pick. :-}
The way to get out of the selection toolbar boxes is Cmd-F6. I admit that's not easy to find in the manual.
-- Bill
Is there a bugzilla? Is that in it?
-
billw58
- Forum Staff
- Posts: 5600
- Joined: Wed Aug 12, 2009 2:10 am
- Operating System: macOS 10.15 Catalina or later
Re: [Possible Bug] Cmd-1 broken after numeric range edit
Yes, it's headed for bugzilla. Thanks for the report and the clear steps to reproduce.Baylink wrote: Is there a bugzilla? Is that in it?
-- Bill
-
Gale Andrews
- Quality Assurance
- Posts: 41761
- Joined: Fri Jul 27, 2007 12:02 am
- Operating System: Windows 10
Re: [Possible Bug] Cmd-1 broken after numeric range edit
Already there http://bugzilla.audacityteam.org/show_bug.cgi?id=496.billw58 wrote:Yes, it's headed for bugzilla. Thanks for the report and the clear steps to reproduce.Baylink wrote: Is there a bugzilla? Is that in it?
Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual