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
David Roth weiss replied 10 years, 7 months ago 19 Members · 23 Replies
-
Clark Morris
June 2, 2011 at 9:43 pmNope, never got an answer or a ‘real’ solution, and it happens on two different Macs, one at Tiger (now upgraded to Snow Leopard…still happens), and another one at Snow Leopard.
I bought a program called “GraphicConverter” (LemkeSoft – $40) which does almost instant batch processing and just convert any large section of stills that aren’t working into TIF files. The converted files always import fine.
For audio files that give the error, I use QT Pro (for one or two files) or iTunes (for batches) to convert to AIF files. Again, the converted files always import fine. (Even MP3s that seem to import OK can still get weird in FCP, so I almost always convert to AIF anyway.)
Not a ‘real’ solution by any means, but it does allow me to actually work.
I’m hoping the real fix is coming this month with a new version of FCP coming out, bug free and perfectly stable in all respects. And I’ll ride to work on my unicorn.
-
Elsa Retief
July 6, 2011 at 7:52 amHi
I had the same problem. Try deleting all your cache files, render files, autosave files ect. Empty your trash, reboot, and it should work then. -
Ty Marbut
September 20, 2012 at 5:39 pmWell, I had the same problem and solved it. Here’s the story:
I did a screen capture with QuickTime (most recent version as of 9/19/12) and was trying to import the .mov files that it created. The raw ones wouldn’t import. Copies wouldn’t import. Copies on another HDD with a duplicated project saved to that other HDD didn’t work. I even tried exporting from QuickTime as a .m4v – same error! I was about to give up.
However, by using another import menu (sorry – not sure which one) I learned that the issue was an unsupported frame rate! The video QuickTime had created had a frame rate of 15.002. I ran the file through Compressor to change it to a 15fps frame rate, and it imported normally.
So, if you can’t figure out why you’re getting this error, check the source video frame rate.
-
Geoff Towle
November 30, 2012 at 6:57 pmChanging the frame rate worked for me. Thanks for the post.
Geoff
__________________
“The more I learn, the more I realize how little I know.”
-
Keith Aisner
March 20, 2013 at 5:14 amDon’t know if you’re still dealing with this issue, but I’ve had it too. I own a copy of Adobe Media Encoder 5.5 and I converted it to .mov there (after unsuccessfully doing the same conversion with QT). After that I could drag and drop it right into Final Cut Pro.
-
Tim Christensen
June 25, 2013 at 4:38 amI encountered this problem too – it seems that resetting all of the cache directories (Waveform Cache, Thumbnail Cache, and Autosave Vault) to a new location, in my case another hard drive altogether, fixed the issue. I was unable to import literally ANYTHING, but doing this solved it!
-
Matthew Rozynski
August 23, 2013 at 9:49 pmForcing the frame-rate worked for me also! by exporting my files from QuickTime Pro and setting the rate there. I am using FCE v3.5
-
Stu Aull
December 26, 2013 at 10:31 pmYEP! same out-of-the-blue-never-had-this-problem-before-in-12-yrs-using-FCP
SOLVED by matching imported clips FRAME RATE with the Projects SETTINGS.
Thanks you guys!!!!!Stu Aull
Alaska -
Robert Lypka
February 26, 2015 at 1:08 pmOver five years after the origin post and the problem still exists.
I was getting the error trying to import a *.MOV file into Final Cut Pro. It played fine in Quicktime — I just couldn’t import it. I used Quicktime to make a copy of the file (without making ANY changes to it) and the problem disappeared.
-
Maria Kristensen
July 2, 2015 at 8:11 amSo- for anyone still using FCP 7: I encountered this error when trying to import .png files – tried all the workarounds, what finally worked for me was moving the files I wanted to import to the desktop – they were located on an external drive, same as the one that contained the project file and masterfiles, but apparently FCP didn’t like that!
Reply to this Discussion! Login or Sign Up