-
Problem: I see some possible solutions:
Or I'm missing the obvious solution, which would be the best outcome. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
AnswerThis is the wrong target. "FX: Browse presets" is intended for browsing, with an encoder or with -/+ buttons. Recalling concrete presets gives you exactly the problem that you describe, because absolute control in ReaLearn is always scaled, which means that source and target values are proportionally scaled to each other, with the target's value range mapped to the source’s percentage. Workaround: The recommended way to do this is to add one mapping per program change message, using the source Specific program change, combined with the target "FX: Load snapshot". The "one mapping per program change" strategy is a lot more powerful because the target for each program change message can be configured in very much detail. E.g. if we had a "FX preset: Select" target, you could identify the preset by name instead of by its position. If adding so many mappings is too much clicking for you, you can quite easily generate all those mappings using Lua (similar to this). The target "FX: Load snapshot" is usually more desirable if you want to jump to specific presets because it's independent of the FX preset order (changing that order will mess everything up). That said, if you need a "FX preset: Select" target, feel free to request it (new discussion with type "Idea"). BackgroundIn the past, I had the idea of introducing a direct (non-scaled) mode as well. This corresponds a bit to your "No glue" option, but it still gives the Glue some power. In fact, I made quite some progress as part of #184. However, I never unlocked that "direct" mode because I thought it adds unnecessary complexity (yet another switch that completely changes the semantics of the Glue section). This increased complexity didn't feel justified because "direct" control is not very common. After all, in all those years, almost nobody requested this behavior. And most importantly, there is above mentioned workaround, which is even more powerful. |
Beta Was this translation helpful? Give feedback.
Answer
This is the wrong target. "FX: Browse presets" is intended for browsing, with an encoder or with -/+ buttons. Recalling concrete presets gives you exactly the problem that you describe, because absolute control in ReaLearn is always scaled, which means that source and target values are proportionally scaled to each other, with the target's value range mapped to the source’s percentage.
Workaround:
The recommended way to do this is to add one mapping per program change message, using the source Specific program change, combined with the target "FX: Load snapshot".
The "one mapping per program change" strategy is a lot more powerful because the target for each program change message …