Can't get Vegas to render in progressive...?

ZapRowsdower wrote on 5/12/2015, 11:01 AM
Hi there, having a real issue getting Vegas to render progressive. My source is a variety of GoPro footage captured in 30p, 48p, and 60p. Regardless of the output settings in Vegas, the renders are always interlaced.

Actually, the rendered files ARE progressive, but they're rendered interlaced. Here's an example, 48p source:

48p

And the output:
Output


Here's the project properties:
Project Properties
And the render properties:
Render template

Same thing happens regardless of 30p or 60p output. Again, the resulting renders are progressive, but are obviously rendered internally as interlaced.

Would love some suggestions on what I'm doing wrong. I've googled to no end and can't find any suggestions.

FWIW this is Vegas 9.0b. (Old, I know, but still functional... mostly.)

Comments

larry-peter wrote on 5/12/2015, 11:11 AM
It's not interlacing, but frame blending. You have three ghosted images in your example, not two.
Two things to check - first uncheck "allow source to adjust frame rate" in your render template. In many templates, I've found that will reduce the render to 1/2 the intended frame rate.
Second, did you begin your timeline with Quantize to Frames turned on in the Options menu? If not, you will always get ghosted frames if resampling is not disabled in the clip properties. If Quantize to Frames is off, you will have to turn it on, and then slightly move each of your clips on the timeline to allow them to snap to frame boundaries.
Check those and let us know.

Edit - I've only worked with GoPro footage at 60i (actually 29.97) so I could be mistaken her, but I would also suggest you check your footage with Media Info to see the precise frame rate. I would be surprised if it's not a fractional number, i.e. 23.976, 29.97, etc. rather than an exact 48 fps. This would only explain your results if combined with one of the above issues unless your clip is VERY long, but even a fractional fps difference will cause ghosting after a few minutes if resampling is on.
musicvid10 wrote on 5/12/2015, 12:18 PM
In addition to the excellent advice, render at Best, not Good quality.
ZapRowsdower wrote on 5/12/2015, 12:20 PM
That was it! Quantize was enabled, but it was indeed a difference between the actual frame rate in the source and the output settings. Turns out it's 50fps, not 48, which is interesting. I re-rendered at 50 and it's clear as the source.

Thank you so much! That makes my day.

Is there any way to get the output to default to the input frame rate? I tried creating a 720p30 output profile with the "allow source..." box checked, but the resulting file was 30p, not 50p.
larry-peter wrote on 5/12/2015, 4:12 PM
I haven't found a way, but I haven't tried too hard because when I get burned once, I don't trust the checkbox anymore. Some of the render templates may work fine, but MC AVC/AAC and Quicktime have both burned me by rendering to incorrect frame rates (usually half, if the fps matches the project AND the checkbox is checked).

I recommend learning to love MediaInfo and use it liberally for matching project settings to your footage (if you don't have VP11 or newer) and checking renders.
ZapRowsdower wrote on 5/14/2015, 7:53 PM
Will do. Thanks again!