[Phillip D’annibale]

Well I don’t have a solution for you other than to say that I think it might be a problem on Canon’s end.

First of all I can’t even download ver 1.3 from their US a site, I had to get it from Canada and Asia. Tried to install both of those files and got a generic “An error has occurred. Error = 1” from both installers (Logged in as an admin, os x 10.6 fcp 7.0.3).

Seeing how it was just released June 6, I don’t think many people have hit it to discover that maybe Canon botched the installer and I can only hope that since I cant get it from the US site, Canon is aware and fixing it. I sent an email to them via their website, so we’ll see…

—–
Phill

[Phillip D’annibale]

OK, well I’m out for the day. I’ll call tomorrow.

[Phillip D’annibale]

Hi Boris,
Thanks for looking into this, I thought it became an official support request when my discussion moved off the board and to many emails in May. The lack of response from Matt led me to believe that I was not going to receive support because the problem couldn’t be solved by any of the suggestions he gave me. (I thought he gave plane ol’ gave up)

I installed 7.03.4 and I am getting the same error as 6.0.72, this time with many more entries into the console log.

How should I proceed to get all this info old and new carried over into an official support request?

Thanks,
Phill

[Phillip D’annibale]

Hi Boris,
is the update you are referring to version 6.0.72? If so I have that update, and that is the one that is completely broken!

Can you explain the OpenGL problem in any more detail? Is it an OS issue that might have a fix or something with the Graphics cards themselves? Come to think of it, I’ve tried to run the CineBench OpenGL test in the past on 2 of the 4 machines (one with FX4500, and the 7300GT), and it has failed the reference matching test every time on both machines.

Thanks,
Phill

—–
Phill

[Phillip D’annibale]

email sent…

[Phillip D’annibale]

Hi Matt,
I do realize that troubleshooting over the web is a very difficult task. Unfortunately due to the nature of the content I deal with at the large corporation I work for I am not allowed to send any content external.

I can tell you that the footage is ProRez 422 (HQ) 1920x1080i60 captured via an AJA Kona on a MacPro. I start with a completely fresh FCP project file and let the sequence conform to my footage

I feel like this is not a footage problem as I have also tried to key 10 bit uncompressed 4:2:2 1920×1080 footage (capture via the same AJA) with the same result.

I will dig around to see if i can find some “safe” content, but even then I risk having a very unhappy corporate lawyer knocking on my door.

I will also try to install 6.0.7 onto a third MP of different specs that never had any version of BCS on it to try a fresh angle.

Thanks,
Phill

[Phillip D’annibale]

Hi Matt,
Clearing the cache did remove the garble, but now when I apply the filter (version 6.0.7x) my canvas simply goes black. I still have no response from the filter’s controls, and Motion still locks hard when applying the filter.

Phill

[Phillip D’annibale]

Hi Matt, thanks for taking the time to respond.

Indeed both my systems are dual monitors, both with a Quattro FX 4500 (one 2x 30″, the other 1x 30″ and one cintique). Removing the second monitor on both systems did not solve the pink holographic issue on version 6.0.5.

Upgrading to the latest (6.0.7x) Chroma Key unit did seem to fix the pink holographic issue when exporting/rendering, but it is now causing an entirely new problem…that is the garbled image that doesn’t have any resemblance to the footage, no response from any of the CKS controls(the garble doesn’t change when adjusting the controls), and causing Motion to lock hard needing a force quit…where as Motion was the only way to export correctly on 6.0.5.

This is happening as soon as the filter is applied to the clip in the timeline (6.0.5 looked fine in the timeline/canvas and had a problem when baking…6.0.7 looks bad all the time), and the garbled footage persists during rendering, and exporting.

Running a single monitor with 6.0.7x does not change this behavior either. Disclaimer I only tested this version on one machine.

So as we speak I am again reverting to 6.0.5 so I can use Motion to export…

[Phillip D’annibale]

Thank you for checking, I will upgrade.

I’m actually having a big problem with the chroma key unit in FCP that a reinstall did not cure, but hopefully this update will. If it does not cure what ails me look out for another thread… 😉

Thanks,
Phill

[Phillip D’annibale]

Ok, well the release notes also said the update included an improvement to the matte choker which is a plug-in that I use with the chromakey unit. Just looking to stay up to date, thanks for the info!