Premeir element 10 bug src/ticktime.cpp-351
impossible d'ouvrir mes projets... des semaines de travail de perdus... besoin d'aide
toujours erreur src/ticktime.cpp-35 et par la suite projet endommagés... et rien ne s'ouvre. Même chose dans les sauvegardes
premier element 10, Windows 7
Bonjour Maxime, Je ne suis pas expert Adobe mais j'ai eu un cas semblable avec Première Pro et une autre erreur. Alors tu ne perdras pas beaucoup de temps à l'essayer au cas où elle pourrait être une solution. J'ai crée un autre dossier à un autre emplacement et transféré uniquement les vidéos et tout ce qui est utilisé pour le montage (images,musiques, titres...dans leurs dossiers respectifs) plus le fichier de projet et aucun autre fichier ou dossier. Tu ouvres ton projet et il va probablement dire qu'il ne trouve pas les fichiers, tu indiques le chemin pour le premier fichier qu'il demande...et s'il y a un miracle, il va retrouvera les autres et surtout il n'indiquera pas d'erreur. Si ce miracle s'accomplit, vérifie quand même chaque chute sur le montage avant de le sauvegarder. J'espère que cela marchera. Andres
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? GrazieHow to repair projects that get a "TickTime.cpp-290" error after opening a specific project.
-
Code de l'erreur: [.../.../src/TickTime.cpp-290]
Bonjour,
Problème à l'ouverture de première pro cc 2014 sur pc,
code de l'erreur: [.../.../src/TickTime.cpp-290]
merci bienBonjour,
Je viens d'avoir le même problème. Après trois heures d'essais multiples, j'ai réussi à régler le problème. C'était pour ma part une séquence bien précise dans mon projet qui faisait tout planter. Si comme moi, c'était une séquence sans importance, il suffit de la supprimer.
J'espère avoir pu vous aider.
Bonne journée -
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. -
Projects Not Opening with Multicam and Warp Stabilizer - "[..\..\src\TickTime.cpp-207]"
Editing a sequence with multiple nested multicam clips and warp stabilizer, if I close Premiere and reopen it, it says "Premiere Pro has encountered an error. [..\..\src\TickTime.cpp-207]" repeatedly until killed by Task Manager. I have restarted the computer, cleared the media cache and deleted preferences. I can import the sequence into another project and continue editing but if I close PPro I have to create another project and import the sequence again or I get the same error. Help!
Hi Kevin!
That is great news. I had a feeling the issue would be gone in the Next PPro. The issue can be easily duplicated by following these steps in CS6:
1) User warp stabilizer on several clips (like maybe 6 or more or so).
2) Take two clips and nest them and sync them for multicam on the same timeline as the stabilized clips (NOTE: these two clips don't actually have to be sync'd...just grab any two clips, stack them on top of each other, highlight them both and right-click and choose "nest", then right-click again and "enable" multicam.
3) Save project. Close project. Re-open project and you'll get the error.
If you do that in the NEXT version, does the error come up? Also, just while I have you...if you go into the settings of Warp Stabilizer, what is the default "method"? Is it still defaulted to "Subspace Warp" or did they smarten up and realize the option "Position, Scale, Rotation" is actually MUCH more effeciet causing less wobble and less cropping of the video 90% of the time? Just curious.
Coltom Media Productions,
I feel your pain. What also stinks is that the error pops up again when you export (or I should say when you queue) up the project into AME. I originally thought the number of continues equalled the number of warps applied but that's not always the case. Although, the more warp stabilizers applied the more times you'll have to hit continue. It often goes in numbers divisible by four. Why do I know all this crazy, useless info...hours and hours of trying to "solve" the issue. Every project I do, every single week has more than 100 clips that are stabilized and multiple multicam sequences so I often have to hit "continue" on the error 300-400 times or more on EVERY project. Can't wait til the next version!
To see more on this issue you can see the original post on it here (note that the staff has recently (and graciously) led the charge to help isolate and resolve the issue):
http://forums.adobe.com/thread/956692?start=40&tstart=0
And then also, it definitely made my "Top 15 list" here:
http://forums.adobe.com/thread/1179004
Good luck!!!...oh, one more thing...the project will open...you just have to keep hitting continue. Sucks, but again, hopefully it'll be resolved soon. -
Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better titleHi Kevin,
I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
What were you doing when this error started to occur?
Nothing special I remember. The only thing I do recall, is:
I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
Do you have iCloud installed?
No.
Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
Do you have a copy that can be opened in an earlier version?
An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
Do you get the same error in that earlier version?
No error here, the file opens properly.
Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
Did you use any unusual footage types in your project?
I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
If you remove them, do you still get an error?
When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
Was the fps interpretation changed in any of the clips?
Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
If so, restore them to their original fps and see if you still get the error.
Unfortunately, since I can't open the project anymore, I can't test that.
Did you use Warp Stabilizer?
No.
Do you have any browser plug-ins?
What do you call browser plug-in in Premiere?
Are there any third party plug-ins used?
I have Magic Bullet Looks 2, and I'm using it on this project.
If so, remove the effect from those clips and see if it improves the situation.
Unfortunately, since I can't open the project anymore, I can't test that.
Some additional infos on my computer.
I use Windows 8.1 (64-bit), all Adobe softwares installed have the last update (for video apps, it's 2014.2)
The language settings are configured in French, but Windows and CC apps are in English.
If needed the 2014.2 project file is here:
https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
Thanks in advance to help us to resolve this weird bug.
Christophe. -
Hey Guys ,
i have a Problem. Yesterday i had making a new Project and i have saved it . Today i would open the Project but i can not open it. It comes a Error
f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
and ..\..\src\TickTime.cpp-364
i hope you can help me .
Sorry for my english , i am from GermanyMalwarebytes ANTI-MALWARE totally solved this problem! Took abt 20 minutes to scan my whole computer, then fix and restart. Haven't had any problems after this (tried several projects that weren't OK from before).
Nice!
Hope this helps!
https://www.malwarebytes.org/ -
I'm getting an error in Premiere Pro CS5.5. While my project is loading and the status bar at the bottom shows that a file GOPR0139.MP4 is loading a popup window opens saying Premiere Pro has encountered and error. [..\..\src\TickTime.cpp-207]. This file is in one of my project bins, however I have not placed it in the timeline yet. After I close the error window the program doesn't crash and I'm able to work on my project. Following this I'll frequently see in the status bar at the bottom an indicator bar saying Conforming GOPR0139.MP4 and GO010136.MP4. GO010136.MP4 IS in my timeline however as I said before GOPR0139.MP4 is NOT.
Anyone know why I am getting this error and how to fix it? I'm using Premiere Pro CS5.5 on a Windows 7 machine.
Thanks!This error happens with almost every project I work on. My typical project is several sequences eventually all combined into one master sequence. Those individual sequences range from just regular edits of 50-100 clips with music and dissolves and a few color correction and stabilizer effects added to a few multicam sequences. I ran about 30 tests to see if I could narrow down what the cause is and I'm still stuck, although if you read this post until the end you'll find that maybe I'm onto something. NOTE: The above workaround of importing this troubled project into a new project did NOT work like it had in the past with this error.
As you know the error in the screenshot earlier in this post occurs when you re-open a project or try to export it to AME. When the error came up, I had to hit "continue" 384 times for the project to open! (Yes, I counted). The project then opened and I could work normally. But everytime I re-opened I'd have to hit continue the same number of times or more! (Now I have to hit continue 396 times for it to open!).
MY TESTING:
I imported individual sequences into a new project, one at a time, then saved and reopened the new project and the error did not pop up for most of them. BUT... I have one "Main" video sequence with about an hour of footage and 350 clips and several multicam sequences nested in it, and another "Highlight Video" sequence with about 125 clips of those clips and one nested multicam sequence. So I tried just importing only the highlight video sequence and now I only had to hit continue 20 times instead of 396 with the project that had the "main" video sequence. So I tested further.
1) I removed the 15 or so nested clips from this Highlight Video sequence that were pulled from a longer multicam sequence and the error went away.
So was it those specific clips?
2) Well I then re-synced those clips and made a new multicam sequence which I imported into the Highlight Video sequence and the issue was NOT there so I figured it wasn't the clips individually.
So was the fact that the original MC sequence was nested in this sequence?
3) Instead of NESTING the original sequence into this highlight video sequence, I copied and pasted the clips from the original multicam sequence into the Highlight Video Sequence the issue did NOT occur...BUT...
4) If I then took those copied clips and right-click and nested them the error did NOT occur...BUT as soon as I right clicked and ENABLED that nested video as a Multicam clip and saved the project, the error DID occur upon reopening. Same result..."...TickTtime.cpp-207" popus up and you have to hit continue 20 times upon opening and it opens.
Strange. Annoying. Frustrating.
So somehow the original multicam sequence is causing the issue right? If I started a new one with the same clips importing and right clicking and "Nest" the video and then right click and "enable multicam" it works fine with no error messages upon reopening. UNFORTUNATELY, I'm not usually opening and closing projects all the time so I don't know when this issue is occuring since it doesn't crash PP or anything.
So, not sure how the number of times I have to hit continue relates to all this. Obviously the bigger sequence has several nested multicam sequences and I have to hit continue 396 times so I don't know where that number is coming from. Its very frustrating and since the "workaround" above does NOT work this time, its a real pain in the ***.
Finally, I thought maybe its somehow the COMBINIATION of the added multicam sequence to the rest of the 125 or so clips that are in that Highlight Sequence. Why do I think this? Well...
Nesting the original multicam sequence into this Highlight Sequence caused me to have to hit "CONTINUE" 20 times upon reopening (once I had saved it and closed it out). Take away the nested MULTICAM sequence and it opens with NO errors. Hmm. Interesting. So I tested further...
5) I took away the 2nd half of the clips (about 50 or so) from the sequence and left in the original multicam sequence that caused the errors before (again, error occurs upon reopening a project) and by doing this the error DID occur BUT, I only had to hit CONTINUE 16 times now, not 20 like before.
6) So I instead deleted the first half of the clips (about 75 or so) and left the 2nd half of the clips as well as this original multicam sequence and guess what? NO ERRORS! Strange. So maybe it is the combination of clips and a nested multicam sequence. Like I said before, when I made a new multicam sequence with the same clips and nested it into this sequence the error did not occur, but taking the original fully edited multicam sequence and nesting that into this sequence the error DID occur...unless I deleted some of these clips. So I'm at a total loss. I guess I could continue and delete clips in smaller groups to try to identify which clips when combined with this multicam sequence are causing the error but I need a break. My mind is starting to unravel after doing so many tests.
Did any of this make sense? I tried to be as descriptive and thorough as possible in my troubleshooting to find what is causing this annoying error to occur. -
Adobe Premiere Elements 10 Error 1 or [..\..\Src\DirectoryRegistery.cpp-283.
I installed Adobe Premiere Elements 10. When I double click on the shortcut icon , I get configuration error 1 which tells me to uninstall/reinstall and then contact Adobe support if it happens again. Uninstalling/reinstalling did not resolve problem so I contacted Adobe support. First time spent about 45 minutes on hold while the person consulted with other colegues and was then disconnected. After waiting about 1.5 hours for call back, I recalled. After about 30 minutes on hold was told that I should call a different number and pay $39 and I could talk to someone who might be able to help me but that this support line did not support this type of problem. Went to online support. Was told to add a new password protected user account, uninstall/reinstall and try to open program using new user account. No joy. Present status : If I double click on shortcut icon, get configuration error 1. If I rignt click and try to 'run as current user get 'debug error [..\..\Src\DirectoryRegistery.cpp-283. If I 'run as the password protected user account get configuration error 1. Note that during the first call, I was sent an email with a 'case number' and a link to check status but the case number has never showed up on the adobe website. Questions:
1. Any suggestions to resolve problem?
2. If I pay the $39, is it likely that I will get the problem resolved or simply get the same run around? I have now uninstalled/reinstalled/restarted at least 6 times and there have really been no other suggestions from Adobe.
3. Suggestions for alternative video editing software if I can't ever get Adobe to boot up. Thanks for your support.You will find best advice over on the video forum. Most of us here are photographers.
Click on the link below and copy and paste your question again. Good luck.
Video questions: Click here for Premiere Elements Forum -
On my Mac, after the installation i get this error when i start - "Premiere Elements 13.0 has encountered an error. [/Adobe/pre/main/MediaCore/ASL/Foundation/Make/Mac/../../Src/DirectoryRegistry.cpp-283]"
any ideas how to fix this, i don't know or haven't faound out how to contact Adobe supporet....Here's the contact link for Adobe support. It's just three clicks from the site's home page.
Contact Customer Care -
[..\..Src\DirectoryRegistry.cpp-283] error when starting Premiere Elements
This error only happens when the laptop is disconnected from our domain. When trying to start Elements I receive error:
Premiere Elements 8.0 has encountered an error.
[..\..Src\DirectoryRegistry.cpp-283]
Then program will not start unless I connect the laptop to the network - which makes a portable laptop useless.
I have uninstalled and re-installed the program with the exact same results.
Anyone got any dieas?
Thankyou in advance.
Crash log file has been included
<?xml version="1.0"?> <!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown"> <time year="2009" month="11" day="19" hour="11" minute="51" second="20"/> <user guid="323c9019-64a6-4b68-8502-a51259f444ab"/> <system platform="windows" osversion="5.1.2600 SP 3.0" applicationlanguage="English (United States)" userlanguage="en_AU" oslanguage="en_AU" ram="2035" machine="Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz" model="x86 Family 6 Model 23 Stepping 10" cpuCount="2" cpuFreq="2394 MHz" busFreq="" locale="English (Australia)"/> <crash exception="EXCEPTION_BREAKPOINT" instruction="0x0097df10"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0x0097df10" symbolname="dvacore::debug::DVA_DebugBreak"/> <stackStatement index="1" address="0x00a0123a" symbolname="dvacore::utility::ThreadSafeMessageDialog"/> </thread> </backtrace> <registerSet> <register name="EAX" value="0x00000000"/> <register name="EBX" value="0x00000000"/> <register name="ECX" value="0x00000000"/> <register name="EDX" value="0x00000000"/> <register name="ESI" value="0x00a0103e"/> <register name="EDI" value="0x00000000"/> <register name="ESP" value="0x00000010"/> <register name="EBP" value="0x00000008"/> <register name="EIP" value="0x00000000"/> <register name="EFL" value="0x00000246"/> </registerSet> <binaryImageSet> <binaryImage start="0x00400000" end="0x00519000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements 8.0.exe"/> <binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/> <binaryImage start="0x7c800000" end="0x7c8f6000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/> <binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6001 .22319_x-ww_f0b4c2df\GdiPlus.dll"/> <binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/> <binaryImage start="0x7e410000" end="0x7e4a1000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/> <binaryImage start="0x77f10000" end="0x77f59000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/> <binaryImage start="0x774e0000" end="0x7761d000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/> <binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/> <binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/> <binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/> <binaryImage start="0x77a80000" end="0x77b15000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/> <binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/> <binaryImage start="0x773d0000" end="0x774d3000" type="__TEXT" path="C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_ 6.0.2600.5512_x-ww_35d4ce83\comctl32.dll"/> <binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/> <binaryImage start="0x10000000" end="0x1013c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/> <binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x -ww_6b128700\msvcp80.dll"/> <binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x -ww_6b128700\msvcr80.dll"/> <binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/> <binaryImage start="0x00350000" end="0x00361000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/> <binaryImage start="0x00370000" end="0x003f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/> <binaryImage start="0x7c9c0000" end="0x7d1d7000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/> <binaryImage start="0x00530000" end="0x005d3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/> <binaryImage start="0x771b0000" end="0x7725a000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/> <binaryImage start="0x77120000" end="0x771ab000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/> <binaryImage start="0x005f0000" end="0x008fb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/> <binaryImage start="0x5b860000" end="0x5b8b5000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/> <binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/> <binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/> <binaryImage start="0x4d4f0000" end="0x4d549000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/> <binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/> <binaryImage start="0x00910000" end="0x0091f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/> <binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/> <binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/> <binaryImage start="0x00930000" end="0x0093f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/> <binaryImage start="0x00950000" end="0x00aa4000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/> <binaryImage start="0x00ac0000" end="0x00b4c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/> <binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/> <binaryImage start="0x00b60000" end="0x00b66000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/> <binaryImage start="0x00b80000" end="0x00b96000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/> <binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/> <binaryImage start="0x74720000" end="0x7476c000" type="__TEXT" path="C:\WINDOWS\system32\MSCTF.dll"/> <binaryImage start="0x01a20000" end="0x01abd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/> <binaryImage start="0x01ee0000" end="0x01f17000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/> <binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/> <binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/> <binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/> <binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/> <binaryImage start="0x01f30000" end="0x01f50000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/> <binaryImage start="0x01f60000" end="0x01f6b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\WS.en_US.DLL"/> <binaryImage start="0x02080000" end="0x02103000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeUpdater.dll"/> <binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/> <binaryImage start="0x605d0000" end="0x605d9000" type="__TEXT" path="C:\WINDOWS\system32\mslbui.dll"/> </binaryImageSet> </crash> <reproSteps> </reproSteps> </crashreport>Where, and how, is PrE installed? When you launch it, are you running as an Administrator?
First, PrE wants to be installed competely on the C:\ and wants direct access to the My Documents folder. It also wants to be both installed and then launched from an Administrator account.
It is not designed (nor is the big-brother PrPro) to function in a fully networked environment. It will extract media, etc. from an NAS, or from a mapped networked drive, but it does not like to run under most networked environments.
It's my guess that there is something in this installation that it is not comfortable with. More details will likely help.
Good luck, and looking for the answers to the questions above.
Hunt -
Premier Elements 7 Error - ../Src/Window.Cpp-251
Hi!
I have a problem with Premier Elements 7. It gives me error message "../Src/Window.Cpp-251". It seems to appear after adding DVD menus. And actually that problem started after using higher resolution clips. Earlier I was using DV files 720x576, but now 1280x720 and 1920x1080. But I have been able to use these clips too. One moment the program hangs and if I try to open the same project again, it gives the error message and will close. I can open the program and start new project or open other projects, but not that one any more.
Technical data:
RAM 4GB
CPU Intel Core2 Quad Q8300
Windows 7 Pro SP1 32 bit
Hard disk has two partitions - program is on the main part and projects and everything else is on the other.
I hope someone knows the solution! Thanks!Welcome to the forum.
Have you seen this THREAD?
The OP had the same error message, and it seems that their User Account was corrupt. That OP also was using a prtitioned HDD. You might want to look over this ARTICLE on partitions.
Good luck,
Hunt -
Windows 8.1, CS4, [..\..\Src\ImporterProcessClient.cpp-127]
A previous issue for CS4 on earlier versions of Windows has evidently recurred after a recent Windows Security update. Here's one evidently resolved previous instance: Premiere Pro CS4 (Vista) error [..\..\SRC\ImporterProcessClient.cpp-127]
Is anyone else currently experiencing this issue?
My own system specs are as follows:
Windows 8.1
Processor: Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz 2.80GHz
Installed memory (RAM): 8.00 GB
System type: 64-bit Operating System, x64-based processor
I am running Premiere CS4 version 4.0.0
There have been no issues loading and using Premiere since I installed it on this computer, which was done shortly after a full hard-drive formatting several months ago.
This morning, Windows requested that I install a security update and restart. Upon restarting, Premiere has refused to open citing the following error:
Premiere Pro Debug Event
Premiere Pro has encountered an error.
[..\..\Src\ImporterProcessClient.cpp-127]
The workarounds cited for previous version of windows, such reducing UAC settings and running Premiere as administrator are not resolving the issue. Based on the previously mentioned thread, I attempted the following command prompt solution:
'cd' to C:\Program Files (x86)\Common Files\Adobe\dynamiclink\
dynamiclinkmanager.exe /REGSERVER
processcoordinationserver.exe /REGSERVER
regsvr32 dynamiclinkmarshal.dll
I received error code 0x80070005, and have followed several Microsoft guidelines for resolving it to. Currently, I remain unable to open Premiere.
I have deactivated, and am in the process of uninstalling, running Clean Script CS4, and re-installing. I will also be checking for updates, but recent attempts at doing so have indicated none were available. Do updates get taken down over time?UPDATE: While the following information should correct the initial issue reported, a new problem has come up and stopped production yet again. Premeire is prompting me to install additional codecs, but the prompt always fails, and asks me to contact Tech Support. My footage is rendering incorrectly now as well.
Note that my footage was editing and rendering just fine before this mess began.
FIXED. I think this is the crucial step, but I'll review everything I did afterwards:
Given that CS4 (via Photoshop, as Premiere is currently not working) seems unable to detect any updates (despite being a fresh installation), and the manual updates seem to all be failing, I found this item about a similar issue for CS3:
https://helpx.adobe.com/creative-suit/kb/cs3-updater-detect-any-updates.html
Adobe recomends setting your computer clock back to October 1, 2011, and checking for updates again. It seems to have done the trick, and my CS4 is installing 12 updates.
ALL STEPS TAKEN:
I cannot reliably point to any one step as the "definite fix" for this, so here's a review of what I did in the order that I did it:
1) Deactivate, uninstall, reinstall, reboot.
2) Lower your User Account Control settings. In 8.1, you can simply run a search in the Start screen for "UAC".
3) Activate the hidden administrator account for Windows 8.1. Open cmd.exe as administrator. Press Window+X and select the appropriate option, then run the command (with no quotes) "net user Administrator /active:yes". Once everything has been fixed, you can repeat this and replace "yes" with "no" to hide the admin again.
4) Log in to the Admin account.
5) Reset your computer's date to "October 1, 2011". Be sure to set it back to the real date once everything is done.
6) Open any CS4 program that still opens (as in, not Premiere Pro).
7) Check for updates. A restart will be required.
8) As mentioned, you'll want to reset the things you've changed on your computer. Set the UAC to whatever it was before the issue, hide your Admin account, and fix your clock. After doing so and rebooting, my Premiere Pro CS4 continued to function normally on my personal user account. -
Hi All,
I was performing the steps mentioned in Oracle Tutorial"http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/biadmin11g_02/biadmin11g.htm#t10"-BI RPD creation.
After Using the AGO function data in the Time series metric(Month Ago Revenue) was null always. I updated the DB features in RPD physical layers by selecting support for time series functions.
After that report started to fail with below error. Please let me know if its a bug and any option to fix it.
Thanks,
Sreekanth
Error
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46008] Internal error: File server\Query\Optimizer\SmartScheduler\PhysicalRequestGenerator\Src\SQOSPMarkMultiTargetSupport.cpp, line 1680. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Sales"."Time"."Year-L1" s_1, "Sample Sales"."Revenue"."Ago-Year Revenue" s_2, "Sample Sales"."Revenue"."Revenue" s_3 FROM "Sample Sales" FETCH FIRST 65001 ROWS ONLY
RefreshI know that there is no relation between "SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date", "SampleApp Lite"."D0 Time"."Calendar Date", it's also the same thing in my own RPD.
But as it's working with the 11.1.1.6.2 BP1 version I don't understand why it's not working with 11.1.1.6.9.
Implicit fact column is not set on my repository, but I don't have any request with only dimensional column, so if my understanding is correct I don't need to use it. Also, the problem appears during the check of the repository not in answers.
thanks anyway -
[..\..Src\DirectoryRegistry.cpp-283] Error on Startup
This error only happens when the laptop is disconnected from our domain. When trying to start Elements I receive error:
Premiere Elements 8.0 has encountered an error.
[..\..Src\DirectoryRegistry.cpp-283]
Then program will not start unless I connect the laptop to the network - which makes a portable laptop useless.
I have uninstalled and re-installed the program with the exact same results.
Anyone got any dieas?
Thankyou in advance.
Crash log file has been included
<?xml version="1.0"?> <!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown"> <time year="2009" month="11" day="19" hour="11" minute="51" second="20"/> <user guid="323c9019-64a6-4b68-8502-a51259f444ab"/> <system platform="windows" osversion="5.1.2600 SP 3.0" applicationlanguage="English (United States)" userlanguage="en_AU" oslanguage="en_AU" ram="2035" machine="Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz" model="x86 Family 6 Model 23 Stepping 10" cpuCount="2" cpuFreq="2394 MHz" busFreq="" locale="English (Australia)"/> <crash exception="EXCEPTION_BREAKPOINT" instruction="0x0097df10"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0x0097df10" symbolname="dvacore::debug::DVA_DebugBreak"/> <stackStatement index="1" address="0x00a0123a" symbolname="dvacore::utility::ThreadSafeMessageDialog"/> </thread> </backtrace> <registerSet> <register name="EAX" value="0x00000000"/> <register name="EBX" value="0x00000000"/> <register name="ECX" value="0x00000000"/> <register name="EDX" value="0x00000000"/> <register name="ESI" value="0x00a0103e"/> <register name="EDI" value="0x00000000"/> <register name="ESP" value="0x00000010"/> <register name="EBP" value="0x00000008"/> <register name="EIP" value="0x00000000"/> <register name="EFL" value="0x00000246"/> </registerSet> <binaryImageSet> <binaryImage start="0x00400000" end="0x00519000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements 8.0.exe"/> <binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/> <binaryImage start="0x7c800000" end="0x7c8f6000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/> <binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6001.22319_x-w w_f0b4c2df\GdiPlus.dll"/> <binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/> <binaryImage start="0x7e410000" end="0x7e4a1000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/> <binaryImage start="0x77f10000" end="0x77f59000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/> <binaryImage start="0x774e0000" end="0x7761d000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/> <binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/> <binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/> <binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/> <binaryImage start="0x77a80000" end="0x77b15000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/> <binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/> <binaryImage start="0x773d0000" end="0x774d3000" type="__TEXT" path="C:\WINDOWS\WinSxS\X86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5 512_x-ww_35d4ce83\comctl32.dll"/> <binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/> <binaryImage start="0x10000000" end="0x1013c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/> <binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b1287 00\msvcp80.dll"/> <binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b1287 00\msvcr80.dll"/> <binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/> <binaryImage start="0x00350000" end="0x00361000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/> <binaryImage start="0x00370000" end="0x003f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/> <binaryImage start="0x7c9c0000" end="0x7d1d7000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/> <binaryImage start="0x00530000" end="0x005d3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/> <binaryImage start="0x771b0000" end="0x7725a000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/> <binaryImage start="0x77120000" end="0x771ab000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/> <binaryImage start="0x005f0000" end="0x008fb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/> <binaryImage start="0x5b860000" end="0x5b8b5000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/> <binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/> <binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/> <binaryImage start="0x4d4f0000" end="0x4d549000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/> <binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/> <binaryImage start="0x00910000" end="0x0091f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/> <binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/> <binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/> <binaryImage start="0x00930000" end="0x0093f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/> <binaryImage start="0x00950000" end="0x00aa4000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/> <binaryImage start="0x00ac0000" end="0x00b4c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/> <binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/> <binaryImage start="0x00b60000" end="0x00b66000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/> <binaryImage start="0x00b80000" end="0x00b96000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/> <binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/> <binaryImage start="0x74720000" end="0x7476c000" type="__TEXT" path="C:\WINDOWS\system32\MSCTF.dll"/> <binaryImage start="0x01a20000" end="0x01abd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/> <binaryImage start="0x01ee0000" end="0x01f17000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/> <binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/> <binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/> <binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/> <binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/> <binaryImage start="0x01f30000" end="0x01f50000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/> <binaryImage start="0x01f60000" end="0x01f6b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\WS.en_US.DLL"/> <binaryImage start="0x02080000" end="0x02103000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeUpdater.dll"/> <binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/> <binaryImage start="0x605d0000" end="0x605d9000" type="__TEXT" path="C:\WINDOWS\system32\mslbui.dll"/> </binaryImageSet> </crash> <reproSteps> </reproSteps> </crashreport>I noticed that your problem is happening when you are starting Premiere Elements. So I recommend that you post your question on the forum specifically for Premiere Elements at
http://forums.adobe.com/community/premiere/premiere_elements
Maybe you are looking for
-
DISAPPOINTED IN APPLE'S LACK OF QUALITY CONTROL/TESTING with MM & iCal
APPLE is seriously dropping the ball; it saddens me because I just switched all personal & business computers from Microsoft Windows because I thought Apple was different. Is it corporate greed, mismanagement, or eager beaver project managers who are
-
I have a Keyrig 49 m-audio and it is not recognize by OS 10.9.4 when it says that mavericks is plug and play. I would really like to do what I am able to do on earlier version of OS... Please help
-
Flash Video with DVD-like motion menus -- Is this possible?
Hi all, I just joined this gropup. I have some SMIL 2.0 presentations with synchnorized multiple audio (several languages supported) and video as well as DVD-like still and motion menus. These are semi-transparent menus and actually are super-imposed
-
Looking for more capacity replacement for HP Pocket Media Drive PN FK526AA / Model PD3200s
Hello, I have searched the web, called HP, and am not able to find an exact replacement or a replacement pocket media drive with more than 320GB space. The current 320GB drive as what I think is a type 4 jack USB connector. The part number of the dri
-
I have nokia 5800 I try to do mapping by using GPS anyone have way to resolve this troubleshooting