> 1) the Cue Encoder and Track/Device Encoders sends data in different ways.
> when mapping a midi control, Live should behave accordingly to which APC encoder is controlling it.
> 2) the Encoders when used as on/off buttons should behave as if they are simple switches between two values.
> racks/chains trees don't seem too APC friendly either.
+5 (everyone in the room, obviously all live users...)
Midi Mapping, whether instant/dynamic or manual, it's useless if data isn't mapped well.
Live could be made smart enough only when related to Controllers like APC where the midi messages of every control seems to be fixed in hardware... with other hardware where every specific knob or button can send 'any' midi message Live can't be so smart. Ableton could at least give the users some possibilities to tell how the software is supposed to manage the incoming data.
On/off switches are just useless working the way they work now on the APC
> 3) you should be given the option to have a visual feedback from the interface (when you tweak a certain parameter, that > parameter jumps on screen and is visible)
As an Industrial Designer couldn't agree more
Feedback is essential. You maybe disable it when you're playing on stage because it's more likely that you'll already be using well crafted Macro Controls by then. Definitely useful before that IMHO (not everyone in the room fully agrees).
> 4) operating from the controllers should try to free you from the mouse as much as it's possible.
> the 'reference' should give you exact information on how something works, not gibberish.
Agree with the 'gibberish' info about the mapping, and with the mapping itself, for Collision.
Analog, Operator, Electric are quite good as they are... apart for a few missing switches.
Sure they can offer some alternative mappings 'out of the box'.
I'm curious how the 'Best of Bank'
'de facto'
'non existent'
'instant mappings'
could help...
> 5) one of the thing I've already done, and that stray411 does in it's video it's to use the Bank/Select buttons to go
> through the scenes... this was also explained, in a different way (and smartly using the cue encoder instead of another
> encoder), in the tips page on AKAI site. Yes, this gives you a way of visualize a specific clip, because you can
> navigate the Tracks, then the scenes, finally selecting a clip. BUT, if you are playing five clips all in five different
> scenes try going from one to another, to another, to another... with the option to autoselect the playing clip on the
> selected track all becomes a lot smoother.
Mixed opinions here on the way Bank/Select Buttons should work.
For some it's best the default behavior (just 'fly over' the scenes without selecting one...),
for others makes more sense to select scenes while going up and down ('a la stray411').
I guess it depends on the structure of your set.
I'm quite ok with the way the Bank/Select buttons already work now, even if it presents some issues.
The possibility of having the playing clip selected when selecting a track could be helpful.
There's a problem though, when you select a track that doesn't have playing clips you still need a way of selecting the scene containing the clip you want to check/tweak before it's launch...
I'd personally prefer have a pair of options/modes switchable 'on the fly'.
I guess that the easiest thing to do is to have a mode where clicking on a clip on the APC just selects it like when you just click on it (not on it's play button) on screen.
> Furthermore, I have still not found a way to EQ more than 1 track at a time without remapping Pan and Send controls,
> which is a total bummer. At this point I think I am just going to have to spring for a Behringer BCR2000 for these
> controls. Sucks because I kinda wanted to keep the rig as compact as possible, but I think this just might be the way it
> is. Anyone have any other ideas?
Someone here it's suggesting Macro Controls detached from a Rack/Chain but just as Group of Controls.
A Group of Controls that could be connected/related to parameters contained on more than one Track and/or Rack/Chain.
A Group of Controls that can then be used as a Device/Macro_Control_Bank in whatever track you through it in.
Some issues came up here and there, a smart public discussion of this should be more fruitful.
> I can surely do some of these things with MAX or Bome_MTPro,
> BUT
> I think that these and other softwares around should be used to do something more...
>not to give the controller/software couple some functions they're supposed to have
> IMHO
> out of the box
Huge debate here!
A couple of us here own Max and/or MTPro and/or others softwares and we are used to 'bend controllers to our will'
although there's a general agreement (especially from the less 'geeky' ones) on the fact that more could come 'out of the box' in terms of 'choices for the user' without having to become a pseudo-programmer
Let's hear from people at Ableton some comments!
Let's just hope they don't comment everything with the three letter acronym 'M4L'.
Fra
(Max, Paul, Dany and 'the unnameable')
still doesn't convince me that this is the right way to handle the switches)
because can't be completely controlled with the default mappings.