16:9 Render Bug

Marco. wrote on 6/5/2005, 4:13 AM
I have stuff with 16:9 pixel aspect ratio in the timeline and now I gonna render this to an uncompressed AVI, again with 16:9 pixel aspect ratio. But the resulting clip does NOT have 16:9 pixel aspect ratio.

This seems only to happen when rendering to uncompressed. Rendering to DV widescreen is just fine.

This is in PAL surrounding and it happens both with Vegas 6.0b as well as with Vegas 5.0d.

Marco

Comments

Marco. wrote on 6/6/2005, 1:33 PM
Nobody else in PAL areas?

Marco
Liam_Vegas wrote on 6/6/2005, 4:11 PM
Not in PAL land... but I notice similar issues when I render to widescreen in various formats... including DV AVI with the YUV Codec as well as uncompressed.

How will you be using the rendered file? In another Vegas project or in some other program entirely?

In my case I have wanted to use this in another project... and the new Nested Vegs of V6 now makes this approach mostly unnecessary.

However... my solution... when I wanted to re-use this AVI in another project was to merely set the properties of the clip to the correct aspect ratio. The rendered file IS still in widescreen - you just have to force Vegas to realize this.

I've never used the rendered file in another tool...but hopefully it is possible to "tell" other tools the video is in a particular aspect ratio even if it thinks it is in the wrong aspect ratio (if you get what I mean).

I would consider this a bug... although.... to my shame... I have never actually reported it as a bug.
Marco. wrote on 6/6/2005, 11:30 PM
I wasn't aware of this bug at all. Somebody else reported it to me. He had the need to use the file in Canopus Procoder. But I can state what he found out after I tested a widescreen uncompressed render - and this is not a V6-only bug. At least it also happens in V5.
I will tell him what you suggested - set the properties of the uncompressed AVI coming from Vegas to widescreen pixel aspect ratio manually (but not sure if this is possible in Procoder). Thanks for this suggestion.

Anyway - I find this should have been fixed in future. I didn't report it the official way yet for I first wanted to get another user feedback. I will do later.

Marco