Comments

Steven-Cooper wrote on 8/5/2019, 11:08 AM

I'm having the same problem on Windows 10 Pro 64 bit - it crashes while trying to load and at least it asks if I want to send an error report (which I did). I have a feeling we're beta testers for ver. 17. I'm glad ver. 16 is working fine :)

fhu wrote on 8/5/2019, 11:19 AM

I had the same problem but I uninstalled the BCC plugins and it opened flawlessly.

nickfrom wrote on 8/5/2019, 11:22 AM

I had the same problem but I uninstalled the BCC plugins and it opened flawlessly.

I thought about doing that but I want to keep the BCC plugins, or several of my old projects will be broken :-/

KPDVD wrote on 8/5/2019, 11:26 AM

I had the same problem but I uninstalled the BCC plugins and it opened flawlessly.

Have you reinstall your BCC plugins again yet? Does Vegas Pro 17 work after that?

JN_ wrote on 8/5/2019, 11:42 AM

I had the same problem on my PC, fixed by removing Boris ….. 11.

It then loads past the opening screen.

There's another issue, I'll start a new thread, common to both laptop and PC, a stream could not be found.

 

Desktop and Laptop basic specs ...

Both run Win 10 ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4 Nov. '18.

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

drone wrote on 8/5/2019, 11:49 AM

Paid for Vegas Pro 17. Downloaded and registered but it does not run - crashes before opening. Have rebooted but still cannot get it to work. Have sent several error reports. Hopeless.

iggy097 wrote on 8/5/2019, 12:55 PM

I also had to uninstall Boris to get Vegas 17 to open.

nickfrom wrote on 8/5/2019, 1:34 PM

I also had to uninstall Boris to get Vegas 17 to open.

Did you re-install Boris afterwards?

iggy097 wrote on 8/5/2019, 1:53 PM

I also had to uninstall Boris to get Vegas 17 to open.

Did you re-install Boris afterwards

I did not, as I don't use it

fr0sty wrote on 8/5/2019, 2:12 PM

"I have a feeling we're beta testers for ver. 17.",

I can promise you that this isn't the case. The software has been very well tested, however there is no way to get every single bug that will pop up on every single system configuration. Unlike Resolve or anything from Apple, Vegas allows you to use just about any hardware to do everything from full screen previews to HDR playback on supported HDR screens, even on consumer-level GPUs. While this leads to an infinitely larger set of possibilities, it also creates a situation where it's pretty much impossible to catch every single bug before a product releases because of the dozens upon dozens of different hardware configurations out there running Vegas.

You can trust the team is monitoring these bugs closely and will be putting out fixes in short order.

Grazie wrote on 8/6/2019, 12:41 AM

Just installed. Needed to uninstall Boris Plugs. Up and running.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

bvideo wrote on 8/6/2019, 12:58 AM

Which version of BCC works after reinstalling? 11 ? One that came with Vegas Pro?

PeterWright wrote on 8/6/2019, 5:23 AM

Thanks guys - I followed your advice and uninstalled BCC, which I never use anyway, and it opened! Cheers!

baksideDisaster_Flicks wrote on 8/6/2019, 11:48 AM

Same issue for me, crashing at launch in BorisFX. I don't really use them anyways so I uninstalled but it's sad that they come with the installation and don't work.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 284)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\BorisFX\ContinuumOFX\11\lib\Continuum_OFX_8Bit.dll
   Fault Address:       0x00007FFB17945857
   Fault Offset:        0x00000000004C5857

bvideo wrote on 8/6/2019, 2:35 PM

Uninstalled and reinstalled, still NG. Actually, uninstalled, reinstalled with a serial# I received last September, then it was OK, but missing some "image restoration". So added the serial# I received in April 2018, then Vegas won't start.

MagixDerek wrote on 8/6/2019, 2:57 PM

In regards to this crash, there is indeed an issue with some of the older Continuum effects running with VP 17. We are in contact with BorisFX to work on a solution or workaround for this problem.

ranself wrote on 8/6/2019, 3:37 PM

Vegas Pro 17 Crashes - BorisFX Folks Can Help!

Just passing this along: Reach out to the good folks at Boris FX if your Vegas Pro 17 is crashing on start up. They can see if your Serial will allow a post-11 Activation, in which case hopefully that should fix the problem.

ranself wrote on 8/6/2019, 3:38 PM

It worked for me

Pete wrote on 8/6/2019, 6:01 PM

I had the same problem but I uninstalled the BCC plugins and it opened flawlessly.

I upgraded from Vegas Pro 16 to 17 and it worked fine on my desktop, but my laptop kept crashing. Removing Boris finally fixed so I can get all my settings! Thank you very much!

tony-pruden wrote on 8/7/2019, 2:12 PM

Same issue here with the Boris CC10 and 11. I had to uninstall them to make it work. There's no problem with Vegas Pro 16. I hope the solution will include a re-install process.

