My project is crashing each time I try to open it with the error :
Premiere Pro has encountered an error
If I use an auto-save project it open normaly but I cannot do a save because the saved project will give me the error.
What can I do. It seems that I'm not alone with this problem but I have not found any solution.
What can I do
I'm using the french version of Windows XP SP3. This is a 32 bit intel machine. I have read that there might be an issue with the french version because it use the dot in english and the comma in french. I have tried changing my regional settings to english United State but it did not fix the problem. I have done a compare between one file that open and a save as copy of the project. I figured out that it actually change some dot for comma :
I just don't know how to stop premiere from putting comma instead of dot. I can't believe that an Adobe Product does not support different OS language.
Thank you for your help or any hints.
OK, we've got both a FR and GR language version of PrPro that is malfunctioning. In the case of the FR version, the OP did change the language of the OS to US English.
For both versions, FR and GR, what is both the OS's language and also the Keyboard setup?
FR = FR (tried US En for OS) - Keyboard?
GR = GR (?) - Keyboard?
Harm, do you use the Dutch version, or the US En version? What language is your OS, and your Keyboard?
Just trying to eliminate variables to see if there is a common thread. Also, besides the language of the program, the OS and the Keyboard, does anyone else know of a possilbe additional language setup - one that I am missing?
[Edit] PS what OS versions are each using?
execuse me, but i don't understand at all what it has to do with the system language? I'm using PPCS4 for half a year now and i never got any problems of this kind. Nothing is new to the system. I've already saved and reopened other projects today. By the way, i have done no changes to the project file that crashed - i just opened it, tried to export a timeline to the media encoder, it crashed, i saved it (don't know why i did it), shut down premiere and as i reopened it i got the named error message.
my keyboard setup is Deutsch - Deutsch (German language, german keyboard setup) and i'm using Windows XP SP3
With CS3 and XP there have been sporadic issues with NTSC and PAL displays that got confused in a project. Say you started a PAL project, imported further PAL footage and it displayed as NTSC in that PAL project. I have not yet encountered that in CS4, but who knows? Maybe the confusion about ,,, or ... or ::: or ;;; still continues. Bill is trying to rule that out, hence his question. Unfortunately, although I'm Dutch, I hate having anything on my computer in Dutch. The only programs I have in Dutch are my bookkeeping program and tax declaration program, everything else is in English. My children all use Dutch as their setup and everytime I have to help them, it is a sheer disaster to find those crappy Dutch translations in menus, forgetting about the difference between Y (yes) and J for Ja (confirmation) and to make things even worse, even my tax declaration program messes things up between the languages, all questions are in Dutch, but when closing it reverts to English.
Bill is trying to understand whether the different languages in use can be the commonality that causes problems.
execuse me, but i don't understand at all what it has to do with the system language?
It may have absolutely nothing to do with any part of the problem. However, there are two different language versions that are throwing the same error. I do not recall seeing this error before, but certainly may have missed it. I'm just hoping to find some common ground here, so others can proceed with finding the cause.
As for the problems with the separators, the only thing that I have seen was in Subtitles in Encore, and confusion between colons and semi-colons. However I have never done any PAL Projects, so it would unlikely for me to encounter the problem.
Maybe Harm either recalls a post with info on this, or KB Article with reference to it. Unfortunately, I do not, and usually just gloss over pure PAL issues, unless there is something else happening in that thread.
ah, i understand.
by the way - i found this thread by typing in the error message part: "[c:\randall\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-14 2]" And it was the only one result on google. What does this path mean? where is it (no folder randall on c) and what does this file (?) do?
PAL footage is denoted in the following format: hh:mm:ss:ff
NTSC footage is denoted in the following format: hh;mm;ss;ff
Notice the difference between : and ; ?
With CS3 is happened occasionally that PAL footage was displayed with ; and a timebase of 29.97 fps in a 25 fps PAL project.
Although I filed a bug report, I have never heard back from Adobe and have not yet encountered this issue with CS4.
BTW, Adobe is great in unresponsiveness about bugs. They have an Ostrich mentality. The bug about the stopping program monitor when using an external monitor has been acknowledged, but that is it. No further communication, they have their heads someplace where it should not be.
Other than the FPS issue, that was about the same with Subtitles. Some Subtitle scripting programs would acknowledge to the user, that they were using the correct separator for, say PAL, and instead of the : stick in a ;. Sometimes, when typing Timecode, I have to jog my memory which is which. For me, it's "NTSCeasy," as I do not have to hold the Shift key for my separator. I know that the Shift-: will be for PAL.
ok, i understand... but why are you talking about pal and ntsc? does it have something in common with the path in the error message (c:\randall\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142 )? and can it really cause a crash?
If there is confusion between the program, the regional settings, the OS and/or the Keyboard, I would imagine that it possibly could. However, it might not, and it would be nice to remove it from the possible causes of the error.
I really do not know who/what Randall is. I have not seen that reference to any error messages. Yes, there are some odd ones, like Vobulator, Stingray, Headless and the like, but do not recall any Randall.
You got me on that one. Maybe how some user had his/her PrPro set up?
As this bug in always present in the CS4 version (16/12/2009). I'm sharing my way to restore the project:
Note that I'm using NotePad++ to edit the project file.
Edit your OS regional settings and change you decimal separator from comma (,) to dot (.) as this bug is always there too (you will see it again when Adobe Encoder will launch the headerless Premiere and crash with the same error).
And finally try to reload your project.
Note about this:
Some data will be changed to incorrect values in your project, like "Opacity" for Title elements, or "Gain" for some audio tracks...
My message to the developer team:
First, you are not god and your coding is not perfect so please use try-catch things that exists today in every languages, it's amazing to see a software like this crashing. Secondly, why the hell removing a node element of the project file avoid the loading of the entire project ??? And finally don't tell me that I'm the ONLY user in Europe that is using comma as a decimal separator
Could all of you that still have this problem go to http://feedback.photoshop.com/photoshop_family/topics/pre10_project_op en_fail and click the "+1" (Add my vote) to make sure Adobe gets the extent of this problem.
Since all solutions presented here in the forum did not work for my project file, and I had a dead-line comming up, I created a script that fixes the damaged project files. It's a simple web page where you upload your file and get the fixed version back. It worked for my project file and I hope it'll work for you as well. You find the page here: