Relative encoder to absolute control *speed change*

Hi , My Relative encorder is too slow when it's translated to absolute control .

I have no idea about scripting midi but i used the preset file on the youtube and it worked (Convert 3F/41)

NOW i'm having a trouble with it's speed ! what shoud i do ?

How to change the incoming value?

Hi, please try the attached. I added an accelleration factor of 3 (tt) to the input.  You will need a different global variable to track each encoder that you need to be absolute. I used ga here.

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

Whoops forgot the attachment.

 


Attachments:
1585844794489_Rel-to-Absolute-w-acceleration.bmtp

I still dont inderstand the midi concepts ! i uploaded my project file could you modificate it ?


Attachments:
1585854590492_Rel-to-abs.bmtp

Ah, I see this is a 3F/41 type encoder. This is even easier. See attached.

 

Se just take the incoming differential value and adjust for positive or negative and multiply the incoming value by 3 and then add (or subtract) that from the original value to get the new value.

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

 


Attachments:
1585855684067_Rel-to-abs-Steve.bmtp

thanks a lot ! it’s working

Glad I could help!

Hey Steve - Is it possible for this acceleration behavior to happen while remaining relative and toggling a keyswitch? The script above works great for relative to absolute for me. Thanks for the guidance in this thread! But the problem I am trying to solve right now is using the relative knob on parameters inside of a plugin such as an EQ. The knobs take forever to rotate through the values. So I thought that I might be able to accelerate the relative knob by default, then hold a keystroke (like control) for fine tuning. But it seems like I would need to send the value out multiple times since relative is a specific value for each knob direction.

Hi @storyteller and welcome back!

Yes, if I understand correctly, we are currently applying a “multiplier” to the outgoing action. Removing the multiplier would slow things down. I think the simplest way to do this is to have 2 translators, 1 with the multiplier and 1 without. Have both translators check a global variable and depending on it’s’ state fire or not. Only one translator should fire at a time.

Pressing a button sets the global variable to a 1 and release it sets it to a 0. So fire the translator without acceleration when the global variable state is 1 only (button pressed) and fire the translator without acceleration when the global variable state is 0 only (button released).
Pressing the button (usually a note-on) would set the global variable ta 1 and release it (usually a note-off0 with set the global variable state back to 0).

I hope this helps!

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz
1 Like