I really want to use VideOSC+ with my work.

Yet when my desktop receives the stream, it throws a "64-bit numbers not supported error.

Ie. starting with which version of PD (most esp which Linux kernel (or Ubuntu version) does this become "supported"?

Thnx.

-S

This is dependant on the pd external and has nothing to do with the OS or the kernel version. 64 bit numbers (double & long) are optional in the OSC 1.0 standard, so not every library implements this. I'm not sure if there is one for pd that supports the data type you need, the osc library by mrpeach doesn't document the version and subset of OSC it supports as far as I can tell, unfortunately.

@meschi Thank you for the info. Very valuable to know.

Still couldn't get what I wanted to work (i.e. resolve the 64-bit not implemented issue).

And have had to cut my losses and pursue a different route for what I want.

Am going to leave it at using proximity detectors instead.

Peace through sharing. Love thru Music.

Thanks, again.
-s

There's an experimental 64-bit version of Pd. Check its download page https://puredata.info/downloads/pure-data/releases/0.54-1-pd64

@alexandros

Thank you very much for the lead. Will look into it. Much appreciated.

-s

There's an experimental 64-bit version of Pd

This is really orthogonal to 64-bit OSC timetags. This version just uses 64-bit floats as the underlying type for float atoms and samples. It does not magically implement the missing OSC typetags. Also, let's please call this the "double-precision" version, as "64-bit" typically refers to the CPU architecture.

Actually, there is no reason why Pd's [oscformat] and [oscparse] could not support the h (= int64) and d (= float64) typetags for sending/parsing OSC message. Of course, single-precision Pd would need to round the values down to 32-bit floats, but double-precision Pd could keep the precision (at least for 64-bit floats; 64-bit integers may still lose some lower bits when converted to 64-bit float atoms).