Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Premiere Pro CC crashing on cross dissolves.

B

Bobby Farokhzad

Well-known member
Joined
Feb 27, 2012
Messages
576
Reaction score
0
Points
16
As the title suggests, I have a serious problem with the latest version of Premiere Pro CC. Cross dissolves on the timeline can cause the app to crash. The solution given to me by the senior Adobe tech was "just don't use cross dissolves in your project" This is somehow ridiculous as any editor will tell you if there is one effect an editor needs, it's a cross dissolve. My workaround was to keyframe the opacity of a clip but again, this is not a viable solution. I am posting this here because there are many Adobe geniuses on this forum and I could really use some help. I am on the latest version of Yosemite and a 2009 8 core mac pro. I realize that this is a slow machine but I never ever had any issues editing with it. It is not possible to roll back to a previous version of Premiere Pro because only the latest version is available on the cloud. Also, I have cleaned all the media cache files and trashed all the referenced multiple times. Any help would be appreciated.
 
This may be a stupid question, but did you try making a new sequence? I was having serious problems like this and come to find out, my stupid self didnt even make a sequence, I had been editing without one
 
Not only did I try making a new sequence, I also made a new project with a new sequence. The problem still exists.
 
did you try setting the default transition to a different dissolve type...like film dissolve ect
 
I did. There were crashes with the film dissolve as well although not as often as the cross dissolves.
 
Are you exporting through media encoder?

If so try exporting directly from PPRO....dont send to the queue....just hit export.
If you are doing that then go through media encoder.

Also try changing export codec
 
Previous versions are available on the cloud...done it a few times myself, right through the creative cloud app(Google it)

When I have these problems it is codec related....usually cineform or a mov of some kind.....usually a single clip in a different codec from the rest and dissolves crash the encode. Sometimes replacing the single clip with the re-encoded version will fix it

Most times it is also the output codec....h264 can crash a lot....try a different option.

If all fails....you could do an opacity blend an assign it to a preset....then drag an drop it into your clips, one for the in...one for the out. But that would be a last resort....as I've never had to do that in PPro since CS3.

Also you could try disabling CUDA or openCL and run software only on the encode

You also could try rendering the previews first(all green bars in the timeline) an check 'use previews' on export

That's all te trouble shooting off the top of my head

Good luck
 
Mike, thank you very much for your help, it is greatly appreciated. I tried exporting to different codecs in both premiere and media encoder... it still crashes. It also crashes when I try to render. I will try to roll back to a previous version and cross my fingers.
 
What is the source format of the files you are applying the transition to?
Are you using GPU to render? If so, switch to software and try it. I doubt it's the transition itself that's the problem.

Wes
 
The bulk of the material is AVC-Intra 100 at 59.97 FPS, but there is a good amount of Prores 422 HQ. The crashing seems to occur in different places at different times, no rhyme or reason at all. I tried a different sequence that was 23.97 and the results were similar.
 
I tried software only mode, that was one of the first things I tried, it did not help. I went as far as uninstalling the entire AJA driver and the Adobe AJA plugin thinking maybe the problem has to do with my Kona card but that didn't help either.
 
Hi Bobby,

Sorry you're having issues. No fun. Do you think you'd be able to narrow down which sections are problematic?
If you can possibly pare the project down and end up with a few sections that repeatedly fail to render this could help us figure out what's going on.
What OS are you running?

Wes
 
Hi Wes, I have tried that. The mere presence of a cross dissolve anywhere on the timeline can cause the app to crash. The only way the app doesn't crash is to fully remove all the dissolves from the sequence.
 
Bobby,

I work on the Pr team. I try to help out on forums when I can find a few extra minutes.
If you'd like to create a small trimmed project I'd be more than happy to download it and take a look.
If I can reproduce it on my end, I can pass it along and get it fixed. That's the key. i need to be able to reproduce it or find out what could be different about your machine.

LMK if you can pare the project down, reproduce the bug and possibly throw it on an FTP - or even dropbox is fine.

Shoot me a PM and I could look into this as early as tomorrow morning.

Wes
 
Last edited:
I am betting this is a issue with the multiple codecs/framerates

have you tried making a sequence of just avc 100, with no prores, and add lots of transitions and see if it crashes.
That will tell you if it is the prores clips causing it(the combination of the 2 at least)
....if so you may have to reencode to another format

This is far from ideal, but I have had quite a few situations where I have to do this to a handful of clips in a timeline....usually it was the clips in a mov container
 
Over a month of back and forth with Adobe and this issue is still not resolved... rather unfortunate.
 
Yea CC and the Yosemite is pretty wonky. I have had all kinds of issues. Something as simple as a jpeg would crash it and cause rendering errors. A bit underwhelmed.
 
Had a similar problem months ago on a Windows PC running 8.1. IIRC, I think I actually re-edited and did away with the cross dissolve and finally was able to render. In my case, it always stopped the render at the same place. Had to restart at the beginning as what had worked successfully wasn't saved.

Been quite awhile ago and I only remember the frustration level rather than the details.

EDIT: Thinking back, I may have used previous cross-dissolves but had no trouble with them. It was this one dissolve about 45 minutes to an hour into my timeline.

At the time I wrote it off as just not having enough horsepower although I was working on an 8 core AMD build, but with only about 16 GBs of memory... but with some Neat Video which really slows things down.
 
Last edited:
Try shortening (or lengthening for variation) your cross-dissolves instead of using default.
 
You must log in or register to reply here.
Back
Top