Answers.Body: <p>What you are experiencing is indeed clock drift between your camcorder and your PC. Whatever their quality, two independent clocks will drift eventually. If the drift ratio is small enough and your takes are short, it will not be noticeable.</p>
  
  <p>Common way to solve this issue is to use a common clock on both devices, which requires a ref input on the camcorder and a ref or wordclock input on the sound recorder, as well as a master clock generator.</p>
  
  <p>In your situation, I would suggest either </p>
  
  <ul>
  <li>to edit at appropriate points to get back in sync. As your audio is shorter than video, it means finding places where you can cut a few video frames without it being noticeable. Not easy if the speaker is on frame all the time but it can be done if you use some other shots</li>
  </ul>
  
  <p>or </p>
  
  <ul>
  <li>find out why the audio recorded on the camcorder is not good enough
  for your use. Camcorders audio inputs can be tricky and require an
  appropriate adaptation of the audio signal in order to get best
  results.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-24T02:20:45.357Z
Answers.Text: So, I had it slightly backwards - video is shorter than audio. (I recorded my stopwatch overnight and compared the times - video's specifically about 0.0036% shorter than "real time.") I'm assuming the same advice still applies, just that it's easier to "squash" audio than video. But is that significant of a recording inaccuracy "normal" for consumer-grade camcorders, or is it a sign that something's seriously wrong with our camcorder? (I can break that out into a separate question if you think others would have better insight)
Answers.UserDisplayName: Matthew Frazier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-24T13:24:59.143Z
Answers.Text: I posted it as a follow-up question: https://video.stackexchange.com/questions/16692/is-0-0036-time-inaccuracy-on-a-consumer-grade-camcorder-expected Thanks for your response to this question!
Answers.UserDisplayName: Matthew Frazier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-21T06:26:56.903Z
Answers.LastActivityDate: 2015-10-22T11:35:05.747Z
Answers.LastEditDate: 2015-10-22T11:35:05.747Z
Answers.UserDisplayName: audionuma
Body: <p>I'm recording our church's sermons using a standard consumer-grade camcorder (Handycam HDR-CX380). Depending on mixer circumstances (our church moves around a lot), I'll either run a line from our mixer to the camera's microphone in, or use the camera's internal mic.</p>
  
  <p>Unfortunately the audio quality isn't so hot. Lately I've been researching some options for improving the quality going into the camcorder's mic, but I'm not sure those will pay off. So what I do is split the audio from the <code>.m2ts</code> file using <code>ffmpeg</code>, import it into Audacity, and line it up with another file that we record on a PC (also using Audacity, but separately). I used to do this by manually subtracting timestamps, but since discovering Audacity's Time Shift tool I decided to start using that for greater precision.</p>
  
  <p>But what I'm finding is that when I use <code>ffmpeg</code> to extract the audio from the camcorder's audio track, there's a <em>very small</em> difference in the recording rate, where the camcorder's audio track is shorter than the PC's audio track by a constant rate. I haven't been able to nail down what it is precisely, but my best estimate is .20-.25 seconds per 50 minutes -- so the camera's recordings are about 99.99% the length of the PC's. It doesn't sound like much, but it causes the lip-syncing to be off about 6-8 frames.</p>
  
  <p>My suspicion is either that the clock in the camcorder is bad, or that the clock in our (admittedly rather cheap-looking) USB audio interface is bad. (The error rate appears to be the same on multiple computers.) I know that I <em>could</em> test it using a clapboard &amp; stopwatch, but I estimate it would take about 8 hours of dead audio/video before the rate difference got to the point that I could reliably determine the problem by looking at the waveforms and timestamps. (And that's a lot of stuff to set up for eight hours.)</p>
  
  <p>So, has anyone experienced similar problems before, that could offer advice on likely causes and remedies?</p>
  
Tags: <ffmpeg><sync><camcorder><avchd><mixer>
Title: Identifying source of audio drift between camcorder and recording PC
UserDisplayName: Matthew Frazier
ThreadText: # Identifying source of audio drift between camcorder and recording PC
  
  (Asked by: username_0 on 2015-10-21)
  
  I'm recording our church's sermons using a standard consumer-grade camcorder (Handycam HDR-CX380). Depending on mixer circumstances (our church moves around a lot), I'll either run a line from our mixer to the camera's microphone in, or use the camera's internal mic.
  
  Unfortunately the audio quality isn't so hot. Lately I've been researching some options for improving the quality going into the camcorder's mic, but I'm not sure those will pay off. So what I do is split the audio from the `.m2ts` file using `ffmpeg`, import it into Audacity, and line it up with another file that we record on a PC (also using Audacity, but separately). I used to do this by manually subtracting timestamps, but since discovering Audacity's Time Shift tool I decided to start using that for greater precision.
  
  But what I'm finding is that when I use `ffmpeg` to extract the audio from the camcorder's audio track, there's a *very small* difference in the recording rate, where the camcorder's audio track is shorter than the PC's audio track by a constant rate. I haven't been able to nail down what it is precisely, but my best estimate is .20-.25 seconds per 50 minutes -- so the camera's recordings are about 99.99% the length of the PC's. It doesn't sound like much, but it causes the lip-syncing to be off about 6-8 frames.
  
  My suspicion is either that the clock in the camcorder is bad, or that the clock in our (admittedly rather cheap-looking) USB audio interface is bad. (The error rate appears to be the same on multiple computers.) I know that I *could* test it using a clapboard & stopwatch, but I estimate it would take about 8 hours of dead audio/video before the rate difference got to the point that I could reliably determine the problem by looking at the waveforms and timestamps. (And that's a lot of stuff to set up for eight hours.)
  
  So, has anyone experienced similar problems before, that could offer advice on likely causes and remedies?
  
  **Tags:** ffmpeg, sync, camcorder, avchd, mixer
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-21. Score: 0 | Accepted answer
  
  What you are experiencing is indeed clock drift between your camcorder and your PC. Whatever their quality, two independent clocks will drift eventually. If the drift ratio is small enough and your takes are short, it will not be noticeable.
  
  Common way to solve this issue is to use a common clock on both devices, which requires a ref input on the camcorder and a ref or wordclock input on the sound recorder, as well as a master clock generator.
  
  In your situation, I would suggest either
  
  * to edit at appropriate points to get back in sync. As your audio is shorter than video, it means finding places where you can cut a few video frames without it being noticeable. Not easy if the speaker is on frame all the time but it can be done if you use some other shots
  
  or
  
  * find out why the audio recorded on the camcorder is not good enough
    for your use. Camcorders audio inputs can be tricky and require an
    appropriate adaptation of the audio signal in order to get best
    results.
  
  > **Comments:**
  > **username_0**: So, I had it slightly backwards - video is shorter than audio. (I recorded my stopwatch overnight and compared the times - video's specifically about 0.0036% shorter than "real time.") I'm assuming the same advice still applies, just that it's easier to "squash" audio than video. But is that significant of a recording inaccuracy "normal" for consumer-grade camcorders, or is it a sign that something's seriously wrong with our camcorder? (I can break that out into a separate question if you think others would have better insight)  
  > **username_0**: I posted it as a follow-up question: https://video.stackexchange.com/questions/16692/is-0-0036-time-inaccuracy-on-a-consumer-grade-camcorder-expected Thanks for your response to this question!  
  
  ---
  
  