Skip to main content
Known Participant
October 1, 2012
Question

Premiere Pro has encountered an error

  • October 1, 2012
  • 4 replies
  • 17726 views

Ever since the last update (latest) I consistantly get this error. There is no way back from it, have to quit PP.

Ive tried converting all audio to 48Hz WAV files. No luck and that shouldnt be nessesary anyway.

Running an 8 core MacPro on Lion (latest builds of everything).

Anyone else having this problem or know what this error means?

Thanks for your time.

    This topic has been closed for replies.

    4 replies

    Participant
    November 5, 2012

    Just got off customer support and this is what worked for me:

    Make sure Adobe Premiere is closed.

    1. In Finder go to:

    Users/...(your userame).../Library/Preferences/Adobe/Premiere Pro/

    2. Rename the folder called "6.0" to "old6.0".

    3. Restart Premiere.

    And the exact same error (AudioPrefetch.cpp-99) was gone!

    Participant
    November 29, 2012

    Now I had the same error again (audioprefetch.cpp-99) on a different project and this solution didn't work

    Inspiring
    October 16, 2012

    Seems pretty obvious it's something to do with audio. 

    Try deleting the preferences for Pr and for your OS Audio Devices.

    Participant
    October 15, 2012

    I had the same error (Adobe Premiere Pro, CS6, Mac Mountain Lion).  My research concluded that it was a 'permissions' problem.  I found this thread with the solution that fixed my problem.

    https://discussions.apple.com/message/10772108#10772108#10772108 

    Hopefully it works for you too. 

    Note that I had some trepeditation about using the terminal command since I know very little about Macs or what was actually being 'fixed' with the recommended command.  I backed up everything before I started.  It's been 3 days now and no unanticipated problems seemed to have accompanied the fix.

    Good luck.

    Participant
    October 6, 2012

    I too am having the exact same issue, anyone know anything about this??? Please its ruing my life haha.

    October 7, 2012

    has any one heard any reasons why the error is occuring?