Hi-quality renders with maya

[beaker]

I do everything at 24fps and then do a pullup in post to whatever frame rate I need to goto(ntsc or pal).

[Deepray]

like the 3:2 combustion pulldown? in this case... wich? WWWSS?, WSSWW?... :surprised

[alexx]

i would suggest rendering with motion blur instead of rendering in fields..
i stopped rendering in fields some years ago and that helped with a lot of problems.


cheers

alexx

[DesignDawg]

Maya's "fields" aren't actually fields at all, as it turns out. They are just split-line renders....kinda a "hack" of fields. If you need fields out of maya, you definitely need to render on the .5's and render fields out of your compositing app. It works great. --But yeah, doing animations at 24 FPS and doing a 3:2 pulldown on them will give your animation a sort of "filmier" look, just because it will move the way film does on TV. However, you'll find that, with fast-moving animations, you may be better of just going with fields.

Ricky

[jason-slab]

so if i'm not outputting to fields, then when i import to after effects do i specify (in the interpret footage dialog) separate fields or do i leave it off?

|jason

[DesignDawg]

If you are rendering half-frames, you will import it and tell it NOT to separate fields, but that your footage is 60 FPS. If your footage is 60 FPS, but your composition is 30 FPS, when you RENDER your comp, tell it to render fields, and it will create the fields from your 60 FPS footage. It will properly interlace it.

Ricky

[jason-slab]

ah i see

thx

|jason

[Grooveholmes]

SHEESH. Fields... What a pain in the ass.:annoyed:

[ilasolomon]

just forget about field rendering with maya! (but if you have
enough time to render a frame twice with maya's slow rendering
engine,...it's ok!)

[Grooveholmes]

This may be a retarded question, but will HDTV's do away with the need for field rendering?

[DesignDawg]

No, it's not a retarded question, but the answer isn't completely straightforward. The quick answer is no. The "i" in some HDTV standards (1080i, for example), stands for interlaced. But there are "i's" and there are "p's" (as in 720p). The various resolutions for HDTV call for different types of renders.
--But the part of the answer that's not black & white is this: You don't necessarily "need" to render fields as it is, with NTSC. You can render non-interlaced, just at 30FPS. No problem. You just get a slightly smoother output if you render fields. (smoother motion-wise, that is.)

Ricky

[Grooveholmes]

Ok I hear ya DesignDawg.

So Basically once HDTV starts blowing up are we going to start having to render things out 3 different ways? Especially during the transition period as it slowly starts to switch over. Seems like from my exp. when you start saying stuff like 'its not completely black and white' then all kinds of new problems come up. :shrug:

[Deepray]

some people told me about render a twice resolution too. it's ok for a smother aliasing?... it's about a maya bug when it renders subdivs edges with antialiasing artifacts.

[beaker]

>>some people told me about render a twice resolution too. it's ok for a smother aliasing?... it's about a maya bug when it renders subdivs edges with antialiasing artifacts.

No it's not a bug, you just need to turn up the quality settings on the aliasing and mess with the multipixel filter settings. Some people render at 2x the resolution because it is sometimes faster than rendering with very high antialiasing settings.

[Mangaka604]

I've been doing work for stuff going out to Asia in HDTV for the past 2 years and now I've just gone back to PAL and I must say, doing animation in HDTV is so much nicer.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.