HelgeK wrote on 8/7/2019, 3:25 PM

Same problem. Tried to re-activate Boris. No difference. Uninstall made it possible to start Vegas Pro 17.

terryA wrote on 8/7/2019, 4:16 PM

Same problem with a twist. I uninstalled BCC but Vegas 17 still does not load. You guys are lucky. I have open tickets with Boris and Magix to resolve the issue. Vegas 16 continues to work fine for me.

update: Boris tech support identified the conflict and eliminated the Continuum error. Go to:

C:\Program Files\Common Files\OFX\Plugins

Delete BCC folder. Done. Error gone.

However, Vegas still crashes on start-up. The error occurs right at "initializing VSTplugins". So far Magix/Vegas have been unresponsive to my support ticket on this issue. I have to say, Boris support was outstanding. Magix not so much.

update #2: I finally got Vegas to start up. Following on the cues in this thread, I arbitrarily renamed C:\Program Files\Common Files\VST3 folder, and poof, Vegas started up. Then renamed it back, and it works fine. I don't know if there was a specific plugin that was causing the problem but now it works. Absolutely no help from Magix support despite an open ticket. I sent them a video of the crash, dump files, etc. All into a black hole. Pathetic.

... and then ...

FXHome Ingnite Pro plugins would not load. No flag or anything, just not there. I continued to use my open Magix support ticket, was told I probably got Ignite from a Vegas suite deal and was not authorized for a new version of Vegas. Except I have had a full license of Ignite for several years, just renewed for Ignite Pro, and it runs fine in Vegas 16. So I ping FXHome. Was told Vegas 17 is not currently supported by Ignite Pro. I can live with that. It strikes me Magix should have known this, or at least should have done some diligence to help me out.

Through this whole experience, Magix (non) support is amongst the worst I have experienced. Throughout my entire Vegas 17 issue -- the support ticket has been open since August 6th, 10 days -- they helped resolve exactly zero.

I have been a Vegas user since Adobe went to a subscription model, around 2010-ish. I have dutifully upgraded with each product cycle. Because of the current frustration, I was ready to dump Vegas, ask for my money back, and go back to Adobe -- at least partially motivated by third-party integration with Premiere and After Effects. GoPro Fusion Studio and some Red Giant products that are part of the Magic Bullet Suite bundle (which I license) are tightly integrated with Adobe, but are not supported at all in Vegas. Still on the fence with Adobe.

But I am going to beat the drum on this support issue. Pathetic and disrespectful to at least one loyal customer. If Vegas Support is monitoring this forum, dig into Ticket#2019080517005405 and tell me what went wrong. Boris was outstanding -- 11 out of 10. FXHome was immediately responsive -- like 90 minutes. If this level of support is your business model, tell me and I'll go somewhere else.

ikashiru wrote on 8/13/2019, 1:18 AM

Same problem with a twist. I uninstalled BCC but Vegas 17 still does not load. You guys are lucky. I have open tickets with Boris and Magix to resolve the issue. Vegas 16 continues to work fine for me.

update: Boris tech support identified the conflict and eliminated the Continuum error. Go to:

C:\Program Files\Common Files\OFX\Plugins

Delete BCC folder. Done. Error gone.

However, Vegas still crashes on start-up. The error occurs right at "initializing VSTplugins". So far Magix/Vegas have been unresponsive to my support ticket on this issue. I have to say, Boris support was outstanding. Magix not so much.

So my work around for this was simply to do this:

Go to: C:\Program Files\BorisFX\ContinuumOFX\11\lib

Rename "Continuum_OFX_8Bit.DLL" to "Continuum_OFX_8Bit.txt"

Load vegas, and you're in! THe Majority of BCC effects from Vegas 16 still work.

Hope this helps some equally frustrated people! Andy

ikashiru wrote on 8/13/2019, 1:37 AM

Same problem with a twist. I uninstalled BCC but Vegas 17 still does not load. You guys are lucky. I have open tickets with Boris and Magix to resolve the issue. Vegas 16 continues to work fine for me.

update: Boris tech support identified the conflict and eliminated the Continuum error. Go to:

C:\Program Files\Common Files\OFX\Plugins

Delete BCC folder. Done. Error gone.

However, Vegas still crashes on start-up. The error occurs right at "initializing VSTplugins". So far Magix/Vegas have been unresponsive to my support ticket on this issue. I have to say, Boris support was outstanding. Magix not so much.

So my work around for this was simply to do this:

Go to: C:\Program Files\BorisFX\ContinuumOFX\11\lib

Rename "Continuum_OFX_8Bit.DLL" to "Continuum_OFX_8Bit.txt"

Load vegas, and you're in! THe Majority of BCC effects from Vegas 16 still work.

Hope this helps some equally frustrated people! Andy

Just to add, you can rename the plugin to .DLL after you have loaded Vegas 17 once and it starts up fine from then onwards. A.