BCC5 Chroma key semi transparent after a render

[Peter Mcauley]

Hi Jeremy,

We’ll take a look at that right away and see if we can reproduce the issue tat you are describing. Can you please tell me whether you are using PowerPC or MacIntel hardware?

Thanks,

Peter.

[Jeremy Garchow]

Intel MacPro.

[Peter Mcauley]

Hi Jeremy,

I just keyed a blue-screen clip using the criteria that you have mentioned with BCC FxPlug and had no problems at all. The final render looked exactly the same as the preview in FCP.

One thing to ensure is that you are using the BCC FxPlug filters and not the BCC AE filters.

So … there may be a difference in the project and with that I’d like to ask you to send me a copy of the timeline and also a few frames of the media that you are using so that we are both looking at exactly the same thing. Please send this to me via yousendit ftp service (yousendit.com). My email address is peterm@borisfx.com.

Thanks,

Peter.

[Jeremy Garchow]

I am pretty sure it’s the fxplug. i just downloaded the 5.0.1 fxplug updater and it installed in the fxplug folder.

I will send you the media shortly.

Thanks a lot.

Jeremy

[Jeremy Garchow]

Email has been sent.

Thanks, Peter.

[Matthew Lopes]

I’m having the exact same problem and I’ve tried everything. Running FCP 6.0.1, OSX 10.4.11, on an Intel Mac with QT 7.3.

The key is perfect until rendered. Any suggestions?

[Jeremy Garchow]

Boris was able to repeat it, so apparently it’s a bug and engineering is working on it.

The workaround is to use the linear key, but it didn’t work as easily as the chroma key on my footage. It works, but much more fuss.

Jeremy

[Peter Mcauley]

Hi,

This is the note from our engineering staff who have diagnosed the problem:

“We have tracked down the problem to an issue in the difference in our color conversion from 8 bit YUV to 8 or 16 bit RGB (where we do our rendering) and our conversion from float YUV to 8 or 16 bit YUV. This is being investigated by a member of our engineering staff (Paul). You can get around this problem (in an obviously unsatisfactory manner), by changing your Video Processing sequence setting from Render 10-bit material in high-precision YUV to Render in 8-bit YUV.”

Thanks for reporting the issue and we will issue an update patch to correct the problem once we have it fixed.

Cheers,

Peter.

[Jeremy Garchow]

Any updates to this problem, Peter?

Thanks for tracking it down by the way.

Jeremy

[Peter Mcauley]

Hi Jeremy,

This problem has been solved and a new build is available for download from our servers. Thanks for reporting this issue to us.

Cheers,

Peter.