Comments

Avellino wrote on 8/14/2019, 8:36 AM

Just to confirm that I did something similar to ikashiru's solution and that worked for me too.

Previous set-up Vegas Pro 16, BCC 11, Sapphire 11 - working OK. (I also had some Boris modules acquired separately outside BCC hence my set-up is slightly messier as a result, with some Boris effects sourced twice).

Vegas Pro 17 was crashing for me on startup as per similar reports from other users. I use BCC/Sapphire all the time, hence giving them up was not an option.

I wasn't keen on uninstalling/re-installing/re-activating BCC/Sapphire since I didn't want to jeopardise my operational environment with Vegas 16 working well with BCC/Sapphire.

Instead, I went to C:\Program Files\Common Files\OFX\Plugins and I inside the following folders I changed the subfolder "Content" to include an underscore "_Content". (As mentioned earlier, I had more of such folders due to my particular setup, but in essence, I changed "Content" in all the folders containing BCC/Boris/Sapphire in the folder name):

  • BCC_OFX_3DObjects.ofx.bundle
  • BCC12_OFX.ofx.bundle
  • BorisFX
  • Sapphire.ofx.bundle

I was then able to start up Vegas 17 successfully. Of course, Boris effects were not operational at this point. I then renamed back each of the folders changed earlier to their original name, one at a time. I started Vegas 17 after each rename operation, which makes it re-build the list of plugins available to it.

Maybe I could have got away with changing them back all at once, but I was keen to isolate any conflict that may still remain in place and I wanted to avoid "overloading" Vegas with too much stuff at once.

To my surprise, when I restored all folders back to the original names Vegas 17 still started OK and it is now fully operational. The BCC/Sapphire effects are available, so all is well. It is entirely possible that some effects may not actually work, but I can live with that. I tried many of the ones I use frequently and they are OK.

The status now:

  • Vegas 16 works fully with all BCC/Sapphire effects as before.
  • Vegas 17 works fully with most (maybe all) BCC/Sapphire effects and it can do all the marvelous new things that I bought it for.

There is the debate on who should then fix this Vegas or BorisFX. Some argue that BorixFX may not be fully compliant with the OFX standard, causing Vegas 17 to crash on startup. If so, there's merit in the assumption that Boris should fix their old versions to make them compatible and let's hope they do so. Even then, it would be highly desirable for Magix to write the code that scans for plugins more defensively to survive a dodgy plug-in. Music software (e.g. Cubase) seems to be able to deal with this situation admirably by "blacklisting" non-compliant plug-ins (you can see them in a list once the application starts up) rather than just throw its hands in the air. Scanning plugins on start-up is not time-critical, hence it can be a tad slower as a price for being crash-safe.

 

AlanMintaka wrote on 8/14/2019, 10:52 PM

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.

That solution worked for me. DLL file has now been renamed back to Continuum_OFX_8Bit.DLL and VP17 still starts without crashing. Nice thing is that I didn't have to touch the Boris FX installation.

BUT - during the VP17 program launches and restarts, I discovered another "feature" of the upgrade: it has the same memory-resident problem that VP 16.424 has. That is, after you exit VP17, it stays in memory. If you then try to restart it without first killing the memory-resident process, VP17 hangs during "Initializing UI....."

Guess I'll be heading over to the existing thread "Vegas Remains In Memory? Like a Bad Smell...." now....

rkm82 wrote on 8/16/2019, 2:10 PM

Same issue here - Threadripper 1920x - crashing on load, after deinstallation of Boris it works.

Stephen-Longo wrote on 8/16/2019, 5:17 PM

I was able to resolve it the easiest way by doing this:
1. rename the file extension dll to bak C:\Program Files\BorisFX\ContinuumOFX\11\lib\Continuum_OFX_8Bit.dll

2. start Vegas Pro 17 and when loaded, quit the program

3. restore the file extension to dll from bak and start Vegas Pro 17

4. Problem resolved!

Stephen-Longo wrote on 8/16/2019, 5:24 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.

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

You can rename it back after Vegas Pro program runs and then exits.