Key Command for ARA

Please add Key Command for ARA in Nuendo 13. Clicking from different dropdowns every time is rather cumbersome.

Steinberg Wavelab Pro 11 has this feature already, which saves a lot of time and effort.

4 Likes

Oh, they still didn’t fix this? :unamused:

+1!!!

There’s already a feature request over here (for N12 back then) with 4 votes.
Maybe you want to give it a vote too if you haven’t already?

1 Like

voted!

2 Likes

Voted again.

1 Like

Yes please again

1 Like

Voted!

1 Like

Its not possible to assign a maco as a key command to invoke an ARA plugin with C13 - except - it doesn’t work.

+1 here

I’d really like this too!

If anyone can get this one on a list for N15 please do!

Plus 1!!

Select clip, click on No Extension in the info line, choose ARA product. :slightly_smiling_face:

Thats two extra clicks. Times that by 100 on a busy vocal editing session

Right click on part, go to menu and select the chosen ARA plughin isnt much different

While I agree that key commands for each extension would be nice, I must say that clicking on the info line is miles ahead of the menu way.
To be honest since I got used to clicking the info line for this, my need for the key command has gotten substantially lower.

2 Likes

It would still be hugely faster with key commands

1 Like

I agree! It’s just that while it doesn’t come through, don’t dismiss the info line option. =)

1 Like

Would be nice! +1

While I can understand people’s need to save time, and no offense, but complaining about extra clicks that in my estimation would add about 90 seconds to your work flow isn’t a big deal. I’ve been doing this for almost 37 years and my mind often reminisces of being an assistant engineer on music mixes in the 90’s where we ran out of outboard gear in the island and the engineer wanted to add an extra delay or effect I had to go down to our outboard gear room, grab whatever device was required, bring it back to the studio, hook it up with an EDAC connector, label it so we knew where it appeared in the patch bay, then patch it into the board, I am reminded of how far we’ve come. :slightly_smiling_face:

When I need Nuendo to do something that it can’t do yet, I often just program my gaming keyboard to do the function for me with one keystroke. It is a good reminder that the word “engineer” is part of being a “sound engineer” :slightly_smiling_face:

Just my thoughts as I turned 60 this year and still enjoy doing what I do.

I hope everyone has a great weekend.

2 Likes

Great story and good to hear you are still doing it!

However, without an assignable keycommand that programmable keyboard cannot solve anything.

whether you want less clicks to be more efficient OR save your joints from RSI, it is just an oversight on SB’s end to not have a keycommand for a popular task.

in the meantime: if one owns a license for Keyboard Maestro, it can find that little button in the info line and then it is one less click i think. Not behind my mac right now but will look up how it is named tomorrow.

1 Like

I wouldn’t call it an “oversight” for a “popular task” but rather a “design decision” to not allow mapping of key-commands to load 3rd party plugins.

ARA extensions are just VST3s. When parsed, they are identified as extensions and just listed in the Extensions menu, presumably in alphabetical order. They don’t even have a “slot number” or associated position within the menu, or are even guaranteed to exist for that matter. In fact, the entire menu option for them disappears or is disabled if you don’t have the supported event selected.

Meaning, selecting a specific ARA extension is by no means the same as a key command for something like “Insert 01: Open/Close Editor for Selected Track/Channel” because their very existence is arbitrary and undefined by the system, as well as contextual for only specific event-types.

I too use @henrique_staino’s info-line method because it’s contextual and easy to use.

I get folks would like key-commands for everything, myself included, but I think it’s important to at least identify what’s going on in the background, what the feature requirements are, and how they could even be implemented in cases like this. To me, anyway.