Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas Pro 8 refuses to deinterlace

  • Vegas Pro 8 refuses to deinterlace

    Posted by Ian Smith on July 19, 2008 at 8:01 am

    I’ve got a device that records video at 640×480@30fps in XviD
    format at high bitrates (8-12Mb/s) with interlacing.
    Desired Rendered formats are all for playback on computers
    thus need to deinterlace.

    I am able to open and deinterlace these files in Virtualdub
    using its own native deinterlace filter, or commercial
    Alparysoft Deinterlace filter also via Virtualdub.

    I’d like to save myself the extra rendering step though, and
    bring em straight into Vegas Pro 8 for some simpler content.
    Vegas will read the XviD formatted AVI files, but as far as
    I can tell *refuses* to deinterlace. I’ve been through the
    manual, and the help, and about a half dozen discussions on
    the net, and the consensus of all is that the following
    settings should do the trick:
    1. Project Properties – Field Order: None (Progressive scan)
    2. Project Properties – Deinterlace method: Blend or Interpolate (depending on content)
    3. In Render template, Custom settings ensure that Field Order is None (Progressive..) where applicable (WMV
    assumes Progressive output for instance).

    1 and 2 should control what is seen in Timeline Preview window (when set to Good or Best)
    and 2 and 3 should control actual Rendering.

    The problem is, it doesn’t appear to do anything at all, anywhere,
    ever. I know what Blend should look like. What I see in
    Preview area is identical to raw input video.
    What I see when I render to uncompressed AVI is also identical to
    raw input video. I have never seen the deinterlace settings
    have the *slightest* effect on anything anywhere.
    I’ve tried converting input XviD files to uncompressed AVI
    first, with no change. I’ve rendered output to AVI, WMV,
    etc, no difference. All of them come out, still interlaced,
    visually indistinguishable from the input.

    Am I missing something obvious? Is there an undocumented
    combination of size/framerate/filetype that simply can’t be
    deinterlaced?

    ian

    Ian Smith replied 17 years, 10 months ago 2 Members · 2 Replies
  • 2 Replies

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