DAW not receiving Lemur App Signals on Wired Network

[maestro2be]

Hello all. I was hoping someone could let me know if this is possible or what little stupid detail I am missing.

1. Lemur iPad 2 connecting to my Macbook Pro using a dedicated AD-Hoc connection or over my studio WI-FI works perfectly (connecting to Presonus Studio One V1 and V2).

2. Lemur iPad 2 connecting to my Dell Laptop running Windows 7 64bit using an AD-hoc connection or over my studio WI-FI works perfectly (connecting to Presonus Studio One V2 64bit)

3. Lemur iPad 2 connecting to my Main DAW machines that are CABLED (CAT5e) into the exact same LAN as my WI-FI network can see the ports and my iPad 2 Lemur app, but no applications will receive any signals from the controls in the Lemur app. This one has me completely stumped. I can see the iPad. They are on the same network (only difference is iPad is wireless, and DAW is wired). I have all firewalls disabled in Windows 7. I know they see each other because the Daemon can connect to the ports on my iPad and vice versa.

I have tried for two days to make number 3 work? What is possibly the problem? Can Lemur connect to a wired machine sitting on the same LAN as the iPad 2? All other applications can connect perfectly fine such as AC-7 core and V-Control. No I do not have the other midi software conflicting with the Lemur daemon as I have uninstalled them completely (rptmidi and Ney-Fi). Lemur Daemon is the only midi application running in the background and in my system tray.

Thanks!

Maestro2be

[Phil999]

you can run Ney-Fi and rtpMIDI without problem next to the Lemur daemon. They don't disturb each other. What your problem is I can't say. If you can connect your iPad to V-Control, it must connect to the Lemur daemon. Your setup should be alright.

I am planning to get a wireless card for my file server, but I'm not sure how to set it up and if there will be any latency. Maybe it is of some use if I tell you how I do it at the moment. I create an ad-hoc wireless network on a netbook that is already wired to my LAN. There are two independent networks. Then I bridge the two network adapters, and from then on I can connect my iPads to any machine in my LAN.

Maybe you also need to bridge your wireless adapter and wired adapter? But I'm not sure, because it should work for all application or none. Do you have fixed IP's or dynamic ones? Maybe it's just a question of dynamic IP's that need a minute to find the network. Again, if V-Control works, Lemur must work also. I'm very new to Wi-Fi, so my experience is very limited. But I also made the experience that no-one really can give answers, neither in private, nor in specialised internet forums. I had to find out everything on my own.

[maestro2be]

Thanks for the response. I just had a breakthrough but not sure why this behavior happens. Here is what I can reproduce 100% of the time.

1. On the DAW machine I will connect to (any of my Windows 7 64bit WIRED machines), when I create inputs and outputs ports (using port 0, 1 and 2 which are required to use the template I have) it fails completely. Nothing ever works.

2. This morning I decided to delete ALL ports and so when you open the daemon there is literally nothing but a blank screen.

3. I open my Lemur iPad app and notice it says "unassigned". I would expect this since I have deleted ALL the ports to my machine.

4. This time when I hit "MIDI TARGETS" on the iPad Lemur Settings, I notice something at the very bottom called "MACHINE NAME : SESSION 1".

5. I decided to try to connect to this. Instantly I was able to control my DAWS on the wired machines!

So the issue is somehow that Lemur does not like connecting to ports MIDI 0-7, but in fact only wants SESSION 1 on my Windows 7 machines. Now here is the really strange thing. I thought ok since you want SESSION 1, let me go ahead and add those ports to the Daemon. FAIL! Instantly nothing works again and all turns red in the iPad. So at this point it connects and lets me move faders etc, but will only connect to a Daemon that does not have any inputs or outputs configured. this means I am restricted to 8 faders, and cannot control any tracks from 9 and above.

Does this make logical sense to anyone or am I a making some stupid error?

[maestro2be]

Additionally to the post above here is my final findings that I cannot get beyond.

1. The Daemon on ANY of my Windows 7 64-bit WIRED machines refuse to let me create more than one set of ports. If I create a set called Session 1, then try to add Midi Port 0, it changes Session 1 to Midi Port 0.

2. Then try to create midi port 1, and it overwrites midi port 0 and changes it to midi port 1. Additionally inside the Daemon, the "MACHINE NAME" --> "SENDS TO" --> "iPAD 2 Lemur" is ALWAYS red. No matter which port I chose, this direction of communication is red on the Daemon Windows 7 Machine.

I am doing an "ADD", so it shouldn't be doing this but it is 100% reproduced here. My Macbook Pro allows me to create as many ports as I want. I additionally went into my iPad Lemur settings and added Targets for midi 0-7 incase Windows would look at the iPad PRIOR to allowing me to create that port. Doesn't work.

At this point I have emailed support and will await someone's help on this as there isn't anything else I can think of. Thanks again for any possible help or confirmation that this behavior happens to you also.

Thanks!

[Phil999]

"Session 1" means the 'normal' network connection between iPad and host. It works without Lemur daemon. For most iPad applications this is the only connection possible. It is also the only possible MIDI port.

Lemur with its daemon running on the computer gives you 8 MIDI ports! Ad 8 OSC ports! That's just one detail that makes Lemur so powerful.

[maestro2be]

Thanks again Phil,

I figured it all out and the cause was so simple yet elusive. I guess after updating to 3.1 it destroyed all of my LOOPMIDI installs. I realized that none of my ports were there any more and when I tried to add them it claimed the driver wasn't installed. I checked my other Windows machines and all had the same error now after this update.

So I re-installed loopmidi and it offered to do a "REPAIR" and I said yes. It took about 2 minutes to finish and then rebooted my machine. Logged back in and I was able to create my ports again. So now all is well. It definitely does and can work with any style of network connection as long as you're on the same subnet.

So all in all, a lot of wasted trouble shooting for no reason other than updating to 3.1 did something to my loopmidi installs. Not to mention that now I am getting an annoying error of Direct3d error, Directx is not installed. This is directly related to update 3.1 also, and I have the most current video drivers.

Thanks again,

Maestro2be

[Phil999]

I also use loopMIDI, but the Lemur 3.1 update did not change anything.

But the important thing is everything is working at your place. The directx-error messages you can ignore, as far as I know they appear if Windows has not started all services quickly enough.