Ctrl+Up Arrow and Ctrl+Down Arrow

[jbone1313]

I've noticed the volume faders move very slowly when using these shortcuts.

Is there a way to make them go faster?

Is there a reason they go slowly? I.e., is that desirable?

Thanks!

[Mercado_Negro]

Ctrl modifier is used in that case for fine-tuning. Wanna go faster? Do not use Ctrl key

NOTE FOR DEVELOPERS: There are inconsistencies on sends' volume faders when Ctrl+Mousewheel up

[jbone1313]

Originally Posted by Mercado_Negro

Ctrl modifier is used in that case for fine-tuning. Wanna go faster? Do not use Ctrl key

Then is there a shortcut key to modify the track volume faders without the Ctrl key? The only one I've seen includes the control key. And it seems the only key-mapable action for volume on faders is a nudge type.

Thanks!

[nicholas]

Originally Posted by jbone1313

Then is there a shortcut key to modify the track volume faders without the Ctrl key? The only one I've seen includes the control key. And it seems the only key-mapable action for volume on faders is a nudge type.

Thanks!

Try holding down both Ctrl and Up or Down Arrow (rather than pressing and releasing - that makes them go faster ...

[jbone1313]

Originally Posted by nicholas

Try holding down both Ctrl and Up or Down Arrow (rather than pressing and releasing - that makes them go faster ...

I def tried that. They kind of start quick, and then they peter out.

[Mercado_Negro]

You can build Custom Actions like Increase Selected Track(s) Volume and Decrease Selected Track(s) Volume. Go to main menu Actions->Show actions list... and left-click on New... button, a new window will prompt to build a Custom Action. Set a Custom Action Name (increase.... or decrease...) and on Filter type nudge volume for selected tracks, you'll see now two actions only. Depending on what Custom Action you want to build first, doubleclick one of them as many times as you like that action to be performed (how faster you'd like to increase or decrease), example:



Each action inserted increase or decrease 0.05dB's above example decrease track(s) volume on 0.20dB's

After building each Custom Action tick Consolidate undo points and click OK. Go to Shortcuts for selected actions and click on Add... to assign a key to it.

[zappsunzorn]

Yes I believe the speed is desired. In a sense the fader moves very fast a small amount. To move at a greater distance a speed would have to be assigned etc and it would most likely feel disconnected at best.

use the SWS plugin's reaconsole
http://www.standingwaterstudios.com/reaper/

[jbone1313]

Cool!!!!

I will try your suggestions. I'm RTFMing, and I haven't yet delved into the custom actions.

Thanks!!

[Youn]

Originally Posted by Mercado_Negro

Ctrl modifier is used in that case for fine-tuning. Wanna go faster? Do not use Ctrl key

NOTE FOR DEVELOPERS: There are inconsistencies on sends' volume faders when Ctrl+Mousewheel up

This was on purpose for as long as I can remember, and I personally love how mousewheel acts based on pixels rather then fixed decibel increment - this means mousewheel adjustments are relatively proportional on low gain settings as they are on higher ones.

I wouldn't mind having mousewhell use a fixed decibel interval, but I'd like to keep it as an option.

[Mercado_Negro]

Originally Posted by Youn

This was on purpose for as long as I can remember, and I personally love how mousewheel acts based on pixels rather then fixed decibel increment - this means mousewheel adjustments are relatively proportional on low gain settings as they are on higher ones.

I wouldn't mind having mousewhell use a fixed decibel interval, but I'd like to keep it as an option.

Youn, I'm not talking about pixels and/or decibels but an "stucked" behaviour when trying to increase sends' volume faders with Ctrl+Mousewheel... I must admit it's no currently happening on 3alpha1 but v2.55.

Justin, Schwa... can this be fixed on 2.x? Please.