Ableton Forum

Hey all

I've installed the new Automap OS V3, and reinstalled the templates as well.... Now my global stop button doesn't work with template 40 (Ableton)...

Anyone else have this problem? Or is it just me?

Everything else seems to work ok, learning is fine, mixer is fine, other transport controls work fine.

Hmmm.

Running - Macbook Pro 2.33 C2D, 2GB RAM, Live 6.05 on OS X

Cheers.

Hey

So what's the deal, does no replies out of 80 views mean that everyone with a REMOTE SL has installed the new AUTOMAP and templates and everything works fine?

No suggestions?

BUMP.

No. My automap templates don't work at all!

But I'm probably doing something wrong as I haven't spent much time trying to get them to work yet.

I didn't reinstall the templates (maybe that's the problem). I just did the full install of version 3 which I think includes everything (templates too). If I were you, I would just reinstall v. 3.0.
Good luck.

I'm having a strange problem. I've reinstalled v.3.0 three times now, and opening several different Live sets I get the same problem, where the first 3 sliders of the mixer end up affecting the tempo, the global record on and off, but not the first 3 tracks like it shows in the LCD. Been trying to fix that for days, can't get anything to stick. Each new set I open has the first 3 faders mapped to those controls and not the first three track's faders. Although I haven't seen anybody else with that specific problem, makes me wonder why mine alone exhibits this bizarre behavior.

jyang wrote: I've installed the new Automap OS V3, and reinstalled the templates as well.... Now my global stop button doesn't work with template 40 (Ableton)...

i had this problem after first installing v3 and reassigning a few buttons in template 40. reinstalled v3, worked, reassigned those buttons again, still works.

Hmmm. I'll try and reinstall it again as a full thing, and post back.

Thanks for the replies this time.

jyang wrote:Hmmm. I'll try and reinstall it again as a full thing, and post back.

Thanks for the replies this time.

Did the reinstall work for you? I ran into the "can't stop" problem this week. some of my live sets accept the stop button, some don't. (?!?)

ehm... ... problem solved. I assigned Midi channel 1CC74 accidently to something else, didn't know that the remote surface doesn't has priority!

sparklepuff wrote:I'm having a strange problem. I've reinstalled v.3.0 three times now, and opening several different Live sets I get the same problem, where the first 3 sliders of the mixer end up affecting the tempo, the global record on and off, but not the first 3 tracks like it shows in the LCD. Been trying to fix that for days, can't get anything to stick. Each new set I open has the first 3 faders mapped to those controls and not the first three track's faders. Although I haven't seen anybody else with that specific problem, makes me wonder why mine alone exhibits this bizarre behavior.

do you have midi assignments to those controls? I've come across this before. automap sends midi messages, if the midi note/cc for an automapped control is midi assigned, that automap control is ignored.

That was probably it. I think I was using a Live Template that had a lot of MIDI assignments, I made a new template and everything has been good since then. Remote SL has been quite enjoyable the last 6 months.

same here, I Midi-assigned another controller to something that used channel 1 CC74, the same message that Automap's "stop" uses.
But surface control maps shouldn't be allowed to be overwritten with manual midi mappings, this is a weak point with ableton live.