Hey wait I know. The time code head in the QT Player must be out of position. I'll just go in and adjust the head stack. Oh wait there's no head stack. ;-( Some days I miss my tentelometer.
--- In Avid-L2@yahoogroups.com, Mark Spano <cutandcover@...> wrote:
>
> You may also have better luck (particularly with the TC burn in losing or
> missing frames) if your H.264 encodes are Keyframes: ALL and Frame
> Reordering: OFF.
>
>
> On Tue, Jul 9, 2013 at 3:07 PM, johnrobmoore <bigfish@...> wrote:
>
> > **
> >
> >
> > I've been using QT Pro to deliver all my file based masters on an SD
> > series and I've had no issue but that doesn't negate you comments because
> > I'm using save as self contained on those. I use QT Pro 7 because it reads
> > the time code burn in put in by QT change. I use to use Sorenson 4.5 for
> > the same kind of things but later versions stopped recognizing the Time
> > Code burn in from QT change. It was frustrating but even though in the
> > interface window the TC burn in showed up upon export it was either black
> > or no TC burn in I can't remember which by my bet would be it came out
> > black. Unfortunately I can't install Sorenson 4.5 on newer OS systems
> > because the installer is legacy. I'd bet if it was already installed on an
> > older startup drive and I upgraded the OS on that disk it might work but I
> > haven't had the time to try that.
> >
> > I will keep your QT comments in mind in the future. Primarily I do this
> > for screening copies that aren't going to be used in a critical metadata
> > situation.
> >
> > One other possibility is that the protools operator was judging sync drift
> > by the QT change TC burn in. I've noticed in my drop frame NTSC world the
> > burn in will sometimes be a frame or maybe 2 frames off at any given frame
> > relative to the QT time code track. This happens with time code that was
> > created in the Avid export and also with time code later added by QT
> > change. The burn in offset is not cumulative so it's not a drift. I would
> > think it has to do with the QT underpinnings and how the time code text
> > track is generated. For screening purposes it's fine and saves a ton of
> > render time.
> >
> >
> > --- In Avid-L2@yahoogroups.com, Mark Spano <cutandcover@> wrote:
> > >
> > > You can't conform anything in Cinema Tools if it is GOP which H.264 is,
> > so
> > > forget that. Here is your problem:
> > >
> > > "exported the QT ref movie using QT Pro 7.6.6 to an H.264"
> > >
> > > QuickTime Pro exports are notoriously bad at preserving proper metadata
> > > like Constant FPS and usually default to Average FPS which doesn't make
> > any
> > > sense to any other application other than QuickTime Player. I would do
> > this
> > > export in Compressor - always preserves proper metadata. No Compressor,
> > > then maybe Streamclip, which allows you to bake in the metadata in the
> > > export dialog.
> > >
> > > I never use QuickTime Player Pro to export anything. Ever. It is so bad
> > at
> > > so many things and most of those are in its exporter. QuickTime Pro is
> > > great for Save As, and that's about it.
> > >
> > >
> > > On Tue, Jul 9, 2013 at 8:09 AM, John Pale <pale.edit@> wrote:
> > >
> > > > Sounds like corrupt QT metadata. You can fix this with Cinema Tools, if
> > > > you have it. Open the file.. Use the conform feature and set it to
> > 29.97.
> > > > Since the file already is 29.97, it won't actually do anything but fix
> > the
> > > > metadata. The change is instantaneous, no rendering or re-encoding.
> > > >
> > > > You might be able to do it with QTchange as well, but I've never
> > attempted
> > > > it with that program.
> > > >
> > > >
> > > >
> > > >
> > > > On Tuesday, July 9, 2013, John Moore wrote:
> > > >
> > > > > **
> > > > >
> > > > >
> > > > > So as if the file based world hasn't boned me enough today I get one
> > last
> > > > > red hot poker. The show I'm onlining at home I exported a QT ref from
> > > > > Avid. I then use QT change to add a TC burn in. Finally I exported
> > the
> > > > QT
> > > > > ref movie using QT Pro 7.6.6 to an H.264 and I guess my setting for
> > fps
> > > > was
> > > > > set to current or matching the source. Now the QT Plays fine and the
> > TC
> > > > > burn in matches the time code I added back using QT Change. The music
> > > > > audio house is complaining the movie file fps doesn't match the AAF
> > which
> > > > > is 29.97 drop. Some how the audio guy is saying the .mov is 76.85
> > which
> > > > I
> > > > > know can't be right. Now I've never bothered to think about this
> > before
> > > > as
> > > > > it's never been an issue. I know 1080i/59.94 is equivalent to 29.97
> > > > frames
> > > > > per second. So assuming the audio house is using protools why would
> > the
> > > > qT
> > > > > that shows info as 59.60 fps, which I assume is the typical QT
> > inaccurate
> > > > > fps , be an issue to slave with the aaf at 29.97? I'm currently
> > > > > redoing my QT export only this time I set the frame rate to 29.97. Is
> > > > the
> > > > > audio house in error about this or do I always have to export a
> > 29.97 QT
> > > > to
> > > > > match the aaf frame rate. And why is the aaf 29.97 when the sequence
> > is
> > > > > 59.94. Man I feel like everything I know is wrong today and today's
> > only
> > > > > Monday.
> > > > >
> > > > >
> > > > > John Moore
> > > > > Barking Trout Productions
> > > > > Studio City, CA
> > > > > bigfish@ <javascript:_e({}, 'cvml', 'bigfish%40pacbell.net
> >
> > > > ');>
> > > > >
> > > > > [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]
> > >
> >
> >
> >
>
>
> [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 (7) |
No comments:
Post a Comment