TouchOSC<--Processing OSCP5 Library Question

phinsil6

TouchOSC<--Processing OSCP5 Library Question

in Contributed Library Questions • 7 months ago

So I'm trying to send data to touch osc running on my iphone from processing with the OSCP5 Library. basically i want toggle switches and faders to stay in sync with processing says the values are. But Im having difficulties retrieving the data on the phone, or more specifically, the iphone updating. i've confirmed that with my sketch posted below, that the osc comes in correctly formatted (with the PureData basic.pd sketch provided on the website) I also get the little red light on the touchOSC (near the page slider to stand for the fact that data has been received) however the toggle swithces do not change state on the app. Does anybody have a reason as to why this is happening and how to fix it? I hope it is something simple!

Thanks!!

import oscP5.*;
import netP5.*;
OscP5 oscP5;
NetAddress Remote;
int portOutgoing = 9000;
String remoteIP = "192.168.1.131";
void setup()
{
oscP5 = new OscP5(this,8000);
Remote = new NetAddress(remoteIP,portOutgoing);
}
void draw()
{
myDelay(3000);
String labelMessage = "";
// send message to the iPad to update labels
OscMessage myMessage = new OscMessage("/1/toggle1 1");
myMessage.add(labelMessage);
println(myMessage);
oscP5.send(myMessage, Remote);
}
void myDelay(int ms)
{
try
{
Thread.sleep(ms);
}
catch(Exception e){}
}

Replies(4)

phinsil6

Re: TouchOSC<--Processing OSCP5 Library Question

7 months ago

anyone?

andreas.s..

Re: TouchOSC<--Processing OSCP5 Library Question

7 months ago

Hi,

// send message to the iPad to update labels

OscMessage myMessage = new OscMessage("/1/toggle1 1");

myMessage.add(labelMessage);

println(myMessage);

oscP5.send(myMessage, Remote);

}

line 2 in the quoted code above seems to be formatted wrongly. An OSC message consists of an address pattern (/1/toggle1 in your case), typetag (hidden), and arguments (values assigned to an address pattern).

In your case the address pattern seems to be /1/toggle1 so lets create a message with that address pattern:

OscMessage myMessage = new OscMessage("/1/toggle1");

then add value 1 to the message

myMessage.add(1);

this creates an OSC message with address pattern /1/toggle1, 1 argument with value 1, and a typetag i (oscP5 takes care of the typetage, a typetag is part of the OSC protocol, here i refers to the type of the first argument, an int).

Sending this message to touchOSC should result in a toggle change change.

oscP5.send(myMessage, Remote);

andreas schlegel, http://www.sojamo.de

phinsil6

Re: TouchOSC<--Processing OSCP5 Library Question

7 months ago

thank you very much!! this has been bothering me for a while now.

do i need to do anything differently if its a floating value or any other type of value?

andreas.s..

Re: TouchOSC<--Processing OSCP5 Library Question

7 months ago

Hi, float and int are interpreted differently with OSC, the typetag for an int is i for a float it is f. if in your case TouchOSC requires the arguments to be of a specific type only one or the other type will be accepted and hence the message will be processed or not. you can try sending a float with your message by using

myMessage.add( 1.0 );

if you want to convert a float to an int, use

myMessage.add( int( 1.0 ) );

andreas schlegel, http://www.sojamo.de

Top Reply

Statistics

4 Replies
478 Views
1 Followers

Actions

Permalink