Status: 

Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. Start Vuo
  2. Build some Composition with vuo.osc.receive2 node
  3. Put computer to sleep
  4. Wake computer
  5. Start a composition

Have you found a workaround?: 

Quitting Vuo and opening it again causes the composition to receive OSC messages normally.

Other notes: 

When problem occurs Vuo outputs in console: listenForMessages():315 Unknown OSC exception

Comments

Teo, thanks for letting us

jstrecker's picture
Submitted by
Status:
Waiting for review by Vuo Support Team
»
Waiting for more information from reporter

Teo, thanks for letting us know about this problem. So far, we haven't been able to reproduce it or figure out why it's happening.

However, between Vuo 2.0.0-beta4 and Vuo 2.0.0 we improved the error reporting a bit for OSC, so now it might say something more descriptive than "unknown OSC exception". When convenient, could you check the console message that you get with Vuo 2.0.0?

I'm not sure it's related but

dumski's picture
Submitted by

I'm not sure it's related but sometimes I see a message from macOS, that my hostname is already taken and it needs to pick a new hostname for my machine. It happens only sometimes after computer sleep when Vuo Editor is running. But the the problem with OSC described in the bug report is happening after every sleep with Vuo Editor opened (even if it doesn't run any composition).

Also, when the problem occurs it prevents only OSC subsystem of the composition from work (composition is running but cannot receive OSC messages) and console keeps outputting the error, also draining a lot of CPU power.