[Kumpanija Lajthaws]

Hi Bob

thanks again for your kind reply.

The issue is not with one frame, but with a sudden change from one frame to the next.

The problem has manifested itself both in controlled lighting conditions and also outdoors.

I’ve a feeling it’s an internal fault more than anything else — we’re not talking about a gradual change (the way a camera would in response to changing light levels or colour) but rather a sudden, inexplicable shift.

k

[Kumpanija Lajthaws]

Hi Bob

thanks for your input. What I meant, re raw, and that’s why i put it in quotes, is that the effect can be seen on movie files that came off the camera, ergo pre processing by any software.

Also, as mentioned, the camera is locked down, fully manual, with no in-camera shot adjustment. Therefore there should be no reason for the camera to tweak whatever’s coming in. And that’s what’s so annoying about this glitch: it’s a sudden shift, from one frame to the next.

We suspect the camera may be on its way out — but we were curious to see if anyone else has ever experienced the same thing.

k

[Kumpanija Lajthaws]

Hi Toke

Can only answer on the first part of the post: yes, although I have no hard evidence by way of statistics, it does seem to us that Color crashes far more frequently with 1440×1080 footage than it does with 1920×1080.

k

[Kumpanija Lajthaws]

Cheers to all for the info.

In the meantime we tested the camera with a Sigma 10mm-22mm zoom with max aperture constant at f/3.5 and the problem did not manifest itself.

k

[Kumpanija Lajthaws]

Hi All

thank you so much for your contributions.

In answer to the various questions.

The camera did not overheat — the shots were taken as the camera was switched on.

The original footage did not exhibit the shift.

The footage was filmed at 1080p 25fps.

We ran a test, selecting the “Enable 4:4:4 Chroma Filtering” option when encoding to ProRes(HQ) and it looks like it may have cured the issue…

[Kumpanija Lajthaws]

White balance was set on daylight.

Unfortunately don’t have access to L lenses…

[Kumpanija Lajthaws]

aif gives the same problem.

project was kept at 25fps right thru.

k

[Kumpanija Lajthaws]

Me again, Mac’s a 2 x 2.26 GHz Quad-Nehalem, 8Gb. so no issues there.

[Kumpanija Lajthaws]

We’ve experienced the same exact problem, on FCP 6.0.5.

We work with HDV almost exclusively, but CC in Color. So for short 30 sec work, we used to export each clip to ProRes HQ, and then import those clips into Color.

However, for long projects, we found it made more sense, obviously, to go thru Media Manager, and automatically re-encode the clips in Prores HQ.

And yet we’ve hit the same stumbling block that Toke has written here about, only that in our case we’re finding that each and every clip gets deinterlaced, irrespective of whether we’ve applied basic motion to it, or not.

Any takers?

k

[Kumpanija Lajthaws]

Cheers mate.

Worked a treat!

Useless rant — why couldn’t they turn the option on by default?

k