Is the Pullup/Pulldown seleciton on the import settings checked? Also, which recorder is being used? Some still list the recording as 48000 even though it was done as 48048.

Michael

Hi Michael, thanks for your response. I have pullup/pulldown and every other option in the audio tab unticked. Is this correct for 48.048 files?

I had a meeting with the sound guy last night and it seems that he is using two machines and after much checking by me I was able to ascertain that his second recorder was incorrectly set to 48,000 which explains my inconsistent syncing issues and the fact that the last 3 shoot days he's only been using the second device. I have sent the rushes for the last three days back to their studio to be correcty adjusted in PT to 48.048. Problem solved I hope!

The only other issue that I wanted to run by you is a problem we are having with the smart slates which are constantly out by 30 to 60 seconds. I went to set this morning to double check everything extensively and sound recoder and slate are perfectly in sync with the crew checking the code between the devices constantly (i even took stills over the course of 3 hrs to check drift and all was fine). However when I get the wav files for the dailies back here each day my assistant is finding them to be up to a minute out. The sound guys are using a 2x 4 Channel Sound Devices 744T recorders(slaved) and then supplying editorial with wavs on lacies. is there any known bugs with timecode when importing for either avid or 744T? 

The assistant has just given me the thumbs up on the sample rate adjusted test we have just received from PT guys. Looks like one problem solved!

Thanks for your help,

Matt

I think i've found a bug with importing bwf's into Avid. I did a simple test where I imported the audio file into FCP and into MCA.

Avid source start timecode: 05:21:19:17

FCP source start timecode: 05:21:39:00

The fcp timecode lines up with the smart slate and is correct (I hate to say it) however the same audio file in MCA does not represent the correct timecode.

Any workarounds? I don't want to tell the producers that after fighting hard for Avid on this job over FCP, that the Avid is causing us to be behind shoot by an extra 2 days constantly, especially after they've invested in smart slates for this very reason. 

I've tried this phenomenon on MCA Vers 2.8.3 and 2.8.0 with the same errors in timecode across both systems.

Please help as I can't keep the wolves from my door much longer!

Matt 

 Yes... this is a know issues since the production audio is most likely recording 30fps NDF timecode? When working in a 24fps (23.976) project, the Start is converted to 24fps based on samples from midnight calculations. The "workaround" is to switch project to NTSC via the tab first, import the files,  (now the timecode should be correct), Duplicate the START into the Sound TC and switch back to HD and should be good.

Michael

Hi Michael, thanks for the info. The only thing is that the audio is definitely recoded in 24/48 as I checked on the recorder myself.  Here's a link to the file if you have time to take a look at it. Sounds like http://www.mattbennettedit.com/wav/

If so does that workaround still apply?

Thanks again for taking the time to help with this,

Matt

Ok Michael - I think I get it now. So when audio is recorded on set at 24 its actually 30ndf timecode.

Switch the project to SD 23.976 NTSC import files selecting 30 frame non-drop and files should be fine. This seems to work although my files are still out by maybe 6-10 frames which is much better than 30 - 60 seconds. Is this correct? Is it essential to duplicate info into sound tc column? I will providing sound post with an OMF file once I reach lockoff stage.

Can you please confirm this workflow for me and also will there be a fix for this in future MCA versions?

Thanks,

Matt