Something horribly wrong with FCP and the color red

I couldn't say about those of you getting it from an external source such as a DVD, and that might throw Pannie out of the equation.

Man, turn it down! We're just trying to help here...

I did have the chance to test in the same environment several cameras and Pannies had much worst reds than the rest -always thru FCP and in NTSC. Even compared with much worst cameras.

Here are the test results I got some years ago.

GS150 - NTSC - FCP5 - BAD
GS250 - NTSC - FCP5 - BAD
DVX100 - NTSC - FCP5 - BAD
Sony PD - NTSC - FCP5 - BETTER
Canon XL1 - NTSC - FCP5 - BEST
Sony HC35 - NTSC - FCP5 - BETTER

GS150 - NTSC - AVID - BETTER
GS250 - NTSC - AVID - BETTER
DVX100 - NTSC - VEGAS - BEST

GS300 - PAL - FCP5 - BEST
MD9000 - PAL - FCP5 - BEST
 
The problem is not "all Mac."

If it were, then every Mac user would experience it.

From what I've seen and read, few do.
 
Guys, I've seen problems with reds, especially from the DVX, in pretty much every editing app, especially if the reds are really hot. It's not a problem you always see, so even though it might appear that a particular app is the culprit, it probably isn't.

Not sure why this getting so heated. It may be a topic about reds, but the tone of the thread doesn't have to be that way.
 
Hi David:

I have really only experienced the blocky reds on my DVX footage, never on my HVX in FCP. According to Graeme Nattress, my blocky reds were a result of 4:1:1 DV processing on my DVX footage. The FCP chroma smoothing filter helped immensely. Not sure of what the other red issues are that he is experiencing.

I agree, jeez, we are here to help each other, right? Tone the testosterone down guys.

Dan
 
Last edited:
I don't see too many problems with HVX footage; I agree. But one place I DID see a problem -- a couple of times -- was when i transcoded HVX footage to HDV. It wasn't for anything important, so I didn't worry about it too much.

I don't think that issue is at play here, is it?
 
I get the fact that there are varying results when compressing NTSC footage.

The problem I'm addressing is independent of that. It is recent, it is BAD and it effects anything NTSC related being processed by Mac. Again for the cheap seats, the camera is not the problem. Forget the camera - it's the codec.

I re-installed the most recent Mpeg2 codec on my rig at home and still have the problem. I'm going to find an older version of MPEG2 and replace it to see if that corrects it. I just did a clean install of FCS2 on a computer that did not have the red issue and now it does.

It's the software. I just have to figure out which codec is the culprit.
 
The only component installed related to mpeg2, at least to my understanding, is this:

AppleMPEG2Codec.component

It is installed either as a part of QT or a part of FCS2.

And what exactly is "the problem?" Are you concerned with blockiness in the reds when playing DVDs or something else?

In other words, could detail a workflow that produces the problem that you identify?

I've asked you do this from my initial responses, and you haven't provided a detailed system spec and/or workflow.

Is there something that is preventing you from providing this information?

All anybody is trying to do is to assist.
 
But the picture I posted with the 2 rappers is a direct export from my 720p 50 timeline in FCP to .jpg and not from a DVD! And I see these red block when I edit in FCP on several different apple computers... so for me it comes from the HVX200 or Quicktime that doesn't handle red in a very good way!

Steven
 
And I posted a screen grab of a direct import from 720/24pn of a huge US flag with no blockiness.

So, what are we to conclude?
 
I'll just add my cents quickly.

I think it's a QT issue:

I had pristine footage shot on an HVX on a PowerBook with Tiger, FCS2, and the newest QuickTime update. Moved the footage to view on an iMac just five feet away, and I got crazy blocking issues. Tiger, FCS2, but an older QT version. When I updated the iMac's QuickTime Pro using Software Update, my HVX footage looked just as it did on the PowerBook.

-andrew
 
What version of QuickTime did you move from on the PowerBook?

What version of QuickTime did you update to on the iMac?

If this information isn't provided, how can anybody test the issue?

Is is frustrating that nobody seems to detail crucial information like version numbers.

If some one did, I could pass on to Apple.
 
I'm sorry, when I said it was related to FCP I meant it was related to 'the way Apple handles Video'.

I'd bet on the issue having something to do with QT.

So up to now, we know it involves QT and NTSC footage.

If you guys start making tests as I once did, you'll find out NTSC Panasonic cameras -as great as they are- get much worst reds in QT environments than Canon's and Sony's.


I'm anxiously waiting for your findings.
 
This isn't as simple as having 'Use High Quality video setting when available' clicked on the first page of the QT player prefs by any chance?
I had some footage that was giving me heart attacks when viewed as QT, until I found that setting.
 
Here's what I have.

FCS2 on 10.5.1

QT 7.3.1

I don't have the red issue.

Can someone else publish the same settings on a machine that HAS THE RED ISSUE?
 
Here's what I have.

FCS2 on 10.5.1

QT 7.3.1

I don't have the red issue.

Can someone else publish the same settings on a machine that HAS THE RED ISSUE?

I've got Quicktime 7.4.1 and I DO have the red problem.

It's looking more and more like the latest version of Quicktime might be the culprit.
 
Can you go back to 7.3.1?

And I have 7.4.1 on a test volume.

Is there a way to test to see if I also have the red issue?

Can you give a quick example of how to demonstrate it?
 
Can you go back to 7.3.1?

And I have 7.4.1 on a test volume.

Is there a way to test to see if I also have the red issue?

Can you give a quick example of how to demonstrate it?

Find any DVD or NTSC source with something predominantly red in it; taillights, stop signs, red shirts, hats, cars, whatever. It also seems to be effecting any color that contains red as a primary element like solid oranges and purples. If you've got it, it will be nearly impossible to miss.

Watching the DVD for the movie Sunrise was the first time I noticed it. I was running it out of my Mac through an HD projector. At first I thought there was something wrong with my projector and when I found out that wasn't it I started tracing it back through my computer. I went through and checked all my settings, my video card, my monitor and finally chalked it up to just needing to update all of my gear since I couldn't find the culprit. Then I found the same problem on a new G5 at the office. Since then I've seen at least 5 other Macs with the same issue.

There is definitely a bad codec somewhere.
 
Hi all,
Back in action here on the forum. Here's what I have:
What version of QuickTime did you move from on the PowerBook?

QT Pro 7.4.1 w/ Final Cut Studio 2 also installed.

What version of QuickTime did you update to on the iMac?
QT Pro 7.2.x --not exactly sure, but it was farily old. w/ Final Cut Studio 2 also installed.

If this information isn't provided, how can anybody test the issue?

To be honest, I was just throwing something into the fray. I added what I could before I left town.


I If some one did, I could pass on to Apple.

Thanks.
 
Ugh. It's getting worse.

I updated Quicktime last night. Here's what the trailer for Bangkok Dangerous looks like on Apple's own website.

Does everyone else see the Lego-sized red bricks that make up most of this image?

BangkokDangerous.tiff
 
Back
Top