-
720p29.97 Animation -> 720p59.94 ProRes?
Here’s my situation: I was given a 1280×720, 29.97, progressive Animation codec Quicktime file. Delivery spec was D5-HD, 720p59.94. My output device can not cross-convert, so I figured, well, if all I need to do is duplicate frames, I’ll just drop the QT into a 720p59.94 sequence and render and layback. What happened was the video looked mostly right, except for a few patches where there were graphic fades and transitions. The render looked like it was skipping certain frames and the dissolves were stepped rather than smooth. I would think that FCP would do the easiest and dumbest thing and just duplicate each frame in the sequence, but it seems that it doesn’t do that. I managed to get what I needed by using Compressor to transcode the original QT file to my desired sequence output spec, but ran into an anomaly there as well. Using Frame Controls ON, with everything set to Fast (especially retiming = nearest frame), it gave me exactly what I wanted (duplicating frames to get from 29.97 to 59.94) except it made a strange output at the top between the 2-pop frame and the first frame of video. There it duplicated the first frame of video onto the nearest 14 or so frames where black should have been. So it went from 2-pop, 59 frames of black, first frame … to 2-pop, 105 frames of black, 14 duplicated frames of first frame. Not a problem in the end, just lopped off the duplicate frames in my finishing sequence. Weird.
So it begs the questions: what is FCP doing to the video when it renders 29.97 progressive Animation into 59.94 progressive ProRes? And if I can’t trust FCP to render correctly, using Compressor yields great but odd results. What would you have done?
-
3 Replies
-
Hi Mark,
Your Animation have been rendered as Progressive and if you put it together with interlaced footage, will always look more choppy because it have 30 instead of 60 images per second.
If you want that to look more smooth, you need to export the Animation from AE at i60fps.[Mark Spano] “I managed to get what I needed by using Compressor to transcode the original QT file to my desired sequence output spec, but ran into an anomaly there as well. Using Frame Controls ON, with everything set to Fast (especially retiming = nearest frame), it gave me exactly what I wanted (duplicating frames to get from 29.97 to 59.94) “
If Compressor is “Duplicating frames” is doing a bad job.
What Compressor must do is from every Progressive frame, produce two different fields.There is “Re-interlacer” plugin in the Re-Vision FieldsKit.
But I insist, better than the Compressor or FieldsKit way is to get the Animation properly exported as i60 from AE.
rafael
PS: Where i wrote 30, I meant 29;98. The same for 60, I meant 59.94 -
[Rafael Amador] “Your Animation have been rendered as Progressive and if you put it together with interlaced footage, will always look more choppy because it have 30 instead of 60 images per second.”
There’s no interlacing in this project at all. I am talking strictly from 29.97 progressive (Animation codec) to 59.94 progressive ProRes.
-
Hi Mark,
Sorry I’ve read your post too fast.
I don’t know what FC do when you drop p29’98 in a p59’84 sequence, but FC doesn’t shines when talking about time-base changes.
This process should be done in Compressor, Motion, AE or so.
Rafael
Reply to this Discussion! Login or Sign Up