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.

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.

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 bien

Bonjour,
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

Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better title

Hi 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.

How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

This is a guide to repair projects that get a "TickTime.cpp-290" error after opening a specific project.
Prerequisites:
Project repair tool (download link below)
WinRAR or any file archiver
Damaged project file
As an example, let's say the name of my damaged project is 'test.prproj'
Steps:
1. Download the project repair tool here: https://www.dropbox.com/s/3fyja0ws7l5gkbt/pp-repair-0.1.35.zip?dl=0
2. Rename your project file extension from 'test.prproj' to 'test.zip' (a warning appears saying the file might become unusable. Do not be concerned about the warning. Click OK and move to the next step.)
3. Extract the contents of 'test.zip' to a location on your computer. (Right click on the file and select ‘Extract files’ > Choose a location > Click OK).
4. Go to the extracted location. Note the file 'test' has no extension.
5. Rename the file, 'test.prproj'.
6. Launch the project repair tool, and then select the file 'test.prproj' (the one that we renamed in the last step).
7. Deselect all the check-boxes in the project repair tool.
8. Click the Repair button.
9. After a few seconds you see a message saying 'Success'.
10. Open the repaired file in Premiere Pro and then reset the workspace. Choose Window > Workspace > Reset Current Workspace.
11. Click the Save button to reduce the project size.
12. Your project is now repaired.
NOTE: If a file containing letters such as ã, å, ê, í, ú don’t repair, rename the file to something that doesn't contain these letters.

Hi Rameez,
first of all thanks a bunch for the tool - it saved our neck this morning on a tight deadline.
One minor note: I did get a message that the (already uncompressed + renamed) file is not uncompressed until I ran the tool as Administrator so you might want to add that to the FAQ entry...
Other than that I'm very much interested in what triggers this bug so we can potentially prevent it.
Background:
Specs: Windows 8.1, German locale (ie comma is decimal symbol), Premiere Pro CC 2014.2 installed in English
My colleague who ran into the TickTime.cpp-290 error remembers having created a new workspace while working on the project. That seems to have triggered the issue as we haven't had any trouble on other projects yet. It also got saved into the project file:
<MZ.Project.WorkspaceName>Bearbeitung</MZ.Project.WorkspaceName>
Any autosaves after he added the workspace were corrupted as well while the ones dating back to earlier still open fine.
I'd like to mention that Premiere did import previous (German language) workspaces - dating back until CS5. Not sure if that comes into play.
On the other hand, the debug log looks like there only is an issue with the decimal symbol:
10:08:06: Input: C:/temp/trouble/uncompressed/final.prproj
10:08:06: Path: C:/temp/trouble/uncompressed Basename: final Extension:prproj
10:08:06: 19852-> from: <PlaybackSpeed>0,069148936170212769</PlaybackSpeed>
10:08:06: 19852-> to: <PlaybackSpeed>0.069148936170212769</PlaybackSpeed>
10:08:06: 23970-> from: <PlaybackSpeed>0,0062741915889604422</PlaybackSpeed>
10:08:06: 23970-> to: <PlaybackSpeed>0.0062741915889604422</PlaybackSpeed>
I really need to make sure that this is no general problem with German locales as we have multiple users on this kind of config and can't afford projects breaking.
Or do we "just" need to watch out to get rid of the old workspaces? I'm a little puzzled to be honest.
Maybe it helps to mention that we are on CC Enterprise
Best regards,
Mike

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

Copy Paste of clips within a sequence closes the programm saying TickTime.cpp-290

Hello
I got the problem after a while when I want to copy and paste a clip or audiofile within a sequence the programm closes by saying Error TickTime.cpp-290.
It also happens when I open certian sequences.
All video/audiofiles are the same format.
I already used pp-repair.exe like in the forum but the problem isnt resolved. Importing the projectfile in a new project it tells me the same error.
Has anyone an idea?
Thanks

Hey,
Thanks for the answer.
Yes unfortunatly all values were correct and I had not to replace any comma by a full stop.
Do you have another idea?
regards

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.

Premiere Pro error TickTime.cpp-290

Hi, I have a serous problem with Premier Pro. This is the message:
Please, can somebody help me?
Thank you.
[Moved from the general Cloud forum to the specific Program forum... Mod]

look if this matches?
A guide to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

Error ticktime.cpp-290

