MIDI Kinetics Forum

I just found out there is a MIDI Port - it's just unnamed. So a blank row shows up in the lemur daemon which i can connect to Lemur In and Out. So my setup looks like your last 2 rows. Only instead of 'MIDI' I have a blank column. However: the remote port entries are red instead of black. So I ...

I have a Focusrite Saffire and this worked for me sending MIDI to external synths. Make sure your Focusrite is on and visible in the MIDI setup window. Hit rescan if it's greyed out but on. Open the info for the focusrite to get the name of the MIDI ports - on mine they are helpfully called MIDI ...

Do you mean the /path/to/some/device address? Yes that can be scripted, as ever more than one way to do it. I have been doing some template work to make Lemur companions to the Push controller and have been going through the various abstractions and whatnot for Mu. Have a look at the Mu Framework ...

So on the m4l side of things, have the udp port change dynamically per m4l device based the ableton track number it resides on. Live API could be used for that. So for example, receive port 1000 on track 1, 2000 on track 2, etc. then whenever that track is selected in Live, send a variable of the ...

OSC can be funneled exactly like MIDI, except more flexibly. Think of the OSC outs on Lemur as being exactly the same as a MIDI channel except instead of being numbered 1 -16 they are set to a port number (default is 8000). if you set up Lemur to use all the outputs on different numbered ports, then ...

There are a couple of ways: Make all the controls use the parent container OSC assignment. Add an "OSC channel" select to the M4L patch that selects the UDP port. Edit the container mapping in each template instance. If you want to have a single template to send to multiple "channels" then a more ...

Unless you received a cease and desist from Liine over the publication of your update (which would be a harsh seeing as they have always strongly favoured a collaborative community) I think you may have been a bit quick to retract your release. I too am stuck without mu on my legacy lemur since ...

I have the same issues with Live9 all the device controls are not working and my custom devices are broken too. I am hoping that whatever the issue with the "unofficial" patch to mu is will be resolved as I didn't get a chance to download that before it was pulled. As far as I can tell though it is ...

At $300 I am very tempted to get a second one for parts or just pure controller overkill. Like Joe Soap I am curious why you needed the daemon. I haven't fired it up in ages since the lemurHost code was updated for the last legacy version of mu. All templates and coms can be done over Ethernet ...

Nobody from Liine able to comment on this?