Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Interlacing Artifacts Rendering to DV Sony Vegas

  • Interlacing Artifacts Rendering to DV Sony Vegas

    Posted by John Simmons on November 27, 2011 at 1:49 pm

    Hi, I have noticed that after rendering my footage to DV there are interlacing artifacts that aren’t there in the original footage. They are small lines that flicker randomly. Here’s an example screenshot:

    I have set the correct project settings and used the Match Media Settings first, Pal DV Widescreen, 25fps, Lower Field First and the De-interlacing Method set to None. The video is recompressed because of colour correction etc. With the filters deselected the video preview displays No Recompression. I have tested each filter to see if one of those is the problem but every filter gives the same result. I have kept the default settings to render to DV (Interleave Every 0.250 Seconds etc.)

    The footage is Sony PAL-DV Widescreen, I’m using Sony Vegas Pro 10. Is there a known issue and a fix or do I need to render to another format?

    Thank you

    John Simmons

    John Rofrano replied 14 years, 5 months ago 3 Members · 8 Replies
  • 8 Replies
  • John Rofrano

    November 27, 2011 at 5:21 pm

    [John Simmons] “I have set the correct project settings and used the Match Media Settings first, Pal DV Widescreen, 25fps, Lower Field First and the De-interlacing Method set to None. “

    That is not correct. NEVER set your Deinterlace Method to NONE if you are using interlaced video!

    Change your deinterlace method back to the default which is Blend Fields and your problems will go away.

    ~jr

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

  • John Simmons

    November 27, 2011 at 11:13 pm

    Hello John, thanks for helping me again. I thought that setting was for deinterlacing your output turning it into progressive 25fps, that’s why I left it at None. I have tested the clip with the Deinterlace Method set to Blend Fields and Interpolate Fileds and I’m still getting the same problem.

    John Simmons

  • Nigel O’neill

    November 28, 2011 at 2:49 am

    [John Rofrano] “Change your deinterlace method back to the default which is Blend Fields and your problems will go away.”

    John, there must be a difference in the default PAL project properties template. Out of the box, mine defaults to NONE. This has also happened to other editors I work with in PAL-land.

    My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • John Rofrano

    November 28, 2011 at 11:53 am

    [Nigel O'Neill] “John, there must be a difference in the default PAL project properties template. Out of the box, mine defaults to NONE. This has also happened to other editors I work with in PAL-land.”

    Hmmm… How do you think Vegas determines if it’s in”PAL-land?”. My experience is that Vegas doesn’t even default to PAL. It defaults to NTSC which means people in PAL countries have to make the change to PAL manually and save it as their default preference.

    The Deinterlace Method is totally separate from the project properties and does not get saved as part of the template. It simply stays at whatever you change it to but it always starts out as Blend Fields when first installed.

    If you don’t believe me, you can reset Vegas back to the day it was installed by holding the Ctrl+Shift keys when you start it and you’ll see that it will revert back to Blend Fields. This will also wipe out any preferences you have so I wouldn’t advise doing it but the point remains. Blend Fields is the default.

    ~jr

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

  • John Rofrano

    November 28, 2011 at 11:55 am

    [John Simmons] ” I thought that setting was for deinterlacing your output turning it into progressive 25fps, that’s why I left it at None.”

    No. That field is to tell Vegas which method it should use to deinterlace footage if it ever has to do internal deinterlacing to apply FX. It does not deinterlace your video. It’s actually for preserving interlacing correctly.

    [John Simmons] ” I have tested the clip with the Deinterlace Method set to Blend Fields and Interpolate Fileds and I’m still getting the same problem.”

    OK, make sure you have your project set to Blend Fields. Next, right-click on a video event with your DV footage, select Properties and look on the Media tab and tell me what Field Order Vegas is using for your footage?

    ~jr

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

  • Nigel O’neill

    November 28, 2011 at 12:01 pm

    John

    I am not disputing your expertise. Out of the box, Vegas does indeed default to NTSC and when I select the PAL template, I have to change the deinterlace method from none to blend. It does this on every single installation I have done.

    My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

  • John Simmons

    November 28, 2011 at 1:03 pm

    It is using Lower field first. I rendered to Mainconcept AVC as a test and there was no artifacts. It seems to just be when I render to DV. I have found a solution though, https://www.bubblevision.com/underwater-video/Vegas-YouTube-Vimeo.htm This is something I wondered if it was possible when I started using Vegas, using Avisynth instead so i’m very happy i’ve found it now to eliminate this problem. I will now use Blend fields on interlaced material.

    Thank you

    John Simmons

  • John Rofrano

    November 28, 2011 at 2:03 pm

    [Nigel O'Neill] “I am not disputing your expertise. Out of the box, Vegas does indeed default to NTSC and when I select the PAL template, I have to change the deinterlace method from none to blend. It does this on every single installation I have done.”

    That’s really odd because I have not seen that behavior. I regularly work on fresh installations of Vegas while testing VASST software products and I’ve never seen Vegas default to none. Perhaps it is triggering off of a country code in Windows? I can reproduce that behavior on any of my test systems.

    Are you using a special version of Windows, or just an English version with the country code changed? If so, what do you change in Windows to make it “PAL” specific? I’d like to see this for myself.

    ~jr

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

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy