Forum Replies Created

Page 1 of 4
  • Simon Chan

    July 16, 2008 at 7:28 pm in reply to: “Bad Pixels” Apple ProRes 422

    Only solution we came up with was to render it all out Uncompressed 10bit then go into the source QTs and export Tiff frames out where the bad pixels were and replace those frames in Final Cut. Then export another Uncompressed 10bit QT out for our master…

    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

    July 9, 2008 at 9:58 pm in reply to: “Bad Pixels” Apple ProRes 422

    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

  • Simon Chan

    July 9, 2008 at 9:55 pm in reply to: “Bad Pixels” Apple ProRes 422

    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

  • Simon Chan

    July 7, 2008 at 9:07 pm in reply to: “Bad Pixels” Apple ProRes 422

    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

  • Simon Chan

    July 7, 2008 at 8:33 pm in reply to: “Bad Pixels” Apple ProRes 422

    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

  • Simon Chan

    July 2, 2008 at 6:25 pm in reply to: “Bad Pixels” Apple ProRes 422

    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

    July 2, 2008 at 6:23 pm in reply to: “Bad Pixels” Apple ProRes 422

    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

    January 17, 2008 at 10:01 pm in reply to: DON’T install QT 7.4 if you use after effects

    Im trying Targa sequence.

    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

    January 17, 2008 at 9:59 pm in reply to: DON’T install QT 7.4 if you use after effects

    Doesn’t work…

    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

    January 17, 2008 at 9:46 pm in reply to: DON’T install QT 7.4 if you use after effects

    Im testing your solution right now.

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

Page 1 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy