Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro File Import Failure – Unsupported format or damaged file (Only for certain projects)

  • File Import Failure – Unsupported format or damaged file (Only for certain projects)

    Posted by Dan Schneider on January 8, 2013 at 12:42 am

    I have two projects that I’m working on that rely on the same footage. One day, after moving the directory where these projects are located to another location on my drive, I am of course forced to relink the footage when I open up the project again. I go to relink the footage in the first project, and everything works fine. However, for the second project, when I relink, for certain files, it gives me the error: File Import Failure – Unsupported format or damaged file.

    Yet I had just imported these files fine in the other project. I even went back and opened the first project, and it had no problem with the files that the second project did have problems with.

    What’s going on here? Am I missing something?

    Nick Brown replied 12 years, 3 months ago 4 Members · 8 Replies
  • 8 Replies
  • Trevor Ward

    January 8, 2013 at 1:27 am

    [Dan Schneider] “What’s going on here? Am I missing something?”

    Yeah, you’re using Premiere Pro.

    Oops, did I say that out loud? I don’t mean to be a hater. But I think I am.

    -Trevor Ward
    Red Eye Film Co.
    http://www.redeyefilmco.com
    Orlando, FL

  • Dan Schneider

    January 8, 2013 at 2:11 am

    You know, these forums aren’t for haters. They’re for actual help. I recommend that you keep your opinion to yourself and only use these forums for helpful advice. Why are you even browsing this forum in the first place?

  • Trevor Ward

    January 8, 2013 at 2:49 am

    I’m browsing because I’m a recent convert from FCP. I’m desperate for help as the transition for me from FCP to PP has been pretty unpleasant.

    -Trevor Ward
    Red Eye Film Co.
    http://www.redeyefilmco.com
    Orlando, FL

  • Gerard Tay

    January 8, 2013 at 3:02 am

    Could ve a corrupt clip. You can try running Corrupt Clip Finder. There’s a free trial period.

    https://www.digitalrebellion.com/promaintenance/

  • Dan Schneider

    January 8, 2013 at 3:06 am

    I see. It can often be difficult adjusting to a new piece of software, so I can understand your annoyance at Premiere. It does take a bit getting used to. Myself, I started with both Final Cut and Adobe Premiere, so I know a fair amount of the problems that can arrive when ‘thinking’ in a Final Cut kind of way and not knowing how to do it in Premiere. If you have any problems like that, don’t hesitate to ask for help.

  • Dan Schneider

    January 8, 2013 at 3:26 am

    Gerard,

    Unfortunately, I’m on Windows, and so I can’t try out that application. However, I seem to have inadvertently found the reason behind the error. Apparently clearing all of the Adobe Media Cache solved the problem. It probably had some sort of saved .pek/.cfa/other file that kept telling it that the file was corrupt when it actually wasn’t. The same problem happened to me earlier in the year where it worked on my laptop but not on my desktop. It now makes sense that it had to do with the cache which wasn’t shared among both computers.

  • Gerard Tay

    January 8, 2013 at 3:52 am

    Good to know. Thanks for sharing.

  • Nick Brown

    January 29, 2014 at 6:26 pm

    I just had the unsupported or corrupt file problem in a CS6 project. On the timeline that was working perfectly when I closed the project 2 weeks ago one video file was not loading and appeared red in the timeline. Using Sony’s media browser, it play as it should. The tip of it being a cache file problem was correct. I re-created the PluginCache file by closing PP then holding down the SHIFT key and releasing it when the initial workspace appeared. This cleared up my problem. I’d almost forgotten about this solution because CS6 has been very stable.

    Remembering the days when Adobe was improving the horse it rode in on. I needed to use this trick often in all versions from 4.2 on When I started editing with Adobe we were ridden hard and put away wet. Premiere was a rightfully a joke to professional editors. I started with Adobe because I couldn’t afford a better but much more expensive system. It could get the job done but not without a considerable amount of frustration.

    This horse need to edit every few weeks but when I do need to edit I enjoy working in PP. I’m wondering, have I been put out to graze, no longer needed in the race to dominate the creative software industry? Will the subscription only policy be changed? I hope so because I don’t want to support a company that does not value the customers to build it’s empire on. It will cost me $600 a year to upgrade with Adobe that’s as much as I spent in 3 years before the subscription only went into effect.

    I am very thankful that Adobe built the great CS6 environment for me to work in. I just hope that the Adobe marketing team can find a way to have a editor without a $600 per year budget stay with them.

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