Welcome to our community

Be a part of something great, join today!

  • 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 :)

how do you render your 4K files?

Viktor Sloth

Well-known member
Joined
Apr 12, 2012
Messages
69
Reaction score
0
Points
0
Location
Denmark
Website
duende.works
hello my dear RED 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.


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. filling up the ram of the GPU



the error from AME is always about the GPU:

Error compiling movie.

GPU Render Error

Unable to process frame.

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




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?

so how do you guys get your 4K files out?
 
So, it's a GPU problem.. but why? i have the GTX 1080 Ti with 12gigs of ram.

It's not a GPU problem, obviously.

Or rather, any GTX 1080 Ti in good working condition has no issues. The same can be said for a very large number of graphics cards from both Nvidia and AMD, including what we'd call entry level cards today.

Just to be sure: we're talking straight up 4K output here? Not clips with various effects or noise reduction applied (that might need special trouble shooting)?
 
Adobe is always using the monitoring videocard. Thus, if you have 2 cards - one for GPU Compute, other for UI - you should know, that Premiere/Media Encoder will always use the UI one. I have two cards in my PC, one is 1080 1st gen, second one is gtx 570 with 1250MB ram. Usually i'm doing final render from Resolve, so working on edits in Premiere at 1/4th on a timeline with GTX570 is fine for me. But if I need to make a final render from Premiere, I just switch the monitor from one card to another, and then restart the software (to update the hardware config).

Also try out software rendering only and look for any hickups at the same spot.
 
Last edited:
First export a master to a friendlier codec (like Cineform) at 4k and then render that new master file to H264. Adobe has horrible H264 encoding issues and doing a dual export actually saves time if you can believe it.
 
Can't comment on the technical GPU aspects but I'll second Brendan's advice. A few months ago I kept hitting this issue and exporting as ProRes then transcoding that to .h264 seemed to do the trick. Not pretty but does the job ¯\_(ツ)_/¯
 
Hey Andree,

It's both with and without effects.
The RAM just slowly gets full. It's like it's not dumping the ram on the GFX, but just keeps adding until it's failing.
But, effects or no effects - it will be difficult for me to edit a whole project without any effects whatsoever, even lumetri colors, just because Adobe crashes, haha.
I'm sure that i can get it out with software rendering, but that will take unacceptable long time.
 
First export a master to a friendlier codec (like Cineform) at 4k and then render that new master file to H264. Adobe has horrible H264 encoding issues and doing a dual export actually saves time if you can believe it.

I really don't want to believe it.. but adobe will always be adobe...
I will try another format than directly to h.264 as a test.
 
This might be a solution for your rendering problems and it's only €259 https://www.blackmagicdesign.com/dk/products/davinciresolve/ and they have an other program also € 259 https://www.blackmagicdesign.com/dk/products/fusion/ which is also not to bad.

And the best thing is that there is also a free version of both programs to test it out upto UHD.

I had that installer laying on my desktop for a while... you probably know the feeling about having time to learn it!
it's always after THIS project I will try to learn it, and then it just never happens.
 
There are a number of reasons it's a bad idea to go directly to H.264 on a timeline for 4K master.

One reason may be that your graphics card is trying to do all the graphical operations from your timeline AND do hardware encoding of the 4K h.264 stream, and struggling to do it all at the same time. This is not so much an issue with the Video Card across the board, as it's ability to juggle multiple intensive tasks at the same time (hardware encoding AND 4K colour correction on GPU etc.) While it may be able to handle both tasks easily independently, as others have pointed out doing the whole procedure on card at the same time can create bottlenecks that makes the process fall over.

Approaching encoding 4K material as a two step process will result in smoother workflows. In fact, in general, approaching all encoding of any GPU intensive work, even in HD, as a two step process improves workflows unless you are writing to slow drives.
 
There are a number of reasons it's a bad idea to go directly to H.264 on a timeline for 4K master.

One reason may be that your graphics card is trying to do all the graphical operations from your timeline AND do hardware encoding of the 4K h.264 stream, and struggling to do it all at the same time. This is not so much an issue with the Video Card across the board, as it's ability to juggle multiple intensive tasks at the same time (hardware encoding AND 4K colour correction on GPU etc.) While it may be able to handle both tasks easily independently, as others have pointed out doing the whole procedure on card at the same time can create bottlenecks that makes the process fall over.

Approaching encoding 4K material as a two step process will result in smoother workflows. In fact, in general, approaching all encoding of any GPU intensive work, even in HD, as a two step process improves workflows unless you are writing to slow drives.


thank you craig!
i will change my workflow and from now on create a 4K master from either Cineform or Quicktime and then H.264 files from that.
will you then reccomend to not render these 4K masters out with aid from the GPU? but do it solely on the CPU?
 
I just upload prores files and let vimeo or what ever host service convert from there. Vimeo keeps the original files if you got a pro account so works as a bit of a master backup as well. Saved me a few times :).

Here internet speeds is not much of an issue so I upload 4k proress 422 in about realtime.
 
I just upload prores files and let vimeo or what ever host service convert from there. Vimeo keeps the original files if you got a pro account so works as a bit of a master backup as well. Saved me a few times :).

Here internet speeds is not much of an issue so I upload 4k proress 422 in about realtime.

Ahhh Björn...
I envy you. I moved from Denmark to Berlin and in Berlin fast internet just does not exist, but it sure did back in the North ;)
 
I've often solved my rendering issues by changing the rendering mode from GPU Acceleration to Software Only. This is tragically slow but it works. I'll second Brendan's advice too though, Cineform is the way to go
 
Back
Top