Boris FX/Graffiti not working in VP11 build 424

AlistairLock wrote on 11/2/2011, 2:11 PM

Hi,
I have been happily running the demo, and the Boris FX and Graffiti plug-ins run happily.

I bought VP11 today and have upgraded from build 370 to 424.

Now the plug-ins no longer run. After placing a new instance of either plug-in the colourful Boris banner does not open to enable you to open Boris FX or graffiti.
Attempting to remove the plug-in crashes Vegas.

On opening a project with an instance of Graffiti or FX already placed, the plug-ins run, but I can't access the plug-in to change their settings.

Reverting back to build 370 "solves" the problem.
Has anyone else seen this behaviour?

Thanks in advance.

Comments

dxdy wrote on 11/2/2011, 2:19 PM

I am running the Boris BCC 7 chroma keyer very successfully in build 425, and it runs fine. This may not be the same as Boris FX.

AlistairLock wrote on 11/3/2011, 9:20 AM

I've reverted back to build 370, and the plug-ins are working again.

Here are my system specs.

Machine 1 (my main editing machine)

Nvidia GTX570
Intel(r) Core(TM) i5 CPU 750 @2.67GHz2.67 GHz
RAM 4 GB

Windows 7 32 bit

Now, oddly enough, (or not) on my second machine, the plug-ins continue to operate normally, but the machine setup is different...

Machine 2 ( a slave machine normally used when I am composing music)

Radeon HD 5670
Intel(R) Core(TM)2 Duo CPU E7400 @ 2.8GHz 2.79 GHz

RAM 8 GB

Windows 7 64 bit

So is it the Graphics card in the main machine possibly?
The problem is the same if GPU acceleration is on or off.

I shall also send this message to support and see what happens.

Tech Diver wrote on 11/3/2011, 2:19 PM

According to the version compatibility chart at http://www.borisfx.com/host/matrix.php ,
neither Graffiti nor FX are not supported on versions of Vegas beyond 9.

Peter

AlistairLock wrote on 11/3/2011, 3:41 PM

Yike,
something I did not even think to check for.

I have to ask the question then, and hope support gets back to me;

Why are the plugins working on build 370 on one machine, and continue to run under build 420 on the other?

Desdinovah wrote on 11/5/2011, 10:58 AM

I had the same problem with Magic Bullet Looks and I had to uninstall 424 and go back to 370 to get the Edit function back. Hopefully it's something that will get fixed. I use Looks on every project and if I lose it on future builds then I may have to stick with Vegas Classic (or migrate to Premiere Pro--which I don't want to do).

AlistairLock wrote on 11/5/2011, 6:32 PM

I hope both our problems are sorted on the next release...

AlistairLock wrote on 12/17/2011, 6:12 AM

Well I'm happy with the new update.

Even though Boris FX 9 and Graffiti 5 are no longer officially supported in Vegas 10 and 11, they now work again in the new release. I don't understand how or why, but I'm happy.

Also, elsewhere it was reported by another user (and I also experienced), a problem with waves audio plugins. These now work. "Fixed a crash that could occur when using audio plug-ins protected with PACE iLok system"

Thank you.