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.

Similar Messages

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.

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 PRO DEBUG EVENT Premiere pro has encountered an error. [c:\cloudroom\releases\2014.09\shared\adobe\mediacore\mediafoundation-.

potete darmi una mano a risolvere il problema?

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

Premiere Pro Debug Event Error

When loading Adobe Premiere CS4 I get an error message.
"Premiere Pro has encountered an error.
[..\..\Src\ImporterProcessClient.cpp-127]"
I have windows 7 Proffesional 64bit operating system. And the CS4 student edition.

Thank you sir. Seeing that two Adobe experts suggested the same thing, I went ahead and sliced and diced, narrowing the sequence down to a single problematic .MOV file. I went to the original project, and replaced the file with the same video file and it worked! So the issue was a corrupt file link from it's folder to the Premiere project.
The problem is now solved!
Michael

Premiere Pro Debug Event Problem [HELP NEEDED]

Hello guys & fellas, hello staff!
Since a few hours I've got a huge problem starting premiere pro cc 2014!
Since the beginning I'm not able to load an existing or begin a new project anymore, which is very annoying, because of the fact that I am a youtuber and I have to edit videos to upload them. Now I have to make a break until the problem is solved.
Thank you very much for your help!
Best regards
Kevin

Hey there thank you for your quick answer!
I was looking for the data you were writing of, all I could find was this: (of course in german)
Which one do I delete?

PP CS6 "Premiere Pro Debug Event"

Hi,
i've got CS6 Production Premium with Plugins (Element 3D, RedGiant ColorSuit, Keying Suit, Trapcode, Universe)
Sinc today I have a Problem by opening a PP-Project:
I deleted the Cache. - no effect
I move the Common Plugins to a Backup-Folder - no effect
I reinstalled CS6 PP - no effect
I reinstalled CS6 PP and run the Adobe Cleaning Tool - no effect
I made a System Restore from my Windows 8.1 (4 weeks ago)
The last time I worked on a Project was one week ago - so the error could not be caused from the System
Who knows this "Debug Event"? What can I do?
This Error comes on all Projects when I open a Project work on it and press "Save". The next time I want to open it - the Error comes.
Pleas help me!
Jojo

OK
just saw that i'm not alone with this Problem...
Debug event f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe

Premiere Pro Debug event

Anyone seen this one?
...\..\Src\AudioRender\AudioPrefetch.cpp-84
Plays just fine, encodes just fine, but damned if you wanna touch that file -- instant crash.
everything else is working good, until oooh! we're in that sequence, touch the audio and DOOOOH! Crash!
This is a clean install of CS-3, right after a clean install of the O/S (WinXP) with nothing else involved.
opened a project I'd been working on, all the other 54 scenes appear to be playing friendly, and the audio files in question are part of clips used throughout the project (Repeatedly) it's just in this one instance they are going nutzoid.
Ideas?

I just ran into this problem, trying to figure ways around it.

Premier Pro Debug Event?

I am trying to open my project I've been working on the last four days. I'm getting this error message:
Premier Pro Debug Event
Premier Pro has encountered an error
{..\..\src\clip\MasterClip.cpp-2802]
Then when I hit continue it stops working, and I can't get into my project. I used Pluraeyes, and then I used NewBlue Color fixer last night. I've used them before and have not encountered a problem, but does this have anything to do with it. Please any suggestions, I cannot lose these four days of work?

Try this:
http://blogs.adobe.com/genesisproject/2011/02/premiere-pro-cs5-maintenance-two-great-tips. html
and then, restart, launch Premiere Pro, open a new project and then import your old project into it. If it works, then save it, try to clean out anything you don't need and hopefully that will help you.
Good luck,
Dennis

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.

Premiere Elements Debug Event

Hello,
I recently installed Premiere Elements 8 to my pc and have been plagued by a debug event everytime I attempt to drag and drop a video clip into the editing pane.
The following is the error that pops up everytime: Premiere Elements Debug Event. Premiere Elements has encountered an error. [..\..\Src\PathUtils.cpp-190]
A button that reads "continue" is in the error box and Premiere closes abruptly after I click on it.
I have no clue what this means and it would be great if someone could help me out.
Thanks!

Having a new PCI-Express graphics card installed as we speak and should have my machine back by Monday,
Many users have had issues with integrated graphics chips, both here, and on the PrPro forum.
I hope that the new card will take care of your issues. If you go with nVidia for the PCIe graphics card, please disable both of these "gamer-only" moduels: PhysX and 3D Stereovision. PrE cannot use them and they really mess things up for Adobe programs.
Good luck, and hope that all is perfect on Monday!
Hunt

Premiere Pro bug event

I finally completed editing a project on CS3 this afternoon. I decide to play it one more time before exporting it and I get this:
Premiere Pro Bug Event
Premiere Pro has encountered an error
[..\..\scr\audio\monitormixer.cpp_153]
Everytime I've tried anything, I continue to get this error message and nothing I do stops it from popping back up.
Has anyone experienced this? Is there a solution?

A link with many ideas about computer setup http://forums.adobe.com/thread/436215?tstart=0
And even more hardware discussion http://forums.adobe.com/community/premiere/hardware_forum
Including this post about 3 possible builds http://forums.adobe.com/thread/598040?tstart=0
Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

Premiere cs5 debug event

Everything works fine except this.If you
capture dv threw 1394 in cs5 after a
period you see a message
"Src\filemanagerImpl.cpp-94'
and premiere wants to close.
In EVENT window down and right
i have a message 'the file is busy and could not be updated'
I used cs4 before with no problem
AND now i am forced to capture
with cs4 with no problem at all.
Does anyone knows what is this.
Vista 64 ,i7,gtx 470,12g ram.

Yes i know that i can capture the tape as one big file,but i can not capture the tape in many separare clips.Is this a bug or something??

Popup Error: Premiere Elements Debug Event

Hi,
After a succesfull installation our users can start and work in Adobe Premiere Elements 7 (APE7).
But if they save there project and try to close APE7 they get a popup. (see attached Screenshot .45.jpg, dutch version, but message is something like: There is a serious problem ...etc).
APE7 crashes and when they start again, our users see the folowing popup. (see attachesd Screenshot .46.jpg)
I also attached a screenshot from a part of a ProcMon logfile
It looks if Adobe Premiere Elements doesn't work with folder redirection (Appdata to share). In our situation we redirect users "document and settings\<user>\application data" to a networkshare (homedirectorie on a fileserver)
I tried to set the location forthe project savefolder to drive d:\, a removed the media cache to d:\ but that seems not enough.
What would you advise me to do?
Best regards,
a denm

After a succesfull installation our users can start and work in Adobe Premiere Elements 7 (APE7).
But if they save there project and try to close APE7 they get a popup. (see attached Screenshot .45.jpg, dutch version, but message is something like: There is a serious problem ...etc).
This leads me to believe that you are in a networked environment, possibly in an academic institution's media lab.
Unfortunately, if you are, things will not be all that easy. Both PE and PrPro (plus its Encore authoring app) are designed around the user having full Administrator privledges and their files not being in a networked environment. One can work with simple P2P LAN's and even with media on a NAS, but a full networked environment causes major problems. Giving students full Administrative privledges also has a high potential for problems from an IT standpoint.
Adobe TS is the best course. They may have some solutions for your problem. There are also several thread on the forum on academic networked situations. In a few of these, there were good suggestions, but so much will depend on the exact networking employed.
I've file Feature Requests for more network support with these programs, even though it does not directly affect me. I see a great sales potential for Adobe to get as many copies of their editing programs into the hands of students, and the lack of full networking capabilities stands in the way. You might also wish to file a FEATURE REQUEST for this.
Now, if you are NOT networked, ignore my post.
Good luck,
Hunt

Premiere Elements Debug Event MonitorMixer.cpp-201

Hello.
Today while editing a vacation video I encountered this message window:
I'm using Premiere Elements 7 in WinXP 32 bit service pack 3.
Audio card is a Creative Sound Blaster Live 5.1 with latest drivers installed.
The video source of the project is a *.VOB taken from a DVD, JPG pictures, MP3 audio (no errors in Getting Media)
Actually I'm halfway of the editing and yesterday was going great as usual, same files, same sources.
I did not install anything new, just shut-off the computer and restarted.
Audio Hardware settings > Default Device: Premiere Elements Windows Sounds (the only one available) // ASIO settings: SB Live Wave Device + AnvsoftSound_Device
Here are the ASIO Settings:
Here I can change all the settings and click OK, but when I check the settings are back again like in the above picture.
My Project settings:
Section of the Timeline that has been working correctly until today:
Suggestions are very welcome.

This is wierd.
Always while testing I slided the timeline bar where the time/numbers are (the one half dark/half grey) and now everything works fine.
But... what's that bar standing for? How does it work and what does it do?

Premiere Pro Debug Event trackitemgroup

Similar Messages

Maybe you are looking for