Is it possible to force CNMAT odot objects to send 32bit floats instead of 64bit?

    Aug 10 2018 | 8:29 am
    I am trying to send OSC message to Reaper. I have already done this in the past using only factory objects and udpsend. Now, using CNMAT's o.prepend to add tags and printit to check the data type, it seems that I have 64bit float arguments in my OSC messages.
    In Reaper, the OSC Listen... window displays the tags correctly as well as a [d] after them but reports an "unknown argument type" afterwards. For instance: /track1/polar_distance [d] d:(unknown argument type). Obviously [d] stands for double and indeed if I discard o.prepend, I can see in Reaper that my arguments are now plain [f]loats and the error messages disappear.
    So, is there a way to force odot objects to output 32bit data or convert the data downstream without having to unbuild and rebuild all the tag stuff ?

    • Aug 10 2018 | 2:37 pm
      Got the information: o.downcast converts the data to adapt to an older OSC version (1.0/1.1) hence 64bit data are converted to 32bit.
    • Aug 10 2018 | 4:06 pm
      Nice to see someone using odot, and that it can handle this case. I’m trying to learn the ropes so I use it fluently. So many apps speak OSC now, it seems like the best way to do it.