View Full Version : De-saturation issue


Rachael Rowan
February 3rd, 2007, 01:56 PM
Hello XDCAM HD Users,

I was wondering if anyone has had any problems with major de-saturation when shooting HD HQ and then loading via a deck in SD (into an Avid)? It comes out very, very de-saturated (not a little, but a lot) even when it was shot in Hi-Sat mode and looked quite saturated in the camera and on a field monitor (properly set). This isn't from only one camera only, either, but several cameras with various settings. Now, I don't have the deck here with me, as I'm out shooting far away, but I was wondering if anybody has had any similar problem and thus has some information that might help improve this?

Thanks!
R

Nate Weaver
February 4th, 2007, 09:38 AM
Since we don't know how you're going from deck/SD downconversion to Avid, it's hard to even list anything to check, but I'd look for an issue between deck and Avid.

I've ever seen anything like that in my work.

Matt Trecartin
February 5th, 2007, 08:30 AM
Yes, how are you getting from the deck into the avid? thru a mojo? we need to know in order to help you.

I would think that its a faulty component cable, or maybe your input settings in the avid? Maybe its a setting in the deck?

Does the picture look right on the screen on the deck?

Look for the obvious easy answer first. I have never had a problem like this.

Rachael Rowan
February 6th, 2007, 04:53 PM
Thanks for the input. I'm not there, I'm quite far away, so I don't know exactly what's happening. It is into an Adrenalin and not through a mojo. I was more wondering if anyone else has experienced something like that with a downconvert from a deck, to know if this is a common issue or some issue with the set-up.

Andy Mees
February 6th, 2007, 09:55 PM
we're not seeing any significant de-saturation issues on downconverted footage ... you may want to have your deck checked out as it could be a hardware issue.

Rachael Rowan
February 7th, 2007, 05:30 PM
Dear Andy,

Thanks for the suggestion. That is a very good point. I'm glad to know nobody else is seeing this issue.

Best,
R