Skip navigation
SetAdMichael
Currently Being Moderated

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

Nov 13, 2011 11:29 AM

Hi all,

 

have spent my hole day at my brother but still no idea what this error could be. After having this project in APE 8.0 and editing it now with the newly bougt Verion 10.0, everything was fine... Opened and saved it several time but today there were suddenly problems: Even a complete new project with the same material and same cut is now broken after having saved and exportet it....

 

When we are trying to open the project, we're getting the error:

 

--------------

"Premiere Elements has encountered an error.

 

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

 

CONTINUE

--------------

And in the next window:

 

-------------

Project could no be loaded. It's damaged oder has old elements (not same words, cause my brother is using the german version)

--------------

 

 

I have tried everything so long: new installation, opening the damaged project on another computer with ELements 8.0 (identical error also there), deleting cahe, deleting Prefs, loading Auto-Backup (also damaged) and so on... Another "Test-Project" I have created with 2 clips is working fine.... I have no idea what to to else... The project is just a "normal" HD project with 20 Minutes and 20 Clips...

 

Everything on google (about 8 sites) I have tried - no success until now... :-(

 

so: any ideas???

 

Thanks a lot!

 

Michael

 
Replies
  • Currently Being Moderated
    Nov 13, 2011 11:46 AM   in reply to SetAdMichael

    Michael,

     

    I am not familiar with that particular error, but I would immediately look in the PrE AutoSave folder, and Copy those PREL files to another folder. If the PrE 8.0 Project is still intact, I would do the same with the AutoSave PREL files from it to.

     

    Then, I would explore Opening the AutoSave PREL's, to see how things behave. Note: AutoSave files are FIFO (First In - First Out), and are being constantly overwritten, as one edits over time. That is why I suggest doing the Copy action immediately. If the default has not been changed, there should be five PREL's, in each of those two folders (the PrE 10, and PrE 8 Projects' folder hierarchy). When looking at the files in Windows Explorer, set the View to Details, so that you can see the Date/Time of each file. The AutoSave PREL, marked 3, may well be more recent, than say 5.

     

    Good luck, and maybe others will have more input, specific to the exact error messages.

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2011 3:16 PM   in reply to SetAdMichael

    OK, quick question: As PrE will continue doing AutoSaves, while you edit, so that with a long session, if something has gone wrong early, the older AutoSaves will have likely been overwritten - on the PREL files, do any date from back when things worked well? If so, and as you say, they are also showing problems, my question would be, what has changed with the system, from the time that things worked, until now? Have you added any new software, or hardware? Have you reconfigured anything that you can think of?

     

    As a test, create a new System Restore Point for now, and then reboot to Safe Mode, choosing to use another System Restore Point, from when things worked well. Reboot, and attempt to load one of the PREL's. Do you get the same errors?

     

    Good luck, and let us know how this test goes, please,

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 19, 2011 6:51 AM   in reply to SetAdMichael

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

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 28, 2011 6:13 AM   in reply to SetAdMichael

    Try following which is workaround for this problem, should resolve the issue:

     

    For the issue that ends up in a corrupt project, please do the following:

    1.     Download perl from http://www.activestate.com/activeperl...

    2.     Open cmd prompt

    3.     Run this command from there

    perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" damaged.prel >working.prel

    4.     Please specify the path for the prel files that cause the issue in place of the text “damaged.prel”

    5.     Reopen the project and let me know how it goes.

     

    Exact command with paths should go like

     

    perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" C\Users\...\Desktop\AVCHD.prel >C\Users\...\Desktop\AVCHD_working.prel

     

    Please let us know if this is resolved or not.

     

    Thanks,

    Tahseen

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 28, 2011 10:48 PM   in reply to SetAdMichael

    Well, then share the project file with us. Sent you a mesaage about where to send the file.

     

    Thanks,

    Tahseen

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 4, 2011 8:27 AM   in reply to Mohammad Tahseen

    Hello Mohammad,

     

    I get the same error Message after replacing the "," with "." in the Keyframe sections. Unfortunately most of the backup files contain the same error. Only those still existing from Premiere Elements 9 (still installed) are correct. Can you please give a clue what's wrong with the new files. - I could send you my project file too, if it helps.

     

    I am using a German version of Windows 7 - 64bit and Premiere Elements 10 - 64bits.

     

    Greetings,

    Jens.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 6, 2011 11:17 AM   in reply to SetAdMichael

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 6, 2011 11:47 PM   in reply to SetAdMichael

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2011 2:06 PM   in reply to cloud565

    Hello,

     

    HANDLE WITH CARE - I found a solution for my file!

    My Theory seems to be working: It seems be the wrong interpretation of language settings.

     

    1st fix (see above, you did this already):

    • This fix replaced all numbers having "," as a separator and 12 or 24 digits after the separator. Numbers like "0,000000000000" or "0,000000000000000000000000" were replaced by the same values with "." instead of ",".
    • perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" damaged.prel >working.prel

     

     

    2nd fix (I found out this works for me):

    • The second error is in the <Keyframes> lines. When I replaced the ";" by "," or ":" (see below) the file could be opened successfully. But I don't know if this is causing other problems with keyframes.
    • HANDLE WITH CARE
      perl -p -e "s/([-0-9]+?)\.([0-9]{12,24});([0-9]{15})/$1.$2,$3/g" damaged.prel >working.prel
      HANDLE WITH CARE
    • A sample Line before replacement looks like this:
      <Keyframes>914457600000000,-0.027113247662782669000000:0.6475177407264 70950000000,0,0,0.000000000000000000000000,0.166666666666666660000000, 0.000000000000000000000000,0.166666666666666660000000,0,0,0.0000000000 00000000000000,0.000000000000000000000000,0.000000000000000000000000,0 .000000000000000000000000;914711616000000,-0.027113247662782669000000: 0.647517740726470950000000,0,0,0.000000000000000000000000,0.1666666666 66666660000000,0.115712793257603460000000,0.166666666666666660000000,0 ,0,0.000000000000000000000000,0.000000000000000000000000,0.00000000000 0000000000000,0.000000000000000000000000;915981696000000,0.49961149692 5354000000000:0.408149182796478270000000,0,0,0.11571279325760346000000 0,0.166666666666666660000000,0.000000000000000000000000,0.166666666666 666660000000,0,0,0.000000000000000000000000,0.000000000000000000000000 ,0.000000000000000000000000,0.000000000000000000000000;916235712000000 ,0.499611496925354000000000:0.408149182796478270000000,0,0,0.000000000 000000000000000,0.166666666666666660000000,0.000000000000000000000000, 0.166666666666666660000000,0,0,0.000000000000000000000000,0.0000000000 00000000000000,0.000000000000000000000000,0.000000000000000000000000;< /Keyframes>
    • Can Adobe please confirm these problems. I could send my broken file too if it helps.
     
    |
    Mark as:
  • Currently Being Moderated
    Dec 11, 2011 1:59 PM   in reply to SetAdMichael

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 7, 2012 10:11 AM   in reply to SetAdMichael

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 7, 2012 2:45 PM   in reply to Kinou31

    If your problem is exactly the same, you should start by using exactly the same solution that worked for the original poster.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 8, 2012 2:37 AM   in reply to Steve Grisetti

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 8, 2012 3:27 AM   in reply to Kinou31

    Hi Kinou,

    I know how you feel, it's really frustrating. Just one hint, though... In my solution, I did not list all erronous occurrences of "," ! I listed some of the common patterns, but there are other lines where you really have to do a search/replace on an individual basis. So, if you really want to recover your project, it is my experience that you have to go through the entire file looking for the tags and the syntax that I described above. One missed "," where a "." should be will corrupt the project! I could see my progress in the increase of the percentage the project loaded before I got the error message. Hope this helps...

    Good luck, Rainer

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 12:06 PM   in reply to Kinou31

    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.?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 12:03 PM   in reply to Kinou31

    I spend some time, same as you. Did al those 3 things. script1, script2 and replace ,,  0,5  and the ,< thing. But again same error.

    And there is post above with text "This list is not complete"

    What need to be done more?

    I find this very annoying!

    All Automatically created recovery/saved files have different date and timestamps and i thougth to use one of the latest. But that also does not work? Same Keyframe.h-142 error.

    When will the fix come Adobe?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 10, 2012 1:49 PM   in reply to sgm_maffe

    Remember, this is a user-to-user forum.

     

    If you'd like to contact Adobe, click the Contact Adobe button at the bottom of any page on this web site.

     

    They are open to bug reports and feature requests.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 12, 2012 11:35 PM   in reply to SetAdMichael

    Made a console application (Windows) that solved this problem for me (based on the above regex but with some modifications). Make sure to backup your data before trying this! You need .NET4.

     

    http://www.slottet.org/downloads/Premier10ProjRepair.zip

     

    Usage:

    Premier10ProjRepair.exe <input.prel> <output.prel>

     

    Thanks to SetAdMichael for the help with this. Hope this will be resolved properly soon! My experiences with Premier was so good until this fatal error occured .

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 13, 2012 1:03 AM   in reply to Sanctus799

    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....

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 13, 2012 8:29 AM   in reply to sgm_maffe

    With a PREL, the file size will depend on what one is doing. If a Project is Trimmed, Assets are Deleted, etc., the size of the file may well shrink. It is, after all, just an XML database, and contains links to Assets, plus instructions, that will be used, when one Exports/Shares to an AV file.

     

     

    Good luck,

     

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 16, 2012 3:11 PM   in reply to SetAdMichael

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 21, 2012 8:16 AM   in reply to Viba IT

    Yes yes,my prel is working again, thanks to tip in that post:

    upload your defect prel file and get a working back!

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

     

    Nice job!

    Only "one little thing", you need to check all the video- and audio fade-in and fade-outs!

     
    |
    Mark as:
  • Currently Being Moderated
    May 20, 2012 3:26 PM   in reply to sgm_maffe

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    May 21, 2012 9:07 AM   in reply to ERognlid

    Puh, solved my problem.

     

    I found a relativly easy way of figuring out the odd numbers Rainer talked about in his post. My solution:

     

    I run the perl script from Michaels post.

    Then did the ,< and ,, replace from Rainers post.

     

    Ending up with finding the odd numbers

     

    1) I made a copy of the perl file and change the filtype to .txt

    2) Opend this file in Excel

    3) Used filter sorting for <keyframe

    4) kopied that into a new workbook witch I saved as a txt fil

    5) I opend this file in notepad uses and replaces all the , with |

         (This step should not be necesary, but excel did not sort out the colums in my next step if I did not replace hte , )

    6) opend the new txt file and selected colums separated with |

    7) then I looked trough the file for abnormalities. It was relativly easy spotting the errors.

    8) When spotting an error, I searche for the number in my original PREL fil, witch I had opend in notepad and fixed the error

     

    I then repeated the proces from step 3 sorting for <startkeyfram

     

    I saved my project, but it is stupide that this error occure and Adobe has not mad a fix for it. If my memory is not wrong the exact same problem occured in an earlyer version of Premier 5-6 years ago.

     
    |
    Mark as:
  • Currently Being Moderated
    May 29, 2012 11:35 PM   in reply to sgm_maffe

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 3, 2012 12:36 PM   in reply to SetAdMichael

    hello... i found a really really easy solution for your/my problem on the internet!

     

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

     

     

    just upload your corrupt file and the fixed file will be automatically downloaded to your PC! it helped me a lot and my project works fine again!!!

     

    best regards and hope it will help you (although it's been a while since you posted it here)

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Jul 22, 2013 12:30 PM   in reply to Bill Hunt

    I don't have more solutions, but an observation on specific actions that may have caused this.  I have created more than 10 DVD's with no problems.  Then I used the "Fun in the Sun" disc menu on two projects an both were corrupted.  Another video created between theswe two was fine and used a different menu.  I always create a file version on my network storage to view for errors prior to burning DVD's.  The menus did not work correctly on these disk based versions, although the moves did play.  I just could not navigate the menu correctly (no highlights appeared).  The only other difference I can think of is the use of fade in at the beginning and fade out at the end.  I believe I have used this before, but perhaps not.  Although I can't be 100% certain, I hope this gives Adobe a clue as to where to look and may help some of you. 

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points