I'm having the "ticktime.cpp-290" error a lot, recently. I've tried using the repair executable that can be found here, on the forum, but it isn't solving my problem.
What should I do next?
OS: Windows 8.1 - CC 2014.2

You informations are very poor. What version of Premiere,what OS, what OS version, what footage do you use, when the error message appears.
Question over questions. But without these informations nobody can help.
Take a look here: https://forums.adobe.com/thread/1264170?tstart=0

I can not open or start adobe 10 i keep getting a debug event src\EMS\WSEMSUtil.cpp-715

S

jeffs2wife
Do you have Windows 7 64 bit? Then there has got to be those two exe files in the route listed
Local Disk C
Program Files
Adobe
Adobe Premiere Elements 10
and in the Adobe Premiere Elements 10 Folder are the two .exe files
Oops. I think that I left out the Adobe in between Program Files and Adobe Premiere Elements 10 when I wrote that path in the previous post.
Another route to those .exe files...right click the desktop icon, select Properties, select Shortcut Tab, and click on Open File Location. If you are getting better results clicking on one of those .exe files than you are double clicking the desktop icon for the program, then
right click the Adobe Premiere Elements.exe file, select Send to: and then Desktop (create shortcut). Then use that shortcut that will appear on the desktop to open the program moving forward. By using the Adobe Premiere Elements.exe file, you will gain the perk of bypassing the Welcome Screen. If you want the Welcome Screen, then just create a replacement desktop shortcut to it the same way but using the Adobe Premiere Elements 10.exe file.
As for the latest driver for your ATI Mobility Radeon HD 5650, you should head to the AMD web site and plug in the requested information to see what it shows for your video card driver.
http://support.amd.com/us/gpudownload/Pages/index.aspx
Please update us on your progress.
Have you tried flushing the preferences yet?
Thanks.
ATR

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.

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.

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

Hello everybody,
I just ran into this extremely annoying problem:
Premiere Pro CS6 cannot load my project anymore. It gives the following error message:
Premiere Pro has encountered an error.
f:\mightysilt_win64\shared\adobe\mediacore\mediafoundation\api\inc\keyframe
My autosave files all refuse to open giving another error
..\..\src\TickTime.cpp-364
When i press continue it says the project might be damaged or contain outdated elements.
I do not know what that means...
I do not know what i did last before the problem started, except for adding some layers (lightstreaks) rendering the file and then stopping that thinking "I'll do it later"
What a mistake. The projectfile didn't open anymore when i got home. All my autosaves now give similar errors.
I got warpstabilizer on some clips but would gladly give that up if there was a way to open these files. I cannot import them to a new project. Essentially the files refuse to open in any possible way.
You can find my latest projectfile here: jajageweetmaarnooit.prproj - Google Drive
I am desperate, this movie needs to be delivered tomorrow and i have to start all over.

I even tried to transfer my project to a different computer, but still the same problem.
From what I understand form my google-searches, this error might be related to 'Regional Settings' and Keyframes, where decimal separators "." got replased by "," on non-Eglish Windows systems.
I've tried the solution suggested on some adobe help-page:
Solution
Download perl from http://www.activestate.com/activeperl/downloads.
Run the following command using command prompt on your computer:
perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" damaged.prproj >newfile.prproj
Replace damaged.prproj with the path of the prproj file that you are trying to open. For example, you are trying to open picnic.prproj saved to the Picnic folder of your computer's C drive. The path in this case is C:\Picinic\picnic.prproj.
Replace newfile.prproj with the path where you want the new file created. For example, if you want to create the file in the same location, use C:\Picinic\picnic1.prproj.
You rename the file to avoid conflict arising due to similar filenames in the same folder.Using the above example, the command is:
perl -p -e "s/([-0-9]+?),([0-9]{12,24})/$1.$2/g" C:\Picnic\picnic.prproj >C:\Picnic\picnic1.prproj
And I've even tried uploading my file to this page, with no luck: http://www.vibait.com/software/premiere-fix-keyframe.h-142/
Some people are suggesting to open up the project file in a textedior to change the ',' and '.' manually. But I found this to time-consuming as I don't know which commas to keep and not.
Paying € 250 or more to "Recovery for Adobe Premiere Projects with Error" is not an option.
But as mentioned, I've already started this project over once, and would not like to do it again, only to run into the same problem.

How to fix TickTime.cpp-346?

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 Germany

Malwarebytes 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/

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

Similar Messages

Maybe you are looking for