I doubt they added pull up or down on purpose in the field but who knows. The wave files were imported directly into the 23.976 project and they display 24 frame code even thought the original files have 29.97 drop frame code. I'm beginning to think that what is being seen as drift might be offset but that's just a guess as our sequences seem okay but the editor working off site said "drift". I'm wondering if the reinterpretation of the .wav time code to 24 frame code on import might be causing some offset depending on where the files time code starts. On some clips when I choice 23.98 code when importing there is a 1 frame discrepancy between the (24) code and file start code (30). I'm thinking depending on what the AE used for sync he might have been fooled matching this time code to the video time code. Just a guess. They are also telling me the files were brought in with the polyphonic wav box checked when they aren't poly files. Don't know if that even factors in.
---In avid-l2@yahoogroups.com, <cutandcover@...> wrote :
On Thu, Oct 23, 2014 at 2:46 PM, John Moore bigfish@... [Avid-L2] <Avid-L2@yahoogroups.com> wrote:Got a multicamera Arri Alexa shoot done at 23.976 but the audio was recorded at 29.97. The offline editor says the audio is drifting. I'm of the impression that audio depends on samples not frame rate so if they shot 23.976 video and recorded 29.97 audio at 48K if we import the audio directly into the 23.976 project it should come in at 48K and run the same clock time. I have no idea why production did this mismatch in frame rate but that's what we've been handed. Fortunately it's a very simple stage performance with multiple cameras.What might be happening that would cause a drift of the audio?
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
No comments:
Post a Comment