[Lyle Aspinall]

I had the same issue with some smartphone footage, and this solution fixed it. Thank you. Ultimately it was a matter of matching the color space in the export to the color space in the sequence, the latter of which had been auto-generated from the originating clip.

[Lyle Aspinall]

My face is red. I discovered my own problem. The solid on which the beam was built had been slightly knocked off centre. Ugh. Once I put it back where it belonged, all was well.

Hopefully my mistake can help help someone else.

[Lyle Aspinall]

Adding/customizing that script…

StartPointLayer=thisComp.layer(“Null 01”);
StartPointLayer.toComp([0,0,0])

helped me out of a pickle. I knew how to track two ends of a beam separately, but I couldn’t figure out how to accurately place the start/end point. As soon as I applied the track, the end of the beam would always offset. Problem solved now. Thanks!

[Lyle Aspinall]

Four years later and I’m having the exact same issue. I also saw this issue posted at https://reduser.net/forum/showthread.php?105335-Pr-CC-Screen-Flashes-Making-Program-Unusable

Is there a solution yet?

My specs:
Windows 7
Intel Xeon CPU E5-1660 v4 @ 3.2 GHz
Quadro M2000
32 GB RAM
64-bit

[Lyle Aspinall]

I’m having a similar issue with a Sennheiser EW112P G3 kit. Just like Jason, I first scan for a new frequency with the receiver, then I ensure the frequency I select is clean of any other RF, and then I sync my transmitter to the receiver. I’ve re-done these steps about five times, choosing frequencies from all over the B spectrum, but no matter which one I try out, I always get a background static that sounds similar to mild wind noise.

I’ve plugged the receiver into two different types of Canon cameras: an EOS 5D Mark III DSLR and an XA10 (on both XLR and 1/8 inputs). The audio problem is no different between the two. Setting the DSLR on auto-gain audio makes the issue very easy to hear. Cranking the XA10’s XLR level also makes it really easy to hear.

I can reduce the problem by dropping the receiver’s AF Out to -30, but then I really have to boost the transmitter’s sensitivity to compensate. And when I set the DSLR’s audio manually, I have to really crank it up to help compensate for the -30 AF Out. The resulting sound isn’t great.

Even at -30 on the receiver’s AF Out, you can still hear the static problem if you really listen.

I can’t think of anything I might be doing wrong, but I’m certainly not yet ruling out user error.

[Lyle Aspinall]

Jeremy wins top marks here. He’s exactly correct. I completely uninstalled Calibrated, and the blocks are gone.

Back in the day, when I was using Final Cut Express and not Pro, I was looking for something that would play/convert my Panasonic HVX200 DVCPro fooage, and I installed the demo version of Calibrated at that point. Once I started using FC Pro, I’d completely forgotten about Calibrated, and the demo trial period ran out. Little did I know that anything I tried to do in FC Pro with DVCPro footage was first going through the outdated/unlicenced Calibrated software, which resulted in the grey boxes.

Reinstalling Calibrated the other day meant I had a fresh demo of Calibrated that very likely would have caused the grey blocks to reappear once the trial period was over.

Thanks again, Jeremy. You’re the first person to pinpoint the problem, and that’s after having posted to two forums and asking around to various colleagues.

[Lyle Aspinall]

Problem solved: I had to install Calibrated{Q} DVCProHD Decode 1.5, available here: https://www.apple.com/downloads/macosx/video/calibratedqdvcprohddecode.html

All my little grey blocks have magically gone away!