Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Sony Vegas 11 – Slow motion doesn’t render correctly

  • Sony Vegas 11 – Slow motion doesn’t render correctly

    Posted by Jono Shavelar on February 20, 2012 at 2:39 am

    Hi all,
    Thanks for taking the time to read this, first post here.

    I’ve basically got an issue where Sony Vegas renders videos fine until it gets to a part with slow motion. I’ve successfully rendered quite a few videos but any time I try to render a slow motion clip the render % hangs and the program locks up, the only way to close it is to close the process.
    I’ve tried a few different formats, wmv, avi and MP4, the latter of which actually give an error message whereas wmv just hangs.
    The render also starts to fault, the colours mess up towards the end, quite hard to describe but here is an example;
    How colours should look: https://i.imgur.com/1vcUT.png
    How colours come out: https://i.imgur.com/IFS0e.png (they flicker between this and normal)
    (As you can see I’m trying to render BF3 gameplay. This problem also occurs with slow motion from many other sources though.)

    The error returns this:
    “Problem Description
    Application Name: Vegas Pro
    Application Version: Version 11.0 (Build 520)
    Problem: Unmanaged Exception (0xc0000005)
    Fault Module: C:Windowssystem32nvcuda.dll
    Fault Address: 0x06469866
    Fault Offset: 0x00049866”

    Many thanks for reading, I hope someone has an idea of the issue..

    Jono Shavelar

    View post on imgur.com

    Jono Shavelar replied 14 years, 2 months ago 4 Members · 5 Replies
  • 5 Replies
  • Steve Rhoden

    February 20, 2012 at 5:48 am

    When you slow motioned the clip, did you use the
    Velocity envelope method or the ctrl hold while dragging
    the edge
    method?
    Also make sure that particular clip is Quantize to frames.
    To do this you enable the Quantize to frames icon in the
    toolbar then you move and reposition the clip….just
    a shot in the dark hoping we find a solution for this.

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    1-876-832-4956

  • Mikhail Petrushin

    February 20, 2012 at 6:10 am

    Fault module — nvcuda.dll.
    Have you tried to disable GPU usage in Vegas Options and in Renderer options?

  • Jono Shavelar

    February 20, 2012 at 11:53 am

    Ahh thanks for the replies guys, really appreciate it, I managed to find a fix for this which was as you said, disabling GPU acceleration, but I couldn’t edit or amend the post because I’m a newbie 🙂

    Thanks a lot though! Any idea if I should be concerned about my GPU? Or think it’s more likely to be driver based? I’ve got a 560ti and it got through a few G80memtests fine..

    Thanks again 🙂

  • Matt Carlson

    February 20, 2012 at 11:02 pm

    This is a bug that has not been addressed yet and not anything specific to a lack of proper workflow or hardware. Most people do not do a lot of time stretching with Vegas video because it’s stretch algorithm is jerky in its output compared to other NLEs so the glitch does not present itself in usual use. Transitions will reduce to one color at a certain point when a stretched event is involved. Turning off GPU acceleration is only a moderate fix. The glitches will happen less but they will still happen. The really pernicious part of this bug is that it has no obvious consistency to it. I rendered a project part and noticed the output had the glitch. Without changing anything minutes later I rendered the same part and it was fine. Several iterations later it was back… then not. Changing to 8 bit color completely eliminated the problem (but of course the project’s color corrections were unusable and had to be redone.) I assume your project is in 32 bit full range color?

  • Jono Shavelar

    February 21, 2012 at 9:35 pm

    My project was indeed in 32-bit full colour, it’s a shame to hear that it’s likely to rear its head again, although I’m probably unlikely to use slow motion in the future..
    Still, thanks for the comments, glad to see I’m not the only one who had the issue, which I thought was the case after I spent so much time googling the issue..

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