NEW workstation perfect playback dreadfull render....

[Jaimy Soares]

Hi guys,

I'm pulling out my hairs at the moment.

I just build a new windows workstation:
2x Intel Xeon E5‐2620 V2

2x MSI Geforce GTX770 2GB (SLI)

64GB Kingston ValueRAM KVR16R11S4/8I

I came from a mid 2010 imac 27', world of difference inside of premiere, 5K smooth playback at 1/2, but when it comes to rendering there is a twist. Putting out a 4K 2:1 h.264 at 25/50mbps from 5K 2:1 files a three minute timelines takes about 3hours! to export. Is this normal? What is going wrong? 5K 2:1 on a 1080P timeline to MPEG2 HD takes 1hour 20minutes.

If fiddled a bit with adobe to let them recognize the GTX 770, because it didn't in the beginning. But now I'm wondering if he uses the cards to the fullest capabilities..

The nvidia driver is 337.88

Hope someonde can help!
I thank you so much already!

 

[Jaimy Soares]

Davinci lite renders a basic grade+lut same material in 15min...

 

[Brian Merlen]

how much ram is being addressed and how fast is you media storage (and renders and where do you output to, as many details as possible helps)

could be ram or storage issue is my guess... in an ideal setup adobe has separate disks for renders, media, and export location, that alone speeds stuff up a lot...

and i know on mac it lets me specify how much ram i make available to it (I'm on cs5 not CC)

 

[Jaimy Soares]

Output to a SSD, media storage is a 5200rpm, and the renders a different disk also 5200 rpm, he is using about 52% of the ram.

 

[Brian Merlen]

try putting all on the SSD and report back.. 5200rpm single discs (or 7200rpm if you meant that and had a typo) aren't particularly fast compared to raid 5 solutions. might be an I/O issue...do you have any big fast RAIDs to test as well? if there are still problems let me know, and id probably suggest trying a titan GPU if there is still issues and its not I/O. I heard good things about Titans (or the new version)

 

[Jaimy Soares]

Strange I read out my GPU's they are not working while rendering so its all on the cpu's, that's the problem I think! Will try a clean adobe instal

 

[Jaimy Soares]

In DaVinci while playing and rendering I can see a 50 to 80% GPU use, in premiere none. But premiere says he's seeying the card. weird

 

[Jaimy Soares]

Update: In premiere and aftereffects wile playing back in the timeline I see GPU usage, so he recognizes the cards, while exporting there is no use. Probably not the drivers, the same while encoding in AME. Maybe resolve 11 then....?

 

[Rob Trombino]

Jamie,
Premiere doesn't use the GPU for rendering. Only the CPU. Also, it doesn't use SLI either. The 770 is a great card but it really needs to be at least a 4gb. Resolve likes that too. I believe your main bottle neck is your storage setup. Everything needs to be on separate drives (i.e. – OS, playback/playout, scratch, render).

 

[Brad Allen]

Premiere doesn't use the GPU for rendering. Only the CPU. Also, it doesn't use SLI either.

This isn't correct sorry Rob. Premiere certainly uses GPU acceleration on export. It's part of the reason AME has the option to toggle between Software (CPU) and OpenCL/CUDA acceleration.

Whilst it's technically true that Premiere doesn't use SLI (frame sequencing and acceleration for gaming), it can still utilise multiple GPU's when exporting - see below.

Finally, for customers using configurations containing multiple GPUs, Premiere Pro CC can use all of them during export (but not during playback) so customers who require the fastest possible encode times will be able to leverage all the GPUs they own.

I'm unsure why you're having such bad luck Jaimy. Are you able to test doing an encode via AME selecting CUDA acceleration for one and software for the other? Would be interesting to compare the times for encode.

 

[Rob Trombino]

Hi Brad.

I can't find it listed anywhere that premiere uses the gpu for final codec rendering on export. The only thing I found is that it will use the gpu on some effects at final render but not the actual codec rendering. But please correct me if I'm wrong on that.

 

[Stacey Spears]

Jaime, you should try and run as two steps to see if the bottlekneck is the export or the encode. Export to uncompressed and then encode into H.264.

 

[Jaimy Soares]

Will try that, Found out btw if I do a dpx export in davinci, takes about 15min instead of 3hours, then import in aftereffect and then fling the sequence in AME it takes about 20min to encode, a little work around for now, with a couple of big deadlines. Will do a new Premiere install when the rush is over and some new tests.

 

[Brian Merlen]

i still think I/O on your discs should be looked into...cuz thats a big issue these days in general, the best workstations in the world won't perform optimally if you can't feed it data fast enough/output fast enough. For instance SNS Evo (a big array) can do 4k playback over normal cat5e ports, mainly because its got a ton of discs behind it pushing the stuff... I/O could very well be something to look into..

 

[Mike Harrington]

not only are GPU's used for rendering (scaling, h264 encoding ect) but the primary acceleration is in the new SDK with r3d debayering....
I get faster performance from 2-3 gpu's then from a rocket....do you have CUDA acceleration enabled

there is obviously a bottleneck somewhere, hope it works out...but this is definitely not typical

 

[Brad Allen]

Hi Brad.

I can't find it listed anywhere that premiere uses the gpu for final codec rendering on export. The only thing I found is that it will use the gpu on some effects at final render but not the actual codec rendering. But please correct me if I'm wrong on that.

Hi Rob,

You may be correct that the codec itself may not be accelerated via the GPU (I'm actually not sure but suspect most codecs are probably all CPU encoded) but there is still work that the GPU does before it's passed off for compression via a codec. Especially in the case of R3D's now, the GPU can assist in debayering and scaling operations (ie 5K to 4K or 5K to 2K) that would otherwise be very heavy tasks for the CPU. It will also continue to process any GPU accelerated effects which were used on the timeline being exported

 

[Jaimy Soares]

Yes it's anabled, did an export for a preview in premiere, render in out and then a match sequence setting export, 4:28min timline, done in 8 minutes, 4min in out render, 4 min match sequense settings.
But still the same if I use a codec and then render directly. It's so strange, found 1 thread on the internet with the same problem but no solution.