In the wee brain dead hours of a double shift festival I'm contemplating the age old problem of batch imports of .movs that have changed in length. I'm on a show where they have put motion effects on imported graphics and some of them show a little hitch during their moves. I figured this is a by product of the motion effect but then at the end of the show where we include graphic elements in their raw form I noticed the same type of glitch on some of the graphics when they didn't have a motion effect. A little detective work discovered that the original temp graphic was indeed one frame longer than the final graphic. I get why these batch import problems happen but I'm curious about how frame rate plays into this. I was also told that at some point one or more of the graphics were delivered at a true 30 frames not 29.97 which is what the final graphics came in as. In fact this alone may account for the one frame discrepancy but I'm not
sure. These clips are without sound so what under the hood compensation is Avid doing when a true 30 fps .mov is imported into an HD 59.94I 1080 project. I know about ignore QT rate console command but without invoking that is Avid really going to alter the .mov on import that would have a a negative effect on the motion quality like a skipping frame at some point. Just curious if the crux of our current issue is a by product of the change in frame rate or if the graphics person inadvertently gave us a final rendered .mov that is one frame longer. Curious what others think might be the primary culprit.
John Moore
Barking Trout Productions
Studio City, CA
bigfish@pacbell.net
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (1) |
No comments:
Post a Comment