Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Video Plug-In Effects “DXT” causing Render Crash with GPU “on”.

  • Video Plug-In Effects “DXT” causing Render Crash with GPU “on”.

    Posted by Pedro Cabrera on April 9, 2013 at 6:01 pm

    Like a good number of folks out there, I also have been dueling the “Render with GPU ON” dragon. Up to a few minutes ago, I had to keep my GPU off to be able to work. But I think I might have stumbled onto a solution for my problem.

    I went through the project and removed/deactivated all the video FX events that have a classification of “DXT” (ie, Glint, Wave, Border, …).

    I’m not sure what DXT is, the only thing I can find is “Video Plug-In Development Kit” download on Sony’s site. I don’t develop plug-ins so I’m at a complete loss about “DXT”

    After removing all of the “DXT” video FX events, I was able to render my project using my GPU reducing the rendering time by over 75%.

    I reported this to Sony on my open support ticket. Hopefully I will hear something back.

    Has anyone in the creative cow community stumbled upon something like this? Or maybe can explain what could be causing this problem.

    I appreciate everyone’s expertise and time with this matter.

    Pedro

    — My Video Editing Machine —
    (** only used for editing **)
    Vegas Pro 11
    Intel i7-3970x 3.5Ghz
    Intel Dx79sr MB
    32 Gigs of 2133 mhz Kingston RAM
    nVidia Quadro K5000 video card
    SSD HD (for O/S)
    2 – 2TB HD (1-media only, 1-everything else)
    Lg Blu-Ray Writer
    Corsair Pro 1200 Powersupply
    Corsair Hydro H100 Liquid CPU Cooler
    Corsair Carbide 500r Mid-Tower System Cabinet
    ———————————————-

    Michael j Toffan replied 13 years, 1 month ago 2 Members · 1 Reply
  • 1 Reply
  • Michael j Toffan

    April 10, 2013 at 12:08 am

    Hi Pedro

    Looking at your system specs, you have a very high end PC, which though slightly different, should have similar performance to mine. I have used your format to describe my system below:

    Vegas Pro 12
    Windows 7, 64bit ultimate
    Intel i7-3930x 3.2Ghz (2011 hex core cpu)
    ASUS P9x79 Premium MB
    64 Gigs of 1600 mhz GSkill RAM
    ASUS nVidia 680 video card (1500 Cuda cores, 2048 MB GDDR5)
    OCZ Vertex 4 SSD HD (for O/S)
    2 – 2TB HD in RAID 0 configuration
    Pioneer Blu-Ray Writer
    Corsair AX1200 Pro Powersupply
    prolimatech megahalems cpu cooler

    My single biggest problem rendering with the GPU enabled was the dynamic RAM preview setting. Once I started setting dynamic RAM preview to zero in the Preferences under Video tab, I have had good success rendering AVCHD to MP4 with GPU rendering set to either OPEN CL or CUDA. I typical use the Internet HD 1080 template under Main Concept AVC/AAC with a customized template set to progressive only and best quality.

    To see if I was having your issue, I took a 15 second slider clip with a nearly blown out window at mid clip that really brought out the glint and added “Sony Glint” plugin set to Sparkle and “Border” plugin set to a .0951 white border. I rendered three cases, one with GPU set to OPEN CL, one set to CUDA and then I deleted the plug-ins and rendered with CUDA.

    I was able to render all three cases without crashing; however, it was very clear from the render time that the Glint and Border plugins are taxing the system. The results:

    Sony Glint and Border GPU set to:OPEN CL Render Time: 3m 48s

    Sony Glint and Border GPU set to:CUDA Render Time: 3m 36s

    Delete Glint and Border GPU set to:CUDA Render Time: 0m 32s

    The glint and border cases clearly are challenging cases and will certainly stress the system. If you have not yet tried setting your Dynamic RAM preview to zero…doing so may help.

    Your system specs are so similar to mine, it seems you should be able to have similar results. My clip is certainly different than yours; so take my results with a grain of salt, hopefully this quick study gives you a reference and maybe some ideas to check.

    Mike

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