Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

[Jonas_D_Hollander]

Hello everybody,

I just ran into this extremely annoying problem:

Premiere Pro CS6 cannot load my project anymore. It gives the following error message:

Premiere  Pro has encountered an error.

f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

My autosave files all refuse to open giving another error
..\..\src\TickTime.cpp-364

When i press continue it says the project might be damaged or contain outdated elements.
I do not know what that means...

I do not know what i did last before the problem started, except for adding some layers (lightstreaks) rendering the file and then stopping that thinking "I'll do it later"

What a mistake. The projectfile didn't open anymore when i got home. All my autosaves now give similar errors.

I got warpstabilizer on some clips but would gladly give that up if there was a way to open these files. I cannot import them to a new project. Essentially the files refuse to open in any possible way.

You can find my latest projectfile here: jajageweetmaarnooit.prproj - Google Drive

I am desperate, this movie needs to be delivered tomorrow and i have to start all over.

[Kopecky]

Hallo Kevin,

Du bist hier in dem Forum zwar als Einzelperson eingetragen, aber sind dann Deine Stellungnahmen als offizielle Antwort von Adobe? Ich will dass fast nicht glauben, dass Adobe nach so viele Jahre so schnell gute Name verliert.

Warum wollen Sie (Adobe) das Problem erst in zukünftigen Versionen von Premiere Pro zu verhindern? Wir die Benutzer von der Premiere Pro erwarten, dass Sie diese Fehler noch bei jetzige Versionen beseitigen. Das Sie sind eigentlich dem Käufern von Adobe Premiere schuldig. In Ihren Text klingt das so, dass bei den nächsten Versionen, das bedeutet teurere Miete das erledigen? (Studenten haben schon die Ermäßigung, aber wie ist das z.B. mit Rentnern?)

Ich kann, wahrscheinlich auch mehrere Benutzer nicht auf i.Clouds verzichten. Wenn ist Ihnen schon die Ursache bekannt warum Sie als Hersteller keine Gegenmaßnahmen durchführen? Oder haben Sie keine Fachleute die das kennen? Wenn Herr Michael Schleider schafte auf Anhieb sofort eine provisorische Lösung, warum Sie nach schon so lange Zeit keine?

Ich - wir glauben noch Adobe und eintäuschen Sie uns nicht.

Vojtech Kopecky

[Kevin-Monahan]

Hi Kopecky,

I read a translation of your text and I think I understand what you were saying. I can respond to the translation.

Kopecky@t-online.de wrote:

Hi Kevin,.

You're registered in the Forum, but as an individual, but then are your opinions as official response from Adobe? I want that almost do not believe losing Adobe After so many years as fast a good name.

  Translations by Microsoft® Translator

Yes, I am the Support Product Manager for Adobe digital video products. I am also responsible for these forums.

Kopecky@t-online.de wrote:

Why do you want to prevent (Adobe) the problem only in future versions of Adobe Premiere Pro? We expect users of the Adobe Premiere Pro that you troubleshoot this more current versions. That you are actually guilty of the purchasers of Adobe Premiere. In your text that sound so that when the next versions, which means more expensive rent do that? (Students have been the discount, but what with pensioners, for example?)

  Translations by Microsoft® Translator

It sounds like you are upset that we have a bug written for future versions of Premiere Pro CC, but not for Premiere Pro CS6. Feel free to write a bug report for a fix in Premiere Pro CS6: http://adobe.ly/ReportBug

We do not yet have a bug written against CS6, so I would encourage all on this thread to fill out the official bug report to give us details of your issues. Bug reports from customers have a lot of weight here at Adobe. The more bug reports that are sent, the more likely we can create a fix in previous versions. Sorry if this is not the answer you wanted to hear.

Kopecky@t-online.de wrote:

I cannot, dispense probably several users on i.Clouds.If you are already the cause why you perform no countermeasures as a manufacturer known? Or have no specialists who know the drill? When Mr Michael Schleider immediately made a provisional solution, why you so long after it right off the bat time no?

  Translations by Microsoft® Translator

I'm sorry that you are upset, but we are doing our best to react to errors introduced by a popular application from another company. I think it's great that there are users that can help fix the problem with patches, etc. If you are upset that we did not immediately release a similar patch, please let us know in that bug report I recommended for you to write.

Kopecky@t-online.de wrote:

I - we believe still Adobe and a fool you not us.

  Translations by Microsoft® Translator

I understand your frustration, however, I don't appreciate name calling here on the forum. I would ask that you refrain from doing that in future posts. I'm a real person and am only trying to help.

Again, the best thing you (and others) can do is provide a detailed bug report. Our engineers will not see your forum response, but will see that report.

Thanks,

Kevin

[Whitetornado]

Bug report submitted.

[christianl79878423]

