Vuo version: 

OS version: 

  • Mac OS 10.8

Steps causing the bug to occur: 

  1. load the composition
  2. send osc
  3. crash

How did the result differ from what you expected?: 

shouldn't crash.

When did you first notice this bug?: 

happens always as soon as osc begin be streamed

Have you found a workaround?: 


Other notes: 

osc are in pixel units. Each /skeleton/0/3 message is followed by a couple of integers - pixel units.


Binary Data check testa.vuo4.18 KB

Crash reports: 

File crash.rtf48.87 KB


Thanks for the report,

smokris's picture
Submitted by
Waiting for review by Vuo Support Team
Waiting for more information from reporter

Thanks for the report, mic. We've already found and fixed a few OSC-related crashes for the upcoming Vuo 0.9.0 release.

Which software are you using to send these OSC messages? (From the crash report you sent, it looks like it might be sending corrupt messages.)

Hi, it's a custom software

cremaschi's picture
Submitted by

Hi, it's a custom software called ofxKinect2ProjectorCalibration. Quartz Composer qcOSC receiver does not crash, but does not receive anything. Osculator receives - so i use this as a bridge.

Could be that the problem is due to the fact osc values are 0..1280 ?

I don't think that would be

smokris's picture
Submitted by

I don't think that would be the problem; I've tested Vuo's OSC receiver with full 32-bit and 64-bit integer values, and 32-bit floats.

Could you try receiving ofxKinect2ProjectorCalibration's data with OSC Monitor or another OSC logging app, and paste the output (or a screenshot) here? (It would be helpful to see the exact data format.)