mRpinC

I've got the following setup: APC40, Live 8.1.2b6 and M4L 8.1.2. I'd like to midi map 16 buttons in the APC clip launch section to a device that Bjorn at Covert Operators has been working on call the Clip Mapper: See this thread (It's an amazingly useful midi control extender device): 

http://forum.ableton.com/viewtopic.php?f=35&t=132437&p=1095446#p1095446

The 16 APC clip launch buttons would be midi mapped to 16 buttons on the clip launcher. By triggering pre-programmed clips, the clip mapper has the ability to switch through different mappings, so the midi-mapped APC 16 button grid can become multi-functional and control an unlimited number of devices/parameters

The problem is that there are some live devices, like Looper for example, which don't allow full interaction via the live API. Therefore the clip launcher is NOT able to control play/stop/rec, etc. on the looper (rendering it useless really!). The only work around I can see for this is to create a middle man M4L midi patch, which the clip mapper talks to and which sends midi notes/ccs to control loopers (or whatever) which are in other tracks.

Does anyone know of something similar or even a proof of concept which I could use as a template?

Would any midi loopback (IAC) type stuff be needed or could I send the midi messages directly to the looper/devices?

Any help greatly appreciated as I'm so close to having my ideal DJ setup!

I've got the following setup: APC40, Live 8.1.2b6 and M4L 8.1.2. I'd like to midi map 16 buttons in the APC clip launch section to a device that Bjorn at Covert Operators has been working on call the Clip Mapper: See this thread (It's an amazingly useful midi control extender device): http://forum.ableton.com/viewtopic.php?f=35&t=132437&p=1095446#p1095446

The problem is that there are some live devices, like Looper for example, which don't allow full interaction via the live API. Therefore the clip launcher is NOT able to control play/stop/rec, etc. on the looper (rendering it useless really!). The only work around I can see for this is to create a middle man M4L midi patch, which the clip mapper talks to and which sends midi notes/ccs to control loopers (or whatever) which are in other tracks. 

Does anyone know of something similar or even a proof of concept which I could use as a template? 

m4l-patchhelp-required-to-sends-midi-notes-to-devices-in-other-tracks

You could try using send/receive objects to transmit midi between devices.

Note however that it doesn't ensure accurate timing.

Basically, the amount of jitter/delay is not predictable.

You could try using send/receive objects to transmit midi between devices.
Note however that it doesn't ensure accurate timing.
Basically, the amount of jitter/delay is not predictable.


Thanks Broc. I've heard that you can use the MAX/MSP Midi device to route midi back into live. Do you know if this works?

The problem with MAX/MSP Midi devices is that they are available in Live only if Max is actually launched. For instance, if you just launch Live and don't use the M4L editor, they are *not* available. So I think it's much better to use IAC for loopback.

I see... Probably best to go with send/receive as you mentioned earlier. Do you know of an example patch that has the send (master?) and receive (client?) patches?

Essentially, all I want to do it trigger drum hits which will be input quantised in any case, so accuracy is not paramount

I see... Probably best to go with send/receive as you mentioned earlier. Do you know of an example patch that has the send (master?) and receive (client?) patches? 

Essentially, all I want to do it trigger drum hits which will be input quantised in any case, so accuracy is not paramount


It's actually quite simple. Just make sure to send each midi message as a list, using [pack] on the sender and [unpack] on the receiver.

M4L Patch/Help required to Sends MIDI notes to devices in other tracks