-
“Bad Pixels” Apple ProRes 422
-
One more thing…
Tried to switch the sequence to 10-bit, and problem persisted.
-Todd
-
What format and frame rate are your clips, Todd?
-
We are using latest QT Version 7.5 (149.5)
Final Cut 6.0.4
Your experience is exactly like mine. After Effects isn’t as bad as Final Cut. In fact After Effects hasn’t had nearly as many glitches and they vanish pretty quick. I think its a bug in the codec using ram…
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 -
Our clips are 1080p 24p and 30p. We shot 30p on accident. The glitches exist in both 24p and 30p clips…
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 -
Alirght guys, do me one favor.
Duplicate one of your clips at the finder level. RIght click on that copy and choose OPen with > Cinema Tools. Depending on the frame rate of the clip, confrom it to it’s frame rate. So if the clip is 29.97, confrom to 29.97. If it is 23.98, conform to 23.98. Import that clip into FCP and see if it glitches.
Make sure to Duplicate the clip first. If it works for that one, don’t go doing a bunch as there’s one thing to check and that’s timecode.
Jeremy
-
Jeremy, our sequence is standard 525 NTSC 29.97. We are using ProRes 422 as both clip and sequence settings, even though I tried changing the sequence settings to 10-bit uncompressed to no avail.
ProRes is something that is newer to us, but we have switched over to doing a lot of projects in that format due to small file sizes, and fairly lossless quality (or so we thought).
I’m going to be trouble-shooting this one for a few days, so I will post back if I come up with something, Simon. I am kinda glad that this problem is happening somewhere else, only because 2+ people troubleshooting is certainly better than just me.
Simon, it also sucks that it appears the QuickTime update won’t fix the problem.
Let me know if you come up with anything.
-
Todd, Simon’s footage is AVCINtra based P2, what’s yours?
-
Our footage is SD NTSC 29.97 from BetaSP and/or D-beta source captured through a Kona LHe component (beta) and SDI (d-beta). We also had the exact same problem yesterday with some HDV 1080/60i footage captured through FireWire into it’s native codec.
The same clips captured in a different room are OK. This problem is very, very weird.
The only other factor I can think of is that this problem box is running Tiger. We have 2 Tiger boxes and 2 Leopard boxes, but it doesn’t really seem like the OS would be affecting clips at random on just one of the Tiger boxes. We are planning an upgrade on these to Leopard soon anyways, so I’ll let you guys know if that for some strange reason cures the problem.
Jeremy, I haven’t tried the Cinema Tools thing yet but I will try to get in that room and reconform the clips to 29.97. That is if the glitches are there today. So strange…
-Todd Beabout
Vazda Studios -
Todd, your problem sounds a bit different from Simon’s problem.
Have you checked the RAM in the offending machine?
-
Just wanted to post back because there is another thread relating to this same problem here:
https://forums.creativecow.net/thread/8/987007
Simon, any luck resolving the problem on your end?
-Todd Beabout
Vazda Studios
Reply to this Discussion! Login or Sign Up