-
m2v render problems…HELP!
After getting my copy of AE CS3 I was pretty psyched about the m2v output option. I had been using an old version of QT Pro and I hated it due to the washed out blacks that accompanied the final file.
However, I am having the hardest time with getting a good file rendered out. I either have a problem with stuttering motion or aliased edges. I have been playing around with the field order at every link in the chain . I usually just render out a QT Ref file from Avid, import it into after effects, and then render out. Field order defaults to none in this process. Keeping all the possible field order settings at none (or progressive) I get a weird strobey effect in motion clips. I then change d the output in AE m2v to field order lower first. Motion looks better but I get a lot of aliasing. I went ahead and interpreted the QT ref so it was also lower field first and did the same thing…same result. I then changed it in the output render settings to lower field first…same result. I am beginning to get really frustrated. The picture itself looks great aside from the problems I am having. Nice deep blacks and a good range of contrast. But that means nothing if I can figure out the problems here. I even rendered out a physical QT from Avid specifying lower field first and made sure all the other settings were set to lower field and still got the same problem. HELP!
-
5 Replies
-
What is your source footage’s field order? You should interpret the footage inside of AE as whatever it is (None for Progressive), if you see bad aliasing around the edges try enabling ‘Preserve Edges.’
What are your settings for rendering to m2v? Do you see the same artifacts/aliasing when you render Lossless?
Are you setting the output to render fields in the Output Module, the Render Settings or both?
Darby Edelen
DVD Menu Artist
Left Coast Digital
Aptos, CA -
What is your source footage’s field order?
I am assuming lower field although when rendering out a QT ref movie, you do not have that option. I tried Animation codec with a lower field order and got the same results. Everytime i import the QTs though, it does not automatically interpret lower field even if I set it in the Avid (or I ask my editor to do it) I have always checked the preserve edges box.
What are your settings for rendering to m2v?
29.97 drop frame lower field VBR best quality
Do you see the same artifacts/aliasing when you render Lossless?
I havent tried it but its worth a shot
Are you setting the output to render fields in the Output Module, the Render Settings or both?
I believe I tried it in the output module and both the render settings and the output module.
Any help would be greatly appreciated. I am getting pretty frustrated after trying to solve this problem for a couple of days. Since I am not the editor here, I am unsure if possibly there is something that I am missing when the footage is sent to me. Could it possibly be upper field first?
-
[Bill Paterno] “Could it possibly be upper field first?”
Maybe, but doubtful if you’re working with NTSC. A Lossless render out of AE will tell you whether it’s the m2v codec (or settings in the output module) or not so I’d try that first.
Darby Edelen
DVD Menu Artist
Left Coast Digital
Aptos, CA -
One more thing I was thinking of. The Quicktime is D1 NTSC as oppposed to 720×480. Should I be exporting from Avid a 720×480 QT?
-
Okay…I forgot that I had a copy of BitVice on my one computer. So, long story short, I am able to encode a sweet m2v with the program. Not sure what the problem was using AE but I dont care at this point. I have a deadline I need to meet! Thanks for the help.
Bill
Reply to this Discussion! Login or Sign Up