OH CRAP!

[Barry Bishop]

I was recording audio using the Sony EX1 and recording video from the Scarlet. When I drop the native R3D into premiere and the audio track from the Sony EX1 they don't sync up. It seems the audio is drifiting. Both were recorded at 30fps. Did I just botch this!

Or is it the RED mag is playing 23.97 and i need to debayer the footage to 30fps?

 

[Andy White]

Did you record 30P on the EX1? The frame rate for that is 29.97P (if I remember!) - and Scarlet is 29.97.

Maybe check the timebase of both sets of footage (in separate timelines)?

I'd hazard a guess it might be the timebase of the EX1 footage? Do you have any clapperboards or something to take a sync point from? Basically, are they 'always' out of sync or 'drifting' out of sync?

Maybe start a new Premiere timeline and rebuild?

* Just a thought - did you roll video & audio on the EX1? That might be your quick answer to run them both and see what happens with sync... and, if you didn't have claps, you can matchframe quickly

Hope it's just a gremlin

 

[Barry Bishop]

Ok I went inside Premiere and it says 23.97 frame rate...but I recorded according to the LCD at 30fps. Is this cause CINE-X is defaulting to 23.97 till you export it?

Frame Rate 23.97
Data says Record Frame rate 29.97

Is it safe to assume because of the nature of the SDK Premiere is using the 23.97 as well? Thus upon exportation will it actually read properly? Im debayering some footage now, but would like an answer before its done.

 

[Brad Webb]

Did you change the Scarlet record time base to 29.97fps and not just your fps?

 

[Andy White]

What's the file saying in RCX? Is it's timebase 29.97 (30)?

I don't use Premiere, but it it sounds like a gremlin... open up a new premiere timeline and set it to 29.97. Then drop in your files and see what happens?

 

[Kevin Marshall]

Did you just change the FPS option on the Scarlet to 30fps, or did you actually go into the menus and change the project to a 29.97 timebase? Because the former would yield an overcranked 23.98 clip, rather than a normal 29.97 clip.

EDIT: Well looks like a couple other people beat me to it....

 

[Barry Bishop]

Did you change the Scarlet record time base to 29.97fps and not just your fps?

Um checking into this now!

 

[Blair S. Paulsen]

Bear in mind you have both a "base" or project frame rate AND the frame rate you chose to record at. Did your LCD read "Varispeed" in the lower left where the audio meters would otherwise be?

You do not have to use matching base frame rates when using multiple cameras but I highly recommend it. In any case, if the audio was recorded on a camera set for 29.97 and that is your target frame rate for the finished product you might be best off just re-rendering the 23.976 at 29.97 and then syncing.

Cheers - #19

 

[Barry Bishop]

The agency is going to hate me!

 

[martinnoweck]

what agency?

 

[Marc Wielage]

All these things can be fixed, given enough time and money. I have dealt with cameras shooting at different frame rates before. If the pictures can merge onto a single timeline, and your edit system can deal with the frame-rate disparity, then all you have to do is make a sound pull up every :30 seconds or so to pull up X number of frames to get the sound in sync.

People sometimes forget, the sound drives everything in multicamera scenes. If the sound is drifting (or, as in this case, the picture is drifting relative to sound), then you're screwed. Keep chopping away at the sound until it's back in sync.

Stuff like this is an important learning experience. Next time, do a workflow test, hire good people, and keep the sound separate. And make absolutely sure that the frame rate and timecode isn't just close... it's exact.