CA Headless Debug Event CA Headless had encouted anerror (../../Src/sequence/Sequence coo-2233)

Hello
After Installing premiere elements 12 my computer shows following after starting:CA Headless Debug Event CA Headless had encouted anerror (../../Src/sequence/Sequence coo-2233)

Similar Messages

After Effects Debug Event error [..\..\Src\Win\AsioHost.ccp-885]

anyone knows how to fix this , everytime i do a ram preview it freezes and gives me this error and it comesback and does it again
I have rebooted many times, cleaned the Cache Purged, removed unused footage etc

meaning decrease the layer size in order to make it work?
with my system
Windows Vista Ultimate 64bit (service pack2)
Dell Precision T7400
Intel Xeon Cpu x5472 @3.00GHz 2.99Ghz (2 processors) quad cores
8GB RAM
Adobe Master Collection CS4
how much ram do i let after effects use ?
this is how i have it set up
if these settings are wrong withing my machine can any of you let me know what will be the correct set up for it?

Adobe Premier Pro CS3 Debug event

I have Preimeir Pro CS3 with a Debug Event error
..\..\Src\Audo\monitormixer.cpp-153
what is it, how do i fix it

Work through all of the steps (ideas) listed at http://forums.adobe.com/thread/459220?tstart=0
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 and your project and output settings

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

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

Debug Event

As soon as I touch anything within the program I get the notification 'Premiere Pro Debug Event' with the error [..\..\src\AudioRender\AudioPrefetch.cpp-87]. Then the projgram shuts down. Am using Premiere Pro CS5 on a newer Windows 7 64 bit machine. Haven't had problems before. Tried clearing memory, reboot, import sequence into a new project... I have only a mix of 1920 px images and GoPro footage plus an mp3 as a sound track. Any help would be a ppreciated!

Ann -it didn't help... Same message appeared after I played sequence about 5 seconds...

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.

PrE 8.0 Debug Event [..\..\Src\PathUtils.cpp-190]

Hi everyone. I'm having a debug event when trying to drop a clip into the timeline. I've read some of the other threads but that doesn't seem to be my problem. My scratch settings are all set to the hard drive (not a network), although the software was installed by an admin. I tried to open a project in the admin account and the same thing happens. I have 234GB free on the hard drive. As far as I know all of the settings are correct on the video. The clip is a converted .mts > .avi (I also tried .mts in the program and .mts>.mov; same problem). The camera is a Canon VIXIA HF100 set to 1080i 60i HD (which is the setting I used in PrE as well). Once loaded into the program the clip itself will play when double clicked but the video skips almost immediately then will freeze (the audio is normal). Once the clip is dragged into the timeline for edit the debug event occurs and the system crashes. Would the video card come into play here? That's the only thing I can think of. The system specifications and crash report are listed below. Thanks for any help.
Toshiba Tecra A11
Intel Core i7
2.67 GHz
2.98 GB RAM
XP Professional Service Pack 3
***Not sure what video card I have but in "Sound, Video and Game Controllers" I have....
Legacy Audio Drivers
Legacy Video Capture Devices
NVIDIA High Def Audio (X 4)
Realtek High Def Audio
Video Codecs
I saved the crash data as well....but it was 21 pages long so I didn't want to post it here. Would that help? If so, any particular page or the whole thing?

Thanks for your fast response. And you're right, the setup is a bit weird. I teach at a high school and the equipment was basically given to me to work on school projects. So I'm trying to make it all work together. In college we had all Mac labs with Final Cut Pro, which I am used to. This program with PC is throwing me for a loop. I did make a short video in the AXP setting, then set the project to what you said - When I hooked the camera up to the computer, it connected (all the folders and whatnot popped up and the camera indicated it was connected). I hid all of the folders and opened PrE. When I tried to bring it in from the camera, the capture window came up but it said there was no camera connected. I tried a few times and it didn't work. I tried taking the SD card out of the camera and importing it into the program that way. That didn't work either. The file was copied to the hard drive from the SD card but still came
up in the program as an .mts file. The same crash happen when dragged into the timeline. Should I just try all the updates then? I don't know why the computer won't recognize the camera. I left it there for a minute or two in case there was a delay and still nothing. Thanks again.

Debug Event: [...\ ...\src\TickTime.cpp-290]

