[Ryan Holmes]

You’re not gaining quality by transcoding your footage. All your doing is putting your 8-bit 4:2:0 into a different container (8-bit 4:2:2), but your not gaining extra sampling information.

Like Steve says, if you need to transcode because the apps you’re using don’t like that particular codec so be it. But you won’t be gaining any quality by doing so. If it smooths out your workflow I’d say transcode to a standard mezzanine codec (like DNxHD or ProRes). This can be helpful if you need to pass footage off to other apps that may not play well with various codecs or a mixed codec timeline. If not, I think you’re just chewing up time and it won’t make your keying any easier or better.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

I-frame distance is a type of compression scheme, as Mark notes, consisting of I, P, and B frames.
I = Intra coded frame
P = Predicted picture
B = Bi-predictive or Bi-directional picture

These options are set upon compression by adjusting the “Keyframe Distance” in your encoder of choice (Compressor, Media Encoder, Sorenson, Telestream, etc.). For a read through take look at Wikipedia:

https://en.wikipedia.org/wiki/Video_compression_picture_types

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Some users of the new Mac Pro have reported problems as well under 10.9.2.

My suggestion is to turn off any CUDA (or OpenCL) rendering. Just use the good old Mercury Playback Engine Software Only to render out your project. I assure you it’ll be slower, but I haven’t read problems related to using that aspect of the Mercury Engine for rendering.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Melvin Betaphats] “Turning off open cl support would defeat the purpose owning this machine end of the day!”

Adobe has to issue a patch for the problem. Until then patch is released, I would recommend turning off OpenCL when rendering. Yes, it will be slower, but you’ll have the deliverable product you need.

I would also submit a Bug Report directly to Adobe:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Vivek Jaiswal] ” I tried using Canon XF Utility to recreate the MXF files as you suggested but it didn’t work out. Please suggest if there is another way to solve this issue.”

Once you create the stand alone MXF files you’ll need to transcode those to something FCP 7 can see (like ProRes). MPEG Streamclip, Compressor may work….There may be a MXF plugin for FCP…but I haven’t used FCP in several years so I’m not familiar with that part of the market.

Another option is to download the trial version of Adobe Creative Cloud and use Prelude or Premiere to transcode the Canon MXF files to ProRes. Adobe’s products can see the MXF files natively. Do your transcode there and get into FCP.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Turn off CUDA/Open CL enabled rendering/exporting. Try only using the software rendering engine. It will likely be slower but if it gets rid if the glitch….

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[jordi robert] “So, if it happens again, what would be the best solution during shooting?”

Since this is a set, I’d recommend testing during off times. Since you’re not under a run-and-gun scenario spend a day testing out different settings.

Ultimately, the biggest variable is your shutter speed. The shutter speeds used will depend on where you’re shooting (America vs. Europe), type of lights, frame rate, etc. You’ll need to experiment with different shutter speeds within your space to see which one mitigates the effect the most. Typically staying at a shutter speed that is twice your frame (what’s called 180 degrees) is usually the best way to go.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Warren Eig] ” my 5D Miii is at firmware 1.2.3. I’m waiting and hoping ML releases a Raw solution with this version of the Canon’s firmware.”

We had 1.2.1 on our camera to test the “clean” HDMI out. It was alright, but at only 8-bit it didn’t give us huge leg up. Once the hack was usable we just rolled our firmware back to 1.1.3 to work with ML RAW. Not too big a deal.

https://www.magiclantern.fm/forum/index.php?topic=5383.0

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

[Warren Eig] “Have you tried ML yet?”

Yep…we run it on our 5D3. It’s gotten to be more straight forward about how to load it, but I wouldn’t try it on rental gear.

The dynamic range and clarity is absolutely incredible…but so are the overall file sizes. It adds quite a bit of time in post to move the data, transcode it, etc. So it’s not for every job, but there are times when it is useful.

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost

[Ryan Holmes]

Did you light the scene with fluorescent lights?

It looks like the type of effect that happens at some frame rates/shutter speeds when shooting with a rolling shutter camera, like a DSLR. Unfortunately, there’s no fix in post. Best thing to do or is to reshoot it.

Now that you know what they look like, be on the lookout for them when you’re on set. You can see them on a monitor or even the small LCD on the bag of the camera if you look close enough (just not always easy to do when you’re in the midst of shooting).

Ryan Holmes
http://www.ryanholmes.me
@CutColorPost