Danielpremiere wrote: I have only recently upgraded at Premiere CS6 (from CS3) using PC. I am experiencing this problem with cross dissolves not being smooth with the hardware MPE GPU Acceleration (CUDA) enabled. It was one of the first things which I noticed when I started using CS6. The problem goes away when the MPE software only is used. Are other users still experiencing this problem, and is there any hope of an improvement from Adobe? Many thanks Daniel I still experience this problem with every single cross dissolve. It's more noticeable on certain contrasting shots that and I hardly notice the issue until I export and view the video outside of Premiere. But yeah, its still a crappy problem and who knows if it's gonna get fixed ever. The THIRD post in this thread has a great example from another user what the issue looks like. I do not have GPU acceleration enabled and I still have the issue so I don't think that's related, but that's interesting that it appears to go away when you disable that. If you export the video with and without CUDA enabled, do you notice a difference? Care to post it here? Either way, I ended up creating my own opacity preset for fading in and one for fading out and had the keyframes NOT be linear which is the issue. Instead, I went with EASE IN and EASE OUT for each keyframe in my preset. I guess just plain old "bezier" would have been okay too but I took it a step further with EASE IN/OUT. Good luck! Oh, and fill out a "bug report" on this HERE. ... View more

Same thing here. I was just handed a completed project with multiple sequences, some multicam, etc. and no errors. I added Warp to a bunch of the short little clips and got the error upon reopening. Warp Stabilizer is nice but is proving to be extremely BUGGY in its current form. I sicerely hope Adobe cares enough to fix it. Another example of it's bugginess is if you add warp, then toggle the effect off, and then accidentally reanalyze the clip again, Premiere Pro crashes. Not a very stable effect. ... View more

Thanks Greg. What's the number to call? I have a saved project just for this purpose where I've cut it down to just 5 clips and it still triggers the error. If I do one of a few different things to these clips I can make the error go away. I'm hoping that's a start. Would love to talk to someone and hopefully figure out whats up. Hope the agents are more tech support and less script readers Thanks again! ... View more

EselJaye wrote: @DMH "Or at the very least, I wish there were staff on this forum that could help." You mean beyond suggesting the "Bug Report"? Yes. Sending in bug reports to Adobe feels like feeding a city's parking meter even when the city has no parking enforcement. With no feedback, or no back and forth its really frustrating to not know if they care at all about any one issue. ... View more

EselJaye wrote: What I have discovered, through admitidly not overly scientific methods, is that if you eliminate the Warps in Pr and and do them in Ae the TimeTicks disappear -on my PC at least- Problem then is render times tend to jump up. So, one needs to balance hitting the "continue" button a few hundred times with additional render time. More importantly though is, I have now experienced a couple of "Program failed to launch" errors, when I still had the Warps in Pr after clicking the "continue" button -as I have/had only a couple of Warps this is more troubling. Has anyone else had this happen especially with more than just a few Warps? I normally have about 50-80 warps for any given project. The program has never failed to launch for me. Thank god. But with that many warps I'd probably rather have to hit continue a few hundred times rather than wait out that much Ae rendering. Now again, in the example above I started with 396 continues and then deleted files all the way until I had 5 clips left and got it down to 4 continues. If I removed the Warp or the nested multicam the error went away. Either way, it sucks that Premiere CS6 is such a buggy program that makes working a pain in the ass. Wish there was a way to give tech support my project with just 5 clips and let them figure out the error. Or at the very least, I wish there were staff on this forum that could help. ... View more

