I believe there is a caveat when it comes to changing frame rate with QT change and some NLEs including Avid. The interface issues a warning prompt something to the effect that some NLEs won't register the QT Change frame rate changes. Not sure of the specifics of when it will or won't work correctly.
--- In Avid-L2@yahoogroups.com, electropura212 <electropura212@...> wrote:
>
> As Cinema Tools is no longer available (if you don't have access to a
> legacy FCP), an alternative would be QTChange.
>
> On Wednesday, November 14, 2012, Mark Spano wrote:
>
> > Any time I get graphics at 24.0 or 30.0, I immediately conform these in
> > Cinema Tools to 23.976 or 29.97 PRIOR to importing in MC. Because, yes, as
> > you discovered, MC will attempt to compensate, usually dropping a field or
> > frame every now and then.
> >
> > As far as batch importing: if the length differs at all, it will not work.
> > That's far more destructive - I've seen severe frame dropping or
> > duplicating to match the original length.
> >
> >
> > On Wed, Nov 14, 2012 at 4:31 AM, John Moore <bigfish@...<javascript:;>>
> > wrote:
> >
> > > **
> > >
> > >
> > > 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@... <javascript:;>
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Search the official Complete Avid-L archives at:
> > http://archives.bengrosser.com/avid/
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
> [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 (4) |
No comments:
Post a Comment