Skip to main content
Known Participant
August 3, 2017
Question

Crash when using 'Replace Footage' Function

  • August 3, 2017
  • 23 replies
  • 9372 views

This is a continuation of a thread that was closed, but this issue is not answered or resolved. (LINK)

I'm experiencing a consistent issue when attempting to replace footage by Right-clicking on the clip in the Project Bin and selecting "Replace Footage". I get the dialog box to select the replacement and then I get one of three outcomes:

1. Premiere crashes suddenly and completely. (45% of the time)

2. The Dialog box goes GREY and remains on screen. You cannot close that box. No replacement took place. (45% of the time)

3. The replacement completes successfully. (10% of the time.)

This started on upgrading to CC 2017 in January.

I'm replacing footage several times an hour, so this has a huge impact on my workflow. A fix would be welcome!

    23 replies

    Inspiring
    November 14, 2019

    This just happened to me twice today. GREAT, ANOTHER PREMIERE BUG. Damn adobe sucks, can't wait to get away from this horrible company once and for all

    Daniel Hoover
    Inspiring
    June 4, 2018

    If nothing is working to fix the "Replace Footage" crash, try this (in CC2018):

    1) Create brand new project

    2) Open original project so both projects (new and original) are open simultaneously

    3) Copy all bins/sequences/items from original project to newly created project

    4) Save and Close all projects

    5) Open newly created projects and try Replace Footage

    This worked for us, our issue was that our original project had been saved from a template .prproj from an old version of Premiere that had been upgraded through multiple CC versions.  So making a new project helped "reset" the Replace Footage command.

    New Participant
    June 4, 2018

    I have the same issue... exact same problems as OP.

    Filed a bug report because i couldn't find any on this topic in the list.

    Strange, because it seems to be a problem for many users, and many have filed reports?

    Please Adobe people, have a look at this.

    It really is annoying when we have to continually restart, retry, retry, restart etc, or even replace files by hand in complex edits, when we know it COULD be done very easy if it worked like it should!

    Thanks.

    gregd80865280
    Participating Frequently
    June 4, 2018

    I ended up figuring it out.

    Turns out I had 4 images with an apostrophe in their file titles which was causing the project manager to crash. Once I removed them it worked. Maybe look through your timeline and see if any file names have weird character.


    In my opinion this is an unacceptable crash and I hope premiere fixes it soon. Not sure if I will work in Premiere again after this film due to how unstable it is...

    gregd80865280
    Participating Frequently
    June 4, 2018

    or what sorry that was for a different error in premiere.

    the upgrade to CC2018 worked to fix this bug, but not the other one.

    Too many errors in that program...

    GD

    Daniel Hoover
    Inspiring
    May 11, 2018

    Hmm, try importing the media into your project again, then option+shift drag-and-drop (alt+shift on PC) the newly imported instance of the clip onto your offline ones.

    gregd80865280
    Participating Frequently
    May 11, 2018

    OK this works! Phew. does this help isolate the problem at all? do I have to do this for all 1,000+ clips?

    Daniel Hoover
    Inspiring
    May 11, 2018

    No idea what causes the problem, but I'm glad the workaround is helping.  Hopefully not all of your clips have to be replaced like this!  Also watch out for things like volume/gain applied to clips that you replace - that will have to be redone.  Video clips seem to work better at being replaced properly via this method.

    Daniel Hoover
    Inspiring
    May 11, 2018

    Literally everyone in this thread that posted an OSX version said they are on 10.11.6

    That's what we have and it's still an issue for us.

    It can't be a coincidence that all of us reporting this bug are on the exact same OSX version.

    gregd80865280
    Participating Frequently
    May 11, 2018
    Please download the attached file to view this post
    Vinay Dwivedi
    Adobe Employee
    Adobe Employee
    May 11, 2018

    Hi Greg,

    It seems to be the corrupt plist file. Try the step below and check if it helps.

    Close Premiere Pro and other Adobe applications.

    Click on Finder and click on 'Go" option.

    Select 'Go to Folder" and Type ~/Library (to go to user library)

    Go to Preferences and move the following plist file on the desktop : com.adobe.PremierePro.CC12.plist

    //Vinay

    gregd80865280
    Participating Frequently
    May 11, 2018

    Nope, still crashes

    gregd80865280
    Participating Frequently
    May 11, 2018
    Please download the attached file to view this post
    Known Participant
    March 14, 2018

    For what it's worth, my workaround now is to use the Replace With Clip > From Bin function. It's more steps, but it's 100% reliable in my experience.

    1) Import your new/updated footage into the project.

    2) Select one of the new files in the Project pane.

    3) Switch to the timeline and right-click on the old clip that needs replacing. Select Replace With Clip > From Bin. This will replace the old clip with the new one, maintaining all effects, keyframes, ins/outs, etc. you have on the clip.

    4) Wash rinse repeat

    The trick is ensuring the new clip is still selected in the Project pane even though focus is on the timeline.

    Note to Adobe: This is a workaround, not a fix. Please fix this!

    New Participant
    March 14, 2018

    Still an issue. Using CC 2018 12.01 on OSX 10.11.6. This has been a problem for far too long at this point.

    New Participant
    March 12, 2018

    I am having the same issues with an aftereffects project I have used and updated since 4.1   The original project is 14 years old.  Now since I got my new MacBook Pro and loaded CC2018 I get the crash.  It is simply loading a series of .jpg images with the same sequential names DSCN0001, DSCN0002.... through a couple hundred images. it has ALWAYS worked every time. I can't get it to work once.  I tried renaming the file folder with no success.

    This is a massive problem and affects my income and renders my new MacBook Pro useless.