Livecontrol 2: Midisettings on PC

Solve problems with help from the Liine team and fellow users.
Post Reply
mat
Regular
Posts:127
Joined:08 Dec 2011 09:21
Location:Germany
Contact:
Livecontrol 2: Midisettings on PC

Post by mat » 23 Jun 2013 13:06

Hey there,

I got some questions regarding Midisetup with Lemur and Livecontrol 2 on PC Win7 32 bit.
Although I have posted some of that somewhere else, I think it is good to create a new topic and sum it all up..

1. With which virtual Midiports LC2 works?

I had success using loopmidi http://www.tobias-erichsen.de/software/loopmidi.html as suggested in the setup guide.
However, I used maple midi port 1-4 http://www.maplemidi.com/Maple_driver.html during the last years parallel on iPad and Jazzmutant Lemur without any trouble,
but that does not work with livecontrol => I got feedback on Lemur but can not enter values (?)
Any else Midiport working? Or anyone experience also this problem?
It seems that it is based on sysex data (as Nick posted somewhere), not every virtual Midiport sends/receive those... or maybe this have to be activated in preferences of these ports?

2. Is it true, that it is not allowed to open the remote in and out for Miditarget0 in Ableton while running LC2?

I experience trouble while opening those... including auto-shutdown of Lemur app, strange behavior (like some fader controlling other stuff) and even some crashes in Ableton.
The reason for opening remotes additional to the settings suggested (http://liine.net/assets/files/lemur/LC2 ... OSXWIN.pdf) was that my synth modules send on Miditarget0 and I wanted a bidirectional Midicontrol. On my setup without Livecontrol I had "remote" activated for in and out without any trouble.
(mirrored to the Miditarget0 settings on Lemur e.g. Ableton: loopmidi1 in, loopmidi2 out ; Lemur Miditarget0: from loopmidi2,to loopmidi in1)
So I changed my synth modules to send on target1 and opend parallel loopmidi 3 and 4 for these. This time with remote. and it works like charm.

3. Can it be, that LC2 - even with remotes closed(!) - send Midi to custom controls on Miditarget0?

While I entered my sequencomat on a custom interface, I experienced strange interactions: If I do something in LC2s Launch - e.g. start a clip - it does something on my sequencer - e.g. mute steps - :o ... so I found out that the Sequencomat module has accidently some Midicontrols on Miditarget0 active - which is not needed at all, cause it only uses OSC. After setting all Miditargets of Control object to "none", everything works fine. (I will send a updated module to my users soon!)
Not sure how it behaves with other modules, cause I changed my additional pages to send on target1 for reasons mentioned above.

Any feedback is highly appreciated!

Thanks :) mat
Lemur modules and sequencer: http://music-interface.com
Setup: Win7professional 32bit, Intel Core 2 Duo @ 2,66 GHz.,Tascam US-144MKII, Ableton Live 8.4,
Arturia Analog Lab., Max/Msp, Maxforlive, Lemur Legacy + Ipad, Akai MPK61, Doepfer Pocket Control

nick_liine
Liine Staff
Posts:340
Joined:01 Oct 2010 11:06

Re: Livecontrol 2: Midisettings on PC

Post by nick_liine » 03 Jul 2013 07:15

mat wrote:
2. Is it true, that it is not allowed to open the remote in and out for Miditarget0 in Ableton while running LC2?

3. Can it be, that LC2 - even with remotes closed(!) - send Midi to custom controls on Miditarget0?
Indeed, LC2 uses MIDI Target 0 extensively. It is highly unadvisable to enable Remote in Ableton Live for ports connected to Lemur's MIDI Target 0. If you want to add custom pages to the LC2 template, you should used MIDI Targets 1 to 7.

Post Reply