Hey all,

Have what is hopefully a fairly simple enquiry. I am using OSC to connect an encoder to pure data on a raspberry pi. I have an incoming message, and would like to use this to set a slider value. In Max/MSP I do this all the time, but googling/looking through these forums there doesn't seem to be a straightforward way to do so. Does anyone have any advice? Appreciated

@dmanz You should set the slider range to match your incoming data.... the min and max values you expect to receive (in the properties of the slider.... right-click the slider and select properties).
Then just connect the output of [route encoderOne] to the slider.
David.

I get the error "hsl: no method for "10"" - basically I need to convert the incoming message to an int. In Max, this is really easy - what is the standard method for doing so in pure data?

It's strange the [print] doesn't display the quotes if they are present in the output of [route].
Can you add a [print income] after [netreceive] in order we see if the message is clear?

FYI this patch works great

Mabye

[symbol]
|
[float]

does the trick?

Pobably it is not encoded as float but neither has no symbol selector.
A symbol without 'symbol' selector looks like a float but isn't.

(btw there is [int] but ints are floats in pd)

@FFW The data might be arriving as symbols.
@dmanz One thing to try is replacing [list route] with [list trim] in your OP.
Also [rawprint] is a useful object for message analysis and can be found via Help/Find externals in the Pd top menu..
It will tell you whether atoms are floats or symols.

Once we know what the problem is it can probably be solved.
If the encoder is sending the value as part of the header (preceded by a backslash) then it will be a symbol (an OSC message header .... the "route" is made of backslash separated symbols).
David.

@dmanz could you print the raw netreceive output, before oscparse? They will appear as lists of bytes -- that would confirm what is the type tag for the number, and how the number is being represented.

It's all guesswork without knowing that.

hjh

Hey all - thank you for the help and advice. The solution was the

[symbol]
|
[float]

combo that @lacuna suggested. rawprint is great to know for future debugging.

Dan

Perhaps you don't even need [symbol]. You can give the patch a try without it, it might work.

@dmanz said:

I get the error "hsl: no method for "10"" - basically I need to convert the incoming message to an int. In Max, this is really easy - what is the standard method for doing so in pure data?

Have a look at the '-n' flag

I think this is what you need

There were other hacks to turn it into a symbol, but this was just a bug that needed fixing. But in order to keep backwards compatibility, I added this new '-n' flag to the object, and it was included in Pd 0.55-0

I guess it all begs the question though: Why is the rpi program sending numbers as strings?

hjh