Page 1 of 1
Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 5:28 am
by snaper909
Hy Guys,
Is there a way to make a "bridge" in M4L between a Lemur project and Live?
I've made a nice little controller in Lemur, but wouldn't really map again every time when I open a new session.
Is it possible to assign the incoming CC messages to Live through the live.remote object?
Re: Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 10:35 am
by snaper909
May somebody have an example for the "instantmapping"?
Re: Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 11:40 am
by S4racen
Like with Remote Scripting??
Cheers
D
Re: Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 12:29 pm
by snaper909
S4racen wrote:Like with Remote Scripting??
Cheers
D
...kind of.
(For my own use, no future product plan...but possible
:D:D)
Anyway.
Live forget the mapped CC's after creating a new session.
So I have to make something with Max (its OK) or make my own control surface script in Python (not OK...)
Re: Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 12:30 pm
by snaper909
S4racen wrote:Like with Remote Scripting??
Cheers
D
Oh, and creating a live set with the mapping and save as a default is not an option, cause if you remove or add channels you have to re-map them again
Re: Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 12:32 pm
by Machinate
Lemur sending OSC into Live, MaxForLive device controlling Live via live.remote et al.
This is the way to go, in my opinion. Midi mapping is pretty much useless for something you want to use in multiple projects.
Re: Midi CC "automapper" for Lemur project?
Posted: Thu Nov 14, 2013 12:35 pm
by snaper909
Machinate wrote:Lemur sending OSC into Live, MaxForLive device controlling Live via live.remote et al.
This is the way to go, in my opinion. Midi mapping is pretty much useless for something you want to use in multiple projects.
That is OK for me too.
But how to?