Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • OS X 10.9

How severely does this bug affect you?: 

●●●● — It prevents me from using Vuo at all.

Steps causing the bug to occur: 

  1. Use decode movie image to playback 30p video file in Image Generator Protocol
  2. Render out movie to file from export menu making sure to select 30p and no motion blur (we want same frames in and out-for example resizing movie files etc)
  3. Resultant movie is not smooth, jitters, putting:
floor(time * 30)/30

between image generator time & frame number of decode movie does not help jittered frames

Have you found a workaround?: 

YUP, VUO 1.2.0 does not have this bug. (But that isn't a workaround in Vuo 1.2.2)

Other notes: 

I think this may be because currently decode movie image uses frame time to serve the closest frame, and if the time value does not spit out a number close enough to the framerate of the video it misses a frame.

Would there be a way for the value of time within image generator to be quantised to a framerate? Or in Render Movie settings to change that framerate quantisation?

Here is a test with frame number and timecode before exporting from Vuo: https://youtu.be/HmN3tjFV6pA

Here is the output of decode movie image rendering the above file, set to 30p: https://youtu.be/1sDg74HH_FE

Here is the same output test, this time setting motion blur to 180º and 8 times temporal oversampling: https://youtu.be/D7DRE1TohLo

Here is the same output test, this time setting motion blur to 180º and 64 times temporal oversampling: https://www.youtube.com/watch?v=pwamalLh-nM

Also note that all Vuo processed videos loose the first frame (frame 0) as well as many other dropped frames.

UPDATE: Vuo 1.2.0 does NOT exhibit this behaviour, all frames a there. (apart from frame 0, which is also a bug): https://youtu.be/OrlCW-zt2mk

Screenshots: 

Comments