midi in/out for MaxForLive

lh_midiinoutV1.03 – A pair of objects to access all midi data types from within M4L devices.

Updated to work smoothly with core midi changes and multiple occurrences of the same midi controller (e.g. 2 x Launchpads)

lh_smidiinV1.00 – A reworked version of lh_midiin, which outputs a stream of ints as opposed to formatted lists of incoming midi. Useful for receiving long sysex messages.

February 7, 2011 | 4:37 pm

Perfect thank you, ill have a play in the morning.

February 8, 2011 | 4:52 am

Amazing, thank-you so much for this. I can now build my Live MIDI Show Control device.

Apola Kipso
April 19, 2013 | 1:48 pm

I installed by copying them into a folder I have added as a path to M4L. lh_smidiin and lh_midiin show up and I can insert them in a patch, but they are sort of greyed out and don’t have any inlets or outlets.
I’m on OS X 10.6.8 – would incompatibilites show up like that in Max or did I install them wrong? Any help would be appreciated!

May 22, 2013 | 10:10 am

Is there a version for Windows?

May 29, 2013 | 5:01 pm

I had the same issues on 10.6.8 as Apola. Any chance there is a Snow Leopard version in the works?


June 9, 2013 | 1:26 pm

Same issues as everyone else:

1.03: Does not work at all
1.02: The help files load but the object itself has no inlets and does not load

OSX ML, Latest M4L and Ableton.

June 9, 2013 | 1:41 pm

The issue may be related to this: http://abstrakt.vade.info/?p=62

It certainly shows up as a folder on mine

December 3, 2013 | 2:50 pm

Okay! This v3 version did not work at all? Trying to find a solution by adding Pkginfo etc, nothing worked. Searched for an earlier version and that resulted in a working .mxo (in the v3 release the inlet and outlets didn’t show up). I uploaded the .zip in the attachment!

October 16, 2014 | 9:06 am

dear mr hunt – i’ve tried to reach you via the mail-address provided with your externals but have had no success so far.
i’d be gracious if you could briefly send me you’re current contact to benni (thethingy) fnfnfnfn.de as i have some questions about your license. thanks a ton!

April 25, 2015 | 8:40 am


I am trying to use lh_midiinout in M4L to send Bank and Program changes to an E-mu Virtuoso 2000.
I set up a patch that works fine when using the midiout port of Live, but does not work when using lh_midiout instead.

With V1.02, I get invalid bytes (as seen with the MIDI Monitor app), when sending the midi messages.
With V1.03, the lh_midiout object does not have any inputs or output ports and does not even show up in "List Externals and Subpatcher Files".
I tried relaunching both Live and MAX before each trial.

My goal, once this works, is to build a complete controller for that synth, so I will later need to use SysEx (which is why I am trying to use lh_midiinout).

I am on a Mac with OS X Yosemite 10.10.2, with Live 9.0.6.

Any help or hint appreciated.

April 25, 2015 | 11:21 am

lh_midiinout is a 3rd party external on system level, and thus depending on the OS it may not be reliable and future-proof.

You could use UDP/OSC instead for sending special midi data from Live and convert OSC back to midi with a standalone Max application.

May 3, 2015 | 9:01 am

I do not have Max (only MaxForLive), so using a standalone Max application is not a solution for me.
Would it be possible instead to use Live MIDI Remote Scripts?

May 4, 2015 | 4:12 am

Marco you can use a Remote Script yes, but it’s a little bit of work.
You have to set a User remote script, give its encoders parameters the corresponding CC values from your controller. Then in M4L select your User remote script as the control surface you want to listen for, grab the desired CC it’s receiving and do whatever you want with it.
I’ve actually made a patcher for that, but didn’t find the time to properly document and post it on the web.
Send me your email address via mp and I’ll give you the patch.

Viewing 13 posts - 1 through 13 (of 13 total)

Explore More