Image Generator / Movie Export / Aliasing Issue

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.11

How severely does this bug affect you?: 

●○○○ — Not much; I'm just letting you know about it.

Steps causing the bug to occur: 

  1. Export Movie from Image Generator Comp.
  2. Change Aliasing to 4x
  3. Rendered file is black.

Have you found a workaround?: 

I cannot export aliasing above 2x

Other notes: 

Mac Pro 2013 D500 GPU's

Play Movie URL list crash

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.11

How severely does this bug affect you?: 

●○○○ — Not much; I'm just letting you know about it.

Steps causing the bug to occur: 

Reported in 127 alpha 1 was that no finished playback event was sent, trying to cycle through a list of movies now I'm getting the finished event, but I'm getting a crash after 2 movies played or after the lists wraps at position 1 again)

Have you found a workaround?: 

No

Screenshots: 

Compositions: 

AttachmentSize
Package icon CycleVideoList.zip2.27 MB

Crash reports: 

AttachmentSize
Plain text icon CycleVideoList - Bug Report.txt67.39 KB

Vuo sends all OSC out messages 3 times.

Status: 

Vuo version: 

OS version: 

  • Mac OS 10.11

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

  1. Create any minimal setup to send OSC messages with Vuo (my example composition is attached)
  2. Open some other application to see what messages Vuo sends (I have tested with Osculator and with VDMX)
  3. All messages sent from Vuo comes 3 times to receiving application

Have you found a workaround?: 

No

Other notes: 

You can see from my screenshot, there is minimal example composition which sends one number to OSC output when screen is clicked. (There is input console of Osculator open, which shows all incoming OSC messages with time stamps. So all numbers coming from Vuo, comes 3 times with almost same time stamp. (So, before that screenshot I have clicked 3 times, but 9 messages have been sent). I have tested same with VDMX and with couple of much more complex OSC out compositions, but now I just narrowed this down to find a reason why my OSC "bus" is so full of messages.

This is annoying, but I don't know how to work around it. I have problem with too much OSC traffic which makes, my OSC receiving VDMX behave less responsive, so fixing this bug would cut the traffic to third.

Screenshots: 

Compositions: 

AttachmentSize
Binary Data VuoOscOutBug.vuo4.14 KB

Pages

Subscribe to RSS - Mac OS 10.11