Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Proper Pulldown Method? or is this a bug. Vegas 12 pro

  • Proper Pulldown Method? or is this a bug. Vegas 12 pro

    Posted by Brad Leigh on January 26, 2013 at 5:35 pm

    Good morning!
    As posted before, I have some animation codec renders that were rendered at 30fps in error. The renders took days so I am salvaging them by selecting Playback rate .999 resample off. Vegas runs smooth image looks great and renders smooth. BUT somtimes the event will look like double vision in the preview window from the time line even though it is crisp in the trimmer window. It seems if I do any editing to the event before setting the playback rate I get this blur. I’ll have to delete the event and replace in the timeline. But sometimes even this doesn’t work. the preview window is always blurred with a particular clip.
    1) Snap is on
    2) It seems to render fine.
    3) Does not seem to be interlacing issue because there are no horizontal artifacts just full faint double image.
    4) Preview device ” Deinterlace filter” is on
    5) Preview device set “Best Full” on external 1920×1080 computer monitor fed from 2nd DVI port on video card GT420.
    6)GPU is set off. ram preview set 256 but I don’t use it because I am getting rock solid 29.97 fps.
    7) no effects, no plug ins installed except New Blue titler ( not used), edit is just crossfades and titles using the sony text generator.
    Vegas Pro 12 (not at that computer so I do not have build number)
    Any Ideas?
    Thank You in advance
    Brad

    i7 2600 3.4 Ghz 8Gig Ram , Win 7 Pro, Vegas Pro 12

    John Rofrano replied 13 years, 3 months ago 2 Members · 5 Replies
  • 5 Replies
  • John Rofrano

    January 26, 2013 at 5:57 pm

    [Brad Leigh] “1) Snap is on”

    Is Options | Quantize to Frames Alt+F8 ON (i.e., checked)? Maybe you are looking between frames.

    ~jr

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

  • Brad Leigh

    January 26, 2013 at 6:24 pm

    John
    As the embarrassment washes over me. I’ve been working to many hours.
    I usually work in Audio software and Carrara where I think of “snap” as to “frame”
    ie Frames. So you are correct when I said snap I was thinking wrong. I never remember turning off Quantize, but I may have to slide an audio event.
    I assume the only way to check is too zoom in and look at each event.
    I’ll check it when I get back to my office.
    Another V-8 moment!
    Many Many Thanks again.
    Brad

    i7 2600 3.4 Ghz 8Gig Ram , Win 7 Pro, Vegas Pro 12

  • John Rofrano

    January 26, 2013 at 7:03 pm

    In recent versions of Vegas Pro there is no need to ever turn off quantize to frames because it doesn’t affect music or other audio that’s not part of a video stream. It only affects video and audio that is part of a video file and I can’t think of any instance where you would not want to quantize video to frames since the frame is the smallest increment of video (not counting fields).

    ~jr

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

  • Brad Leigh

    January 26, 2013 at 9:19 pm

    John
    Thanks for the tip of not needing to turn that off for audio only events.
    I checked my settings Quantize was on. Looked at all frame boundries. All looked dead on the frame. Noticed that this only appears on the external preview monitor on a certain clip. It is clean in the vegas software Preview window. It has happened before but I thought it was the 30 vs 29.97 issue.
    Further Investigation revealed it was only on any external preview device. I switched the project setting to Progressive and the problem went away. Project was set as interlaced because I intend to insert HDV footage. But I’ll try to insert some interlaced footage and see how that responds.
    Thank You again for your help.
    Brad

    i7 2600 3.4 Ghz 8Gig Ram , Win 7 Pro, Vegas Pro 12

  • John Rofrano

    January 27, 2013 at 1:56 pm

    I can’t imagine what’s causing it other than a possible bug. Let us know how you make out.

    ~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