14.0.2 crashing - screen shot

[neilw16441096]

Proir to this upgrade no issues exporting this movie.

Neil Wieteska

[thnord]

Can you tell us a little bit about the source media and your export settings.

[neilw16441096]

The source material is UHD Prores HQ422,  Prores HD 1920x1080 and some time-lapse rendered at 388x2592 Prores 4444. All 25 fps

Export settings Quicktime ProresHQ 422  1920x1080, maximum render quality, highest bit depth with audio exported also. 

Also crashes using H264 as export codec, again with maximun render quality and highest bit depth selected

Neil Wieteska

[neilw16441096]

sorry, the time-lapse frame size should have been 3888 x 2592....

[neilw16441096]

Any suggestions how to handle this?

Neil Wieteska 

[thnord]

We've investigated the issue further and if you are encountering the issue I think it is you will have the Max Bit Depth checkbox enabled either in your sequence settings or your export settings. If so, try disabling that setting and running the job again. If that works, then you've hit the bug we are investigating. I sincerely apologize for the inconvenience. At this time disabling the Max Bit Depth checkbox is the only workaround.

[neilw16441096]

That does seem to be the issue and unchecking that allows a render.

Thank you for the help.

Regards,

Neil Wieteska

[R Neil Haugen]

So, what is happening in your project at 5:24? Typically, a timecode reference tells you there's a problem to correct at that spot on the sequence. Sometimes you need to go as far as removing the clip from Premiere and re-importing it. Often clearing the cache/media cache database files while Premiere is closed and relaunching the app is enough.

Just a bit of general information on export/render settings.

Max Render Quality is primarily of use in frame resizing, which you are doing in some of your media. It's for dealing with "jaggies" on diagonals resulting from frame-resize computations. So ... when there are no frame-size changes, MRQ doesn't do anything.

Max Bit Depth is primarily of use when doing color/tonal work when you don't have a "Mercury Acceleration" option in the project settings dialog set for using your GPU. It forces the CPU to use GPU style math ... which will work it a bit slower but get better computations for bit depth.

In other words, if your Project Settings dialog Mercury Acceleration option is set to "software only" you probably need that MBD option set to "on".

However, if you're running a GPU being used by Premiere for color/tonal work, the MBD option may or may not be of any use. I've left that off most of the time and never had an improper bit-depth of the exported file.

[neilw16441096]

Thanks for the reply. The 5.24 is when the first UHD shot comes in after the HD title and this happens in another sequence I've tried, but with a different shot after the HD title. I've exported various codecs from both of these sequences prior to this upgrade with no issues. 

[R Neil Haugen]

If you take a moment to rework that clip, and try an export of just the first few minutes for testing, does it export that clip? And note, you may need to re-import the clip if Premiere's database has screwed up somehow on meta for that clip.

Neil