Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP7 Audio Madness

  • Edward Kulzer

    March 9, 2010 at 4:54 am

    Yep; suspicion of corruption was first up to bat. Copied the seq into a new project & ported over only the relevent media piecemeal, leaving out the XDCAM footage, which SUPERFLUOUSLY slowed the project opening (“searching for data in movie file”)… And for quite a while, copying into the new project solved a lot… til this new bit of audio houliganism.

  • Matt Lyon

    March 9, 2010 at 5:05 am

    copying your sequence into a new project is not the same as copying the CONTENTS of your timeline into a new timeline. Try that and see if it makes a difference.

    Also, do you know what clip(s) is causing the “searching for data in movie file”? Do you have quicktime files that contain references to other media?

    Matt Lyon
    Editor
    Toronto

  • Edward Kulzer

    March 9, 2010 at 5:22 am

    You’re right; sorry, I was unclear. I made a new seq in the new project, copy / pasted the old Master seq’s contents into the new project’s new seq. And the new project’s new seq worked perfectly for twelve out of today’s 16 working hours—- then the audio glitch out of the blue.

  • Matt Lyon

    March 10, 2010 at 2:41 am

    cool, thanks for the clarification. I have to say, I’m stumped though 🙂

    If this odd behavior happens in other projects, with different media, I’d say the problem is with your machine or install of FCP.

    If the problem is confined to just this project, I’d say the issue is more likely something to do with some bad media (be it camera footage or render files or cache files).

    Anyway, please let us know if you manage to solve it!
    Thanks,

    Matt Lyon
    Editor
    Toronto

  • Bj Ahlen

    March 11, 2010 at 11:38 pm

    Did you try the FCS Maintenance Pack?

    Free 15-day trial…

  • Edward Kulzer

    March 11, 2010 at 11:43 pm

    I bought it for my home system, but the client (on whose system the problem propagated) couldn’t spare the expense). We limped past the finish line by avoiding Stereo-Pairing altogether, program-wide.

Page 2 of 2

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