Problem importing key bindings to 2.1.0 or 2.1.1

Using Windows Vista and Windows 7, I had just updated both to 2.1.0 using the installer and found I’d lost my key bindings. I still had 2.0.5 on an older laptop so I exported the bindings and tried to import them into 2.1.0.

Still having trouble, I went to the forum and discovered the 2.1.1 release so I installed it, again using the installer. In each case, I copied my favorite non-included effects into the plug-ins folder first. In 2.1.0, I registered all of them, and in 2.1.1 I enabled all of them.

When I imported the keyboard bindings, the ones assigned to effects didn’t show up in preferences->keyboard, nor do they work. What am I missing? Most of them are Alt- combinations, but I have Alt- combinations assigned to track alignment and various other operations, and they all work.

This is a consequence of the major rework of effects for 2.1.0, and it’s noted in the first yellow box at the top of the Release Notes 2.1.0.

As noted there, you can find the old shortcuts listed in the audacity.cfg file.


Gale

There were significant changes between 2.0.6 and 2.1.0 (hence the jump in the version number). Unfortunately, a consequence was incompatibility with older keybinding XML files. From the release notes for Audacity 2.1.0 (http://wiki.audacityteam.org/wiki/Release_Notes_2.1.0):

Shortcuts created in previous Audacity versions for the Generate, Effect and Analyze menus will not be recognized by 2.1.0 and cannot be imported from an XML file. However the shortcuts can be recreated and will then be respected. The previous bindings can still be viewed in the [NewKeys] section of the > audacity.cfg settings file> .

Update:

After manually entering the missing key bindings, I found that the ‘B’ (play to selection) and ‘C’ (play cut preview) keys were crippled in 2.1.1. Restoring Defaults re-enabled these keys.

I exported this key bindings file from 2.1.1 and imported it into 2.1.0 for test. It works there, but cripples the aforementioned keys in 2.1.1. If I find time, I’ll try to isolate the offending binding, but for now I’ve dropped back to 2.1.0 so I can get productive again.

Thumbs up on the new meters! They’re a real improvement on my small laptop screen. I’m using RMS display mode - difficult to see the ‘recent peak’ mark when it’s yellow, and RMS is useful information for checking channel balance.

(edit) Thanks Gale & Steve - I started this post then did some experimenting then finished it and never checked for replies before submitting it.
Audacity_2-1-1-keys(bad).xml (20.2 KB)

B and C (or whatever binding you assign to them) have been fixed now for the next 2.1.2 release. Sorry about that.

You can work around it in 2.1.1 by recording a few seconds after you open a project window, then delete the recording.

I agree a yellow or orange recent peak is not easy to see. What would you suggest to improve visibility? Thin black vertical borders, and accept it’s wider?


Gale

I think the borders would get in the way just below 0dB, although that could be fixed by dropping the one on the right when the point is reached. Or, you could make the marker black for part of its height - that would give the eye something on which to fixate quickly.

Or, how about just not using the gradient color for the recent peak marker? Or putting the gradient color in the background like on a meter face? It could be a lighter saturation value to keep the bar clearly visible. Alternatively, since the scale is common to both channels, it could even be a stripe in between the two bars, at a slight expense of bar thickness.

You might find it easier to see the yellow/orange Recent Peak if you widened out the recording meter. I have my meters set up so they span the whole width of the window, but with the recording meter taking up 4/5 of the space leaving 1/5 for the playback meter. With this setup I have no problem observing the Recent Peak levels whatever the color at the time.

I would specifically not want us to change the colorway of the Recent Peak meters as the color is intended to be an indicator of the level of signal saturation.

Peter

If you find the small meters difficult to see, and if you don’t mind losing the screen space, you can also drag the meters out of their dock position, resize them to double height, and re-dock them. You can also leave them floating by the side of the main Audacity window and/or resize them so that the meters are vertical. Lots of options to choose from. Experiment to find which suits you best :wink:

Agreed, but this is about making that colour more visible. Low visibility of recent peak in the gradient meters is another reason I personally prefer the RMS meters.


Gale

No problem here, but glad we have a choice so we can keep everyone happy :wink:
I think it would be good to see more metering options in the future - there are still those that want “true peak” meters (and I’d still like a log scale that goes down to -inf dB).

I’d love to have some quaint old meters like I used to have on my older tape decks with the light-up back and the swinging needle :sunglasses:

Peter

Wouldn’t it be nice if someone could make this into an Audacity module: http://plugin.org.uk/meterbridge/

If the exiting meters had an optional dark background with white meter ticks, it might be easier to see the gradient meters current peak.


Gale