-
Vertical Lines in FCP ftg & “The Big No-No” (screen shot included)
Hello the COW! (this is also posted in AE and Auto Duck forums)
OK, so I did the big no-no…I updated my OS and updated Final Cut Pro in the middle of a project. Ugh. I don’t know what happened, but here are the details:
Yesterday(July 13), I was working with some green screen footage exported from FCP to AE, in 16-bit. I was able to get a great key very easily, and there was a noticeable difference between the 8-bit key, and 16-bit key. The 16-bit was MUCH cleaner.
OK, fast forward to today(July 14)… I updated my Mac OS from 10.4.1 to 10.4.2, and updated to FCP 5.0.2. Why? Because I use Automatic Duck plug-ins to Import/Export ftg between FCP and AE, and the Automatic Duck people said that FCP 5.0.2 fixed the bugs that was disabling video preview when using BlackMagic cards. With me so far?
OK, so now when I open up the same project I was working with yesterday, in 16-bit, the footage has weird vertical lines running thru it, but when I switch to 8-bit, the footage looks fine. Here’s a side-by-side comparison | VIEW IMAGE |
I don’t know if the updates have anything to do with this, but that’s the only thing that’s different from yesterday. I can work in 8-bit, but the comp I’m working on looks much better in 16-bit. I can render out all of the green screen ftg(with keys) at 8-bit, then import the keyed clips back into the project, put them into my comp, and then render the full comp at 16-bit. But, WHY is this happening??
Ugh. Any feedback is welcome!!
Thanks!
Jason -
9 Replies
-
UPDATE:
I also tried re-capturing(both with FCP and Decklink 5.0) footage with the new updates(OS X 10.4.2 & FCP 5.0.2), but I still get the same lines when I work in 16bit space in AE.
Thanks,
JAson -
A wild guess but take a look in the Shake forum where there have been discussions about the 10bit codecs not working properly in QT7 –
Good luck
Paul
Freelance DS/Symphony
London -
What are your render settings in FCP? Have you tried changing them, or deleting your renders and then re-rendering?
gir
-
Gir-
In FCP, I am capturing at 29.97fps, uncompressed BlackMagic, 10-bit, NTSC, 4:2:2, 720×486(D1). These lines you see occur when I try to work in 16bit space in After Effects. The clips look fine in FCP.
Yes, after I performed the upgrades, I deleted all media, re-captured, but still get those funky lines in 16bit space in After Effects.
Thanks for your response!
Jason -
Are you using the Apple or the BM 10-bit codec?
Try removing the BM codecs and recapture with the Apple codecs. I’ve seen this sort of situation happen where the AE render engine get’s “confused” by which V210 codec to use.
Hope this helps,
Jason Rodriguez
Virginia Beach, VA -
i got this problem too.
-
I’ve seen the same problem here too. Haven’t had time to track it down yet though…
Chris Tomberlin
Editor/Compositor/Owner
OutPost Pictures -
OK, I’ve narrowed down the problem, but unfortunately don’t have a solution. The problem is during the importing of any “v210” codec into AE. Basically, by turning things on and off in the AE preferences text file, I’ve been able to determine that you can bring in footage at 16bit (as long as its not v210) and you won’t get the green lines in AE when set to 16bit. You can also render out to a “v210” codec and no green lines. Unfortunately, if you are capturing uncompressed 10-bit in FCP, you are capturing with a v210 codec.
This must be a Quicktime bug. Anybody geekier (and I mean that in the best possible way) than me able to support this argument?
Thanks
Chris Tomberlin
Editor/Compositor/Owner
OutPost Pictures -
Chris-
Thanks very much for sharing the fruits of your troubleshooting! I agree, it must be a QT bug. Hopefully a patch will be issued soon. I’m going to try re-capturing with non-v210 codecs and see if I like the results.
Thanks!
Jason
Reply to this Discussion! Login or Sign Up