On my APC, it doesn't matter how fast I turn the encoders, they always change the same parameter range per degree of movement, so if i twist a filter sweep around, i can return the cutoff to its original position by returning the encoder to the position where i picked it up.
On my Push, the range travelled seems to depend on how fast you turn the encoder, so if I turn it slow, I can comfortably sweep a 127 step cutoff with one turn. However if i turn the encoder fast, it doesn't travel half that range and I have to turn the encoder round a couple of times to get the full range. If I'm turning fast one way and slow the other, then return the encoder to its original position, the parameter value is not what I started at.
I find this behaviour really confusing and unmusical. Is there any way to disable this sensitivity of the encoders to the speed they are turned?
Is it supposed to be useful, or is it just the way the encoders work?
Encoder speed sensitivity troubles
-
TomViolenz
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: Encoder speed sensitivity troubles
-
Last edited by TomViolenz on Tue Apr 22, 2014 7:08 pm, edited 1 time in total.
-
staplesyrup
- Posts: 75
- Joined: Thu Jul 05, 2007 9:56 am
Re: Encoder speed sensitivity troubles
I think thats to do with takeover of parameters with controllers that send absolute values. Those settings don't affect the speed sensitivity.TomViolenz wrote:Just wondering (not close to my Push now) but could it be the difference in setting in the Midi preferences between pick up and value scaling?!
-
staplesyrup
- Posts: 75
- Joined: Thu Jul 05, 2007 9:56 am
Re: Encoder speed sensitivity troubles
I just realised this only happens with max for live parameters. Live's own devices respond consistently at all speeds. Might move this to Max for live forum.
Edit: wierd - If I use the User mode, and map an encoder to a live parameter like a send, the opposite happens, the parameter makes a big change if you move fast , and a small change if you move slow. Max for live is the other way round. Confusing!
Edit: wierd - If I use the User mode, and map an encoder to a live parameter like a send, the opposite happens, the parameter makes a big change if you move fast , and a small change if you move slow. Max for live is the other way round. Confusing!
-
TomViolenz
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: Encoder speed sensitivity troubles
-
Last edited by TomViolenz on Tue Apr 22, 2014 7:09 pm, edited 1 time in total.
-
Valiumdupeuple
- Posts: 1155
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: Encoder speed sensitivity troubles
Hey fellows,
I think that really needs to be emailed to ableton as a bug report.
I think that really needs to be emailed to ableton as a bug report.
Re: Encoder speed sensitivity troubles
Valiumdupeuple wrote:Hey fellows,
I think that really needs to be emailed to ableton as a bug report.
So maybe you could do it.
-
staplesyrup
- Posts: 75
- Joined: Thu Jul 05, 2007 9:56 am
Re: Encoder speed sensitivity troubles
Can anyone confirm this behaviour?
-
Valiumdupeuple
- Posts: 1155
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: Encoder speed sensitivity troubles
Yeah, I could, but I didn't have the time to test in the conditions described in this thread, so... I can't by now !login wrote:Valiumdupeuple wrote:Hey fellows,
I think that really needs to be emailed to ableton as a bug report.
So maybe you could do it.
They know the problem, I've just read how they describe it.
But, you know...