search

helgoboss / helgobox

Helgobox: ReaLearn & Playtime
https://www.helgoboss.org/projects/helgobox
GNU General Public License v3.0
206 stars 20 forks source link

Unexpected encoder behaviour with virtual mappings #622

Closed IOphonics closed 2 years ago

IOphonics commented 2 years ago

Hello, I'm having trouble using virtual mappings. I'm using the Midi Fighter Twister and the respective controller preset, trying to control VST parameters. Nothing too fancy. In general, it works really great, but with virtual sources/targets I'm getting value behaviours I can't explain.

When I add a new mapping, learn an encoder as (virtual) source and a random VST parameter as target, the values in ReaLearn and the VST don't reflect what the Fighter's LED ring is showing. When I turn the encoder to the right, the VST parameter doesn't change until I turned the encoder about 180 degrees. Then the values start going up. When I change direction to the left, the values continue to go up for another 180 degrees until it's starting to decrease. Changing direction again causes the reversed behaviour. I tried to find a clear logic in it to describe to problem better, but I couldn't...

I'm using the default Midi Fighter Twister controller preset and following mapping: ReaLearn_mappingWindow

I don't understand the behaviour. Do you have any idea what I'm doing wrong here?

IOphonics commented 2 years ago

I think I understand the behaviour a bit better now. For example, when I turn the encoder 20% to the right and then change direction, the values continue to go up for another 19%. When I then turn the encoder 10% to the left and change direction again, the values continue to go up for another 9%. That seems to be the rule. But there's nothing in my pretty basic mapping that would explain that, as far as I can see. And like I said, the LED ring on the Twister shows normal behaviour, and when I don't use virtual mappings everything works as expected. So the input seems to be right.

helgoboss commented 2 years ago

Looks like you didn't configure your encoders as relative encoders first in the Midi Fighter Utility (or as the wrong relative type). This producedure is described in the list of tested controllers. You can jump to the list of controllers by right clicking the header panel in the Help submenu (latest version 2.13.0).

IOphonics commented 2 years ago

Sure, you're right. I had the wrong relative type...

Thank you very much! You're help is very much appreciated. So is your work. ReaLearn is an incredible piece of software. And all your effort in documenting, explaining and developing it further is such a huge gift to the reaper community. Only love to you.