MIDI Kinetics Forum

hi guys,

I am not able to get my Lemur IPad App send OSC commands to my laptop (mac osx). I am able to do so using TouchOSC, so do not think it is a network ports issue.

I have created an OSC Target (0) on Lemur App with my laptop IP and a some port ( 8500 ). I then loaded OSCMonitor on my laptop listening at port 8500.

I created a custom button in my Lemur project with an action ( On Expression x ) : oscout(0,'/test/osc/command',0); I ensured that the target is OSC 0.
When i press the custom button, no command seem to be sent to my laptop.

Note: To be sure it is not my programming skills, I used "Singular" template from the library, and I can't make it work as well..

If I do the same on TouchOSC app, I could see the commands intercepted by the OSCMonitor.

Am I doing something wrong ??

Thanks!

your test should work. I would try again with a simple fader object. No custom OSC command or custom button, just the default object.

Thanks for the tip, I tried using the fader and no success..., I have the latest version of the App (3.1.0), wondering if this is a bug in the app. Anyone else having this issue ?

Hi
You may find it is sending it once but not updating because there is no change in the data to be sent . . .
Try oscout(0,'/test/osc/command',x); instead - this will send 0 for 0ff and 1 for On . ..
Cheers
MM

Yes I had this issue yesterday and.. I wasted time looking through other OSC templates, even reading the manual a bit.
Then I watched the Liine video and tried that.
The problem was that I used an IP address for my computer as the Lemur OSC target.
I put in the local hostname of the computer and it worked fine. : )

http://liine.net/en/support/
http://www.youtube.com/watch?v=WBBZrgPf ... r_embedded

azfx wrote:Thanks for the tip, I tried using the fader and no success..., I have the latest version of the App (3.1.0), wondering if this is a bug in the app. Anyone else having this issue ?

Thats interesting..!, I thought they reverted back to IP in the latest version :

What's New in Version 3.1.0
- OSC targets revert to IP instead of saved hostname.
- Interface names now displayed in tabs.
- Multitasking bug fixes.
- OSC handling bug fixes for very long strings and lists.
- Support for SysEx messages up to 256 bytes.
- Scripted lists length limit increased to 256.
- Knob object bug fix.
- Z variable bug fix.

I will test it out using hostname, and let you know, Thanks!

azfx wrote:Thats interesting..!, I thought they reverted back to IP in the latest version :

What's New in Version 3.1.0
- OSC targets revert to IP instead of saved hostname.
- Interface names now displayed in tabs.
- Multitasking bug fixes.
- OSC handling bug fixes for very long strings and lists.
- Support for SysEx messages up to 256 bytes.
- Scripted lists length limit increased to 256.
- Knob object bug fix.
- Z variable bug fix.

I will test it out using hostname, and let you know, Thanks!

Actually that meant there was a bug where saved hostnames would be replaced by IPs, which is now fixed

hehe yes I don't think I would have tried a hostname in there until the video directed me to do so..
I spent several hours doing everything but using a hostname.
It just did not occur to me that an IP address wouldn't work these days because TCP/IP is my work.
cheers!

azfx wrote:Thats interesting..!, I thought they reverted back to IP in the latest version :
I will test it out using hostname, and let you know, Thanks!

host names rarely worked for me (e.g. with Konkreet Performer), so I always use IP's.

Hi
Both methods should work , hostname or IP address .
Hostname makes it easier to track in some network configurations
IP can also be good with statically allocated IP's

Cheers
MM