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!
I've now concluded that the number of error messages you have to click through is the same as the number of times that warp stabilizer was applied. This is very dissappointing as I use that effect a lot but I think I'll have to avoid it until I'm done with the rest of the editing and then apply it and cross my fingers.
Please file a bug report for Premiere Pro CS6: http://www.adobe.com/go/wish
I have tried to reproduce the problem in Premiere Pro Next (our upcoming version of the application). I couldn't reproduce the bug.
My timeline looks like this:
Awesome, that's good to hear! I'm excited for it. So it's Next, not CS7?
Also I figured out that replacing clips with AE comps and stabilizing there
works just fine and the project opens correctly in Premiere. Just as an FYI
is anyone else has this problem.
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):
And then also, it definitely made my "Top 15 list" here:
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.
Why don't you just do the multicam editing, then use "replace with after
effects composition" to stabilize? I've begun doing that on this project
and the error is completely absent in both applications and it works
perfectly. A little more time consuming than the normal workflow but
definitely better than clicking through the error.
I haven't done that because again every project has several hundred shots with hundreds of clips that are stabilized and the back and forth with AE would proabably add up to more time than it takes to quickly hit "continue" 300 times. The multicam clips generally don't need any stabilization. Both ways technically "work" to get past the error, but my point was that it'll be nice to not have to deal with any of this in a few weeks (assuming CS7 is gonna hit in May sometime (6th?)). Also, truthfully I'm not completely familiar with AE although I may utilize it more in the next version given it's added warp stabilizing vfx features that are coming which look amazing. Being able to isolate what I want to be stabilized will be very helpful. For example, sometimes something as simple as a CU of a guy nodding his head throws off Warp Stabilizer as it thinks the nodding is the camera shaking. Either way, glad to hear you enjoy your workaround.