“Bad Pixels” Apple ProRes 422

[Josh Kanuck]

I don’t know if this is the ultimate solution, but i have had similar problems with pro rez renders. sometimes if i change the rendering from 10-bit to 8-bit it solves these phantom glitches.

josh

[Jerry Hofmann]

This could be a playback problem caused by a display card issue. Might try reseating that card… if you don’t see it externally, nor in AE, it’s likely not actually recorded with the artifacts, but is a display card being cranky.

Jerry

Apple Certified Trainer

Author: “Jerry Hofmann on Final Cut Pro 4” Click here

8-Core 3.0 Intel Mac Pro, Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D, AJA Io HD, 17″ MBP, Matrox MXO, CD’s

[Simon Chan]

It’s a good theory but we transferred the footage to our other Intel based Mac as well and we have the same issues.

Simon Chan @ Artificial Army
G5 Dual 2GHZ 4.0 Gig Ram, Decklink HD, Atto UL4D, Huge 320R, Final Cut 6.0.2, After Effects CS3

[Simon Chan]

It’s a good theory but we transferred the footage to our other Intel based Mac as well and we have the same issues.

Simon Chan @ Artificial Army
G5 Dual 2GHZ 4.0 Gig Ram, Decklink HD, Atto UL4D, Huge 320R, Final Cut 6.0.2, After Effects CS3

[Jeremy Garchow]

How’d you transfer the clips? Straight off of the card? Do you still have access to the orig. P2 material?

[Simon Chan]

P2 Data is gone. The data was copied on location from P2 cards through laptop to hard drives. Then the data was transfered from the hard drive into final cut.

Simon Chan @ Artificial Army
G5 Dual 2GHZ 4.0 Gig Ram, Decklink HD, Atto UL4D, Huge 320R, Final Cut 6.0.2, After Effects CS3

[Jeremy Garchow]

[Simon Chan] “P2 Data is gone. “

Hmm, that’s not good. No chance for a reimport then, eh?

[Simon Chan]

Well the thing is the glitches don’t exist on the transfered QT’s. They only occur randomly in Final Cut. And actually now in After Effects as well. They don’t happen in the same place. If I re-open Final Cut and play the sequence the glitches will be in a different place than the last time I played it. And when i render the glitches happen randomly in places as well.

Simon Chan @ Artificial Army
G5 Dual 2GHZ 4.0 Gig Ram, Decklink HD, Atto UL4D, Huge 320R, Final Cut 6.0.2, After Effects CS3

[Jeremy Garchow]

[Simon Chan] “Well the thing is the glitches don’t exist on the transfered QT’s.”

Still it sounds like something is bonked with that media and reimporting might cure it.

Do you have a Kona? You are still on a G5?

[Todd Beabout]

We are also experiencing a similar issue here on our systems. Well, one particular workstation really.

These glitches appear completely at random, and not just on the external monitor, but in the Canvas, Viewer, and even in QuickTime when I open the source file.

Blowing the render will sometimes make the glitch go away, but then when we re-render it will show up somewhere else in time, and even another part of the screen. There might be more or less glitches each time we render, it’s a crap-shoot.

I’m going to update that workstation’s QuickTime version to 7.5 (on 7.4.5 now) at the end of the day today and hopefully that will help, but who knows.

It might be worth mentioning that we are running 4 FCP suites off a Terrablock shared storage. In this guy’s room there was a glitch on his screen (canvas). I match-framed it into the Viewer and the glitch was still there. Then I used “Reveal in Finder” and opened the file in QuickTime. Glitch still there. Then came into my edit suite and opened the QuickTime file. No glitch. Hmmm. Went back to his room, and the glitch has disappeared from his FCP project, but was STILL present on the source QuickTime that was open on his box. Shut QuickTime, reopened file and it was gone.

Baffling. Any thoughts?

I’ll let everyone know if the QT update helps. We are on FCP 6.0.3 BTW.

Thanks!

-Todd Beabout
Vazda Studios