Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Boris FX BCC9 OpenCL Build error

  • BCC9 OpenCL Build error

    Posted by Mike Hinkel on June 14, 2015 at 5:51 pm

    I’m getting an error when attempting to use BCC9 Fast Film Process or Fast Film Glow in Sony Vegas Pro 13 build 453. The message reads an error occurred in the Boris FX Open CL Engine….clBuildProgramerror. Any reasons why or a way to fix? Thanks, I never had this problem and are the only two fx I found with it so far.

    Russ Froze replied 10 years, 10 months ago 4 Members · 9 Replies
  • 9 Replies
  • Tom Vance

    June 14, 2015 at 9:38 pm

    Mike,

    I can’t confirm that issue with my setup. I’m running a Radeon R9 280.

    Possible it is a video card issue? Does it do it if you turn off gpu acceleration?

    –tom

  • Mike Hinkel

    June 14, 2015 at 10:12 pm

    Tom, Thanks. GPU, on or off, results are the same. Scratching my head to why all of a sudden after the upgrade.

    Mike

  • Russ Froze

    June 15, 2015 at 9:11 am

    Yes I get the same error on Veg pro 12, The only way I can get it to work is to go into the plugins preferences and uncheck off enable gpu then once the error message is replaced by the normal image in the viewer I go back into the purlins preferences and check enable gpu again. It’s nuts I know but there it is.
    Russ Froze

  • Jon Kozenko

    June 16, 2015 at 4:18 pm

    Mike,

    What is the exact model and driver for your Graphics Card? Are you using a Quadro card? Also, what is the exact build of BCC OFX that you have installed? Lastly, just to check, do both Vignette and Vignette Dissolve give the same error?

    Thanks,

    Jon

  • Mike Hinkel

    June 16, 2015 at 4:44 pm

    Hi Jon, I have a NVIDIA GTX460. with the 350.12 driver. The error does not show in Vignette and I don’t see a Vignette Dissolve unless it is within another FX or transition. The build BBCOFX90a_64bit Sony

    Mike

  • Jon Kozenko

    June 17, 2015 at 8:45 pm

    Mike,

    If you back-track your Driver to version 333.11, does this fix the problem?

    Thanks,

    Jon

  • Mike Hinkel

    June 18, 2015 at 1:28 am

    Jon, I don’t see that driver version on the Nvidia website. I reinstalled Version 334.89 and that did the trick. It was the last one in my driver download folder. I don’t remember putting the 350.12 into the machine. Weird.

  • Jon Kozenko

    June 19, 2015 at 9:22 pm

    Mike,

    Outstanding news!

    Russ, if you are using a similar card/driver, try back-tracking to this driver and let me know if it helps.

    If so, both of you are experiencing problems coinciding with an existing issue, in which case hopefully we can get a driver fix established.

    Thanks,

    Jon

  • Russ Froze

    June 20, 2015 at 1:18 am

    I’m using a Quadro 4000 which serves me well with compositing and 3D programs. So I’m not too concerned. But if you can suggest a fix, that would be nice.
    Russ Froze

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