ckckck

 objects only accepts 32-bit integers – anything larger and it wraps around.

These 2 objects however are fine with processing and generating 64-bit ints internally, and sending 64-bit ints via the outlets.

On a sidenote, the integer and message objects also seem to handle 64-bit integers differently, I'm assuming the integer object uses the MSB as the signing bit.

Please check the quick test patch below that demonstrates the issues.

At this point my only workaround is to send 64-bit ints to 

 objects as string literals. My question is: does anyone know from experience if this impacts performance? I'd rather stick with integers throughout. Any suggestions most appreciated.

I noticed that the jstrigger and js objects only accepts 32-bit integers – anything larger and it wraps around.

At this point my only workaround is to send 64-bit ints to jstrigger and js objects as string literals. My question is: does anyone know from experience if this impacts performance? I'd rather stick with integers throughout. Any suggestions most appreciated.

Sending 32-bit / 64-bit ints to js / jstrigger