No. I wasn't even there. I'm the editor.
Just out of curiosity: why? The F3 can be used as a still camera? What would that do to the audio sync?
My quandary is why is the sync out in the timeline and in the source monitor, but when the exact same shots are output in a Quicktime, without changing anything, they are in sync on the output. On top of that, the second camera (Red Scarlet) is in perfect sync. Again, no green dots.
VERY strange.
.Tony
--- In Avid-L2@yahoogroups.com, Jim Gilson <gilsonjamesj@...> wrote:
>
> you didn't, by chance, shoot stills during the video shot?
>
>
> Cheers,
> jim
>
>
>
> -----Original Message-----
> From: Tony Breuer <tonybreuer@...>
> To: Avid-L2 <Avid-L2@yahoogroups.com>
> Sent: Mon, Apr 23, 2012 2:30 pm
> Subject: [Avid-L2] Re: Question about Autosync and double system sound...
>
>
>
>
>
> Jim, Thanks very much for your reply. I double checked and there are no dots, green or otherwise, on the timeline or in the clip on the source monitor.
>
> I sure as hell can't figure this one out.
>
> Tony Breuer
>
> --- In Avid-L2@yahoogroups.com, Jim Gilson <gilsonjamesj@> wrote:
> >
> > if your playback, on the timeline, is a "green dot" effect, it will go out of sync.
> >
> >
> > Cheers,
> > jim
> >
> >
> >
> > -----Original Message-----
> > From: Tony Breuer <tonybreuer@>
> > To: Avid-L2 <Avid-L2@yahoogroups.com>
> > Sent: Sat, Apr 21, 2012 12:04 am
> > Subject: [Avid-L2] Re: Question about Autosync and double system sound...
> >
> >
> >
> >
> >
> > Steve,
> >
> > Have you tried outputting the footage to whatever our final will be? I'm cutting a feature doc where some scenes were shot on an F3 with a Red Scarlet as a second camera. I thought the F3 footage was a couple of frames out of sync but oddly the red scarlet was in sync when I aurally synced the two cameras (The time codes were NOT jammed-thank you production crew). I tried slipping the audio on the F3 thinking it some how drifted. I checked to make sure they were all the same frame rate (they were). But when I output a Quicktime the F3 footage was again out of sync while the timeline was in sync. I slipped the audio on the timeline back to where it looked out of sync on timeline playback and out put again. Voila, the out put was in sync. I have NO idea what is going on but I now edit with the timeline out of sync but knowing the output will be fine. The client (every time we screen from the timeline) says "YOU'VE got that shot out of sync" but says nothin g whe n screening a Quicktime.
> >
> > Does anyone have a gun I can borrow? (Bob Z's shotgun will do).
> >
> > I don't know who or what to shoot first: the DP? the AC? Sony Chairman? The client?
> >
> > Anybody else had this problem?
> >
> > I'm learning patience and Zen like acceptance. Deep breathing helps.
> >
> > Tony Breuer
> >
> > --- In Avid-L2@yahoogroups.com, Steve Hullfish <steve4lists@> wrote:
> > >
> > > I have a question:
> > >
> > > I shot something multicam with two Sony F3s and a high end mixer/recorder (I don't remember what). We jam synced the timecode at the beginning of the shoot and both cameras appeared to be on the same timecode as the audio recorder, but now that I'm using Autosync using the timecode to match the audio to the cameras, I notice that the audio is probably LEADING video by two frames. Is there a way to Autosync but off-set the audio by a specific number of frames? Obviously I can just slip everything by those two frames for every shot once I get it done, but I'd rather have the audio actually in sync in the clips. I could also do it by IN point on every clip, but then I have a lot of clips to do and would rather have a fairly automated system.
> > >
> > > The sound guy ran audio continuously through 2+ hours of shooting. The two F3s started and stopped a LOT.
> > >
> > > Steve Hullfish
> > > contributor: www.provideocoalition.com
> > > author: "The Art and Technique of Digital Color Correction" (2nd Edition now available)
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
No comments:
Post a Comment