actually I’m sending this data already form my own external… the issue is, Im sending the screen lines out by sending to screenLine1 , which then gets manipulated via PD… and has to be processes by packOSC.
(so that means packOSC needs to know how to translate the messages)
I actually had solved the issue using null symbols, but ive tripped over a bug in the OSC handling in mother host, basically
oscsend localhost 4001 /oled/line/1 sss "mix" "" "10.2"
here I’m using a null symbol to generate a space, and it works EXCEPT bizarrely when the first symbol is 3 characters, at which point the osc parser, gets confused by the empty string, and scrambles the subsequent symbols, so gets displayed at mix 0.2 !!!
if its 2 4, 5,6 it works, just not 3… also if the next character is not a null it works too.
so this work fine
oscsend localhost 4001 /oled/line/1 sssssss "depth" "" "" "" "" "" "" "5.2"
so im a bit caught up, I can work around it in PD, but then setScreenLine in mother host trips me up…
anyway, Im starting to think this is not the correct approach… I think I’ll actually just connect my external directly to the mother host osc port, and bypass PD/mother.pd altogether… this will allow me direct access to the new graphics primates too
anyway, good news is the new formatting does look really nice… so once over this hiccup I’m going to be pretty happy with it.