[321launch]

That’s exactly what I ended up doing. Worked great…thanks!

[321launch]

Unfortunately, I need the 4:3 stuff to be full-frame, not letterboxed on this particular project, so I redesigned the menus to work in 16:9 and also when cropped to 4:3. But at least it works consistently now.

Thanks agin.

[321launch]

Thank you for your input. I am rethinking this and will probably take Noah’s advice… it’s just a shame you can’t use the wider screen when you are designing menus.

[321launch]

You might be right about the software version, the problem did seem to start when we upgraded to FCP 6. What version of FCP are you running?

“I changed the field order from Not Set to Lower (Even).”

So when you brought your clip in, the field dominance property defaulted to “Not Set”. Ours always default to “Lower Field”, which we then have to change, and this is our problem.

Not sure why you can’t duplicate the aliasing problem, maybe it is specific to our configuration, but it is definitely seen by all six of our editors on all six of our systems.

Thanks, by the way, for all the testing you’ve done on this!

[321launch]

I do understand that all NTSC footage is interlaced, that is exactly why FCP’s incorrect interpretation of our renders is a problem. If you take something that is frame rendered and interpret it as lower field, it looks aliased. When you change the clip’s properties so that the system understands that it is frame rendered, everything looks great.

“Are you talking about field ORDER, field DOMINANCE, or color framing?”

I didn’t know there was a difference between field order and dominance, but I was referring to working at different post houses, some used lower-field systems and some used upper-field systems, but all of them were NTSC. None of them were TV stations though, perhaps in the broadcast world it has to be lower field.