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

Similar Messages

MediaCore Importer Process Debug Event

I have a Xp 64bit computer running CS4. I keep on getting MediaCore Importer Process Debug Event Errors on differnt projects. The error details are sometimes different but usually they say. Src/importer/ImporterInstance.cpp.-641
I have scanned for viruses
I have repaired windows
I have repaired premier
I have deleted and reinstalled premier
I have updated the drivers on my video card
I have looked around here and haven't found much for help. It might be a specific file given me problems but I have not tracked it down yet. It might be a codec problem. I am running out of ideas

My computer was working fine until 2-3 weeks ago. No changes except for maybe a CS4 update. Scanned for viruses nothing but a few cookies.
Supermicro board
dual 2.6 ghz intel quad xeons
8 gigs of Wintec Ram
Nvidia Quadro (dual monitor)
Alesis audio card
Adaptec raid controller
Seagate hard drives (about 2 tb raid 10)
Pannasonic DVCpro Deck (firewire)
Windows XP 64 (just repaired - trying to fix problems)
It is connected to a Cisco Switch for file sharing.
Updated CS4 PP
Most video footage is from gyhd100u but we get footage and video from many sources
I am looking for a post from someone who has had this problem, fixed this problem, or has some insight to what a MediaCore Importer Process Debug Event means.
I have been using Adobe Products for over 10 years and I am very computer savy. Even if you are looking to fix the same problem send me some info and maybe I can narrow it down and fix it for both of us.
Right now I think it might be my video card. When I repaired windows I upgraded the drivers on it now I have even more problems. I am rolling them back right now. If that doesn't work I will rollback premier

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

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.

Corrupt audio file prevents me from opening Logic project file

