Audacity Forum

DickN wrote:

Gale Andrews wrote:Drag a selection from 5s to 10s seconds in the third of three 20-second tracks. CTRL + B to add and close the label. Drag from 7s to 8s in the third track. Down Arrow. Now ENTER will toggle a selection of 7s to 8s in the label track.

Tried it, didn't work! Shift+Click in the Track Control Panel does it, but Enter doesn't. I'm using 2.0.0 under XP (SP3). I have hh:mm:ss+CDDA frames selected as time unit and Snap To enabled.

Neither of us are saying how we closed the label. I did it with ENTER, so "CTRL + B to add, then ENTER to close the label".

DickN wrote:
My experiment:
1-Drag a selection from 5s to 10s seconds in an audio track.
2-CTRL + B to add a label track.
3-Close the label.
4-Click at 2 sec in the audio track.
5-CTRL + B to add a label.
6-Close the label.
7-Drag any selection in the audio track except one matching a label.
8-Arrow Down (to label track).
9-Enter (does nothing).
10-Drag a selection in the audio track matching the 5-10 sec range label (per the yellow vertical lines indicating match).
11-Arrow Down (to label track).
12-Enter now toggles selection in label track.
13-Click at the 2 sec point in audio track (yellow match line should appear confirming match to point label).
14-Arrow Down (to label track).
15-Enter now toggles selection in label track.
16-Stay in label track; Right Arrow to move cursor.
17-Enter now does nothing.
18-Left Arrow (returns cursor to match point label).
19-Enter now toggles selection.

Can't reproduce any of those failures on Win 7, even with hh:mm:ss+CDDA frames selected as time unit and Snap To enabled.

I'll have a look on XP some time if no-one else does.


Gale

Gale Andrews wrote: Can't reproduce any of those failures on Win 7, even with hh:mm:ss+CDDA frames selected as time unit and Snap To enabled.

I'll have a look on XP some time if no-one else does.

Just tried it on Vista Home Premium, and it works as you describe for Win 7.

Is there a way I can move this topic to the Windows forum?

DickN wrote:

Gale Andrews wrote: Can't reproduce any of those failures on Win 7, even with hh:mm:ss+CDDA frames selected as time unit and Snap To enabled.

I'll have a look on XP some time if no-one else does.

Just tried it on Vista Home Premium, and it works as you describe for Win 7.

Is there a way I can move this topic to the Windows forum?

Done. I also edited your first post and added a link to this post of yours.



Gale

Thanks

Just noticed the command descriptions in Preferences->Keyboard (default bindings):

'Move Focus to Previous and Select' Shift+Up
'Move Focus to Next and Select' Shift+Down

DickN wrote: Just tried it on Vista Home Premium, and it works as you describe for Win 7.

Last week I was editing a rather large project on the Vista system and the behavior was just as I described earlier for XP, to wit:

DickN wrote:Enter toggles the selectedness of a label track only if the current time selection exactly matches a label on that track .

(That's from http://forum.audacityteam.org/viewtopic ... 94#p181894.)

This may shed some light on the mechanism of the problem: It's not entirely an XP vs Vista issue. It's at least partly a memory issue. My XP system is on a laptop with 1.5 GB RAM, and I'm frequently waiting for the drive light to go out before a command executes. That hardly ever happens with smaller projects on the Vista system, but with this project it did. I had transferred 2 C90 cassettes into Audacity, and had at least 2 hours of stereo before I started working on it. Then I had to filter out all the nasties from two air conditioners and a squeaky paddle fan - an average of 8-9 notches. I was keeping "before and after" versions so I could hear how all these holes were affecting the overall sound. Response to commands was getting even slower than what I'm used to on the XP laptop, and using Enter to select/deselect Label tracks was working only if a label on the track matched the select range.

I'm not ready to call it entirely a memory issue because on the XP system the problem occurs even in a test project with only a few seconds of audio, but last week's experience on Vista suggests memory is at least a factor.