Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Memory errors when rendering Quicktime MOV files

  • Memory errors when rendering Quicktime MOV files

    Posted by Todd Geer on June 16, 2010 at 2:11 pm

    I have a project which is long enough to require that several separate MOV files be created so that they can be sent via disc to someone else.

    I created regions in the project, a minute long each, seven of them.

    Highlight region one, render as, render loop region only, file1.mov, works fine. Highlight region two, render as, blah blah, memory error.

    Restart Vegas.

    Highlight region two, render as, blah blah, works fine. Highlight region two, render as, blah blah, memory error.

    If I restart Vegas between each render, I get no memory errors.

    Have the latest QT.

    Thoughts?

    Todd Geer replied 15 years, 10 months ago 2 Members · 3 Replies
  • 3 Replies
  • Douglas Spotted eagle

    June 16, 2010 at 3:21 pm

    latest QT is part of the problem. Older versions are better.
    Set Dynamic RAM to zero as a starting point.
    Be sure your system is running lean. QT and Vegas together=cycle pig.

    Douglas Spotted Eagle
    VASST

    Certified Sony Vegas Trainer
    Aerial Camera/Instructor

  • Todd Geer

    June 16, 2010 at 4:20 pm

    Hey, DSE. Thanks – and while I gotcha, what’s your thoughts about this?

    https://forums.creativecow.net/readpost/24/911126

    I have a ticket in with Sony now, have been piling on the documentation/research in the ticket.

  • Todd Geer

    June 30, 2010 at 4:47 pm

    For those interested in the issue where Sony Vegas cannot see the timecode in AVCHD files, we have a final answer from Support:

    —–
    Thank you for your patience. Our development team let me know that AVCHD timecode (for camcorders that have this) is not something that is supported in Vegas at this time, but to keep a look out in future versions. Thank you for bringing this to our attention.

    If you still have a follow-up question on this particular incident, please feel free to update it. If you have a completely different question, please create a new incident.

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