So why don´t your ingeneers never look to the forum?

So many questions so less anwers and a lot of frustration.

Where is the "Pro" ...???

Why don´t you give a feedback to your kollegs?

I expact a solution - not such advices like "deinstall iCloud" - this is far away from a professional solution... 😞

[Kevin-Monahan]

Hi Christian L,

christianl79878423 wrote:

So why don´t your ingeneers never look to the forum?

There are engineers on the forum and on this post. Sorry you missed them in earlier threads.

christianl79878423 wrote:

So many questions so less anwers and a lot of frustration.

Where is the "Pro" ...???

Sorry for your frustration.

christianl79878423 wrote:

Why don´t you give a feedback to your kollegs?

As much as I am able to, I am giving feedback to my team and to users on the forum.

christianl79878423 wrote:

I expact a solution - not such advices like "deinstall iCloud" - this is far away from a professional solution... 😞

That was the solution for Premiere Pro CC 2014.1 (8.1). We believe we have fixed it in Premiere Pro CC 2014.2 (8.2), but a new problem related to it has cropped up relating to any presets with keyframes that were migrated from 8.1 to 8.2. We are working on solving that issue right now. See the workaround in an earlier thread.

That's the info I have for you on this issue right now.

Thanks,

Kevin

[reneerijfff]

Yes, very happy to be able to work again... I was in real despair until I saw that I was not the only one, and now that your solution works, I'm really satisfied. Next time I'll find this forum sooner...

[berenice-v]

Hello,

i have the same problem, i try yours solutions and nothing change. I'm deseperate.

i work on this project since  2 years....

    windows 7 update

Complete reinstall of Premiere cs6 and CC

      deinstalling iCloud

changing the language settings to English (royaume uni) and setting the decimal to "." (I am normally onfrench in the systems install)

Also trying to fix project files with Martin's script did not help

Someone could help me please?

i try to found a solution since 2 months........:/

thanks everybody

[Syberious]

For the left audio problem, making a new sequence in your project and copy pasting everthing to it worked for me.

[cristiano_ra]

Thank you! Syberious I tested here did not work for me but it was a hint.

[Ashbane]

Unfortunately uninstalling "cloud " didn't help much. Guys this is some serious fail from Adobe side. Paying monthly fee for a product you can't fully use is a joke.

[300188]

Hello everyone,

I also have a problem like the one that is described in all the posts above. But the message I get is slightly different:

Can anyone tell me if it is the same bug as the one that you are discussing? (f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe). I see there is a patch to be downloaded but I don't know if it is safe for me with the different message?

In my case all this happened as I was changing computers end of September.  It happened both on the old computer  on which I had CS6 / CC and CC2014 and on the new one.

I cannot say if the bug is related to a recent upgrade of CS6 or to the fact that I installed CC2014 sometimes end of September. Everything was working perfectly with CS6 and CC on the old computer. The first crash occurred when I created a small  CC 2014 project with imported sources from earlier projects (CS5 and CS6).

I tried to open the same projects that was sitting on an external drive with the new computer. The project were not recoverable and got the same debug event window on the new computer.

I am based in France. I have Windows 7 pro, in French (That was the case also on the old computer)....  desperately need to move on with my work.... Thanks if you can help

[Whitetornado]

Hi, if I were you I would give this tool a try, it made it possible for me to recover a tremendous amount of work, after I uninstalled iCloud. I was able to get back to my earlier projects and get them totally fixed up.

The post : Re: Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

The man who did it : Michael Schleider

The tool : http://www.digitalschnitt.de/Support/cust/PremProPatch_keyframe.h-error.zip

Mes salutations aux amis cinéastes de la France

Marcel

Montréal Canada

[300188]

Hi Marcel and Kevin,

I tried to install the patch but it did not recover my corrupt project.

However I created a bunch of test projects and I found that they all seem to open correctly under CC2014. I then tried to open several older projects created under PProCC and once the CC2014 version was created  they seem to work correctly. What is new is that now PPro opens each time while yesterday once a project was closed due to the error I could not open PPro without restarting my computer....this is a mystery. Nevertheless  my situation  is not as bad as I thought. I only have 2 projects corrupted at this point. One was very short, I did it again in urgency and the new version works, The other one unfortunately involves lot of work and was not repaired.

I understand that apparently iCloud is the guilty one...I hesitate to uninstallit, I fear that all my agendas, notes etc get lost or messed around...(I am not very comfortable with that stuff), I will try to get some support from Apple to do that in a good way. and I will try again to correct my project afterwards with the Patch.

Thanks for your help.

Cristiana

[Kevin-Monahan]

Hi 300188,

300188 wrote:

I also have a problem like the one that is described in all the posts above. But the message I get is slightly different:

Can anyone tell me if it is the same bug as the one that you are discussing?

