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

Let the games begin!

  • Thread starter
  • Moderator
  • #21
OK, had to throw in the towel and raise the white flag... for now.

Edit> too much info posted, have to cut back... But this sums up what I'm doing next.

As for me, I still need a dedicated Resolve box up and running. I'm going to order a new Mac Pro, probably tomorrow. And I'm going to bite the bullet and get the CUBIX GPU Pro 2 X16 with the 4 single-width slots.

As a side note, I learned something about Mac Pro systems today. You can in fact order them with dual 6-core 3.33GHz Xeon CPUs. You have to do it through their business sales division over the phone or in person at an Apple Store location. Pretty cool, if you want to pay the hefty price tag -- IIRC, another $800 or $1K over the 2.93GHz 6-core upgrade. Ouch. I'll pass on that.
 
I was hopping you would be the one to come up with a Solution to resolve the Resolve system hogging issue. I am no software guru or have any knowledge of the code in Resolve Mac, but I often wonder, why Smoke, PProcs5 and Speed-grade can grade in realtime using one Cuda card. they all do choke or slow down after about 15 effects have been added, but with Resolve it only takes 5 nodes to come to a crawl
 
why Smoke, PProcs5 and Speed-grade can grade in realtime using one Cuda card. they all do choke or slow down after about 15 effects have been added, but with Resolve it only takes 5 nodes to come to a crawl

Different architecture. What makes you think you will get 5 nodes in RT playback with 4K R3D raw files? Are you using parallel or serial nodes? Remember that sending video out through the Decklink card adds another bottleneck to the system. Most demos I've seen DaVinci do have always been with 1920x1080 files. In my testing, there were definite performance differences between ProResLT and ProResHQ, for example.

- Oliver
 
I was hopping you would be the one to come up with a Solution to resolve the Resolve system hogging issue. I am no software guru or have any knowledge of the code in Resolve Mac, but I often wonder, why Smoke, PProcs5 and Speed-grade can grade in realtime using one Cuda card. they all do choke or slow down after about 15 effects have been added, but with Resolve it only takes 5 nodes to come to a crawl

I've graded a few music videos and short films shot on RED 4K and 2K. What I do is grade on 4K quarter or 2K half. This looks good enough on the HD monitor, and I have had about 10-12 nodes before it started dropping frames. That's on a 2xQuad 2009 2.26GHz, 6GB RAM and GT120+GTX285 with a Decklink HD Extreme 3D and an eSATA RAID. I think that's pretty impressive, really..

Client doesn't know what's going on in regards of downscaling, and the image looks crisp. 10-12 nodes, tracked power windows, blurs.. real-time playback with sound.. What's there not to like about that, even though it's not full 4K playback? You'll be rendering from the 4K obviously...
 
Back
Top