Ken Burns Effect Follow-Up

[John Rofrano]

That’s really strange. I saw it right away. It looks like a rendering error. Does this happen regardless of the render format that you use? If it does, then it’s probably something in the project. If it doesn’t, it may have to do with the render format.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Terry Fein]

I will check it out tonight. One thing I did notice is that I have been rendering in a custom format of 1620 x 1080 (in order to maintain the 1.5 to 1 aspect ratio my camera uses), but Vimeo is indicating the size as 1632 x 1080.

[Scott Francis]

Are you using track motion or pan/crop for the effect? Do you have any other f/x on? And just like John, what is your native format and render format? I had some weird things like this going from m2t to MP4 and changing the output size….

Scott Francis
Mind’s Eye Audio/Video Productions

[John Rofrano]

[Terry Fein] “One thing I did notice is that I have been rendering in a custom format of 1620 x 1080 (in order to maintain the 1.5 to 1 aspect ratio my camera uses), but Vimeo is indicating the size as 1632 x 1080.”

Well, there’s your problem right there. The distortion you are seeing is the difference between your 1620 video and the 1632 that is on Vimeo. If the original video shows this problem then the issue is with the original codec. If only Vimeo shows this problem, then the issues is with the codec that Vimeo uses to encode. Either way it is just copying the last 12 bytes of video off to the right. This is exactly what you’re seeing.

If I were you, I would stick with industry standard resolutions. 1920×1080 is the HD standard. If you must define your own resolution then it must conform to the specifications of the codec that Vegas and/or Vimeo are using to encode your video file. It looks to me like the codec only accepts widths that are a multiple of 16. Since 16 does not divide evenly into 1620 it had to use 1632 which is the next highest multiple of 16. All it could do is duplicate the pixels from 1620 to 1632. So you caused this problem by not using a resolution that was divisible by 16.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Terry Fein]

Many thanks. I will play around with it tonight. I will use the standard resolution if nothing else works. Interestingly, I get the same effect playing the original mp4 file locally.

[John Rofrano]

[Terry Fein] ” Interestingly, I get the same effect playing the original mp4 file locally.”

So that means that the codec you used in Vegas requires a resolution width in a multiple of 16. That’s all you need to do to fix this.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Dave Haynie]

That’s your problem right there. Rendering to any DCT type compression format (MPEG-2, AVC, VC-1, VP8, etc) is inherently in multiples of some block size, usually 16×16 pixels, though it varies by format.

When you render to 1620 pixels, you have 101 DCT blocks and 4 pixels left over. In the old days, the rendering program would more than likely just reject the 1620 size. Later on, it might have put a black bar there, but these days the standard procedure is to just replicate the extra pixels… that leads to the best compression of the “fractional” DCT block. So that’s what you see, your 1620 being extended to 1632 by pixel replication.

It’s also common for a rendered format to include metadata for a mask, so you don’t see that stuff. The 1920×1080 HD format is actually rendered at 1920×1088.. this allows not just the multiple-of-16 you want for 1080p, but the multiple-of-32 boundary needed for MPEG-2 in interlaced video. Every HD player knows to truncate those extra pixels. But I don’t know offhand if horizontal masking is commonly supported… but certainly, Vimeo is not seeing that mask.

Incidently, I love doing the “Ken Burns” style from stills too… here’s one of my better ones, made from some of my Dad’s best photography:

https://www.youtube.com/watch?v=uQGf7xjWc4E

-Dave

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Terry Fein]

Problem solved. I rendered a small portion of the video using a resolution of 1616 x 1080, and uploaded it to Vimeo. (For pictures, I prefer this resolution to 1920 x 1080, because the pictures were composed based on the aspect ratio used by the camera.) It’s playing properly both locally and on Vimeo. Thanks for the responses and suggestions. I never could have figured this out on my own.

Terry