Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Synch problems with fcp, Rode, h4n

  • Synch problems with fcp, Rode, h4n

    Posted by Adam Bearson on May 10, 2011 at 4:50 am

    Usually I use the in-camera mic as reference, but this time used the Rode plugged into the 60D shooting at 29.97
    Sensheisser Lavs plugged into H4N for real audio…
    Convert footage to 422 48k and synch with Pluraleyes–but audio does not synch…Actually Pluralyeyes does think that it IS synched, but there is a heavy drift (over a second in three minutes of footage).

    Have tried stretching audio, changing easy setups, sequence settings–nothing seems to work. Any thoughts?
    Thank you for any assistance!

    Adam Bearson replied 15 years ago 3 Members · 4 Replies
  • 4 Replies
  • Stephen Best

    May 10, 2011 at 11:37 am

    What frequency did you set the H4n to record at? 44.1, 48, or 96 kHz?

    Regards
    Stephen Best
    https://stephenbest.ca

  • Adam Bearson

    May 10, 2011 at 12:05 pm

    I recorded in 44.1 (stamina mode)–usually that is not a problem, but then went to QT and exported to 48k just to seee, but no difference.

  • Michael Gissing

    May 10, 2011 at 10:22 pm

    Adam, sync drift is an almost daily topic here and some time ago I foolishly took it upon myself to keep answering. Here’s a link to yesterdays explanation-

    https://forums.creativecow.net/readpost/8/1131689

    Search the forum for more. 48khz, 16 or 24 bit is the other must do. Never trust FCP to handle sample rate differences so always have 48khz for sequence and files. Also never use compressed files like mp3 or aac either.

    Matt Lyon has done an excellent tutorial which helps people fix problem sequences with audio issues and also explains the frame stamping problem-

    https://library.creativecow.net/lyon_matt/fixing-fcp-assets/1

    This should help to fix what is already synced. The rest of the info will help you avoid it in the future.

  • Adam Bearson

    May 11, 2011 at 4:31 am

    Thank you. I will explore. Never did figure it out, but am stretching audio for now.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy