rss  subscribe to rss feed     facebook  facebook     twitter  twitter     vimeo  vimeo   
cineform tech blog masthead

Progressive AVIs in Sony Vegas Pro

Using progressive 1080p images in Sony Vegas Pro does not always give you the high resolution results that you may have expected.  This is due to the AVI defaults within Vegas that assumes all HD sources are Upper Field first interlaced. Vegas then deinterlaces the image to be compatible with the progressive project — resulting in the loss of your vertical resolution.

vegasprogThe simple solution is to right click on the imported clip and bring up the properties panel, changing the “Field Order” to progressive.  This works fine, yet you have to do for every clip manually.  To make these change occur for every new imported clip, bring the first clip into the project, setting the properties to progressive and then click on the “Save Settings” icon before closing the properties panel.  Each new imported clip that shares the properties of the first (resolution and frame rate) will automatically receive the corrected settings. Your full resolution is now preserved.

Tags: , , , , , , , ,

3 Responses to “Progressive AVIs in Sony Vegas Pro”

  1. July 7th, 2009 at 8:43 pm

    Eugenia's Rants and Thoughts » Blog Archive » Exporting with Vegas for Vimeo HD says:

    [...] footage onto Vegas, it should be recognized by Vegas as 23.976 fps, fully progressive. If not, look here for a [...]

  2. March 14th, 2010 at 7:24 pm

    Eugenia's Rants and Thoughts » Blog Archive » Starting up with a dSLR and Sony Vegas says:

    [...] for field order, it’s up to you to instruct Vegas what kind of files these are. So, follow the tip on how to do that. When you do that, come back read the rest [...]

  3. May 15th, 2010 at 1:09 pm

    Eugenia's Rants and Thoughts » Blog Archive » Intermediate Usage of the Matrox MPEG-2 I-Frame HD Codec says:

    [...] 3: If Vegas thinks that your progressive footage is interlaced, then use this trick to make it think otherwise. 3 Comments » William Eggington wrote on May 15th, 2010 at [...]

Leave a Reply

You must be logged in to post a comment.