# Fader Level adjustments on buttons

**URL:** https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269
**Category:** Yamaha RCP Module
**Created:** [April 20, 2020, 6:16am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269 "2020-04-20T06:16:23Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![kirb](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/k/3d9bf3/32.png) [@kirb](https://discourse.checkcheckonetwo.com/u/kirb)
#### Post date: [April 20, 2020, 6:16am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/1 "2020-04-20T06:16:23Z")

</div>

So using buttons instead of a fader - isn’t ideal - however, they’ve given us this option to alter a fader level on a button, so it may be more useful if there were an option to increment or decrement a fader level by multiple pushes of said button.

Instead of having a fixed value in the …Fader/Level command, would it be possible to use something like ‘Current Value +1’ or "Current Value -1’. The +and- 1 could also be a variable so it could change more harshly for instance in steps of 5.

Then I guess you could always make this value db - instead of 0 to 1000? (or -32768 [inf] to 1000 [10db])  
So increments of 1 or 2 db…?

Presumably you’d use the ‘Get input channel Fader Level’ SCP command or similar MIDI command to get a starting point?

---

<div class="post-metadata">

### Author: ![Andy](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [April 21, 2020, 4:36pm UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/2 "2020-04-21T16:36:21Z")

</div>

I’ll have a look at this when I get some time. I’m concentrating on the MIDI module atm. 🙂

---

<div class="post-metadata">

### Author: ![corporate\_roadie](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@corporate\_roadie](https://discourse.checkcheckonetwo.com/u/corporate_roadie)
#### Post date: [January 20, 2022, 5:00am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/3 "2022-01-20T05:00:24Z")

</div>

Wondering if there is any chance we could see a feature like this in a future build? We came up with a convoluted way to do this using multiple pages and redirects… basically when you select the increase or decrease button, it changes the level and switches to another page where the buttons have a new inc/dec value. It works, but uses up a ton of pages…

---

<div class="post-metadata">

### Author: ![Andy](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [January 20, 2022, 5:18am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/4 "2022-01-20T05:18:01Z")

</div>

I assume you’re speaking of the RCP module?  
Certainly it’s possible, just haven’t the time to dedicate to it ATM. Perhaps when there’s a Rivage update I’ll see if I can add it then.

---

<div class="post-metadata">

### Author: ![corporate\_roadie](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@corporate\_roadie](https://discourse.checkcheckonetwo.com/u/corporate_roadie)
#### Post date: [January 20, 2022, 4:45pm UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/5 "2022-01-20T16:45:03Z")

</div>

I am using the RCP module on QL1. Thanks!

---

<div class="post-metadata">

### Author: ![Andy](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [January 26, 2022, 1:24am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/6 "2022-01-26T01:24:09Z")

</div>

Please try today’s update.  
I added a “Relative” checkbox to allow increasing/decreasing a value. Haven’t tested it a lot, so I’d really appreciate it if you could test it and try and break it so I know if I added any bugs! 🙂

---

<div class="post-metadata">

### Author: ![Andy](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [January 28, 2022, 6:21am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/7 "2022-01-28T06:21:08Z")

</div>

Well?  
Curious if anyone’s tried it…

---

<div class="post-metadata">

### Author: ![corporate\_roadie](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@corporate\_roadie](https://discourse.checkcheckonetwo.com/u/corporate_roadie)
#### Post date: [February 1, 2022, 5:18pm UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/8 "2022-02-01T17:18:09Z")

</div>

Testing it out now! So far so good using RCP with QL1 from Windows.

We are playing around with stacking commands with delays for “press & hold” functionality. Basically, if you hold the button, it keeps repeating the inc/dec every 500ms, then 300ms, then 100ms until it aborts on button up (canceling any additional actions).

---

<div class="post-metadata">

### Author: ![Andy](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [February 1, 2022, 5:20pm UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/9 "2022-02-01T17:20:17Z")

</div>

Oooh! Interesting. If you get something workable, can you please attach a sample page? That sounds very useful.

---

<div class="post-metadata">

### Author: ![Andy](https://discourse.checkcheckonetwo.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@Andy](https://discourse.checkcheckonetwo.com/u/Andy)
#### Post date: [September 3, 2022, 2:41am UTC](https://discourse.checkcheckonetwo.com/t/fader-level-adjustments-on-buttons/2269/10 "2022-09-03T02:41:29Z")

</div>

A post was split to a new topic: [Hotkey Function](https://discourse.checkcheckonetwo.com/t/hotkey-function/3297)
