Hi David!
Thanks for clearing this up.
When importing my key strokes into Audacity 2.2.0, none of the key strokes
assigned to what is now the Ext-Bar > Transport submenu work. Some others are
affected too, such as Delete Track and Crossfade Clips.
Cheers! Robbie
From: audacity4blind-bounce@xxxxxxxxxxxxx
[mailto:audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of David Bailes
Sent: Saturday, October 28, 2017 3:49 PM
To: audacity4blind@xxxxxxxxxxxxx
Subject: [audacity4blind] Re: Audacity 2.2.0 release candidate available for
testing
Hi Robbie,
thanks for giving your feedback.
1. The commands in the mute sub menu in the tracks menu. These commands act on
all the tracks, rather than just the focused track, and so are there for
convenience. As to why there are not any Solo equivalents, I suppose it's
assumed that you would not want to solo a large number of tracks at the same
time.
2. The commands in the pan sub menu in the tracks menu. If there are any
selected tracks, then these commands act on these selected tracks, otherwise,
they act on all the tracks. So again, they are there for convenience if you
want to set the pan for a number of tracks at the same time.
3. The Ext-Bar > Tools sub menu. The items in this menu are for settings
various modes when using the mouse to interact with the tracks, so you can just
ignore these.
4. The extra menus contain just about all the commands that aren't in the
standard menus, so this does result in commands being in the menus, such as
cursor right and left, which make the user question why they are included.
5. Renaming of items in menus. Even if the names have been changed slightly,
the identifiers used for storing customized keystrokes will still be the same,
so you shouldn't have to reassign your keystrokes. The only case where I know
there is a change is for the record commands, since the the default has been
changed to record append.
David.
On 28 October 2017 at 13:50, Robbie < <mailto:tickleberryfun@xxxxxxxxx>
tickleberryfun@xxxxxxxxx> wrote:
Hi David!
Here are my thoughts and findings after a first test run.
In the Tracks menu, Mute and Pan now have their own submenus. Whether that's
useful is debatable, because I don't see anyone going through the menu each
time they want to mute or unmute a track. Yes, Mute/Unmute was in the Tracks
menu before, but I never saw the point. Why Mute but not Solo?
Since all the above are found in the Ext-Command menu, they might as well be
left out of the tracks menu, to further slim it.
The same applies to Pan. Why put Pan in the Tracks menu, but not Gain? Again,
Pan and Gain are found in Ext-Command, so why not drop Pan from the Tracks menu?
Regarding the rearrangement of the menus, I can see why some of the changes
would make Audacity easier to work with. Putting all the menu items blindies
have keystrokes for in menus you can hide is a nice touch.
I had to smile at the Cursor submenu in Ext-Command though. Who would go
through the menu to move the cursor right, if they could just press cursor
right? I mean, it's the cursor. It's even got its own Keys.
I don't know what to make of the Tools submenu in Ext-Bar. For instance, what
is Ext-Bar > Tools > Selection Tool supposed to do? I tried it with the
Selection Toolbar enabled as well as disabled and it doesn't seem to have any
effect.
I can't comment on the look of the high contrast theme, being fully blind, but
it's an excellent idea, which I shall recommend to VI-friends.
Unfortunately, all the items in the Ext-Bar > Transport submenu plus a few
others have apparently been renamed, so I need to reassign my key strokes. If I
want to work with this version that is. I'm not yet convinced that it serves me
any better than version 2.1.3.
While the design is more customizable, and the usability improved for newbies,
for my own use of Audacity there doesn’t seem to be an advantage in switching
to version 2.2.0.
Cheers! Robbie
From: <mailto:audacity4blind-bounce@xxxxxxxxxxxxx>
audacity4blind-bounce@xxxxxxxxxxxxx [mailto: ;
<mailto:audacity4blind-bounce@xxxxxxxxxxxxx>
audacity4blind-bounce@xxxxxxxxxxxxx] On Behalf Of David Bailes
Sent: Friday, October 27, 2017 9:54 AM
To: <mailto:audacity4blind@xxxxxxxxxxxxx> audacity4blind@xxxxxxxxxxxxx
Subject: [audacity4blind] Audacity 2.2.0 release candidate available for testing
For those of you who are interested in testing a release candidate of Audacity
2.2.0, this is a link to the portable version:
<https://www.fosshub.com/Audacity-devel.html/audacity-win-2.2.0-rc1.zip>
https://www.fosshub.com/Audacity-devel.html/audacity-win-2.2.0-rc1.zip
If you want this version of Audacity to use its own separate settings, then
after you have extracted the files, in the folder that contains Audacity.exe
create a folder with the name Portable Settings.
For a summary of new features see:
1. <http://alphamanual.audacityteam.org/man/New_features_in_this_release>
http://alphamanual.audacityteam.org/man/New_features_in_this_release
2. A section in the introduction of my guide:
<http://vip.chowo.co.uk/wp-content/uploads/jaws/Audacity-2.2.0-Guide.html>
http://vip.chowo.co.uk/wp-content/uploads/jaws/Audacity-2.2.0-Guide.html
If you find any bugs, or have any comments about this new version, just post
them to this list,
David.