Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
Pulling hair out over audio sync with Premier Pro and Audacity
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Mike Brown" data-source="post: 207493" data-attributes="member: 1310"><p>Timecode and "clock" are two different things. Timecode merely labels the frames of video with an address, it has nothing to do with playback or record speed. I can shoot 24p footage and label it with 60FPS timecode or on and on and on. This can be as incorrect or as correct as you make it, with no impact on playback or record speed. Often in post production workflows, footage and audio will have many different pieces of timecode metadata.... source timecode, edit timecode, burned in timecode, etc and they can all be different and reference different things.</p><p></p><p>Clock (word clock in audio land.... gen lock, blackburst bi-level or tri-level sync in video land) ensures that fields or frames or samples are taken or reproduced at the same time.</p><p></p><p>Colin, it sounds like to me you need to do a 30FPS to 29.97FPS pull down on your audio to match the video. If the audio is slow then instead do a 29.97 to 30 pull up. DAW's like ProTools have simple tools to accomplish this.</p><p></p><p>Alternatively you can mess around doing some custom sample rate conversion with some simple stoichiometry. Figure out the percentage difference in length the video is from the audio and then apply the same percentage difference as a pull up/down sample rate conversion. This will bring them perfectly in sync.</p></blockquote><p></p>
[QUOTE="Mike Brown, post: 207493, member: 1310"] Timecode and "clock" are two different things. Timecode merely labels the frames of video with an address, it has nothing to do with playback or record speed. I can shoot 24p footage and label it with 60FPS timecode or on and on and on. This can be as incorrect or as correct as you make it, with no impact on playback or record speed. Often in post production workflows, footage and audio will have many different pieces of timecode metadata.... source timecode, edit timecode, burned in timecode, etc and they can all be different and reference different things. Clock (word clock in audio land.... gen lock, blackburst bi-level or tri-level sync in video land) ensures that fields or frames or samples are taken or reproduced at the same time. Colin, it sounds like to me you need to do a 30FPS to 29.97FPS pull down on your audio to match the video. If the audio is slow then instead do a 29.97 to 30 pull up. DAW's like ProTools have simple tools to accomplish this. Alternatively you can mess around doing some custom sample rate conversion with some simple stoichiometry. Figure out the percentage difference in length the video is from the audio and then apply the same percentage difference as a pull up/down sample rate conversion. This will bring them perfectly in sync. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
Pulling hair out over audio sync with Premier Pro and Audacity
Top
Bottom
Sign-up
or
log in
to join the discussion today!