[Daniel Spagnoli]

Thanks to Adolfo.

Exact Same problem here, 8 core mac, radeonHD card, RAM preview slow.

Disabled my blackmagic card…problem solved…

is this bug fixed in CS5?

Dan

[Daniel Spagnoli]

Thanks Dave and Steve…

I ended up just exporting my overlays out of AE interlaced with alpha and plopping them on top of the captured video in FCP, it laid back to tape (and air) just fine.

Something was screwy with the fields in the video (or the capture), AE wasn’t recognizing it as interlaced and forcing the field separation was causing the glitches on export. I probably could look deeper into it and figure out the true “technical” solution was, but what works, works…right? 🙂 Thanks again for the help!

-Dan

[Daniel Spagnoli]

hey Nat,

What program is telling you it is interlaced?

If it is FCP, ive noticed that sometimes if the settings match what it thinks “should be” an interlaced comp, it will set it to be, even if it isn’t.

You can manually turn off the field dominance in FCP, and if it is a True 1080p, you will get the full resolution.

If you are getting field lines in QT or something, that’s a whole other problem, but don’t ever trust what FCP “thinks” your comp is, it is wrong…a lot…trust your eyes :).

-Dan

[Daniel Spagnoli]

Thanks Dave!

The entire sequence is actually an export from Maya so its defiantly a true 1080p, and while the end broadcast format will be 1080i, we are just trying to lose as little quality as possible passing it from one designer/producer to the next. (have had projects were someone will deinterlace/ then render and reinterlace/only to have the next editor deinterlace it again)

I’ve actually have always used the render queue, but have only been dealing in the world of TV fields for a short time, never thought to look for the field settings in the render settings (I have always been checking the codec settings/output module).

Problem Solved, thanks again!