GPU ram overloads in Premiere/Media Encoder in sequence/export

Hi,

Since I've been using CC 2017 Premiere/Media Encoder my GPU ram constantly overloads. I have a Nvidia GTX960 2GB GPU installed, and before you're saying that 2GB isn't enough, let me just say this. I had no problems at all while using CC 2014.

At first I edited 5min 4K videos in CC 2014 in 20 mins. I used a mix of the very basic color grading stuff like contrast/brightness, luma curve, etc. I had to use 4 or 5 separate effects. Realtime playback was really smooth at Full workspace resolution, and Warp Stabilizer just slowly analyzed the frames. When I saw a review of the new Lumetri Color effects, I had to try it out, and basically I love it so much, I just don't want to go back. It's powerful, easy-to-use, and all-in-one.

I'm not sure whether the problems started because of CC 2017/Lumetri, or because I reinstalled Windows 10 at one point. After updating from 2014 (smooth full 4k playback) to 2017 the playback wasn't as smooth anymore. I had to use 1/8th of the resolution. At first I thought it might've been the drivers... But then I noticed it only happened with GPU intensive processing. Basically, it feels like the whole "Premiere Pro"-program got hardware accelerated. As my GTX960 has only 2GB ram available, I looked at the ram usage through GPU-Z. When the computer is idle, without any running programs, it uses 250MB of my GPU ram. Starting Premiere Pro in an empty project already drives up the ram to 450MB. Adding one 4K video file (5s, 26MB) to the sequence, doubles GPU ram usage to 800MB. Add Lumetri Color, and adjust a variable such as temperature, now the GPU ram usage will add 200MB and you're already at 1GB total RAM usage for 5 seconds of video.

What I notice is that the ram usage by Lumetri Color and Warp Stabilizer (but also playing back long sequences) builds up until it reaches 2GB and everything just goes black in the playback screen. Rendering works most of the time at a second or third attempt in Media Encoder, after I completely restart Premiere Pro.

But today it's just weird. I have a 6MB .jpg, keyframed downscaling, vignette with Lumetri Color and a .mp3. It's about 4 mins long, and when I try to render it in 1080p with Media Encoder, it just stops because it uses more than 1900MB GPU ram, probably peaking at 2GB and... Error.

"

Error compiling movie.

GPU Render Error

Unable to process frame.

Writing with exporter: H.264

Writing to file: \\?\C:\Users\Username\Desktop\export.mp4

Writing file type: H264

Around timecode: 00;00;24;12 - 00;00;24;28

Rendering effect: AE.ADBE Lumetri

Rendering at offset: 24.424 seconds

Component: EffectFilter of type GPUVideoFilter

Selector: 9

Error code: -1609629695

"

All I can think of is that the GPU ram is overloaded and it just stops everything. But when the error appears, the ram usage stays above 1900MB, until I close the entire application. When restarting Media Encoder, it starts at 800MB again.

I believe that all the data by GPU accelerated effects stay in the GPU ram, causing it to overflow until the entire Adobe program is closed.

I suppose if I can limit the regular RAM (to only use 7GB of 24GB) in Adobe, that it should be possible for Adobe to have a function to not ever use more than 1400MB GPU ram? Sure, it will go slower, but at least it will keep rendering without having to retry.

And please don't tell me to what others said about the error code; I am not willing to only use CPU rendering to render a 5min video in 5 hours. At least, that has been the advice to everyone Googling the error code. I have this massive GPU for a reason, low-budget video editing. At the time I didn't even consider doing 4K, and 1080p was just smooth. But now, 1080p even causes render errors...

My specs:

Operating System: Windows 10 Pro 64-bit

Processor: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8 CPUs), ~4.0GHz

Memory: 24576MB RAM

DirectX Version: DirectX 12

Card name: NVIDIA GeForce GTX 960

DAC type: Integrated RAMDAC

Display Memory: 14261 MB

Dedicated Memory: 2016 MB

Shared Memory: 12245 MB

Card name: Intel(R) HD Graphics 4600

Display Memory: 2160 MB

Dedicated Memory: 112 MB

Shared Memory: 2048 MB

Driver Version: 20.19.15.4531

Hybrid Graphics GPU: Integrated

--The only error in DxDiag that was Adobe related--

+++ WER9 +++:

Fault bucket 129340799662, type 5

Event Name: RADAR_PRE_LEAK_64

Response: Not available

Cab Id: 0

Problem signature:

P1: Adobe Media Encoder.exe

P2: 11.0.2.53

P3: 10.0.14393.2.0.0

I was using an older version of CC 2017, and made sure to update to the latest release before posting on this forum. My current (updated) CC 2017.1.2 still have the same issues. It could be that my GPU ram is just too low (2GB). But isn't there a workaround to limit the GPU RAM use in Adobe itself, or maybe extend the GPU RAM to an allocated space on my SSD. Both not ideal, but I think way better than editing 720p proxies at 1/8 resolution. Plus, making proxies takes an hour. Rendering every cut, every change in the sequence, in order for smooth playback just doesn't work either. Plus, when rendering every cut in the sequence, the same render error can pop up too.

I hope someone could help me. Continuous render errors are not really awesome...

*If any Adobe tech person reads this, here's a suggestion: Rename the Lumetri Presets to something without Lumetri. When searching the effects, I have to type Lumetri C to skip a whole list of presets. Without the presets I could just search "lumet" and done.