i have exactly the same problem. since i used it the first time. i really hate this programm!

Hello SedAdMichael,

it seems Adobe Software has problems on system using non-dot decimal separators. To verify this, could I ask about the decimal separator your system is using (language setting). Is it a comma "," or a dot "."?

Greetings,

Jens.

Hi Michael,

>  I changed the separator to "." instead of "," but the same error occured when trying to open the project....

it's correct that changing the dot separator will not make PRE 10 able to load the file correctly - I had no doubt in that, but having a system with "," supports my theory that this breaks the prel-files on saving. Using the dot separator in the system might not lead to corrupted files when saving the projects (that's my theory, I'd like to have confirmed).

> thanks for trying to help us... But unfortunately this didn't resolve the problem

I'm not just trying to help, I like my file getting fixed too

• As the Problem seems to lie in keyframe.h: Can someone please tell the correct format of all keyframe lines, so we could find out which lines are incorrect and fix those. - Until a patch is released.
• I have two hours of video in my prel file and it's about 5 MB large and spent a week of working hours. The perl replacement was successfully but is still not working - my file now fails when loaded at 86 percent with exactly the same error message. How do I find out which line or element fails, so I can replace more dots by commas

Greetings,

Jens.

P.S. I hope Adobe will give us a patch soon and a fix-tool or a description how to fix the old files. Many language settings are using "," as a decimal separator, so whole countries are affected.

Hi everyone,

after getting some hints from you about the possible cause of this error, I have been able to fix my project and I'd like to give you back my insights...

First, I uploaded the project file in the Windows Editor. By comparing the file to an earlier backup version which worked fine, I found the following:

At one point in time PE10 corrupts the .prel file by inserting "," in decimal numbers instead of the required "." for the <StartKeyframe> as well as for the <Keyframes> tags. The correct syntax of both these tags seems to be as follows:

<StartKeyframe>-xxxx,yyyy,0,0,z.,z.,z.,z.</StartKeyframe>

<Keyframes>-xxxx,yyyy,0,0,z.,z.,z.,z.</Keyframes>

xxxx is a 17 digit (integer) number

yyyy is either a (decimal) number z. or a range z.:z. or a boolean value (true or false)

z. is a decimal number (number followed by a ".")

In my corrupted .prel file, all numbers which were supposed to be "z." were actually "z," which caused the error.

Only some of the occurrences of this error can be captured by the script described above, namely replacing the "," followed by 12 or 24 "0" with a ".". Unfortunately, there are a lot of other occurencences which have to be dealt with in order to correct the .prel file. One can get a number of algorithms for speeding up the process of replacing the erroneous "," with ".",

e.g. search for ",000000" and replace it by ".000000"  (similar to the scipt above) but you also have to consider 

search for ",," and replace it by ".,"

search for "0,5" and replace it by "0.5",

search for ",<" and replace it by ".<  etc., you get the idea....

This list is not complete, you still have to search manually for some odd numbers!! However, as you progress with replacing the erroneous "," you will see the perceantage of the .prel file loading successfully increase and at the end of the day (more an hour really) the file will load completely. I have not tried to fully automate the process. Hope this was a one time effort!

The above procedure is a pain in the neck, but if your son has spent an entire weekend on a project it is worth the effort! Hope this will work for you as well. Adobe should be able to fix this easily. Good luck!

Best regards, Rainer

Hi everyone,

I have the same problem after many hours on this project.

"Premiere Elements has encountered an error.

[d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]

My project weighs 3 499 038 octets.

without explanation, suddenly, my project has been altered and also all versions of the same project automatically saved in Adobe Premiere Elements 10.

This is the first project that I create with Adobe Premiere Elements 10 on my new pc.

I use a Intel Core I7 with Windows 7 Pro FR 64bits, 120Go SSD Harddisk and 16Go DDRAM.

I have applied all solutions proposed above without success.

I would like to have your opinion on two points.

1 - do you think it is possible to find a solution to my problem?

2 - how to be on not to meet again this problem on other projects?

Best regards,

Kinou

Balma, France.

Thanks Steve,

but that's exactly what I did.

I applied SetAdMichael solution first

and after RainerBl solution

and after cloud565 solution

and even several times each. I thank them for their work.

I will completely recreate my project, if I have the same problem again I will choose, with regrets, another video editing software. Indeed Adobe seems unable to explain and fix this bug. Adobe Premieres Element 10 is not sufficiently reliable to be used resulted seriously.

It is unacceptable to lose the result of a several days, including backups.

I feel like I have been deceived by purchasing this version which ultimately cost me a lot of time and money spent unnecessarily.

Best regards,

Kinou

Balma, France.

Adobe i have also this problem. I spend lots of hours to a project. All went fine till now with those error:

d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142

I don't have a D: drive ??

My project was ready in the first place. I saved it. The only thing i did was: Share it with YouTube. I choose the setting "High definition 1920 ...." rendering starts en uploaded it to Youtube.

I was very angry because the output on youtube was very bad. The 720p and 1080p where not as good as on my timeline. It was very late so i closed Adobe Premiere, and the pc asked me to save the file?

I thought: save the file? i did nothing change? ... but i did choose yes... stupid... maybe i must choose No.

Just now i would like to render again but i get the Keyframe problem..

Why Adobe why? Please can you fix this problem with a simple workarround? I have a deadline.

Have no time to do the scripting with Perl. Do you have a faster way.?

After running your exe, i have the same h-142 problem.

But i did find out something else.

The last working backup from my prel file is from 5-1-2012. This file is 3.223 kb

I then worked some hours and the corrupt prel file is from 8-1-2012. But this file is smaller: 2.462 kb ?

When you work at a projects, for as far as i know, the prel file will each time growing ... or not?

Can i send my files to someone who can look at whats going wrong with my last working good en defective prel file?

Would be very pleased....

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.

I have the same problem. I have tryed all the solutions and are currently browsing trough my prel file for dot or comma errors that this solutions dont catch. But how do I know if this key frame is correct

<Keyframes>914305190400000,264,93505859375,0,0,0.,0.16666666666666666, -39.557989075251342,0.16666666666666666,915205848338028,124.6753234863 28,0,0,-39.557989075251342,0.16666666666666666,0.,0.16666666666666666; </Keyframes>

or it shoud be 264.93505859375

?

I also have another recurrent keyframe

<StartKeyframe>-91445760000000000,0.500000000000000000000000:0.5000000 00000000000000000,0,0,0.000000000000000000000000,0.0000000000000000000 00000,0.000000000000000000000000,0.000000000000000000000000,5,4,0.0000 00000000000000000000,0.000000000000000000000000,0.00000000000000000000 0000,0.000000000000000000000000</StartKeyframe>

How can I know that 5,4 is correct, not 5.4?

Is there a way of knowing where in the file Premier Elements find the error?

All,

first of it is unbelievable that this still is an issue in Premiere Elements 10, when the issue is known for at least half a year. That just ruined my morning. Thanks everyone for the fixes here, that saved me 3 hours of redoing everything from the last working auto-save.

Thanks to VibaIT for hosting a website with the script, so everything was working again in 3 minutes.

Cheers

Pelle

http://www.vibait.com/software/premiere-fix-keyframe.h-142/

works like charm...