KVR Audio

risome · Post by **risome** » Tue Sep 20, 2011 6:46 am

I havent upgraded automap pro since 3 and it works fine with LIVE Suite (current version) I noticed in your video the plugin is labelled camephat( automap) do you get the same problems when using the non automap versions.I dont use plugins that have automap after there name and everything works fine.

risome · Post by **risome** » Tue Sep 20, 2011 6:48 am

Ps i use a remote 25sl a launchpad and 2 LIVID block controllers

KBKB · Post by **KBKB** » Tue Sep 20, 2011 11:46 pm

maki wrote:what was the earliest verson of Ableton Live that had nice compatibilty with Automap?

8.1.3 works

after that they changed something (Ableton told me)

and it stopped working properly

KBKB · Post by **KBKB** » Tue Sep 20, 2011 11:54 pm

thecontrolcentre wrote: As previously mentioned, using the Live Automap template, rather than wrapping plugins

What are you talking about?

........

Selective Quoting??

..........

I have been in comunication with Ableton Live since Thu, Oct 21, 2010

Still no fix 1 year later

KBKB · Post by **KBKB** » Wed Sep 21, 2011 12:03 am

Cheers for the extra input

risome wrote:I havent upgraded automap pro since 3 and it works fine with LIVE Suite (current version) I noticed in your video the plugin is labelled camephat( automap) do you get the same problems when using the non automap versions.I dont use plugins that have automap after there name and everything works fine.

...............Then you are not using AUTOMAP?

Danno · Post by **Danno** » Wed Sep 21, 2011 12:21 am

Sorry to butt in... but is the problem with the WRAPPED plugins? Or even just when using it as a control surface?

thecontrolcentre · Post by **thecontrolcentre** » Wed Sep 21, 2011 11:31 am

KBKB wrote:
thecontrolcentre wrote: As previously mentioned, using the Live Automap template, rather than wrapping plugins
What are you talking about?

Using the Live template in your controller, and setting that controller as a remote in Live's preferences, rather than "wrapping" your plugins with Automap. It works for me (and many others). To control plugins using this method, just click on them, and assign whatever controls you need (some plugs do this automatically, depending on the number of parameters that need to be mapped). If you don't understand, then perhaps you need to read the section in the manual about remote control.

KBKB wrote:Selective Quoting??

Yes. You didn't quote the part of the reply from Ableton where they told you that trying to fix your problem was a high priority.

KBKB wrote:
support@ableton.com on Aug 29 2011 wrote: thanks again for your mail on this topic.

The bug has not yet been fixed with Live 8.2.5, where we concentrated on other stuff
they were concentrating on 'other stuff' rather than 'functionality'

support@ableton.com on Aug 29 2011 wrote: thanks again for your mail on this topic.

The bug has not yet been fixed with Live 8.2.5, where we concentrated on other stuff. See http://www.ableton.com/releasenotes-lesson

Currently, the Automap/VST automation issue is rather high on our list, but I still can't give you a specific date or version where we'll address this.

risome · Post by **risome** » Wed Sep 21, 2011 11:53 am

KBKB wrote:Cheers for the extra input

risome wrote:I havent upgraded automap pro since 3 and it works fine with LIVE Suite (current version) I noticed in your video the plugin is labelled camephat( automap) do you get the same problems when using the non automap versions.I dont use plugins that have automap after there name and everything works fine.
...............Then you are not using AUTOMAP?

Of course i am.The idea is to let the user map what he wants to control to simplify the process when using a plug in with hundreds of parameters .You wont have issues if you use the non automap wrapped plugs.

luckystrike · Post by **luckystrike** » Thu Sep 29, 2011 6:55 am

So what's is the cause of removing OP's KVR review? I'm curious to know.

w1nt3rmut3 · Post by **w1nt3rmut3** » Sat Oct 01, 2011 2:21 am

I find it hilarious that people who supposedly don't have this issue apparently don't know how to use Automap. You guys, if you're not using the Automap wrapped plugins, and you still have to assign midi controls in live, you're not using Automap! "Don't use automap" is not the correct solution to Automap (or, rather, Live) being broken.

risome · Post by **risome** » Sat Oct 01, 2011 2:31 am

Funny it may be but my setup works fine using the not wrapped plugs with automap in fact its only 3rd party plugins that don't get there parameters automatically assigned ,Lives native plugins do.

deleted · Post by **deleted** » Sat Oct 01, 2011 10:21 am

DELETED

thecontrolcentre · Post by **thecontrolcentre** » Sat Oct 01, 2011 10:29 am

w1nt3rmut3 wrote:I find it hilarious that people who supposedly don't have this issue apparently don't know how to use Automap. You guys, if you're not using the Automap wrapped plugins, and you still have to assign midi controls in live, you're not using Automap! "Don't use automap" is not the correct solution to Automap (or, rather, Live) being broken.

Thanks for this. Having checked with Novation, I now realize that I'm not actually using Automap, when using the Live template in my ReMOTE SL. I had thought that my ReMOTE SL and Launchpad needed Automap to be running in order to "communicate" with Live, but it turns out not to be the case. Please ignore my earlier posts.

kmonkey · Post by **kmonkey** » Sat Oct 01, 2011 11:29 am

edit:nevermind

tinusk · Post by **tinusk** » Mon Oct 10, 2011 4:24 pm

Same issue here. Using Ableton 8.2.6 on Windows 7, ASIO, a Zero SL MK1 and Automap 3.7.4 (haven't checked Automap 4 yet). The automation is jerky for Automap wrapped plugins and the automation only seems to be recorded if the plugin window is visible. In addition to that, the LCD screens and Automap window both don't update to the correct value of the parameter being altered.

This seems to be a polling problem on the Ableton side, because Ableton is responsible for correctly reporting the value to Automap which in turn sends it to the Zero SL. This works vice versa for input to Ableton, which would explain the jerky automation.

This problem doesn't seem to occur for native devices, but those are controlled by the completely different (non-Automap) Ableton template 40 anyway. This template bypasses the Automap layer and uses a dynamic mapping similar to the Remote Scripting capabilities of Ableton.

Switching back to MME/DirectX seems to partly fix the jerky automation problem, but the plugin window still needs to be visible. Any serious DAW user would confirm that MME/DirectX and other native audio drivers are not the way it should be done.

I sincerely hope that the developers at Ableton will fix this issue soon. It's a shame not being able to correctly use such a nice controller. In theory, if Ableton is willing to work together with Automap, it would be one awesome system. In practice however, I presume the guys at Ableton have much higher priorities for supporting other (Akai) hardware which they might make more profit on.

There are several long-standing issues with Automap and Novation controllers like the SL and SL MKII series which can only be resolved by Ableton. One would only have to take a look at both the Ableton and Novation support forums to confirm this.

Ableton Live is completely incompatible with any Automap product since v8.1.3