Heya

It's critical that I be able to keep the .0 in my floats, but pd seems to drop them if I send it through anything. How can I prevent this?

My patch:

[6.0 7.0(
|
|
[send /any $1 $2(
|
|
[packOSC]
|
|
[udpsend]

If I connect a [print] after [send /any $1 $2(, I can see that the .0's have been dropped from my original message.

Same thing happens if I connect [6.0 7.0( straight to the [print] object.

A float is a float, so 1.0 is the same as 1. If you need to keep the .0, you'll have to do some manipulation using something like [makefilename %d.0]. But that will convert it to a symbol, not a float. If possible, it might be better to test if the incoming float is equal to its int version in the software that is receiving the OSC message.

Thanks Maelstorm! I needed the .0 because the data is being sent to Processing, and a bare 1 is recognized as an int (which triggers a failure).

I may just seperate the int's from floats in pd and send them with different typetags to processing, and from there convert the ints to float using float().

You should be able to force the type using the [sendtyped( message.