Yes, it is. Some of the text is truncated, however, so I can see why you might be confused. It is due to an update to Apple iCloud. Uninstalling iCloud solves the issue. There is a patch on this post to repair any existing files.

We know about the issue and are working on a fix. File a bug report here: http://adobe.ly/ReportBug

Thanks,
Kevin

[limafotografo]

Melhor solução até agora para mim funcionou

Hello @all,

I'm back and updated the programm, so more project files should be recoverd correctly without changing anything else in the project.

It's still the same link:

Version 0.0.1.21:
www.digitalschnitt.de/Support/cust/PremProPatch_keyframe.h-error.zip

Please let me know if it works now for everybody.

Michael Schleider

[300188]

Hi, I'm afraid I tried again and my project can't be recovered. The message when opening in PPro CC  says  " the project seems damaged, impossible to open it"

[cmfmakiss]

Hallo Michael,

ich bin sehr froh jemanden gefunden zu haben der sich mit diesem Problem auskennt!!!
Ich arbeite gerade an meiner Bachelorarbeit - eine Dokumentation - bin deshalb sehr aufgeschmissen! - und habe gestern Abend die hier oben angegebene Fehlermeldung erhalten. Ich kann die Datei nicht mehr öffnen, leider sind auch die letzten 3 Autosave Dateien beschädigt. Leider hat dein Programm bei mir nicht geholfen - auch nicht die upgedateten Versionen die ich hier im Verlauf gefunden habe.

Kannst du mir helfen?
Ich arbeite mit CS6.
ICloud habe ich nicht auf meinem Rechner. - kann es also nicht deinstallieren 😕

https://www.dropbox.com/sh/dl7jouhcqg0p8zk/AAAx3pubinMtuGPG8BG1zCwja?dl=0

Viele Grüße
Clara

[eknightGER]

I have the same error, but unfortunately not only for used projects. I cannot even create a new project for Premiere CC 2014.2 anymore. Each time I start the program, it shows me the start screen. Once I click on "new project" and enter the respective data I get the error screen:

Then Adobe Premiere Pro CC 2014.2 crashes violently back to the desktop (via the Windows "we try to solve your problem" issue).

• I cannot create new Premiere projects
• I cannot open _any_ former Premiere project
  • all on 2014.2 crash
  • all previous versions give me a window first for stating that they need to be converted - then they crash with the same error
• I can open the Adobe Premiere files in Speedgrade without a problem, but direct link into Premiere crashes them in Premiere with the same error
• I am not using any keyframes in the 2014.2 files that were broken (only trims)

This is what I already did without any impact to solve the problem

1. Complete reinstall of 2014.2 version of Premiere
2. rolling back to Adobe Premiere 2014.0 (or .1? Cannot say from installer)
3. upgrading back to 2014.2 version of Premiere
4. deinstalling iCloud (my system is now icloud free...)
5. changing the language settings to English and setting the decimal to "." (I am normally on German in the systems install)
6. Also trying to fix project files with Martin's script did not help

I am running Windows 8.1.

As I am also having trouble with new projects (no one else seems to have that): Is there a way to work around this? Is there an empty template that the system is pulling and that causes the issue already and that I could delete for getting a fresh start?

Thank you in advance. @Adobe: of you need any other information, just let me know.

EDIT: I tried to filed a bug report on this using the Adobe bug report form, but it gave me a 413 header length too large error - so I am afraid I have to monitor this thread to learn about potential solutions.

EDIT 2: I submitted a bug report. I reinstalled Premiere CS6 and while I cannot open the newer recent files, CS6 can at least create and re-open new files (I will check keyframes later). At current stage, _all_ my newer Premiere projects are gone and I cannot use Premiere for any new work either. Next step is me upgrading CS6 to the pre-CC2014 stage to see if I can open older files.

EDIT 3 - SOLVED (different from this): My issue seems to be different from this root cause and Adobe helped me in getting it fixed by removing the presets in C:\Users\<username>\Documents\Adobe\Premiere Pro\8.0\Profile-<username>  (delete, rename, or move the file "Effect Presets and Custom Items.prfpset") and they are investigating / testing it further. As I could not create new project files, it had nothing to do with the project files. So this solution will probably not work for those of you having the error described in this post. Many thanks to the Adobe folks for their great help and support.

[Hornet21]

Ciao a tutti,

non so se può essere utile, ma io il problema del debug l'ho risolto rinominando la cartella Adobe all'interno di C:/documenti con "Adobeold".

Ciao

Andrea

[DASTmedia]

too give some feedback:

I got the same Error and i couldnt even create a new project. I reinstalled, same Problem. In the End, i figured out, that Windows 8.1 installed an update for Net Framework. I reverted that and voila, Premiere CC 2014.2 works again!