how do you render your 4K files?

Report · Feb 15, 2018

hello my dear adobe friends,

for years i totally have given up on 4k renders, as it simple just always fails the rendering.

1080p is no problem at all, but bump it up to 4K and it's totally impossible to get out of the system.

prior it has not been such a big problem as clients didn't really request it... but now they do!

i work with RED files ranging from 4-8K footage in a 4K timeline.

Export to a h.264 file in high profile.

in full hd: no problems. the computer chews it up and renders super fast.

in 4K: the computer slows dramatically down until it's inevitably failing.

the error from AME is always about the GPU:

Error compiling movie.

GPU Render Error

Unable to process frame.

Writing with exporter: H.264

Writing to file: \\?\D:\Dropbox\film work\loopers\numero russia - march editorial film_2.mp4

Writing file type: H264

Around timecode: 00:00:21:22 - 00:00:22:06

Rendering effect: AE.ADBE FC PRO 2.1

Rendering at offset: 21,880 seconds

Component: EffectFilter of type GPUVideoFilter

Selector: 9

Error code: -1609629695

So, it's a GPU problem.. but why? i have the GTX 1080 Ti with 12gigs of ram. is this really not enough to render 4k files out?

and how do you guys get your 4K files out?

Report · Feb 15, 2018

Have you tried exporting to an internal drive.

Report · Feb 15, 2018

yes it changes nothing.

i just paid attention to the GPU memory, and it just climbs steadily over 10 minutes of rendering until it crashed when it has used all memory!

anybody had that?

Report · Feb 15, 2018

Is that GPU over-clocked? And note, some come from the factory in "over-clocked" form. If so, that could be an issue with the latest versions of Win10. Just a wild suggestion.

Neil

Report · Feb 16, 2018

Hi Neil!

it shouldn't be overclocked, as i exactly avoided the OC'et versions - bad experiences in the past with that.

My main issue is that I never really had it going. It's always been a struggle to get the 4K out.
Now I just monitored the card and it just steadily fills up the RAM until it crashes... ARgh!

Report · Feb 16, 2018

Ugh ... nasty. Did you file a bug report?

I would suggest posting over on the Hardware forum and hoping that one of the gear experts like Bill Gehrke or Safeharbor11 hop in!

Neil

Adobe Bug Report /Feature Request form ... https://www.adobe.com/go/wish

(They never respond to postings, but all filed reports are collated and distributed to all relevant managerial types, so

Report · Feb 15, 2018

Try Step 2M below.

Unofficial Premiere Pro Troubleshooting Guide

Report · Feb 04, 2019

https://forums.adobe.com/people/Viktor+sloth wrote
hello my dear adobe friends,
for years i totally have given up on 4k renders, as it simple just always fails the rendering.
1080p is no problem at all, but bump it up to 4K and it's totally impossible to get out of the system.
prior it has not been such a big problem as clients didn't really request it... but now they do!
i work with RED files ranging from 4-8K footage in a 4K timeline.
Export to a h.264 file in high profile.
in full hd: no problems. the computer chews it up and renders super fast.
in 4K: the computer slows dramatically down until it's inevitably failing.
the error from AME is always about the GPU:
Error compiling movie.
GPU Render Error
Unable to process frame.
Writing with exporter: H.264
Writing to file: \\?\D:\Dropbox\film work\loopers\numero russia - march editorial film_2.mp4
Writing file type: H264
Around timecode: 00:00:21:22 - 00:00:22:06
Rendering effect: AE.ADBE FC PRO 2.1
Rendering at offset: 21,880 seconds
Component: EffectFilter of type GPUVideoFilter
Selector: 9
Error code: -1609629695
So, it's a GPU problem.. but why? i have the GTX 1080 Ti with 12gigs of ram. is this really not enough to render 4k files out?
and how do you guys get your 4K files out?

I get this all the time, similarly on a very powerful system, and FilmConvert is always, always, always the primary culprit. Although Lumetri causes random crashes too, my Error Log proves that FilmConvert has got a serious bug in this area, when hardware acceleration is enabled.

Meantime, Adobe loves passing the blame, when in reality this is a systemic problem of one side never talking to the other. I have been nagging the New Zealand-based FilmConvert (small) team about this for years, and they haven't budged an inch improving the plug-in (indeed, the version history shows that they haven't made a single change for over two years, which is an eternity in the Adobe Creative Cloud culture). It might be in the end that some kind of GPU memory leak, or whatever, is something that both sides need to work together on - not one or the other.

And it's a totally unacceptable solution for us to bring our renders to a crawl by permanently throttling down to Software Rendering, making our GPUs essentially worthless.