Joey Burnham
Forum Replies Created
-
Thanks Dave,
I figured as much. Funny thing is the client’s encoder is seeing the same frame rate as QT does. I KNOW it’s @ 29.97. So I am finding out now what encoder she uses.DAMN this online push. An unnamed studio wants all these assets online instead of me sending digibeta’s out because it’s just “easier” that way.
Hmph. -
Also, if the file is buggy in FCP but is fine in QT, I’ve found that exporting straight out of QT as whatever codec you are editing in in FCP can solve the problem.
Joey -
it should but to be sure check the settings of your footage by right clicking on it and choosing interpret footage > main
-
in FCP and QT they label anything that’s 23.976 as 23.98
you are fine -
Depends on your standards I guess. Only reason I say that is because I’ve had footage rejected that was converted in AE. Depends mostly on your client. In the conversion world you get what you pay for. Quite well definitely works in a lot of situations but if your client is expecting perfection AE is not the way to go for frame rate conversions.
-
what is your budget? you are correct in nesting your comp into a new 1920 x 1080 comp at 23.976 (NOT 23.98), then scaling to fit. Render that out and take that in your NLE. The conversion from 23.976 to 59.94 (29.97) isn’t pretty unless you go through a proper converter. (Snell and Wilcox, Teranex, etc)
Joey -
in FCP if a file has an embedded alpha it figures that out when you superimpose in the timeline. no composite modes are needed
joey -
render to an uncompressed format and encode your flv in another program. AE is not the greatest compressor.
-
Probably. You can patch out the SD out from the deck and let it do the downconversion. I did a side by side comparison once and if I remember correctly the deck was a TINY bit better.
-
I’ve never been able to downconvert on ingest, just on output…
Any thoughts?