Expected rendering performance.

[Timo Teravainen]

[Michael Jordan] “I can confirm it does. And it is glorious. ;)”

Halleluyah!

Is the prores rendering working on the Lite version also?

[Lauri Laidna]

Yes. All the grading, noise reduction etc is done by the GPU(s). Feeding the frames to Resolve including codec decoding is done by CPU. It depends on the task, what becomes your system’s bottleneck.

The good thing is that Resolve uses multi-core CPUs efficiently and has good performance on Windows.

The priority should be to be able to work realtime and with 1080p this isn’t a problem. And do you really need more than 2x realtime final render out performance? 🙂

[Andrew Smith]

Whats the ‘best way to test nvidia card performance – i want to compare a 285 vs. 470 to see how it stacks up?? Like how do i know how fast its rendering out – is there an app to test nvidia card performance?

[Dmitry Kitsov]

Well, this is my problem exactly. I wish I could get out realime ProRes render, but on me Windows 7 workstation I only get 7 fps when rendering ProRes with just a simple primary grade (no blooms or blurs or NR) on a very powerful system (24Gb, Xeon 5690 with 12 cores, 3GPUs – 1 GTX285 and 2x GTX 580) This is the same speed I get rendering out the same clip in ProRes on a 2009 Dual Core 15-inch MacBook pro.
Is this a beta bug (v3), you think?
I hope someone running a Windows beta could verify this for me. So I can see if it is a problem on my side or problem with a beta release in general.
When rendering 10-bit DNxHD mxf I get 20fps, when rendering 10bit Cineform I get 24 fps.

[Jake Blackstone]

Damn!
I haven’t had a chance to test it, but if it is true, that is impressive!!!
Now it finally makes sense to move Resolve to Windows. No more inferior GPUs, no more restrictive Mac hardware and no more Hackintosh to write Prores.
Happy Days:-)

[Mike Most]

If you need ProRes4444 encoding support – which is not likely, but possible – I would check to see whether this is part of the Resolve implementation. My guess is that they’re using the open source ffmpeg code, which can currently decode 4444 but not encode.

What you consider “impressive”, I consider a logical move now that an open source version of the codec is available, and other vendors have already integrated it. My question to Rohit would be whether this will also be integrated into the Linux release, which is far more significant in my world….

[Dmitry Kitsov]

Guys and girls, I would like it if you were not to stray of the original topic.
I would simply like it if people would share the speed that they are able to render for output (not just grading preview) ProRes in DaVinci Resolve 8.2 Windows Beta 3 as well as the hardware setup they are running.
Thank you.

[Lauri Laidna]

Start the rendering and then check cpu, gpu and hdd usage – and you’ll see where the slowdown is coming from.

For GPU usage download small free program called GPU-Z. You can open multiple instances of it to see all GPU-s side-by-side. Check for MEM and GPU USAGE. And for CPU/Disk use Windows’ own Task Manager and Resource Monitor.

I hope you have at least 2-way RAID0 setup. Also try taking media from one drive and rendering to another.

Hope these will help. I have no experience with ProRes on PC.

[Colin Travers]

IS there a mac version of GPU testing software? i want to test my 285 and compare with the 470 which is on the way!

DaVinci 8.1.1 OSX 10.6.8
MacPro 12-core 5,1 2.66 Ghz
32GB RAM (x4 owc 8gb sticks)
RAID0 8TB
Nvidia GT120/GTX285
BMD Extreme3D
HDlink3D DisplayPort
Dreamcolor/Panny VT25
Tangent Wave / Wacom

Drivers:
Nvidia Cuda 4.0.50
DecklinkExtreme3D 8.6
HDLink3D DisplayPort 3.5.1

[Dmitry Kitsov]

Lauri,
When I use ProRes 1080p4444 as a source and ProRes as an output for a simple grade I get 7, 7.5 fps. While rendering CPU utilization is about 10% percent with the peaks of 25%.
GPUs (image) utilized 2% to 4% each.
I was rendering from a 4-disk RAID-0 external (160MBps) to a 4-disk RAID-0 internal (450 MBps) which is well below the needed bandwidth for the ProRes files.
So it makes me think that perhaps ProRes implementation they have is not multithreaded. Sigh.