MIDI Kinetics Forum

Hi,

About half of the times I reboot, Lemur Daemon forgets its port setup and everything has to be redefined from scratch. Could this be a permissions issue? Please fix. Thanks.

I think it's the Lemur app that saves the port setup, not the Daemon.

In Lemur, the ports should be the same like last time you used the app, and if the corresponding computer is running Deamon, the connection should be always there.

Are you using static IP's or dynamic ones?

There is no mention of static or dynamic IP anywhere in the Daemon. I just need to select the inputs and outputs on the Mac and their corresponding destination on the iPad. But this doesn't get saved and has to be reassigned after almost each reboot.

I see. One way to connect is to do it entirely from the devices. The daemon is running in the background, one can leave it like that. No need to open it or to do the mapping there. It just runs so that the devices can see the computer's MIDI ports (and that the computer can see Lemur's MIDI ports).

OK thanks a lot, I'll try that.

I personally have switched to Core Midi with lemur because of this. The daemon is pretty much useless with a mac because the audio midi setup built in to the OS is way more flexible and easier to use. Try using MidiRTP for a Windows to connect to Core Midi directly to the iPad or Mac OS as an alternative to the Lemur daemon.

I guess its only disadvantage would be if needed multiple midi ports for your routing in Lemur. But i figure there is an easy way to do this with Core Midi as well. You can create unlimited routings and ports with MidiRTP. It would be on the iPad iOS end of the Core Midi im not sure how to configure for multiple ports through network. But i think there is an app utility you can get to manage this on the ipad as well.

I just noticed you are on mac so just spotlight audio midi setup. In the midi window there will be an option for the network. If your mac and ipad are on the same network you will see the ipad available to connect to.

Solution I found was to clear out the Lemur Daemon list and use the Lemur App to connect the two. These connections appear again when you fully quit the Lemur Daemon and restart, even with computer restarts.

Reviving this because I have the same problem again. By the "Lemur App" you mean the Lemur Editor application? If so, it is always referencing the proper inputs and outputs and everything works fine, but often after a restart some MIDI ports don't work anymore (as well as the Kbd/Mouse port) and everything only goes back to normal when I reconnect them via the daemon.