-
HD field problem
Hi all. I hope someone can help me make sense of this.
I have a very basic HD project that is basically keyframed text over a BG. Nothing to dramatic…. just a :02 move vertically and scale down.
My composition settings are HDTV 1080 29.97.
My render setting in the render cue is set to Upper Field First and I am rendering uncompressed at 1920×1080.
After the render, I am taking the movie file into my Smoke for QC on an HD monitor. All settings on the Smoke are correct and confirmed.
For some reason, the field dominance in my AE movie file is reversed.
I went back into my AE comp and changed the render setting to Lower Field First and this fixed the problem.
This really makes no sense to me, as I know Upper Fields should be the correct way to render out my comp.
I must be missing something… but I’ve been in and out of all of my settings and can’t find a thing.
Unfortunately I’m not on my system right now, so I can’t upload any screenshots or explore the problem further until tomorrow morning.
Thanks for any suggestions you may have.
Regards,
Bob
-
4 Replies
-
Hi Dave,
Thanks for the quick response.
Everything is interpreted as upper field first.
The odd thing is that the keyframed text layer shows all the signs of reverse field dominance when viewed on the HD monitor.
As I said, it does correct itself when rendered lower fields
Thought I was an intermediate user but this one has really thrown me for a loop.
Forgot to mention that this is CS3 (maybe a bug?).
Bob
-
Forgot to mention that this is all graphics… no camera.
-
The one .mov (animation codec) I have is upper fields and interpreted as such.
The client is looking for 1080i deliverable.
I’d like nothing more than to do the progressive workaround though (:
-
Hey Dave,
Thanks so much for your help!
My (Smoke) system is actually set up with a TriSync of 59.94 for any and all HD projects. There’s definitely something going on there.
Thinking back on earlier projects, I’ve had some interlacing issues bringing in HD movies from AE. A lot of the time we resolve by just going with progressive.
I’ll give you a shout out when I figure this thing out… definitely a lot closer now.
It seems a bit of anomaly (or maybe just a brain-fart) on my end. I’ll know better in the morning.
Thanks and regards,
Bob
Reply to this Discussion! Login or Sign Up