Ingite Pro crashes Vegas Pro 16

Hello,

I face the fact, that VEGAS Pro 16 cannot start while Ignite Pro (Version 3.1.8110) is installed on my system. De-installation of Ignite Pro solves the problem. Vegas Pro crashes while generating the ofx plugin library during the start and then generates a report, that indicates, Ignite Pro causes the crash. Hope soon for an update of Ignite Pro, which solves the problem.

Comments

  • I've been tinkering with a lot of video editors for the past two months and my first suggestion is to go to preferences and see if it has GPU acceleration enabled. This is a cause of a lot of crashing for a lot of people. Considering that the most expensive version of Vegas Pro comes with Ignite Pro, it should work.

    I recently purchased the Vegas Pro 365 subscription and just canceled it right before the 14 day mark and got a refund. I found it disappointing. 

    However, I installed the free version of Ignite Pro (Express) and it worked great. In fact I liked the Ignite Pro Express effects better than the Vegas stuff.

    Before I even installed Ignite Pro Express I had a huge problem with Vegas Pro crashing. I was using an nVidia 1050ti card and if the graphics acceleration was enabled with that card it crashed like crazy. Sometimes it would crash right off the bat. When I turned off gpu acceleration it stopped crashing. So I would recommend turning off graphic acceleration and see what happens.

    A lot of other people complain about crashes and freezes with Vegas Pro if GPU acceleration is enabled.

    I recently bought a used AMD RX 580 based card and Vegas did run fine with gpu acceleration turned on with that card. What I am finding is basically all the big video editors run better with AMD cards than nVidia cards because they all use OpenCL heavily and nVidia is not fully utilizing OpenCL. This just seems to be universal. This seems to include all OFX video editors and Powerdirecter, which is not OFX.

     

     

  •  It's not Universal, I use several nVidia cards on different machines with Vegas (14 and 15, not 16) and Ignite Pro 3.1 and it works fine.

  • Which nVidia card are you using? I'm just saying that with a 1050ti and the default gpu acceleration enabled, Vegas 16 crashed like crazy.

  • That single card may well have issues,  but you wrote: "What I am finding is basically all the big video editors run better with AMD cards than nVidia cards because they all use OpenCL heavily and nVidia is not fully utilizing OpenCL. This just seems to be universal. This seems to include all OFX video editors and Powerdirecter, which is not OFX."

    It's not Universal.

  • Hi,

    I have the same issue.
    If I install Ignite 2017 Express, then VP Edit 16 crashes as soon as launched.
    I disabled the option to use the GPU acceleration (I have a GTX980) but things are just the same.
    No idea about how to progress....

    Regards

      Roberto

  • edited December 2018

    Most Windows Pro NLEs support Nvidia better than AMD. CUDA on Nvidia cards outperform OpenCL on AMD, and Nvidia has - in general - more powerful GPUs. Editors like Premiere Pro, Resolve, and others will favor CUDA on GTX and Quadro cards. They will not use OpenCL unless you force it, which makes no sense whatsoever. Comoaring OpenCL performance across vendors is, therefore, worthless. 

    Avid supports Nvidia better than AMD, as well. Plugins from vendors like Boris will accelerate with CUDA on Nvidia cards. 

    The only NLEs that tend to favor AMD are the "lower end professional" and particularly many Windows-only editors with code bases that haven't seen as much maintenance. Typically these are Prosumer editors that sit between the consumer and "high end professional" NLEs. Vegas is one of them.

    They had CUDA support in the past, but it wasn't maintained, so it now only works with legacy cards. Nvidia cards are problematic with GPU Acceleration in Vegas, in general,  as a result. Intel and AMD - older and new iGPUs and dGPUs are more stable and work properly. 

    The Vegas developers refuse to release a list of certified hardware. I moved to Resolve as a result. With so much software running better with Nvidia on Windows, it makes little sense to gimp 10 applications just for Vegas; when better alternatives exist, anyways. 

    The statement that "all the big video applications run better with AMD" is completely false. "All the big video applications" come from cknpanies that can afford to hire developers to implement proper CUDA support, which completely reverses that assertion. 

    You have to not have used many of them to come to that conclusion. 

    Vegas Pro has longstanding issues with its support and use of GPUs independent of the merits of any particular brand. It's just mediocre software. 

    I have never really felt a huge difference in Vegas with GPU Acceleration on and off, but it gets buggy if I have it on with the GTX card selected. For example, effect adjustments do not live update. I have to close the effect editing window before the preview will update (obviously not an acceptable workflow).

    On macOS, OpenCL is deprecated and things are moving to Metal. Final Cut, Premiere Pro, and Resolve are already on Metal... because the co.panies that make the "big video applications" are quick to move on these things. 

    Once Resolve 15.1 allowed me to round trip with Sound Forge, Vegas Pro was over for me. 

  • For me: Vegas renders ~2x faster with GPU Cuda support turned on than forcing' CPU Only' and I haven't experienced any stability issues because of it.

  • That's not GPU CUDA support, that GPU Encode Acceleration for supported compressed formats - NVENC.

    CUDA Support is what you get in NLEs like Premiere Pro (Mercury Engine CUDA for Effects Processing) or Resolve (compare their CUDA-Accelerated ResolveFX to Ignite OpenFX in that NLE).

    They're two different things, but developers often call NVENC CUDA because Nvidia put it in the CUDA SDK, allowing them to falsely advertise and get away with it (marketing loophole).  Most consumer NLEs use this trick, and customers wonder why the only thing that has improved on their machine are the render speeds.

    If you render to ProRes, DNxHR, Cineform, HQX, or any other non-delivery format... you aren't going to get any increase from NVENC because it only accelerates H.264, HEVC, VP9, etc.

    Some of us like to archive masters in a less lossy/higher quality CODEC ;-)

  • @iNate No, it's CUDA Encoding support, which only supports up to a GTX 580 in Vegas, as it's hardwired in to the Mainconcept(?) libraries and which was never improved on and which I used to have at the time of that post. Was going to keep it in the PC along side the new card for exports only, but it's too big and thirsty, so is now gone. So in V16: get a 4x faster GPU and watch it encode at half the speed it used to. I wouldn't use NVENC, as the consenseus seems to be the quality is awful, so presumably only for fast test renders, which is what I use MP4 exports for. Masters are a different hovercraft full of eels.

  • 98.6% of people won't notice the difference between NVENC and CPU encoding.  Not sure where you're getting this consensus from.  Lots of people with Resolve use NVENC Encoding, and they aren't complaining.  Most software worth using has implemented at least QSV and NVENC Encoding.  The bitrates and settings that you would encode with in an NLE are not equivalent to what you would use for i.e. Screen Capturing while gaming.  NVENC also has a Lossless Option, as well (produces huge files, though) ;-)

    Masters I would encode to DNxHR or ProRes, at a good [and appropriate] bitrate.

    MP4 is a wrapper that can contain H.264 or H.265.

    For fast test renders, you would lower the bit rate and/or the raster size of the export... that way it exports faster.  That's what editors do when they send AAF/OMFs to Audio Post and provide a video to them.  DNxHD, 720p Low Quality :-P

    That has nothing to do with the quality of NVENC, QSV, or VCE.  Those are mature technologies, at this point. Indistinguishible from CPU Renders, to the layman.

    You will lose more quality to YouTube [definitely] or Vimeo [very, very likely] recompression than you will from using NVENC over CPU to render those files.

    DI CODECs (Cineform, ProRes, HQX, XAVC-I, DNxHR) are bad for file transfer over the internet.  Good for Archiving.

     

  •  Hey, just an observation from my usage with Sony Vegas 16, if i don't launch it in 'Run As Administrator' mode, (by right clicking on its icon), it'll crash.

    If you encounter crashes, make sure to try that if you're running on a PC. 

Sign In or Register to comment.