You are sending an INT? Not a Bool?
Can you guys please read the OSC spec? Specifically the types tables? Example:
OSC Type Tag, Type of corresponding argument
i int32
f float32
s OSC-string
b OSC-blob
h 64 bit big-endian two's complement integer
t OSC-timetag
d 64 bit ("double") IEEE 754 floating point number
S Alternate type represented as an OSC-string (for example, for systems that differentiate "symbols" from "strings")
c an ascii character, sent as 32 bits
r 32 bit RGBA color
m 4 byte MIDI message. Bytes from MSB to LSB are: port id, status byte, data1, data2
T True. No bytes are allocated in the argument data.
F False. No bytes are allocated in the argument data.
N Nil. No bytes are allocated in the argument data.
I Infinitum. No bytes are allocated in the argument data.
[ Indicates the beginning of an array. The tags following are for data in the Array until a close brace tag is reached.
] Indicates the end of an array.
So let’s take a bool, in Renoise Lua semantics, this works:
client:send(
renoise.Osc.Message("/renoise/transport/loop/block", {
{tag="T", value=1}
})
)
client:send(
renoise.Osc.Message("/renoise/transport/loop/block", {
{tag="F", value=1}
})
)
This doesn’t:
client:send(
renoise.Osc.Message("/renoise/transport/loop/block", {
{tag="i", value=1}
})
)
client:send(
renoise.Osc.Message("/renoise/transport/loop/block", {
{tag="i", value=0}
})
)
Pay special attention to the TAG flag in the examples above. Find the equivilant in your PD or OSCTouch or whatever.
Finally, if you want more info than REJECTED, you can extend the GlobalOscActions.lua file. As described in the file, extend it in your local user space. From there, override the process_message() function and add the debug info you want.