Premiere Pro CC 2018 crashes when using lumetri color

[Vincent.]

Hi.

So my project keeps crashing in premiere pro cc 2018.

I'm on the most up to date OSX on my mac. My cuda driver is updated as well.

I have all of the necessary hardware for editing, etc. Not sure how much more information I can provide.

This is what caused my crash:

On one video clip I applied the lumetri color effect onto it and made my necessary corrections. Then I duplicated the clip to another track above and wanted to mask out the top half of my clip because it appeared to be blown out from daylight. After resetting lumetri on that new clip, I hit the pen tool in the mask area of lumetri which caused the project to crash.

Is there a clash when two clips have lumetri loaded onto them, overlapping each other?

[Vincent.]

Edit: It appears premiere pro cc 2018 will crash if you try to use the mask tool on opacity as well.

[R Neil Haugen]

I won't be into the studio until Monday, but I'll give this a shot when I do. If masking Lumetri causes a crash, that's a problem. And the more of us users can pass such info back to the developers, the better.

Neil

[Vincent.]

I've already submitted a crash report.

Additionally, it's crashing when I want to export a project i.e. command M or hit export in 'File'. It won't crash immediately on command M when I don't have Lumetri on in the effects controls.

I really don't know what I'm doing wrong.

[R Neil Haugen]

Weird ...

[R Neil Haugen]

I'm not able to replicate problems with mask or exports involving Lumetri ... I tried dragging a vid up and using pen & rectangular masks, both work just as expected, on a Win10 system. I'm hoping a Mac user will have some time to try this out ...

Neil

[geofk64428442]

After installing 2018 it crashed every time I used it, usually just changing windows.  And when reopening after crash the work was not saved, every just gone.  I uninstalled it, went back to 2017 version.

[NDubePhotos]

How'd you reinstall 2017? Or did you not uninstall to begin with?

[SarahHeatonReeves]

Same problem here.

When premiere pro opens for me....which is hit and miss in itself now......I can barely do anything as it crashes before I have chance to think.

This started happening after I used Lumetri colour presets

[geofk64428442]

It happened to me when doing simple things such as opening new panels, or even saving the file. I uninstalled it and reinstalled 2017. For me all other Adobe updates are fine but this one.

Geof Kern

geofkern.com

[wonderful_Fireball5E82]

I am having the same problem, me when I open the scopes it crashes it does not matter what kind of video i used it just crashes. I tried to get help from the adobe staff and the cant find a solution. One just told that I should format the computer and just put windows again. Need help here!

[R Neil Haugen]

Which version ... number-dot-number ... of PrPro are you using?

OS? CPU/RAM/GPU/vRAM ... ? And video drivers ... this often is a video driver issue.

Neil

[joshs41319915]

Ive installed premiere 2018 and the newest os update and I found If i try to apply any effect the program will crash. If i try to open an old project with effects on it, it will crash. Still looking for the issue

[R Neil Haugen]

Are you on a Mac? If so, the latest issue of the High Sierra OS there seems to have issues on some rigs with PrPro.

Neil

[joshs41319915]

is there a fix to this? I had a feeling it was the OS update

[R Neil Haugen]

Not that I know of, other than rolling back your OS.

Neil

[ScottieB1]

This is a real problem.

Lumetri crashes on Windows 10 as well.

Using the SAME project, which I've been using in CC2017 for a while now... the entire timeline has an adjustment layer, with Lumetri applied and a LUT. In CC 2017 I've never had a problem. In CC2018 it crashes after about 10 minutes, with a popup that says it is Lumetri that has stopped working. If I use 2017 (which I will obviously continue to do) this crash never happens.

While we are at it, can we also talk about how TERRIBLE the coding is for Lumteri and it's LUT drop down? If you install ANY other LUTs, your projects will have the WRONG one applied going forward. This is because rather than read the actual FILE NAME of the lut, it seems to use it's index in the list of LUTs. So if you apply the first lut, index 1, and then install another, your previous LUT will now be index 2, and the wrong one (the new index 1) will be applied. In 2018 this kind of coding is absolutely inexcusable for software that is supposedly professional and usable in a production setting. And also if you render in AME, make sure you have the Luts installed separately for AME, because it doesn't use the Premiere ones?!?! Pretty major oversights here in my opinion.

Hey adobe, I thought the CC thing was supposed to make updates BETTER - seems to me every single one is expected to be beta tested by US.

[R Neil Haugen]

The LUT folder issue is something that came up back in what ... 2015.3, the first of the 10.x build series (if I remember my numbers right). Yea, the using the Creative folder for adding LUTs is very problematic. It's clearly using place in list rather than name for some reason. I've never understood the reason for changing to this, but supposedly it 'fixed' another problem that many users had.

That said, 2018 is running quite well on my Win10 machine ... though for some it's all over the place. Would be nice if that got sorted.

Neil

[avox12]

Same here this suuuucks

[R Neil Haugen]

PLEASE post this on the UserVoice feedback system. Search there for others with the same issue, and piggy-back on their reports.

Neil

Adobe Bug /Feature Request form: https://adobe-video.uservoice.com/forums/911233-premiere-pro

[neumannfx]

OK. So I've been having this problem for a while too, and this is what I've figured out how to get around it.

I like to use the Cinespace 25 preset for a quick grade on these sermons I take care of for my church. The files are large and I have them in both ProRes from the Black Magic recorder and .mp4 versions from a edit workstation backup. Doesn't matter which file I use, the output crashes.

But...

If I output the file with no CCR there is no problem. If I output the file with custom CCR there is no problem. If I output the file with Lumetri Preset it crashes. So I applied the Cinespace 25 preset and then saved that preset as a personal preset (Sanctuary CCR) and the output completed as expected. This worked for both the ProRes file and the .mp4 file.

All this done on an iMac with Nvidia.

I also have a HP Windows 10 mobile workstation that DOES NOT experience any of these problems. The Lumetri presets work just fine on this box.

So that's what I've found. Weird. But so far I can replicate it and solve it.

[R Neil Haugen]

My guess is there's something off in the computer stored file of that preset, or the database data on it. Saving it as something else left out the corrupt bit, or de-messed it somehow.

Neil