Cross Dissolve Changes Luma??
 

I've got an odd problem, that I can't seem to find any solution for. Whenever I use a cross dissolve (or even Natress' G Film Dissolve) when the transition starts the footage appears to brighten and then as the transition ends, it very noticably darkens back to its original state. The change doesn't show up if you step through the transition one frame at a time, but it does render out to the final file. Any one have a clue what this is?

It shouldn't. I mean, it used to do this back with FCP1, but that got fixed. Check your timeline settings - white or superwhite, check rendering is YCbCr (YUV) etc.

Graeme

Yeah, I tried about every combination of white, superwhite, YUV, and high precision YUV there is... I deleted my render files, restarted, and re rendered... still there. Heck, I tried overlapping the the clips on seperate layers and setting keyframes on their opacity and still had the problem. I'm about ready to pull my hair out.... if I had any. My deadline for this piece is tomorrow afternoon, and except for this wonderful screw up it's ready...

Do you have any capture cards in the mac? They can cause issues like this also.

Graeme

Nope, no capture cards... There is a firewire analog to DV converter on there that I use to monitor... could that cause it? It never has in any other sequence...

BTW, if it matters, I'm editing stock footage in photo-JPEG (the footage's native format)

Kevin,
Try converting your stock footage (photo jpeg) into a video file using the same codec that is native to your editing program. There may be a conflict with the color schemes between the two. Different color schemes trying to meld together in a crossdissolve dosen't seem like a good idea.

Robert

Guess I forgot to mention I'm using FCP 5. My sequence right now is a Photo-JPEG sequence, but I guess I'll try changing that...I've tried everything else I can think of so far... though I don't have time to convert all 200 Gb of stock footage to another format...

Stupid internet connection caused a double post...

I changed my sequence to a DVCPRO50 NTSC sequence and that has apparently cleared it up. Thanks for the help guys.