[Frank Ruggiero]

Hi Steve.

Thanks for answering my post. I am working in a 59.94 comp. I did not create it, just modifying it. I noticed there was a prerendered quicktime in the project and it is not interpreted as upper field. Shouldn’t all hd 1080i be interpreted as upper field first?

[Frank Ruggiero]

Where is the final piece going to? Back to Digital Beta?

Definitely do not use Targa sequences for Final Cut.

If it is going to Digital Beta, I would render with the codec of the output board.

If you are not sure, I think its safest to render with animation codec set at highest.

[Frank Ruggiero]

Hi Dave,

Yes, I am really concerned about field issues more than anything. I really need to see the video on some interlaced monitor. As far as legal levels, I plan to use Color Finess’s scopes to make sure my values are within range….

FR

[Frank Ruggiero]

Thanks for your help guys. One other question; would you recommend rendering out in the 601 or RGB color space?

Thanks again,

Frank R.

[Frank Ruggiero]

Hello,

I usually would render animation codecs, but the client wants to cut down on render time in the Avid.

[Frank Ruggiero]

Thanks for you quick answer…

So as far as your concerned, the Adrenaline will except a Meridian codec without an issue (besides the artifacting you mention)?

[Frank Ruggiero]

what happens if you “Place” the .AI file into photoshop? Do you still have those issues? If not, “place” it into photoshop at the highest scale you need and then import the psd (now a rasterized pixel file) in After effects.

Sometimes, I think continuous rasterize can give those edge problems, especially when you are scaling or panning…

[Frank Ruggiero]

I would interpret the fields seperated (probably lower field first) in the interpret box, and then render it out without any fields.

But if your quicktime file is ultimately going to end up being broadcast off of NTSC, I would be tempted to render with fields. If it is just going to be on a computer monitor, then don’t render with fields.

See if the image looks better….

-Frank R.

[Frank Ruggiero]

Hello,

Thank you for responding to my post…I did revisit my issue. Unfortunately, I am still at a loss. I really think it is the limitations of NTSC. I only notice the problem while there is vertical animation. I tried re-rendering at 60fps and putting it in a 29.97 comp. going lower field first but still no improvement. I think it of being like a credit roll in which the speed must be exact or you will see artifacts due to the iinfrmation being caught in between the scanlines.
i may have to change my move so that there is less vertical movementt, ii am not suree what else i can do from here.

thanks again for your information. they were good ideas.

[Frank Ruggiero]

Hi Mylenium,

Thanks for your advice. I tried many different techniques, from motion blur to rendering 60fps. to different field orders. I am starting to feel that this issue may not be a field issue, but more of an NTSC issue. I get some aliasing on the edges of animation that is going up and down. Some of my animation looks fine, it is really only the segments that have vertical movmement. I am starting to think that may be the issue, and if that is the case, my only resort would be to change the animation.

I hoped that rendering out at 60fps could help, but it looked exactly the same. I am looking at the quicktimes directly out of C4D without going through After Effects, and I see that steppiness on the graphic, so I know if the problem is to be fixed it would have to be dealt with in C4D.