This error is driving me nuts. It affects EVERY project of mine. It also affects the other editors that work for me given that they do the same sort of edits as I do. As you can see from the previous posts I've narrowed it down to having literally just a few clips on a timeline and I can make it go away or come back just by adding or subtracting an effect or a nested sequence. Right now, my current project I have to hit "CONTINUE" 244 times when the error pops up (which it does EVERY time I open the project AND every time I export the project). 244 times!! I'd say that's bad, but the last project I got up to 396 times for a full project (Weddings). I use Warp Stabilizer. I nest sequences and make multicams out of those nested sequences. It has to do with those. Thought maybe it was a Mac issue but looks like some people have had PCs. Is there ANY hope at all that this will get solved. I'd gladly donate a project to Adobe to test or whatever. I have no idea on their track record for solving ERRORS like this but it sure does put a damper on your work when EVERY project you work on every single week has an error where you have to hit continue hundreds of times just to open or export it. Unfortunately, importing it into a new project doesn't always work. Any help???? ... View more

Had the same error tonight. Ugh. I already have to hit continue 96 times on this error (ticktime.cpp-207) just to open the project! That error hits every single one of my projects and I once had to hit continue 396 times to open a project (yes, I counted). This one with audioprefetch.cpp-99 is new as of tonight and hit right after I added a series of cross dissolves to the audio of combined clips. I found that collapsing the audio track helped. I also read somewhere that turning off waveforms in the audio tracks will help, but at the end of the day its REALLY annoying. So I tried switching "6.0" to "old6.0" as described in the above post and I still had the same error. The error causes the waveforms in most clips to disappear. I had to hit continue on this error 41 times. Now that's not the 96 that I have to hit on the other error EVERY TIME I open my project but the error was still there. So I went back and deleted a few of the cross dissolves and then the error went away. At least so far... It's been only 5 minutes now since the error appeared, when I decided to come back to this thread so I'm not sure if it will stay away but this is my experience so I thought I'd share. I have almost zero faith in Adobe on fixing either of these 2 errors, but that's only because I sometimes feel like there's so much they're working on and trying to fix that errors like this that hit a few people don't really matter. I've no proof, just a building sentiment. Great, error-rich program Premiere CS6 is. (that sounded like yoda) BTW, I'm on a 2011 27" iMac with AMD 6970M and 16gb RAM, OSX 10.6.8 Premiere CS 6.0.2 in case that matters. ... View more

LancFM104 wrote: DMH79, I just tried to open a small, previously error-free project and I got the error message.  I had to hit "continue" five times.  It appears that my PPro is corrupted and may need to be re-installed. Len Well, please report back if you do reinstall and it goes away. That would be a shocker if its simply a corrupt download of the program, instead of just a buggy software.  I can't imagine with a thread with well over 3000 views that its an isolated incident. But I'm open to all ideas because it definitely sucks. Definitely report back on if it helps to reinstall. I've never opened a project that previously did not have the error and found that it did. Last night I made small adjustments to my work and re-saved the project 93 times!!!...and then reopened to test. Just when I thought I'd nailed it, the next adjustment and save proved me wrong. Like I said, I got it down to where I can do one thing to one clip and make it go away or make it come back but I just don't see what exactly is the cause of the issue. Seems to me to be a combination of just a couple things like I said in my previous post. I will post another bug report with a link to this thread in hopes that Adobe actually reads those things and cares to fix things that are broken. I don't have much faith but that doesn't mean it won't happen. We'll see. ... View more

