Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Dreaded File error:1 file(s) recognized, 0 access denied, 1 unknown

  • Dreaded File error:1 file(s) recognized, 0 access denied, 1 unknown

    Posted by Thomas Thornton on October 20, 2009 at 2:50 am

    Hello All.

    I haven’t used FCP at home in quite a while but just re-set up my Suite today. I wanted to test my Aja io (through Expresscard slot, different FW Bus, and I get this message:

    “File error:1 file(s) recognized, 0 access denied, 1 unknown ”

    Did a search here, came across various answers concerning AVIs, Livetype, etc – But none addressed my issue.

    These are files that previously imported fine, so something must have changed. Files currently in a project play with no problems, and I even tried importing with my Aja offline (just in case)

    So, I checked for updates (none), did a safe boot, repaired permissions, trashed Prefs, everything I could think of and still no dice.

    Details below, any help would be greatly appreciated! I’ve been stuck in AVID land and can’t wait to get back to FC.

    Thanks in advance.
    Tom

    MBP Early 08 2.6 Core 2 duo 4G
    10.5.8
    FCP 6 (yes, haven’t upgraded either OS or FCP yet)
    Aja IO

    David Roth weiss replied 10 years, 7 months ago 19 Members · 23 Replies
  • 23 Replies
  • Peter Berthet

    October 20, 2009 at 3:06 am

    are yo trying to play them from the bin or in a timeline?
    Ive been getting a similar error when playing back media in a timeline because the renders are f**ked for some reason
    so ive render managed the timeline, re-rendered and its all happy days after that

    ~Peter Berthet
    Sydney, Australia

  • David Roth weiss

    October 20, 2009 at 3:33 am

    [Thomas Thornton] “”File error:1 file(s) recognized, 0 access denied, 1 unknown ” “

    This often indicates that you exported a reference file rather than a self-contained file, and that it is no longer recognized because you either re-rendered or made a change to the underlying sequence from whence it was first created.

    David Roth Weiss
    Director/Editor
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

  • Thomas Thornton

    October 20, 2009 at 4:10 am

    Peter – This happens on import, so I can’t even get them into FCP.

    David – That was an option brought up when I did a search here earlier, but I tried all sorts of QT files, even Streamclip and Handbrake’d files just to make sure.

    Tom

  • Alex Barreto

    February 9, 2010 at 5:33 pm

    Came across this while doing a search for the same issue. We recently upgraded to FCP 7 and have been having this File Error issue. It happens with all sorts of files – JPG, TGA, WAV, AIF. The only work around we’ve found is to use Preview to re-export the still files and QT to re-export the audio files. Seems like such a waste of valuable time when these files were importing fine in the previous version. Might there be any new info on this issue?

    Alex Barreto
    Vapor Post

  • Cameron Pickford

    March 11, 2010 at 4:36 pm

    I’ve recently run into this issue as well, with both importing jpegs and wav files. The only work-around I’ve found is saving the files as themselves, and suddenly they import just fine. No idea why. Unfortunately, for the wav, I had to save as a .mov and import it that way. Getting the job done, but there’s got to be a better way.

  • Clark Morris

    March 19, 2010 at 2:29 am

    Yep, I just upgraded to FCP 7 / Snow Leopard and can not import “easy” files into FCP like wav, aif, and jpg (for starters). I’ve also only found that re-saving from a different program on the same Mac works. What a step backwards. If anyone knows a fix for this, please let us all know.

  • Clark Morris

    April 19, 2010 at 2:44 pm

    It’s been about a month since my last post. I’ve upgraded to the latest on everything (FCP, etc.) and I still have JPEGs and WAVs and AIFFs that play fine on the computer (and are NOT reference movies), files that should easily import, and I have to open up and re-save each one of them before they’ll work in FCP. Such a hassle, especially when people hand me entire cards filled with pictures and we just want to ‘look thru them on the big screen.’

    ANYONE find an answer for this one?

    cLaRk

  • Clark Morris

    April 24, 2010 at 2:35 pm

    Well, I found out that if you drag a problem file to the FCP icon in the dock rather than into a bin (or just using normal File/Import) that instead of the generic “Unknown file” error you get a more specific one.

    In my case, every problem AIFF, JPEG, WAV, etc. file that won’t import comes up with the error “Text file too large: text file size limit is 1MB.” (This may not be the exact wording of the error as I’m not in front of the system right now.)

    I can’t find ANYTHING on that error (even when worded exactly as seen on screen).

    No, these are not unusual files in any way I can see. They come from a variety of sources, all of which used to import fine before upgrade.

    If anyone else has this same importing problem…do you get the same “Text file” error if you drag file to FCP dock icon?

    Really hating this, as people are coming in with camera cards with hundreds of pictures that need to be converted before import.

  • Shane Sauer

    October 1, 2010 at 4:05 pm

    I am having the same trouble importing audio ( .wav and .aif files) into Final Cut 7.03 on a Snow Leopard machine. These same audio files are from my sound library and will import fine on Final Cut 7.03 on a Leopard machine. Does anyone have this problem, or know what might be causing it? This has been tested on several machines. A reinstall, permissions repair, and trashed preferences of Final Cut does not solve the issue. I’m stumped!

  • Cameron Williamson

    June 1, 2011 at 8:59 pm

    Soooo, did we ever come up with a fix for this? I having the same problem.

    When in doubt, hit it with a hammer.

Page 1 of 3

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