Hello,
I have meeting a problem for 24 hours on adobe first pro cc on 2014...
Debug Event: [...\ ...\src\TickTime.cpp-290] and adobe announces a grave error then he(it) closes.
I uninstalled everything and quite reinstalled, but the problem persists.
What's to be done to solve this problem which paralyzes all my work?

Hello,
I've got same problem here tonight. I'm working night & day since 1-2 weeks on After Effects & Premiere CC 2014.2 without any problems. Tonight I was queueing some renders in Media Encoder from After Effects & Premiere. When I 'exported to queue' from Premiere, I had an error (don't remember which one unfortunately), but AME was still open and seemed to be OK (also the Premiere render was listed, and I could change the output settings without any problem). To be sure the queue would render without problem I closed AME and try to reopen it... unsuccessfully. And since that time, I can't open it anymore
The error displayed is Adobe Media Encoder has encountered an unexpected error and cannot continue
And at the same (don't know if it's linked but high probability it is), when now I open a project in Premiere (not all the time), the workspace is totally messed up, and if I try to change to another or reset the one selected I got the same error you got, the
Debug Event: [...\ ...\src\TickTime.cpp-290]
and Premiere crashes
Sometimes the error occurs also when I open a project and it crashes with the same error (it doesn't seem "project-related" since sometimes it's OK, sometimes it's not).
I'm running CC 2014.2 versions on Windows 8.1 64-bits.
Nvidia Drivers 344.75 (not the last one, which is the 347.25, but I didn't install or uninstall anything before or after the problems).
I already had the workspace "messed up" problem one time, but it wasn't followed by a crash like now.
PS: Oh, I noticed around that time also a strange behavior from AME. My output framerate was in "30 fps", but after I queued my Premiere file, it was "30 000". I did not understand why the fps format change. Don't know if it's related.
Thank in advance,
Christophe.

PSE 9 and CAHeadless Debug Event??

PS: Have tried to HOLD down 'Shift, Control and Shift' whilst launching Orgnizer as suggested in a previous forum and ALL IT WAS LAUNCH CA HEADLESS BEBUG EVENT Again. Msg always states 'CAHeadless has encountered an error:' [..\..\Src\DataManager.cpp-410]. ???

See if that helps (deleting organizer preferences / turnining autoanalyzer off) :
http://forums.adobe.com/message/5021448

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 CS5 Debug Event

Hi there,
I've been a long user of Adobe software and I've just recently had an issue with Adobe Premiere Pro (first Debug event I've ever had with the software),
In which it has encountered an error with "ComponentChain.cpp-498". Now, I'm running on Windows 7 64-bit way above the minimum specifications for the application. Now, this has only recently started up but its actually preventing me from render or editing any of my footage, and so before I jump ahead with tearing up the system and figuring what is what, I was wondering if somebody could please advise how I would be able to go about fixing this problem.
Thanks

I find only one reference to your specific element (in CS4):
http://forums.adobe.com/message/2462753#2462753
I don't think that helps.
The speculation there was it could be a corrupt project. sometimes corrupt projects can be helped by importing into a new project.

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

Adobe Media Encoder Debug Event (when exporting audio)

I do alot of vj'ing... I have a good pipeline for exporting short film clips, optimized for the vj software I use.
I export photojpg at 75 quality, at 640x480, with no audio.
However, i'm now trying to export some of the same clips, but with the audio intact.
No matter what audio format and bitrate setting I choose, however, media encoder refuses to export the audio.
I've tried it with a number source videos, with various combinations of source video/audio codec combinations, and I continue to get the same error:
Adobe Media Encoder Debug Event
[..\..\Src\Win\WinFile.cpp-754]
When I unclick audio, each clip exports fine, as normal.
What gives?
-Matt Daly

I'll tryed now everything. If I choose update it tells everything is up to date. If tryed to run patch from: "http://download.adobe.com/pub/adobe/mediaencoder/win/7.x/AdobeMediaEncoderTrial_64-7.0.1-m ul-AdobeUpdate.zip", it runs ok but nothing has updated when I start Media Encoder again.

CA Headless Debug Event CA Headless had encouted anerror (../../Src/sequence/Sequence coo-2233)

Similar Messages

Maybe you are looking for