Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas Render Oddities

  • Vegas Render Oddities

    Posted by Sam Nicholls on September 16, 2010 at 8:25 pm

    Hi all,
    Have been having problems with Sony Vegas Pro 9(a) over the past week.
    I have a large project (Around 1hr 47m) with M2T files from a Sony Z7E.

    Firstly, it had problems capturing the audio on the tape, causing the audio in the captured tracks to drop on a random basis (Audio on the tape is all present).

    Once it was established I would just have to find a way to get around this, I found that Vegas would simply stop playing audio despite a wave clearly being present in the tracks – I hadn’t made any changes to settings or even applied any envelopes/FX.

    To get around this, I had to import all the audio to different software and export it as a HQ .wav

    Finally, and the problem I’m here to ask about – The video is comprised of two tracks from two cameras at different angles with simple jump cuts between the two.

    In the track, it was cutting from Camera A to Camera B fine.
    However, when the video rendered, it would cut from Camera A, to Camera B, but minutes earlier, as if all the video had timeshifted.

    Now and again, frames would freeze for a few seconds, also from the wrong timecode of a track.

    The annoying part is the error isn’t consistant, another render had this occur in different places and when I rendered the “damaged segements” on their own, they came out fine.

    My final solution was to render the entire video, look through it for “damaged” clips, render those out seperately (All with same template) and drop those on top – Thus having the final video without the need for recompression. Long winded, and frustrating.

    Has anyone had previous experience with this? Does Vegas just dislike long videos? Should I look at capturing with other software instead of Vegas? Any thoughts appreciated and hope my post makes sense.

    Cheers,
    Sam.

    Mark Mccormack replied 15 years, 8 months ago 3 Members · 4 Replies
  • 4 Replies
  • Mike Kujbida

    September 16, 2010 at 10:46 pm

    My question is why are you still using Pro 9.0a?
    It’s now at 0.0e which means a lot of bug fixes in the past year.
    Do the upgrade first and see if that solves your problems.

  • Mike Kujbida

    September 17, 2010 at 12:50 am

    That should read 9.0e
    Need to get the “brain to finger wiring” checked out once again 🙂

  • Sam Nicholls

    September 17, 2010 at 10:56 am

    Hi Mike,
    Thanks for the reply, I’d been using 9a out of fear of upgrading in the middle of projects (I’d done this before only to find new bugs).

    I understand it would make a lot of sense to update to 9e, which I’m installing as I type, but I was wondering if anyone could actually pin this down to a bug in the 9a version as looking through the release information for 9b\c\d\e, I couldn’t really see anything that would fix this.

    Hopefully it will just be the update.

  • Mark Mccormack

    September 18, 2010 at 6:55 am

    Hi, capturing in HDV long clips i used to loose audio and everything was out of sync. I changed the “maximum ram buffer size” in the capture preferences when capturing and all is well.

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