As a screen reader user, I love the Edit Labels facility. I have just discovered on three different machines running Windows 7, Windows 8.1 and Windows 10 an issue. I can still edit label names and positions and those values are retained. However, pressing Enter on a specific label does not put focus on that position in the track. It is possible to tab along the label track, but that takes some of the fun (speed and accuracy) out of the exercise.
Andrew
On my computer (Linux) it does put focus on the label, but only while the Label Editor is open. As soon as the label editor is closed, the cursor goes to the first label position. I assume that is the same problem that you observe on Windows.
I rarely use the label editor, so I didn’t realise that in previous versions of Audacity the cursor remained at the label that was selected in the label editor. That seems to be an undocumented feature (I don’t see that behaviour described in the manual (Audacity Manual). I’ll log this as a bug and include a note that is should be documented in the manual. Unfortunately it will not be fixed in the next Audacity release as we are too close to the release date, but hopefully the Label Editor will receive some attention before the following release.
Thanks Steve. It was formerly possible to use the label editor to select audio associated with a particular label. I only discovered yesterday that it no longer does that, so not sure just when it changed. It was a really nice feature and, as far as it goes, still is.
Andrew
It changed between 2.1.0 and 2.1.1 and I believe that the change was unintentional (a “bug”). I can see the usefulness of this feature, particularly for visually impaired users. It is now logged on our bug tracking system for fixing.
Gale has documented the current (buggy) behaviour in the Manual for the upcoming 2.1.2 release - and placed a ToDo marker for us to update the Manual once bug 1254 http://bugzilla.audacityteam.org/show_bug.cgi?id=1254 is fixed.
The current behaviour will also feature in the Release Notes until it gets fixed in a later release.
WC
One of the developers has located and fixed the bug, but because we are so close to the release of Audacity 2.1.2 it is unlikely to appear in the release version until 2.1.3.
Thanks to all involved. Not only has the bug been found but has been corrected in RC2 of 2.1.2. A quick skim of the Manual indicates that it also reflects correct behaviour.
Andrew