Pe 13 debug event keyframe error h-142

When I open my previously saved and working project, I get a Debug Event with a keyframe h-142 message (see below).
The workaround proposed in adobe help under Keyframe.h-142 error | Opening projects does not work. I guess because PE13's .prel files are not in plain text format as PE12 and previously, therefore the workaround with perl will not deliver the required results.
Same issue with ALL backup files of this project...
Any suggestions?

I was able to fix the file with the information from post Re: Elements 10 Error: d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142
Here are the steps I performed:
1) rename my corrupt.prel file to corrupt.zip (when opening the file in notepad++, I saw a lot of gibberish and thought the file might be zipped, which it is. I am not sure whether this is only the case in PE13).
2) unzip the corrupt.zip and rename it to corrupt2.prel
3) download perl and run the following commands:
C:\Perl64\bin>perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" corrupt2.prel >corrupt3.prel
C:\Perl64\bin>perl -p -e "s/([-0-9]+?)\.([0-9]{12,24});([0-9]{15})/$1.$2,$3/g" corrupt3.prel >corrupt4.prel
4) Open the file in notepad++ and
search for ",," and replace it by ".,"
search for "0,5" and replace it by "0.5"
and save the file
There, that did it for me. The fixed file does not have to be zipped again for it to open in PE13.