Okay, I've done all I can do. Testing all night. Got down to 5 clips on one timeline. 4 of them are short individual clips (all with warp stabilizer toggled on) and one is a nested multicam sequence. The Ticktime.cpp-207 error occurs upon opening this project and I have to hit continue 4 times now. With only 5 clips I can make the error appear and disappear just by tweaking one or two things. Here's my results: 1) Nested multicam clip PLUS 4 small clips with warp stabilizer turned  = Error occurs upon opening and hit continue 4 times. 2) Nested multicam clip PLUS 4 small clips with warp stablizer toggled off = Error occurs upon opening and hit continue 5 times 3) Nested multicam clip PLUS 4 small clips with warp toggled on each except toggled off on the 4th clip = Error / hit continue 5 times 4) Nested multicam clip PLUS 4 small clips with warp toggled on each except toggled off on either the 1st, 2nd or 3rd clip = Error / hit continue 4 times 5) Nested multicam clip PLUS If I delete ANY of the warp stabilizer effects off of ANY of these 4 clips = NO ERROR 6) Nested multicam clip PLUS if I delete ANY of these 4 clips entirely so there's only 3 small clips left (with or without warp effect toggled on/off) = No ERROR 7) If I delete the nested multicam clip (or even UNCHECK the "enable" multicam in it's sequence) and add it these 4 clips with the warp stabilizer applied to each clip (toggled on or off doesn't matter) = NO ERROR ---------------------------------------- FINAL RESULT: Somehow I've got it down from having to hit continue 396 times to only 4 times and I've withered it down so I only have 4 clips and a nested mulitcam sequence remaining on one timeline AND most importantly I know exactly what to do to trigger the error message, but I still can't figure out WHY it happens so it can be fixed. Ugh! Somehow I hope this helps in some strange way. Wish I could pass this on to those at Adobe that test these bugs. If they even care that is. I'm at a loss. ... View more

Interesting. And how many times do you have to hit continue on the error message to open the project? And did you ever try taking clips away, resaving and seeing if it opens without the error to hopefully pinpoint the cause? Would be helpful maybe as I can pretty much reproduce the error everytime I want now by adding certain combinations of clips. And all my clips are ProRes 422 so its not a format thing. Just wondering if its either certain filters added, certain clips, or a combination of specific elements. Anyway, if you have time, test it out and report back. ... View more

Hmm. Interesting. So did u have any nested sequences in the project? Any warp stabilizer effect applied? Just curious. ... View more

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 ass. 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. ... View more

Thank you very much for all your input. Unfortunately, even though I have the latest iMac Adobe has yet to support its card (AMD 6970M) for hardware acceleration. Even more unfortunate, I don't  really know how to use waveform so I couldn't test the footage in my timeline. Sigh. Still, linear should be linear and consistent and I'm not sure what the exact cause is of the issue. In FCP, I never had to ease in/out. Their linear was smooth all the time. This is all very strange to me. ... View more

I did that. Not quite as obvious as when real clips are used. So maybe its not light to dark issue, I don't know. Like I said though, sometimes its less noticable and sometimes its very noticable like that guy's video. I know earlier in this thread someone suggested to the guy to not select max render quality upon export. Well, I'd rather not do that for 2 reasons: 1) That sucks to have to take away the "benefits" of selecting that box for the sake of cross dissolves  2) The effect can be seen in the actual timeline as well...although admittedly its much more noticable upon export. ... View more

shooternz wrote: Here are some standard cross dissolves in a little example of my work. Great. Now I'm hungry. Well, I watched that about 10 times and I think because its got a lot going on in each clip and because there isn't that much difference in contrast on a clip by clip basis this issue is not really noticable. I had to watch it 10 times to even pick up on possibly one instance...the last fade between the open can and what looks like a pill. That one seems to clip out quickly perhaps. The thing is, not every cross dissolve is that noticable. Some just really stand out more than others. Not totally sure what causes it to be more noticable (maybe something light fading into a more dark shot I don't know) but its definitely there. If there's no way to adjust it to ease in more, I'll just stick with editing stuff on top of each other and use my custom presets that I made that ease in/out. Would be nice to adjust the effects that go on one track though for things like multicam, etc. Oh well. ... View more

shooternz wrote: Thanx for posting. I agree ...your cross dissolves are "ugly" and as you described...seem to go weird over final 10% Never seen that  "issue"  before... in my work. Are these butt cut clips on a single video layer? I don't know because they aren't my clips. The original poster was someone different from a year ago but my clips look the same and yes I tested them butted up against each other and also on top of each other using the cross dissolve with the same results. Its not as noticable if the two clips are similar except in areas of high contrast. The presets I made with ease in/out are helpful for the stacked track editing I just wish I could apply it to the seqences that have all the video clips on one track (eg. multicam) with ease. No pun intended. But according to Jim's recent response its not possible. Bummer. ... View more

shooternz wrote: I would be interested in seeing a video of your manual cross dissolve and the Effect Cross Dissolve. I have never found issue with the FX Cross Dissolve but can understand how one could get issues with a manual one.  (Apart from how time consuming it is and how messy the timeline must get - how do you manage the clip overlap?) Can you post a screen grab of your Key frame window? Looking closer the cross dissolve does have the same abrupt start and end that you see in the original post's sample seen here: http://vimeo.com/14536285 I originally said that it was better than linear opacity keyframing one track on top of another, but after a few tests its not. Hopefully you can see in his video what happens on these fades. After you see a few in a row I really start to notice the first and last 10% clip in/out unless its bezier or even better ease in/out. But like I said in my previous post, I've now got a preset for ease in/out fades but its a keyframe preset. Is there a way to adjust the cross dissolve effect with ease in/out or create a new cross dissolve effect that you can drop on top of two clips back to back on one track? ... View more

I was able to create my own preset fades with the ease-in/out. Thank you for the advice. Now is there ANY way to create a cross dissolve preset (that can span accross two clips when they are back to back on the same track like the cross dissolve effect can) or can I somehow adjust the current cross dissolve so that it eases in/out? The current cross dissolve and film dissolve effects aren't bad, its just not as smooth at the start and end as if you put tracks on top of each other and eased in/out.  ... View more

Jim Simon wrote: Currently those keyframes do not Ease Out or In because I didn't feel it was necessary, but you can always change that and save new Presets. That's awesome. How would I go about changing and saving new presets? Never done that before. ... View more

Jim Simon wrote: is there a way to set it to always default as EASE IN or EASE OUT? Already done. http://forums.adobe.com/thread/1010578?tstart=60 Thanks Jim! Two Questions: 1) Exactly how is this Film Fade Preset different than the current Film Dissolve? How is it different than Cross Dissolve? Does it incorporate a smoother start/finish (eg. ease in/out)? 2) I see in that thread its set to default at 1 second? Can I change that to two seconds somehow by default? If not, its not a big deal as I can just manually adjust, just curious. Thanks! ... View more

shooternz wrote: So what happens if you use the  Cross Dissolve Effect? It's hard to say. I only did it that way a few times. Looking at it now, those (using the effect instead of keyframes) don't look quite as bad.  Not quite as smooth as ease in/out but more smooth than the linear cross dissolve using keyframes. Just wondering I guess if there's way to always have it ease in and out without having to individually click on each keyframe and adjust. A keyboard shortcut? A plug in? Anything. ... View more

shooternz wrote: Are you saying that you are not using the Cross Dissolve Effect ? ie. you are creating all your cross dissolves manually using opacity keyframes? Yes. ... View more

DanielFrick wrote: I've been having this issue since I first started with Premiere Pro (cs5) and it has kept me from using any dissolve transitions or the program altogether: Dissolve transitions (specifically Cross Dissolve) will not end smoothly - there is always a jump at the last, seemingly, 10% or so of the transition. Okay so I realize this thread is old, but I can't stand how normal cross dissolves (I tend to keyframe all opacity changes) have this unsmooth/abrupt start/finish. His video in the original post is exactly what I was experiencing all weekend. Coming from FCP, the same basic cross dissolve is smooth with no jumps. I ended up going into every single one of the disolves and selecting EASE IN and EASE OUT for each and every opacity keyframe. With a huge project and tons of dissolves this took over an hour. Is there anyway around having to do this manually one by one to every keyframe? Like is there a way to set it to always default as EASE IN or EASE OUT? I realize the above work around was to turn off maximum render quality during export. Not sure if that helps, but I don't like the idea of sacrificing export quality for simply having smooth transitions. Plus, its a year later and maybe CS6 has a better way now to handle cross dissolves so they don't come out so crappy. (I'm on a 2011 27" i7 iMac with 16gb ram and the AMD 6970M card) ... View more