Different speed when editting mapping #1204
Replies: 8 comments 1 reply
-
|
I thought it was fixed but no issue remains :( |
Beta Was this translation helpful? Give feedback.
-
|
Hmm. Maybe you can increase the minimum step size? I assume you followed all the Twister-related instructions in the "Controllers" guide? |
Beta Was this translation helpful? Give feedback.
-
|
Yess, I did. And yeah I did try a lot of tweaking with the step size. I
might just do a clean install of realearn :)
…On Tue, Sep 17, 2024, 13:25 Benjamin Klum ***@***.***> wrote:
Hmm. Maybe you can increase the minimum step size?
I assume you followed all the Twister-related instructions in the
"Controllers" guide?
—
Reply to this email directly, view it on GitHub
<#1204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3TMX5ZOYGMHAYCQL3DIB3LZXAGRTAVCNFSM6AAAAABOLE7EJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRWHE2TANQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
No, please don't ;) Reinstalling wouldn't change anything. If you change the minimum step size, it should definitely have the effect that you need to turn the encoder less. That should at least provide a workaround. That works, right? The minimum step size is the most important one. The maximum step size is only relevant for limiting the effect of acceleration. I would be surprised if an open mapping panel influences the effect of encoder turning but I also can't rule it out. No way to test it now as I'm AFK until next Monday. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I can get it in the range where I like it, but the setup is a bit of
a pain right now since the edit window seems to have a different
sensitivity. Requires more back and forth but not the biggest issue. Thanks
for getting back to me so soon at least :)
Cheers!
…On Tue, Sep 17, 2024, 13:50 Benjamin Klum ***@***.***> wrote:
No, please don't ;) Reinstalling wouldn't change anything.
If you change the minimum step size, it should definitely have the effect
that you need to turn the encoder less. That should at least provide a
workaround. That works, right? The minimum step size is the most important
one. The maximum step size is only relevant for limiting the effect of
acceleration.
I would be surprised if an open mapping panel influences the effect of
encoder turning but I also can't rule it out. No way to test it now as I'm
AFK until next Monday.
—
Reply to this email directly, view it on GitHub
<#1204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3TMX55LEFWBJZCNGQQJSTLZXAJO3AVCNFSM6AAAAABOLE7EJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANRWHE3TGNA>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Which FX are you controlling? I couldn't reproduce this until now. I would like to try it with the same plug-in and parameter that you use. |
Beta Was this translation helpful? Give feedback.
-
|
I was using devil-loc by Soundtoys. I believe it was with every fx but not
entirely sure. Thanks for getting back to me! I could perhaps send my
realearn instance? Not sure if that is easily possible.
…On Mon, Sep 23, 2024, 12:16 Benjamin Klum ***@***.***> wrote:
Which FX are you controlling? I couldn't reproduce this until now. I would
like to try it with the same plug-in and parameter that you use.
—
Reply to this email directly, view it on GitHub
<#1204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3TMX55WE33L7IJXRJVDDSDZX7S6VAVCNFSM6AAAAABOLE7EJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZSGQ2TGMQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
The best thing would be if you could send me your project file. You can also send it to [email protected]. |
Beta Was this translation helpful? Give feedback.
-
|
Okay I will! Start of next week I'll have more time so I'll send it then :)
…On Mon, Sep 23, 2024, 17:09 Benjamin Klum ***@***.***> wrote:
The best thing would be if you could send me your project file. You can
also send it to ***@***.***
—
Reply to this email directly, view it on GitHub
<#1204 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3TMX57ROZZHZM75Z3ORBTDZYAVKRAVCNFSM6AAAAABOLE7EJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZSG44DENY>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
First of thanks for this, it's awesome software :)
I'm using the midi fighter twister with velocity sensitive on every encoder. All are set to endless in MF Utility.
I'm running into an issue and I'm not sure where it originates from. When editting a mapping in the main compartment, I set the step sizes to what feels right. But when I close the editor it seems sluggish. Where half a turn would be enough for a full rotation now it takes a whole turn.
I set the max step size "high enough" at 100 in both the controller mapping and the main compartment mapping as you can see in the screenshots. I've used the controller mapping in Reapack.
I hope you can help me!
Beta Was this translation helpful? Give feedback.
All reactions