Does this not work? (copied from SL automap manual, pg 9)R.J.Dubya wrote:Abletoff, thanks for that link to the tempo control workaround. I probably won't even bother, but it was good to read.
Hey man, if you want to access all of the parameters in operator and sampler etc., set it to 'RemoteSL classic' under control surfaces instead of 'RemoteSL' in Live's preferences. They changed the way ableton's automap worked sometime along the way and simplified Live's internal parameter mapping. I personally like the new layout, as the old one has all the parameters, and it's not as organized, but you might like it better the old way. The old one also has device on/off for live devices like vst's do.mikHATz wrote:I havent dug too deep into it yet but im dissapointed with its implementation with Live. Seems like there are lots of params that you cant access via the SL for sampler, operator. The universal automap is really cool, but i dont have too many VSTs, so it doesnt do too much for me, works great with reason though, you can access all params on different devices( except for NNXT of course )
Again, really frustrating that some params on Lives instruments arent accessible via the SL, but its still a great controller , and the fact that the LCDs update is way helpful. I havent noticed the pot pickup thingie yet. hopefully i wont.
As for the pot-pickup, it's only an issue after switching to ableton automap from any other template, and I'm not even sure if it happens on PC (I'm macbook).
Plug-in Automap (template 38 ) is only for third-party plug-ins, so it won't ever work with any DAWs built-in effects or instruments because they would have to be wrapped by novation into the automap version, which is impossible because they aren't VST's or AU's. So ya, for other DAWs, the internal stuff is controlled by 'mixer automap' (template 39), the same template which controls a DAWs mixer parameters, which is essentially just the old automap template for Logic, cubase etc. Ableton just happens to have it's own special mixer automap, and so, like the others, controls all internal stuff from there.Tone Deft wrote:Automap template looks cool, doesn't work with Impulse, Operator, Simpler or Sampler?? WTF? I guess what goes back to the Automap Server option to pick your automap VSTs, Ableton/Novation should fix this. I'm trying to use just the built in instruments these days. The template 40 automap for those are done well, IMO. Do other DAWs have the same problem with built in effects?
if anyone finds a way to make all those f'n decimal places go away on the LCD in plug-in automap, I'd love hear about. Or how to change the range display. It's visually confusing to see that a parameter is at 0.039572 on a range from 0 to 1. And for many plg-ins, all the parameters show up that way, which is ugly.
Whilst the plug-in is in use, the strip shown in the image above will be used to display the settings of the last control moved on the SL. To
edit the settings for a particular control, move it and then type the desired content into the boxes (as indicated above). Although values will
be shown for sliders and pots, typing in different max/min or step values will have no effect as these types of controls have fixed max/min
values and a continuous action.
Unlike sliders and pots, however, the action of encoders and buttons can be edited. When a button or encoder is first assigned, it will
probably be necessary to change the range, as the maximum and minimum values may appear as 1 and 0. This will make the parameter
move from maximum to minimum value with one button press or one encoder step.
To change the sensitivity of an encoder, type in a maximum value that is much higher than the minimum, as follows:
These settings will scale the plug-in parameter being controlled from 1000 to 0, making the encoder action very sensitive and allowing very
fine adjustments to be made. To decrease the sensitivity, enter a lower maximum value, as follows:
These settings will scale the plug-in parameter being controlled from 100 to 0, making the encoder much less sensitive. Setting a minimum
value that is higher than the maximum value at any stage will reverse the encoder action.
Notice that the step value (the last box at the bottom of the plug-in window) has been 1 in each of the examples above. To make the
plug-in parameter being controlled jump up or down in steps as the encoder is rotated, enter a higher step amount, as follows:
These settings will scale the plug-in parameter being controlled from 100 to 0, where the encoder jumps in steps of 20 across this
scale. Therefore, the encoder will jump up/down from the maximum and minimum values in 5 steps.
Buttons can also be given a stepped action. For example, a button with the settings shown above will jump up from the minimum to
maximum plug-in parameter values with 5 button presses. After the maximum value has been reached (or the highest value the step size
allows), the next button press will return to the minimum value and start the next cycle. To make the button step down from maximum to
minimum values (reverse the action), change the minimum value to 100 and maximum to 0.
Multiple controls on the SL can be assigned to the same plug-in parameter, which can be useful if wanting to have a slider, pot or encoder
for making fine adjustments and a button for coarse stepped edits. However, only one plug-in parameter at a time can be controlled from
one knob/button on the SL.
<<<
I admit I am stuck much earlier in this process, but thats the best help I can be.