Similar Messages

  • Debug event: Keyframes

    I have encountered a bug in Premiere Elements 10.0:
    I was editing a movie project, saved it, exited Elements, then tried to reopen it and got the error message
    Premiere Elements Debug Event
    Premiere Elements has encountered an error:
    [d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]
    Looking at my history of auto-saves, I found that the three most recent auto-saves showed the same error, the fourth one could be opened OK. That version was at the state of the project I had before starting to add DVD menus to it.
    Looking further at the project files (prompted by this forum entry: http://forums.adobe.com/message/4038119 and the strange solution proposed by it: using Perl to replace certain commas with dots), I found a striking difference between the last working and the first non-working solution:
    In the file that couldn't be opened, all decimal numbers in <StartKeyframe> and <Keyframe> tags had been saved incorrectly.
    For example, a line like
    <StartKeyframe>-91445760000000000,1.,0,0,0.,0.,0.,0.</StartKeyframe>
    had become
    <StartKeyframe>-91445760000000000,1,,0,0,0,,0,,0,,0,</StartKeyframe>
    Obviously, PE was using the current locale's (Germany) settings for the decimal point (which is a comma) to save those values instead of the dot it needed to be able to reopen the file.
    So I first tried the solution in the above post, but I found that the regex provided there didn't catch all the incorrect commas. I tried it again with the regex
    s/,(?=[,<]|\d{10})/./g
    replacing every comma that was either followed by another comma or an opening angle bracket or a decimal fraction (all of which are > 10 digits) with a dot.
    This looks like it fixed this problem (at least now there were no differences in the decimals between those two versions when I compared them with Beyond Compare), but the file still refused to open (with the same error message). Of course there are still >2100 differences between the two files (there are about 20 minutes of editing between them), but after looking at about 100 of those, I didn't find anything that looked suspicious (at least nothing in the vicinity of "keyframes"). But of course I don't know if I'm looking for the right thing.
    So is there any way to check for other errors that make the file invalid? Any hints?
    Also, how come this bug is still there (it looks like it exists since PE 8)?
    Thanks and best regards,
    Tim

    Ah, drat. Posted too soon: I have "fixed it"!  On the other hand, maybe others can profit from this solution:
    What I had overlooked: There appears to be one case where a decimal number has less than 10 decimal digits, and that's when that decimal number is 0.5. (I'm worrying a bit that there might be other exceptions, but I haven't found any in my files).
    So, the following solution worked for me, allowing me to open the project successfully:
    Using a decent text editor (one that supports regular expressions with lookahead assertions, for example EditPadPro or UltraEdit (when setting it to Perl regex mode), search for
    ,(?:(?=[,<]|\d{10})|(?<=\b0,)(?=5\b))
    and replace all with a single dot (.)
    This regex searches for a comma that is either followed by another comma, an opening angle bracket, a decimal fraction of at least 10 digits, or the number 5 (but only if that comma is preceded by the single digit 0).
    This allows me to open the project again. However, as soon as I save it again, the file gets corrupted again.
    Interestingly (and possibly related), when I try to open the (repaired) file, a PE information window appears ("PE is updating a component. Information is being transmitted..." or something like that in German) and a Windows 7 UAC dialog pops up, asking me to allow the Windows Regserver to modify my system. It doesn't matter whether I allow or deny that request (which appears twice in succession, by the way), as soon as I save the file again, it's corrupted.
    The commands that are asked to be executed are:
    C:\Windows\System32\regsvr32.exe /s "C:\Program Files\Adobe\Adobe Premiere Elements 10\mc_dec_mpa_ds.ax" "C:\Program Files\Adobe\Adobe Premiere Elements 10\mc_dec_mp2v_ds.ax"
    and
    C:\Windows\SysWOW64\regsvr32.exe /s "C:\Program Files\Adobe\Adobe Premiere Elements 10\32\mc_dec_mpa_ds.ax" "C:\Program Files\Adobe\Adobe Premiere Elements 10\32\mc_dec_mp2v_ds.ax"
    But at least I can now re-open that file after "fixing" it.
    Still it would be nice if Adobe could fix this problem. Is this the right place where Adobe technicians will read it and act on it, or do I have to do something else?
    Some system information: Windows 7 Pro 64bit with all current patches, 64-version of PE 10.0 installed.
    Cheers,
    Tim

  • PE 11 new install on WinXP system - Debug event error, can't open program

    Hi everyone,
    I searched the community for similar errors and followed a couple of troubleshooting steps suggested for older versions of PE, but they didn't work. I just installed Premiere Element 11 on my Windows XP office desktop (also installed PS Elements 11, which works without a problem.) Install went well and I rebooted the system as prompted. Every time I attempt to open Premiere however (I am not attempting to load any video files, I just want to open the program to start a new project), I get the splash screen at first, but after a few seconds of "Loading" and/or "Initializing" a bunch of parameters, the program hangs and following screen pops up:
    "Premiere Element Debug Event"
    Premiere Element has encountered an error.
    [..\..\Src\Core\Preferences.ccp-338]
    Continue
    When I click on "Continue" the following window pops up:
    "Microsoft Visual C++ Runtime Library"
    Runtime Error!
    Program: ..e\Adobe Premiere Elements 11\Adobe Premiere Elements.exe
    The application has requested the Runtime to terminate in an unusual way.
    Please contact the application's support team for more information.
    OK
    So, here I am support team... Need more information, lol. I will also add that clicking the OK after the second window pops up often doesn't close the Premiere splash window still visible in the background, I have to CTRL-ALT-DEL and kill it manually by ending the process in Task Manager.
    I installed the same program - same s/n - on my home computer as well, with no issues (that's a much newer, and much faster, Windows 8.1 system however.) I think you are entitled to install 2 copies though, right? So this wouldn't be related to too many attempts to register the same software?
    Thanks for any help.

    umbertob
    Wea re not Adobe. We are Premiere Elements users who visit here under our own free will (unscheduled) to help other Premiere Elements users with their Premiere Elements workflows.
    Please detail the resources of your Windows XP computer. What edition is it...professional, home premium, or other? You realize come April 2014 Microsoft will discontinue support for Windows XP. Apparently you can continue to use it, but Microsoft points to security risks in that state.
    a. how much installed RAM, how much available
    b. how much free hard drive space
    c. is the video card/graphics card used by the computer up to date according to the web site of the manufacturer of the video card/graphics card.
    Did you install the program to the computer default location according to the installation process?
    Please review and then we can discuss the details.
    Thank you.
    ATR

  • An error has occurred while opening the Premiere Pro CC 2014: Premiere Debug Event

    An error has occurred while opening the Premiere Pro CC 2014: Premiere Debug Event
    [c: \ cloudroom \ releases \ 2014.9 \ shared \ adobe \ mediacore \ mediafoundation\API\in
    I don't know what to do, any help?

    Delete the  Effect Presets and Custom Items.prfpset, located in
    C:\Users\<username>\Documents\Adobe\Premiere Pro\8.0\Profile-<username>
    when succesfull make new project and import old one into new one.
    Might need to reset current workspace and pull down the audiotracks first to reveal videotracks.

  • Debug Event : Premiere Pro has encontered an error. [..\..\Src\PPixhandleUtilities.cpp-114]

    Hello,
    I have problems in Adobe Premiere CS3, as below:
    1. =================================
    Debug Event:
    Premiere Pro has encontered an error.
    [.. \ .. \ Src \ PPixhandleUtilities.cpp-114]
    2. =================================
    Adobe Premiere Pro is running very low on system memory. Please save
    your project and proceed with caution.
      ================================================== ======
    I've tried to reinstall Adobe Premiere of her, but the problem persists.
    What should be done to solve this problem which paralyzes all my work?

    How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

  • "CAHeadless Debug Event" Error message

    I have Adobe Photoshop Elements 9.0 installed on my Windows 7 computer and have recently started getting a message that I believe may be associated with that program. The message reads "CAHeadless Debug Event" "CAHeadless has encountered an error - [..\..\Src\DataManager.cpp-410]"
    Does anyone know what may be causing this message and how to cure it. I am able to click the Continue button and everything works as it should but it is a little annoying.
    Thanks
    Patrick
    Message title was edited by: Brett N

    I am also having the same CAHeadless Debug error on PSE 9.
    Switching catalogs does not help.
    Turning off face recognition does not help.
    I have looked through the forums and on the internet and it seems that this is a common problem for PSE 7, PSE 8, and now PSE 9.
    Does anyone have a solution?

  • Premiere Pro Debug Event - Premiere Pro has enconuntered an error.[..\..\src\TickTime.cpp-290]

    Ho salvato un progetto Premiere Pro CC (2.2014) tre volte successive con i nomi: telecinema1.prproj, telecinema2.prproj e telecinema3.prproj. Tutto ha funzionato regolarmente e per fortuna ho esportato tutti i file e anche alcuni _copiati con Project Manager.
    Ad un certo punto però quando ho cercato di riaprire il n.3 mi è uscito il seguente avviso: Premiere Pro Debug Event - Premiere Pro has enconuntered an error.[..\..\src\TickTime.cpp-290] con relativo crash.
    Non mi sono preoccupato e ho provato ad aprire il n. 2, ma anche questo e poi anche il n. 1 mi hanno dato lo stesso problema.
    Ho riscontrato che si tratta di un errore ricorrente, ma non ho trovato nessuna segnalazione con TickTime.cpp-290.
    Cosa faccio? Grazie

    How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

  • Debug Event Error

    About two weeks I asked for help. Hunt kindly responded with a request that if it happened again I am to give him certain information. I tried to do so by replying to his email, but for some reason it is being returned as undeliverable, so here are the basic messges again:
    Quite frequently, I receive the following error message:
    Premiere Elements Debug Event.
    Premiere Elements has encountered an error.
    [..\..\src\PlatformWindowsManager\PlatformWindowsManager.cpp-132]
    The only option presented is a button which, if clicked on, exits the application without saving the content.
    What is happening here? Obviously, this becomes very aggravating after a while.
    Many thanks.
    Walter
    And here is the email I could not send to Hunt:
    Hi Hunt,
    Its happened again. Here are the events.
    I had been capturing files from my DV video camera for about 3 hours. After each capture, I saved the captured file, opened a new file (not necessarily in the same folder) and started another capture.
    I had just completed a capture and saved it and moved the timeline slider to be able to check one of the scenes (I don't remember if I actually pressed the Play button.) when the message appeared again. As before, when I clicked on "continue" the app shut down.
    My assets are:
    Processor: 2.40 gigahertz Intel Core2 Quad Q6600, 64 kilobyte primary memory cache, 4096 kilobyte secondary memory cache
    Memory: 3072 Megabytes Installed Memory, Slot 'DIMM0' has 1024 MB, Slot 'DIMM2' has 2048 MB
    Main Circuit Board: ASUSTeK Computer INC. P5K-E Rev 1.xx, Serial Number: MS1C81BP5K01234, Bus Clock: 266 megahertz, BIOS: American Megatrends Inc. 0906 12/10/2007
    Drives: 1550.33 Gigabytes Usable Hard Drive Capacity, 1195.40 Gigabytes Hard Drive Free Space
               HL-DT-ST DVDRAM GSA-H10N SCSI CdRom Device [CD-ROM drive]
               3.5" format removeable media [Floppy drive]
               Canon MP Memory Card USB Device [Hard drive] -- drive 2
               Maxtor OneTouch II USB Device [Hard drive] (300.08 GB) -- drive 3
               ST3500320AS [Hard drive] (500.11 GB) -- drive 0 (C Drive)
               ST3750330AS [Hard drive] (750.15 GB) -- drive 1
    OS:  Windows XP Home Edition Service Pack 3 (build 2600)
    Display: ATI Radeon HD 3800 Series [Display adapter], ViewSonic VP930 Series [Monitor] (19.3"vis, s/n PQ8053603156, September 2005)
    MultiMedia: ATI Function Driver for High Definition Audio - ATI AA01, Panasonic DVC Web Camera, SoundMAX Integrated Digital HD Audio
    I hope this will help - many thanks
    Regards,
    Walter 

    Walter,
    I would assume that the e-mail notification feature is the little notice of a new reply to a post, that has been checked with the e-mail notification. To contact me, either the e'dress in my Profile, or an Adobe PM (Personal Message) sent from my Profile should reach me.
    Now, with your error message, go to the Event Viewer (located in a couple of different places, depending on one's OS), but usually in the \\\System32 folder. It's also accessible from Programs>Utilities [?]. I have a shortcut on my Desktop, the moment that I get a new computer, so I'll have to look for it specifically, and then can only tell you where it is in XP-Pro SP3 - file name = eventvwr.exe.
    In its opening screen, you'll see two windows. Look to the left and find "Application," and "System." Dbl-click on Application first, and you'll see a long list of programs and Processes. Scroll down, until you see some yellow triangles, and red circles with a white X. The name will begin with "Error," while the yellow triangles will read "Warning." Find some of these around the time/date as your crash. Dbl-click on each to get a dialog box. There may be useful info in there, but if there are any links, please follow those and read very carefully. Much can be contained in those links.
    You might be better to do this, as soon as the program has thrown the error, and crashed. Then, you do not have to search down into the lists. Also do this for System, as well.
    Doing this might lead to some clues into your mystery.
    Screen-cap of Event Viewer:
    Good luck,
    Hunt

  • "CAHeadless Debug Event" Error

    Greetings,
    I am getting the following error popping up in a dialog box about every five minutes:
    CAHeadless Debug Event
    CAHeadless has encountered an error.
    [..\..\Src\Clip\VideoClip.cpp-276]
    I have to click "Continue" to make it going away temporarily.
    As a workaround, if I click Edit > Preferences > Media-Analysis, and clear the "Analyze Media for Smart Tags Automatically" box, the errors stop. But I was wondering if here was an actual fix for this error, instead of just a work-around which I discovered.
    Thanks,
    Shane.
    Photoshop Elements 11.0
    Windows 7 Home Premium SP1 64-bit
    Message was edited by: c_Shane

    They don't take up much space—but since I installed version 11 there has been a lot of weird and strange behaviour, and I'm just trying to figure out what's causing it.
    I deleted psa.prf, restarted PSE, and re-selected my preferences. Unfortunately, I'm still getting the error.
    I notice that when I click Edit > Preferences > Media-Analysis,  and click "Analyze Media for Smart Tags Automatically", a process called "ElementsAutoAnalyzer.exe" starts, and I start getting the error. When I clear "Analyze Media for Smart Tags Automatically", the "ElementsAutoAnalyzer.exe" process ends, and the error messages stop.
    I'm guessing the only work-around is to not use this feature.
    Shane.

  • Pro Debug Event - Error 290 /tick time

    Suddenly a project I was working (and all the auto-saved folders) could not open anymore by giving me the following message: "Pro Debug Event - error 290 tick time"

    Whenever you enounter an error, as a general rule, search the forum to see if it's already been addressed, or to join the discussion:
    TickTime.cpp-290 error after opening a specific project | Premiere CC 2014.2 | Windows 8.1
    Also, I always convert/ingest my media to use the same format that runs natively in PPro and does not require conforming.
    Second, with regards to losing work with projects that can't be fixed. I always save my projects incrementally to new names as I go.  When I hit an issue that cannot be resolved (and occasionally I do), I reopen the previously saved project and try something else.  In fact today I hit a stack error.  It was a three-day edit, and I was on version "(project name)_028.prproj"  I just opened up the previous version "..._027.prproj", repeated the few edits that I lost in "028" and rendered without error.  Follow that?
    Anyway, read the link above for a possible fix.

  • Can uninstalling and installing CS4 fix the debug event error message?

    Hello,
    Can uninstalling and installing  cs4 solve the debug event error message?

    Can uninstalling and installing  cs4 solve the debug event error message?
    Well, that DOES seem to be the scripted mantra of Adobe TS in some out of the way country. According to most reports, that cures everything from trying to Capture over a USB cable to working with footage from your cellphone camera. In most cases, it has cured very little, though maybe the Debug Event error IS something that will be fixed by this.
    Good luck,
    Hunt

  • Debug event prevent opening of project

    Hei
    Suddenly i am not able to open my project. A "debug event" appears:
    Premiere Elements has encountered an error.
    [d:\pre\mediacore\mediafoundation\api\inc\Keyframe/Keyframe.h-142]
    Its importent for me to open this project.
    It worked without problems with the 30-days test version of premier elements. After buying the software, this problem suddenly appears.
    why? And how can i fix it?
    akka heima

    From what I have read and understood about this error (keyframe.h-142 error) I can assure you that the error is not because of the contents of your timeline. It has more got to do with how Adobe writes the project files. The prel file. That is the one that gets corrupt and there have been umpteen attempts to correct it through a script, a webpage, manually replace some entries etc. but nothing has a 100% fix for all the projects encountered.
    We just have to pray that Adobe understands this and provides a fix. It is upto them alone to fix. The only thing I see common in all the cases that I have read through in various forums is that the machine language/installation language is not English. One of the forums was a Premiere Pro forum and there was one post that was 4 years old. So it just seems that it is a problem that Adobe knows but just does not Want to fix/ or know how to fix. Thet should certainly be aware of this. Hope they are because this thread is only growing in all the forums and in Premiere Elements' case it has only surfaced in the latest release, PrE10.
    So to summarize, this is my understanding:
    1. Only seen in Non-English
    2. Been there a long time - (4+ years in Premiere Pro and ~6 months in Premiere Elements)
    3. Happens in Premiere Pro (so PrE is not the only product affected).
    4. Only project file gets corrupt (because recovery on this alone has worked for some)
    5. Has something to do with a comma (,) and dot (.) separator in the project file
    6. Happened in some cases where a previous version project was opened.
    7. Some say it happened aftyer a render was done and project reopened in the same version.
    8. No common steps in any of the reports thus far, to get to this error.
    If I were you, I would just complete the process and log a bug in their database and wait for Adobe to finally hear us..
    My mistake - Premiere Elements has also thrown this error 5 years back!!
    http://www.clubic.com/forum/logiciel-multimedia/bug-dans-adobe-premiere-elements-id404804- page1.html
    Message was edited by: VDOSurfer

  • Getting Premiere Pro Debug Event message when trying to open project

    I cannot open my project any more.
    Last thing I did was saving, then exporting when Premiere pro CC crashed. Now I cannot open the file and also not all Adobe Premiere Pro Auto-Save files.
    I used an AVI file exported from another Premiere project, 2 iPhone videos and an MP4 video from another mobile phone plus a WAV file for sound (home made music video).
    Does anybody have an idea what I can do?
    I deleted the files in C:\Users\...\AppData\Roaming\Adobe\Premiere Pro when Premiere didn't start.
    The Debug Event appears everytime I start the project and when I start Premiere and open the project afterwards.

    This is caused by an update to iCloud. More info here: Crash with keyframe.h-146 error when you open a saved project

  • Premiere crash, when calling a recently saved project (Keyframe Error)

    Premiere Absturtz beim Aufrufen eines kürzlich gespeicherten Projektes.
    Error:[fi:mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\Keyframe
    Message was edited by: Kevin Monahan
    Reason: added "Keyframe Error" tag and to title of post

    Hallo,
    habe das selbe Problem, Windows 7 64 Bit.
    in Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe hatte ich bereits gelesen, das das Entfernen von ICloud helfen könntel. Dies hat bei mir aber nichts bewirkt.
    Was wirklich strange ist, ist die Tatsache, das ich mein Projekt am Sonntag, also vor 2 Tagen erstellt und mehrfach geöffnet  habe und das das selbe Projekt nun (2 Tage später) den Fehler wirft.
    In der Zwischenzeit ist kein Windowsupdate oder dgl. gelaufen...
    Ich hoffe sehr, das Adobe da schnellsten was macht. Ich habe ein Projekt, an dem ich schon seit einem Jahr arbeite und auch das ist aktuell nicht zu öffnen....
    Bisher habe ich immer grosse Stücke auf Adobe Premiere gehalten. Ich hoffe ich muss meine Meinung nicht revidieren...

  • Keyframe error after switching my windows to English interface. How do I fix it?

    (I got a Keyframe) Error after switching my windows to English interface, I could save and open projects normaly!   Unfortunately damaged projects still didn't worked...  But the new once are ok, and I hope that error won't happen again! But guys from http://www.premiere-pro
    tengo estos errores.
    Message was edited by: Kevin Monahan
    Reason: Next time create a shorter title, then put the text describing your issue on the next page.

    Hi C Del Producciones,
    Uninstall iCloud. See this forum post: Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
    Thanks,
    Kevin

Maybe you are looking for

  • Photoshop CC: unable to open Raw files from Canon T1i

    I am trying to edit photos in the raw CR2 format I took with my Canon T1i.  I cannot get the new Photoshop CC to open them.  I think I need a plug in to do this but cannot find out where to download the plug in.  Please send a link to the plug in 5.4

  • Why is one TIFF pixelated when saving .pages file as .doc?

    Hi, when I save my Pages file as Word '.doc' format (using the standard 'save copy as' method, OR exporting as .doc) one of the high resolution TIFFs in the file always shows up pixelated, the other is sharp. Do you know why one TIFF would be pixelat

  • Merging from an old backup

    I've just received word from a couple of users that they don't have any email at all before a certain date. The only backup I have is a few months old. Comparing random emails from the backup and the current mail store for one of these users shows me

  • How to re-install Photoshop CS5? [was: crash computer with older version (dell laptop)]

    My notebook had a crash and we had to reinstall it. it is a dell machine, winddows 7, Photoshop CS5 this was its summary befoire crash: Adobe Photoshop Version: 12.0 (12.0x20100407 [20100407.r.1103 2010/04/07:14:00:00 cutoff; r branch]) x64 Operating

  • ALE Distribution for alternate BOM environment

    Currently the ALE framework does not support distribution of alternate BOMS between SAP r/3 systems. Does anyone know if there is a workaround for this issue? Please provide any input. Thanks.