Why does automap suck?
-
OvertoneZero
- Posts: 1347
- Joined: Fri Mar 16, 2007 9:16 pm
Why does automap suck?
So, i'm contemplating buying a Remote 61 SL but I keep reading bad things about the automap. What's wrong with it? It seems like a good concept.
On the ad page for the keyboard on Musician's Fiend it claims to contain Automap templates for: * Live Automap - Mixer/Navigation and Effects
Does the keyboard Automap to control whatever the front active window is? For example, I click on a Sampler instrument, and then the keyboard automatically loads the map template and the little LCDs above the little knobs show the parameter for each?
Is this not a convenience and progress? Am I wrong to value the technology?
On the ad page for the keyboard on Musician's Fiend it claims to contain Automap templates for: * Live Automap - Mixer/Navigation and Effects
Does the keyboard Automap to control whatever the front active window is? For example, I click on a Sampler instrument, and then the keyboard automatically loads the map template and the little LCDs above the little knobs show the parameter for each?
Is this not a convenience and progress? Am I wrong to value the technology?
-
brianbacio
- Posts: 116
- Joined: Sun Jun 19, 2005 9:44 am
- Location: Paris, France
-
Grappadura
- Posts: 2123
- Joined: Tue Aug 07, 2007 9:57 pm
same here (sl compact). I read somewhere somebody was complaining about the values that are displayed in the keyboard. They are sometimes translated to values that go from 0 to 1 instead of from 1 to 127. This is not always the case, I´m not sure in which cases it turns out like that, but to me its not a problem. "67" is then 0.5 on the display. So what.
I have a remonte 25sl and I think it is a great device. The itegration with Live is good too. Definately worth checking out these devices.
Steve
Steve
High Quality Sound Effects and Loop Libraries.
http://www.hauntedhouserecords.co.uk
http://www.hauntedhouserecords.co.uk/Blog
http://www.hauntedhouserecords.co.uk
http://www.hauntedhouserecords.co.uk/Blog
automap is great.
i don't know anything bad about it.
the only crappy thing is sometimes the VSTs have non-intuitive names for their faders, but thats the vsti issue, no REMOTE....
i don't know anything bad about it.
the only crappy thing is sometimes the VSTs have non-intuitive names for their faders, but thats the vsti issue, no REMOTE....
www.cachemusic.com
myspace.com/1800cachecall
myspace.com/autonomousunit
myspace.com/kinesicla
myspace.com/pocketonfridays
myspace.com/1800cachecall
myspace.com/autonomousunit
myspace.com/kinesicla
myspace.com/pocketonfridays
-
pat the dog
- Posts: 217
- Joined: Tue Aug 16, 2005 10:56 am
- Location: londoner in amsterdam
Re: Why does automap suck?
sort of... if you're using the live template, then you just make sure that the device you want to control has the blue hand tool activated. this sometimes involves clicking it with the mouse for example when it's not the first device in the chain.OvertoneZero wrote:Does the keyboard Automap to control whatever the front active window is? For example, I click on a Sampler instrument, and then the keyboard automatically loads the map template and the little LCDs above the little knobs show the parameter for each?
but note that with the live template you don't have any control over which parameters are mapped to which knobs except with macro's but then you're limited to 8 parameters. so for vsts and au instruments, it's better to use the "universal automap" template with the plugin in the automap wrapper.
however then the answer to your question "Does the keyboard Automap to control whatever the front active window is?" gets a little more complicated...
on my mac at least, AU plugins function as you describe - i.e. the focussed plugin window gets automapped. but for VST's you first need to click a purple "A" icon in the wrapper, which seems to be only possible using the mouse (which to some extent defeats my objective of using the mouse as little as possible).
so in general it seems better to use AU plugins, but there's a catch - some plugins including Predator and Blue don't inform the host when you change presets, resulting in the SL not updating the parameters - the workaround is either to close/open the plugin window, or only change presets using live's hot-swap browser, or the preset up/down buttons on the SL.
also, you need to be aware that some plugins (such as semi-modulars like albino and zebra) have so many parameters which change depending on the patch, that you may find yourself having to remap parameters manually.
but for more simple instruments like Predator, it works pretty well.
another thing you should bear in mind is that live's 128 parameter limit means that you won't be able to automate all the mapped parameters - but that's the fault of Ableton, not novation.
there is a new version of automap (2.0) due in february, so if any of these issues are likely to bother you, then it might be worth waiting to see what this new version resolves.
-
pat the dog
- Posts: 217
- Joined: Tue Aug 16, 2005 10:56 am
- Location: londoner in amsterdam
then you're better off using traditional midi mapping. the live automap template leaves the 8 rotary pots free for this kind of mapping, or otherwise you could create a user template. but the SL doesn't respond to midi feedback, so in this case you don't get the parameter names or values showing up in the same way that you do with automapped devices.Alien Leg wrote:What if you want to control more than one plugin at a time via automap?
otherwise you might be able to rack up multiple plugins and control them with macros, but then you only have 8 parameters to play with.
-
OvertoneZero
- Posts: 1347
- Joined: Fri Mar 16, 2007 9:16 pm
i recognize that problem... don't know what's wrong...Grappadura wrote:same here (sl compact). I read somewhere somebody was complaining about the values that are displayed in the keyboard. They are sometimes translated to values that go from 0 to 1 instead of from 1 to 127. This is not always the case, I´m not sure in which cases it turns out like that, but to me its not a problem. "67" is then 0.5 on the display. So what.
anybody can help?pieter wrote:i recognize that problem... don't know what's wrong...Grappadura wrote:same here (sl compact). I read somewhere somebody was complaining about the values that are displayed in the keyboard. They are sometimes translated to values that go from 0 to 1 instead of from 1 to 127. This is not always the case, I´m not sure in which cases it turns out like that, but to me its not a problem. "67" is then 0.5 on the display. So what.
when i use automap i have two values: 0 and 1. nothing inbetween. not even 0.5 as mentioned above.
it happens only in automap, with ableton and digital performer.