Ableton Forum

It would be very usefull, for loads of situations, to be able to set the Macro Control dials to a specific amount of steps..

Example;
- let's say; I map Simpler's 'Sample Start' parameter to a Macro Control dial..
- I set that Macro Control dial to, let's say, a divider of 8 steps..

Now if I turn that dial it will control the 'Sample Start' in 8 steps from 0 to 127..
It will 'skip' trough the sample..

Now this is just one example but this can be usefull to so many more situations where you don't need a gradual-, but a stepping slope..

also see my request:

MIDI control data > Quantizable !
http://www.ableton.com/forum/viewtopic.php?t=44120

I was going to suggest quantization of a macro knob but guess who thought of it already ^^

+1

yes.

in general, a knob going from 0-127 is simply not appropriate for all types of parameters.

maybe there could be different flavors of macros.. buttons, crossfaders, etc.

how about being able to increase the resolution of a macro knob ie:
0-127(7-bit) 0-255(8-bit) upto 14 bit or 16 bit value, as well as decreasing.

Quite often the macro knob cannot set a parameter accurately enough due to the lack of resolution.

annihilator.1 wrote:I was going to suggest quantization of a macro knob but guess who thought of it already ^^

+1

What also would be very useful is to be able to set the min/max range for mapped buttons..
Currently it is fixed at 64 which is not very useful..

Poster wrote:It would be very usefull, for loads of situations, to be able to set the Macro Control dials to a specific amount of steps..

Example;
- let's say; I map Simpler's 'Sample Start' parameter to a Macro Control dial..
- I set that Macro Control dial to, let's say, a divider of 8 steps..

Now if I turn that dial it will control the 'Sample Start' in 8 steps from 0 to 127..
It will 'skip' trough the sample..

Now this is just one example but this can be usefull to so many more situations where you don't need a gradual-, but a stepping slope..

Great idea. My suggestion here is that instead of always using the division of 8 steps, why not allowing to specify the desired steps? I could write '0,32,64,127' or '0,7,64,119,127' into a 'steps' field when mapping a parameter and it would divide the mapping to the entered steps.

This could be useful when mapping button parameters in some vsts where they only have 3 or 4 position (like a waveform chooser or octave select) and the vst reacts to these parameters with midi values 0,1,2,3. In these cases, any value higher than 3 has the same effect as 3 because it selects the last option.

It'd be also easier to switch from 3 different values if you know that you've got the first value by moving the fader down, the second value by moving it somewhere in the middle and the last value at the top.

Another situation is the 'sample start' that you say. You could divide a loop into 8 equal steps by entering '0,15,31,47,63,79,95,111'. Or into 16 steps entering 16 values.

8 steps was just an example..
user definable would be best..

Poster wrote:

annihilator.1 wrote:I was going to suggest quantization of a macro knob but guess who thought of it already ^^

+1

What also would be very useful is to be able to set the min/max range for mapped buttons..
Currently it is fixed at 64 which is not very useful..

+1 to both! great suggestions poster!

I was just lamenting the fixed at 64 result myself

Since we are talking about this stuff, I really want to be able to define range for macros too

http://www.ableton.com/forum/viewtopic.php?t=54473

some more on the same tip .. +1

while I agree with the request, the way I get around this is to map the knob to my MIDI keyboard so I can just to values with keys

+1 I need this very badly
It would be great to have a seperated folder at the live devices, where in controllerunits are located. small devices like utility plugin with faders, dials and knobs ready to be mapped. It would be even more awesome to be able to map midi mappings out of the midi assingment browser, or mapping assignments out og the mapping assignment browser to those "controlunits". so you would be able to rack midi mappings.


Well, the best thing I guess would be an internal custom buildable midi controller unit inside of live.
So that you would be able to puzzle together your own internal midi controler out of controlerelements like dial, fader and knob and all this stuff is located in the controllerunit folder inside the live devices browser.

Inqy wrote:+1 I need this very badly
It would be great to have a seperated folder at the live devices, where in controllerunits are located. small devices like utility plugin with faders, dials and knobs ready to be mapped. It would be even more awesome to be able to map midi mappings out of the midi assingment browser, or mapping assignments out og the mapping assignment browser to those "controlunits". so you would be able to rack midi mappings.


Well, the best thing I guess would be an internal custom buildable midi controller unit inside of live.
So that you would be able to puzzle together your own internal midi controler out of controlerelements like dial, fader and knob and all this stuff is located in the controllerunit folder inside the live devices browser.

You have seen Max4Live haven't you??

You can build exactly what your asking and set a live.dial with whatever divisions you'd like then have it sxcale to ensure the end target receives the information in the format it's looking for (sends for example work between 0. and 1. whilst other parameters work between 0. and 127. etc.)

Cheers
D