Hello,
I've been running Logic 8 for a couple years off my MacBook and have never encountered any significant problems of file corruption until recently.
The issue I encountered is this:
I've been producing a lengthy track in an on-going Logic project file for some time and after completing a recording session I saved and started deleting excess track copies to clean up my arrange window. Upon doing so Logic unexpectedly crashed.
After attempting to reopen the project file, it started its normal process of loading its respective audio files, but now it hangs on one particular audio file indefinitely (I'll refer to it as 'audio file x' for ease of reference), freezing and crashing Logic as a result. All of this project file's auto backup files are also incapable of being opened without giving me the same result and crashing Logic.
I have no way of opening this project file and getting at my most recent saved sequence!
I've tried removing this corrupt 'audio file x' from the project's audio folder and dragging it to the desktop, but this had no effect and I still can't open any recent version of the project file.
Older saved copies of the current project file do still open though (most likely because they were saved prior to the corruption caused by this suspect 'audio file x.') When opening an earlier iteration of the project, I get a message '1 invalid audio region found' (I assume referring to the corrupt suspect 'audio file x' that I removed to the desktop) but the project file is still able to open.
I realize I could import the audio files from the most recent version of the crashed file to an older project version and reconstruct things back to the way they were, but it would take me a lot of time and I'm hoping there may be some way to recover the un-openable project file by getting it to stop looking for this corrupted 'audio file x' on startup.
When I click 'show package contents' of the Logic Project file, I notice two items labeled 'displayState' and 'documentData.' From my troubleshooting I've come to the basic understanding that the 'documentData' file contains all the sequence data and settings for its respective Logic Project file.
I think the 'document data' of the unopenable project file in question may be corrupt because whenever I replace it with the 'document data' from an earlier Project file version, the file is able to open. This doesn't do me much good though, because it's document data from an earlier iteration of the project and I need to be able to get at the current sequence I had right before my file crashed.
Is there anyway to open a project file without letting it load its audio files? Or is there anyway I could get inside the 'document data' file to delete the reference/pathway in its audio bin to the corrupt 'audio file x' its hanging on?
Any insights would be greatly appreciated. I'm hoping there's some way I won't have to repeat a couple days worth of work. Thanks for your help!

stooby3535 wrote:
After further troubleshooting I've realized that the suspicious audio file that prevents the project file from opening is actually not corrupted itself. I can still play the audio file in other media software like Quicktime, etc. with no problem.
This leads me to believe the problem opening the project file lies solely with the corrupted 'documentData' file.
Does anyone have any ideas about how I could somehow open this project file and delete the reference of the troublesome audio file from the project's audio bin?
Well... it really sounds like the project itself is corrupted, that's one of the reasons all project files won't load from a certain point on.
Try this.
Reboot the Mac.
Open the Applications folder and boot Logic from it's icon.
As soon as the Logic Logo/graphic window appears on the screen hold down the control key. You will see a message pop up that says something like "Launch the Core Audio Driver" there will be yes/no choice available... select NO.
Go to the File menu and selct "open" go find your project file and see if it will open. If it does.. delete the audio file in question... however.. I would also look at any plugins you recently installed and are possibly using in this project...this sounds more like a plugin problem rather than an audio file problem, but that's just a gut feeling.
Anyway, if it opens delete whatever you suspect and save under a different name.
Reboot Logic and see if it can load the project.
pancenter-

After renaming and moving to my desktop an iMovie project, i can not open it. I moved it back to iMovie but still it is not working. I noticed that there is not an Event Folder for the project. Can someone help me?

I renamed an iMovie project, then I moved it out of iMovie to my desktop. It did not work from there. Finally I managed to move it back to iMovie, but still does not work. I can't edit it, it does not even appear as an option. I found out that the Event Folder for this Project is gone. Is this the problem? Is there a way I can get it back? Can somenone help me?? Obviously after so many mistakes you can tell I am new on this. Any help will be appreciated it!!!!!

OK Let's take a step back.
If you imported video clips from a camcorder there would be an Events folder in the Movies/iMovie Events/ folder.
You have the option as you import from a camcorder to send your Event to an external drive instead. In this case, it would be in the iMovie Events folder at the top level of the external drive.
If your project has no video clips, but only photos, there may be no events folder, only links to iPhoto.
Similarly, if your camera imported your video clips to iPhoto, and you used the iPhoto event in iMovie, then your clips are in iPhoto, and there is no separate iMovie event.

Have Software Performance issues & now it simply won't open any project!! Help!

Hi,
I have following issues
1. I am working on Premiere Pro CS5 and when it comes to minor modification of images/clips, I just use Photoshop or After Effects to carry out the modifications, and then when revert back to premiere, the software hangs up for like 3-5 mins!!, This I have notice, even if I simply go to desktop and come back to premiere, it hangs (meaning NOT RESPONDING!)
2. I call Adobe customer support (case id:183193833 status:Open - Pending Adobe Response), I go through all the instruction they gave, then finally made me uninstall and reinstall Premiere Pro... I now get the following error when open any project file
pop-up window "Premiere Pro Debug Event" Says Premiere Pro has encountered an error. [..\..\Src\QTTrack_Video.cpp-735]. then a button "Continue". which when I click, next popup window "Adobe Premiere Pro CS5" Says Adobe Premiere Pro CS5 has stopped working. Windows can check online for a solution to the problem. button 1:Check online for a solution and close the program button2: Close the program.
Problem details
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    Adobe Premiere Pro.exe
Application Version:    5.0.3.0
Application Timestamp:    4ce382d1
Fault Module Name:    dvacore.dll
Fault Module Version:    5.0.0.0
Fault Module Timestamp:    4ce336ac
Exception Code:    80000003
Exception Offset:    0000000000104d2b
OS Version:    6.1.7601.2.1.0.256.1
Locale ID:    1033
Additional Information 1:    fc72
Additional Information 2:    fc72325d047ec53d08c05b1cad32ae3b
Additional Information 3:    3bb9
Additional Information 4:    3bb9ad9d78b4f1030aa5aa4d8446047a
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Can someone help me out of this? Please!
My System Config
OS: Windows 7 Ultimate (64bit)
Nvidea Quadro FX 4800
16 GB physical RAM
Xeon E5630 @ 2.53Ghz x 2
300 GB free space on C drive
259 GB free space on the drive that contains the work files
Regards
Sonal

not sure if i understood that... but this problem exists only with Premiere and not with any other application of CS5 Master collection!
John T Smith wrote:
I replied in your other thread... CS5 goes into "hibernation" when you switch away, and must "wake up" with some internal housekeeping when you switch back
I think (not 100% sure, don't have it yet) that PPro CS6 now allows multi-tasking

InDesign crash on open of Project

This has actually happened quite a few times in the last two weeks. New Windows7 computer. Just installed CS5 a few weeks ago on this machine.
Will open an existing project and InDesign will say it needs to close. When opening the project again, it seems to open just fine. Would appreciate any help with this problem. Here is the event log:
Log Name:      Application
Source:        Application Error
Date:          1/14/2011 10:07:55 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
Description:
Faulting application name: InDesign.exe, version: 7.0.3.535, time stamp: 0x4ca67222
Faulting module name: AdobePSL.dll, version: 12.0.0.7524, time stamp: 0x4b885409
Exception code: 0xc0000005
Fault offset: 0x004e188d
Faulting process id: 0x564
Faulting application start time: 0x01cbb4052e950dcf
Faulting application path: C:\Program Files\Adobe\Adobe InDesign CS5\InDesign.exe
Faulting module path: C:\Program Files\Adobe\Adobe InDesign CS5\AdobePSL.dll
Report Id: 71cf97ef-1ff8-11e0-9ffb-842b2bb0d9fa
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-01-14T16:07:55.000000000Z" />
    <EventRecordID>3284</EventRecordID>
    <Channel>Application</Channel>
    <Security />
</System>
<EventData>
    <Data>InDesign.exe</Data>
    <Data>7.0.3.535</Data>
    <Data>4ca67222</Data>
    <Data>AdobePSL.dll</Data>
    <Data>12.0.0.7524</Data>
    <Data>4b885409</Data>
    <Data>c0000005</Data>
    <Data>004e188d</Data>
    <Data>564</Data>
    <Data>01cbb4052e950dcf</Data>
    <Data>C:\Program Files\Adobe\Adobe InDesign CS5\InDesign.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe InDesign CS5\AdobePSL.dll</Data>
    <Data>71cf97ef-1ff8-11e0-9ffb-842b2bb0d9fa</Data>
</EventData>
</Event>

I can understand entirely how someone used to a structured conversation could get confussed by a group discussion with everyone having the same problem but describing it in different way. I can tell you that productivity is better from unstructured conversations than it is is from structured one-on-one discussion. More people benefit from it.
Let me explain - and tell the OP how to fix the issue. Well... How I fixed it on 4 PCs from taking Peter's advice to someone else.
My Computer is just over 18 months old. An i7 950 with 12 gig of Grade A, DDR3 ram and an ASUS mainboard and Radeon HD5850 graphics card. Everything (board, CPU, graphics and RAM) is fluid cooled and software monitored with log entries whenever there is a hardware glitch.
This system originally ran 64 bit XP Pro but I got so frustrated that none of my applications needing access to the extra RAM seemed comfortable running in 64 bit. In December 2010 I installed a fresh set of hard drives and Windows 7 64 bit. I also updated Indesign to version 5.0. By March 2011 I got so distressed by the continual interuption to my workflow by Microsoft installing updates and not letting me shut down until they were installed, I switch off the whole update system. Apart from keeping Radeon fed with the latest patches and weekly colour profiling, the system has run flawlessly except for InDesign stalling and crashing whenever it is started by selecting a .IDD file.
I bit the bullet yesterday and let Microsoft update my OS (and Office). Six hours later - (I kid you not) with over 250,000 files altered or replaced, the PC reported it needed to be restarted. On restart it reported 4 updates were being installed as I watched in horror as nearly 190,000 additional files were replaced or altered. This is not a patch or an update. Microsoft needs to warn uses that it is about to replace the entire OS. It smoother and faster now. But the really important thing is that I can now start InDesign by selecting files on any drive with any file manager (Explorer included) without the program hanging or crashing.
So Peter... I know to someone used to working with code or databases, the rambling way this thread has progressed might be cause for frustration but at the end of it all, I'm pretty sure my original assesment that there was a miss-match of code between MS and Adobe seems to be correct. I've installed the service pack and updates on my notebook and both of the art PC as well as my own workstation. The issue appears to have been a flaw in Windows itself because if it were in Adobe's software, the problem would still exist, would it not?
The problem is one that can be cured, even prevented by keeping Windows up to date. I don't recommend doing it my way unless only one machine with no work pending is involved. I wish I could pinpoint the actual link library responsible for the problem but too much was done over too long a time for me to back track and look. Thanks for the prompt about the service Pack Peter. I always work on the basis "don't fix what isn't broken". Interestingly enough that ID problem didn't exist on the first fresh install of Win 7. Only after MS had fed it daily with "security" patches.
Doug

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.

AE CS5 crashes on opening a project

Hi all (again),
I'm working on a project which, fortuately, has been rendered without an issue. Fingers crossed, it won't need to be returned to!
It's rendered fine, although multiprocessing was disabled during rendering due to a plugin (which I'm going to assume was Kronos; just because it's been incredibly buggy in my experience). When the multiprocessing was disabled, windows reported the close of the processes as a crash. Still, it all rendered fine.
Now when I go to open the project it crashes about a second after loading. I've attached the error message below.
Has anyone encountered this before? It's not critical *now* but if I can't go back and amend work from a previously fine project then that gives me serious cause for concern going forward. Hell, it doesn't even matter what's causing the fatal error - I need whatever the issue is to be flagged when it occurs - not when I'm powerless to debug the project because I can't open it.
Incidentally I've tried loading the project with capslock on and off - it doesn't seem to make a difference.
Is there any way I can get into the project without loading plugins?

One of your project items is damaged and the crash occurs in MediaCore when it attempts to bypass it. I recommend you flush the media cache, trashing the prefs and also consider reinstalling AE. Also move all files involved in the project to a different location so the project opens with them all missing. you can easily relink them later. If Kronos may be corrupting the project, I would inquire with the Foundry for the latest version and also licensing issues. Sometimes licenses that have run out prevent a product from working and then drag down everything. Since the plug-in uses CUDA, naturally also graphics card issues may figure in...
Mylenium

Crashes while opening specific project in Professional 2010

Hi,
I am keep on crashing my MS Project Professional while opening specific project, able to edit other projects without any issues .
event viewer gives following error message, not able to find pdb files to debug
Faulting application name: WINPROJ.EXE, version: 14.0.4751.1000, time stamp: 0x4b8e2648
Faulting module name: WINPROJ.EXE, version: 14.0.4751.1000, time stamp: 0x4b8e2648
Exception code: 0xc0000005
Fault offset: 0x0018e4a4
Faulting process id: 0xe44
Faulting application start time: 0x01d019598e0af28c
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\WINPROJ.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\Office14\WINPROJ.EXE
Report Id: 03f5cf9b-854d-11e4-b02f-1c659dacae4b
any pointers to trace the issue
S.Venkata Appaji

Appaji,
My guess is the file is corrupt. But first, let's make sure you have SP2 installed. It appears from the version number above that you do not. You can download SP2 at: http://support.microsoft.com/kb/2687457. I also recommend you install the June 2013 cumulative
update. You can get that at: http://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2817385&kbln=en-us.
If after installing the updates you still cannot open the file, go to the MVP website at, http://project.mvps.org/faqs.htm and take a look at FAQ 43. Use method 4.
Hope this helps.
John

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.

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.

Premiere Pro Debug Event trackitemgroup

In Premiere Pro 5.5, I get a Premiere Pro Debug Event ending in "trackitemgroup.h-2" that crashes the program every time the project is opened. Premiere will open other projects/create new projects, and importing the sequence and media into a new folder will bring up the same error, but won't always cause a crash.
Thank you for any help

Thanks for the quick reply.
I basically did what you suggested, and didn't explain very clearly; created a new project file, imported the assets into that project, and then imported the original sequence. When I opened the original sequence (in the new project), all of the video showed up correctly, but I got the same error; the difference was, this time it didn't completely crash Premiere. I could just click OK and continue with the project (had to repeat that process a couple of times, but the project stayed open).
More details: this was a day-turn local news package, video shot on a Sony NX5U, reporter voice track recorded as a .wav file. This is the same workflow we've used for 6 months, and I've never run into this issue. Like I said, new projects with the same workflow are fine. I guess I could try playing each file in the timeline one at a time and see if one of them is having issues, but in the course of trying a few, they seem to be fine.

Debug event prevent opening of project

Similar Messages

Maybe you are looking for