Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Weird stripes after rendering with Sony vegas10pro – MPEG Streamclip (v.1.2.1b5)

  • John Bean

    March 1, 2012 at 6:41 pm

    Do you see interlace artifacts in your Vegas real-time PREVIEW window?

    If so, Vegas has not interpreted your source media file correctly.

    If this is the case, then when you render out your video as interlaced, Vegas is rendering an interlace video of an incorrectly deinterlaced source video. So, it’s like you are increasing the interlacing factor 2x!

    That is why the interlace artifacts in your render video looks terrible!

    Like I stated, when *editing*, Vegas will automatically deinterlace your interlace videos – regardless of what your DEINTERLACE METHOD project setting is.

    This is because it doesn’t make sense to edit the upper and lower fields of an interlace video separately. You edit the FULL FRAME, hence, Vegas automatically deinterlaces it for you when editing.

    So if there are glaring interlace artifacts in your real-time Vegas PREVIEW WINDOW, then some setting is wrong.

    How-to verify that Vegas has interpreted your source media properly:

    Right click your source media file on the track and go to “Properties”. This will bring up the source’s MEDIA PROPERTIES. Verify that Vegas has interpreted your source media scan type as UPPER FIELD. Also verify that the source media’s FRAME RATE is correct and matches your project setting’s frame rate.

    If you are unsure of your source media type information, you can use an external app like GSpot or MediaInfo to see what it says about source media type. Then verify that Vegas has interpreted it properly to match.

    Again the two fields to check are:
    1. SCAN TYPE
    2. FRAME RATE

    Post a picture of your source media properties information if you want us to verify.

    YOU CAN ALSO TRY THIS:

    1. In PROJECT SETTINGS, change your setting for SCAN TYPE to PROGRESSIVE (None).
    2. Then render out a PROGRESSIVE video.

    If you still see interlace artifacts then Vegas has definitely interpreted your source media file incorrectly.

  • John Bean

    March 1, 2012 at 8:50 pm

    I just noticed that your picture contains your PREVIEW WINDOW.

    The interlace artifacts there strongly suggests that Vegas has not interpreted your source media’s SCAN TYPE correctly.

    Just try this out. Open up the MEDIA PROPERTIES for source media. Under the VIDEO tab you should see SCAN-TYPE options. There are only 3 options: UPPER, LOWER, and None (Progressive).

    Change your scan-type until you find the one that does not give you the interlace artifacts you see in your preview window.

  • Vitalijus Ramanauskas

    March 2, 2012 at 6:47 am

    And it finally succeeded.
    There is link: https://www.youtube.com/watch?v=zcv7JhX6LTE&feature=related

    And thanks John Bean . For my project in the picture, I found best settings and lines disappear in PREVIEW WINDOW :
    Field order : NONE (progressive scan), Deinterlace method : INTERPOLATE FIELDS

    But I have another question :
    Render as- Save as type- MainConcept AVC/ AAC (.mp4)- Custom settings- Constant bit rate (bps): 768,000 v.s. Variable bit rate (maximum (bps) ? and Average (bps) ? WHAT is it ? What should be the numbers 190,000 ………… 240,000,000 ? What settings are best ?
    Thanks again !

  • John Bean

    March 2, 2012 at 10:28 pm

    Variable Bit Rate vs Constant Bit Rate

    variable – the bit rate can vary around the target median bit rate you have set

    constant – the bit rate remains constant through out the video

    It really just depends on the quality of your video and where the video is going to be stored (uploaded) to.

    If your source videos are all of very high bit-rate, similar or equal in value, then a constant bit rate might be a good choice. For example, say all of your source videos are around 25 Mb/s. Then you might want to use a constant bit rate of 25 Mb/s.

    If your source videos are all of varying bit-rates, or your final composition contains a lot of frames of varying bit-rates, then the variable bit-rate setting may be a good choice here.

    A variable bit-rate will allow frames that have a lot of information (ie. action, movement, effects, etc.) to have a higher bit-rate by *taking* bit-rates away from frames with less information, so that the target MEDIAN bit-rate you selected is maintained throughout your video.

    The other consideration is storage of your video. A variable bit-rate can potentially in most cases lead to smaller bandwidth (storage) requirements. Frames that have very little information (like black frames) will not require a lot of bandwidth. But if you chosen constant bit rate, then every frame in your video will be encoded at that constant bit rate even if it is not necessary to do (like on black frames).

    Those are probably to the two main things to take into consideration.

    For most cases, VARIABLE BIT RATE is the best choice.

  • John Bean

    March 2, 2012 at 10:37 pm

    So your MEDIA PROPERTIES for your source video has a SCAN-TYPE field order of NONE (Progressive)?

    Then, why do you need to set the DEINTERLACE METHOD to INTERPOLATE?

    If your source video is PROGRESSIVE (None), then the DEINTERLACE METHOD can be left at NONE. It doesn’t matter what you set the DEINTERLACE METHOD two because your a PROGRESSIVE video does not need deinterlacing.

    Or perhaps, you mean you changed the PROJECT SETTING Field Order to NONE?

  • Vitalijus Ramanauskas

    March 3, 2012 at 7:02 am

    Thankyou Joahn…

Page 2 of 2

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