User configurable defaults for 'device control'

[drchoc]

Like the subject says I want more control.

I love the macro and automapping concepts for device control, but would really like to be able to save the defaults so that I can avoid needing to 'switch' banks as much as possible.

For example with operator I would prefer to be able to tweak the filter, lfo and algorithm without needing to switch banks. In a performance scenario these kind of parameters give more scope for destroying a sound than the current default. We all have different needs

[prebentious]

It can be done with Max for Live, but not otherwise, I believe

[drchoc]

Well this should be a standard feature imho, and could provide all users with easy to use customisation. Switching banks is archaic.

[dancing Ray]

You can make a rack and assign the desired parameters to macros. Then they´re automapped whenever you select that rack.


Don´t know if I understood the problem right, though...

[Jarvisimon]

Like the subject says I want more control.

I love the macro and automapping concepts for device control, but would really like to be able to save the defaults so that I can avoid needing to 'switch' banks as much as possible.

For example with operator I would prefer to be able to tweak the filter, lfo and algorithm without needing to switch banks. In a performance scenario these kind of parameters give more scope for destroying a sound than the current default. We all have different needs

I was just about to post a new thread on pretty much the same subject. Controller mapping!

I have mentioned my take on this before but on occasion, I don't mind repeating myself, so here goes.

Similar to the way the blue hand automaps the selected instrument to your controller, I would like to see something similar to be made possible inside instruments (including external vst's).

If I pull up NI Massive synth, I would love to click on any of its components, be it envelope, LFO or whatever and have that module instantly map to my controller (100% user configurable mapping....much the same way as user mapping scripts are written but with more detail). This way, a simple click would allow me easy access to Oscillators, envelopes etc.

This could also be taken one step further again with multi controller access. If I wanted one controller to map to an Oscillator and a second controller to map to the filter and a third and a fourth controller to map to wherever else, this should be made possible.

I would also like to see a sequencer track for controllers, so that controllers could be automatically swapped around for Verse, Chorus etc, thereby potentially making Ableton Live a truly powerful Live tool.

I don't know enough about Max4Live, however, this should be possible inside Ableton without it.

I posted a similar thread on the NI forum just before I found this. Of course it should apply to all plug ins, not just NI, however, it would then need some communication between Ableton and whoever else wanted their plugs to have such tight integration within its environment.

As I said in the NI forum, I do hope their coders are reading this and taking notes. We are incredibly fortunate in that we have these products on the market, all of which are super capable, I just hope they learn to talk each others language a little bit better. It is to everyones benefit.

[drchoc]

You can make a rack and assign the desired parameters to macros. Then they´re automapped whenever you select that rack.


Don´t know if I understood the problem right, though...

That is way I currently do it but I figured it was unnecessary and would be neater if no racks were required, especially if you are using max for live devices, then you dont always want to use a racked device.

I fully appreciate that a lot of thought must have gone into the current defaults but for me (and I suspect many others) they are not always ideal. For a live set obviously things will be prepared in advance, but this fix/tweak could mean one less rack is required on your track saving screen real estate and setup complexity.

See this document from nativeKontrol that summarises the current defaults
http://www.nativekontrol.com/uploads/Li ... apping.pdf

For example with the flanger the bank 1 defaults are

Encoder 1: High Pass
Encoder 2: Dry/Wet
Encoder 3: Delay Time
Encoder 4: Feedback
Encoder 5: Envelope
Encoder 6: Attack
Encoder 7: Release
Encoder 8 : controls nothing!!!

I would choose

Encoder 1: High Pass
Encoder 2: Dry/Wet
Encoder 3: Delay Time
Encoder 4: Feedback
Encoder 5: Envelope
Encoder 6: Release
Encoder 7: LFo amount
Encoder 8: Lfo Rate

A simple change that for my purposes makes flanger way cooler.

Perhaps I am making a fuss over nothing on the assumption that this change would not take too much work from Ableton. But these kind of subtle tweaks give us more power especially when Live focuses so much on the device control aspect.

Thanks