Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy File Error: Unknown File .wav

  • File Error: Unknown File .wav

    Posted by Gillian Borg on January 13, 2014 at 2:39 pm

    This situation is doing our head in, and I’d really appreciate some help if someone knows what is missing.

    We have an hour and half long Apple Pro Res 422 master self contained file which only needs to be aligned with final sound mix in a new sequence for final delivery.

    Similar to our previous workflows, our Sound Designer just sent us a .wav file for the final audio (24 bits, 48kh) but for some reason, FCP doesn’t like it anymore and gives us this error in red.

    We have gone all over the forum and read all possible posts, and have already tried the following:

    1. Changed the file name and location
    2. Closed project, started a fresh one and tried a new import
    3. Switched user, installed FCP in a new one and tried a new import from a shared drive
    4. Asked our sound designer to send us an .aif instead
    5. Asked our sound designer to export it from Logic instead of Pro Tools

    The only thing that worked is re-compressing file in soundtrack pro and sending it back. But we really don’t want to re-compress the final soundmix, it’s crucial that the sound file is untampered.

    So, what are our options, or what are we doing wrong?? Any help will be really appreciated!

    Gillian Borg replied 12 years, 4 months ago 1 Member · 1 Reply
  • 1 Reply
  • Gillian Borg

    January 13, 2014 at 9:14 pm

    Hi Dave,

    Thanks so much for getting back to me and apologies, my lack of understanding of audio led me to use the wrong terminology.

    I meant exporting it from Soundtrack Pro was adding a ‘dither’ (and not re-compression) which apparently adds white noise to the audio file. However, we have now successfully bounced the audio from Logic pro which, I am being told, will avoid the issue.

    So this workaround has enabled us to import the file, however it has been an annoying episode to say the least. Would you know what causes this?

    Many thanks.

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