Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Big Iron Shootout: MacPro vs Dell and HP

  • Bret Williams

    August 11, 2012 at 1:25 am

    Yeah I can’t think of an editorial app that doesn’t utilize multi processors and GPU. Sans FCP legacy. Motion, FCP x, compressor, after effects, resolve, premiere, photoshop, and I’d figure Avid.

    The iMac is now a horrible platform for Adobe. The GPU isn’t supported for ray tracing in AE, and it’s not supported in Premiere without a hack. However I’ve found that the hack actually slows performance and eventually causes a freeze.

  • Oliver Peters

    August 11, 2012 at 1:38 am

    [Bret Williams] “Yeah I can’t think of an editorial app that doesn’t utilize multi processors and GPU. Sans FCP legacy. Motion, FCP x, compressor, after effects, resolve, premiere, photoshop, and I’d figure Avid. “

    Actually NLEs don’t make good use of multiprocessors. They may use all the cores in a single processor, but they don’t make good use of more than one processor. That’s why a faster 4-core will often outperform a slower 8-core. Avid actually does a good job of processor utilization and in the case of Photoshop, it does lean on the GPU more than ever. Motion is big on pushing the GPU.

    It’s also a matter of when and where this performance is applied. For example, in X, the machine doesn’t kick in full during renders, but it does when rendering upon export. One of the reasons to avoid rendering while working, unless you really need to. It’s all about optimization rather than brute horsepower – although a bit more use of brute horsepower would be welcomed!

    Another example. People keep saying that Resolve has to have a second GPU. That’s flat incorrect. There is a benefit, but it’s hardly essential. Yesterday on a MP 12-core with an ATI 5870 and 32GB RAM, I was working on Resolve Lite. Playback was real-time (24fps) but rendering was actually at about 50fps! Not too bad at all. Seems like there, Resolve actually uses the power.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Michael Gissing

    August 11, 2012 at 2:18 am

    Oliver, what codec & frame size? Adding a second powerful but cheap NVIDIA GPU to a Win Resolve setup will surely pay for itself if working with challenging footage like R3D etc.

    The fact that Resolve is pretty good with a single ATI says much about their software.

  • Oliver Peters

    August 11, 2012 at 2:35 pm

    [Michael Gissing] “Oliver, what codec & frame size?”

    Typically I’m working in some flavor of ProRes at 1920×1080 at 23.98fps. I think the example I mentioned was 25fps and ProResLT.

    [Michael Gissing] “Adding a second powerful but cheap NVIDIA GPU to a Win Resolve setup will surely pay for itself if working with challenging footage like R3D etc.”

    True, but it can cause other issues if this workstation is being used for more than just DaVinci. Not sure on Win machines, as my work is all on Macs. BTW – I never work natively in R3D. I feel it’s a very inefficient approach for anything except down and dirty short-form jobs. I convert to ProRes using Redcine-X Pro first. Resolve Lite will take larger frames than HD, but the max output is 1920×1080.

    Here’s a review I did last year when R8 was released, with some performance tests that I did at the time:

    https://digitalfilms.wordpress.com/2012/01/20/davinci-resolve-8/

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Gary Huff

    August 11, 2012 at 5:39 pm

    [Oliver Peters] “Actually NLEs don’t make good use of multiprocessors. They may use all the cores in a single processor, but they don’t make good use of more than one processor. That’s why a faster 4-core will often outperform a slower 8-core.”

    Not from my research. Premiere CS6 will use whatever you can provide, including multiple processors.

  • Oliver Peters

    August 11, 2012 at 5:52 pm

    [Gary Huff] “Premiere CS6 will use whatever you can provide, including multiple processors.”

    You’re probably right. I haven’t a lot of specific testing, but PProCS6 definitely performs better with plug-ins and has faster renders than X on the same machine.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Gary Huff

    August 11, 2012 at 7:09 pm

    [Oliver Peters] “You’re probably right. I haven’t a lot of specific testing, but PProCS6 definitely performs better with plug-ins and has faster renders than X on the same machine.”

    Too late. Jerry Hofmann has already proclaimed X to be the fastest NLE in the entire woild!

  • Chris Harlan

    August 11, 2012 at 8:50 pm

    [Gary Huff] “Too late. Jerry Hofmann has already proclaimed X to be the fastest NLE in the entire woild!

    Period.

  • Michael Gissing

    August 11, 2012 at 11:20 pm

    Thanks Oliver. The reason I mentioned a Win machine is that up to date grunty GPUs are cheap compared with Mac needing older more expensive NVIDIA cards. I have the same issue with my MacPro already running an ATI card for FCP. Resolve Lite was working on that machine and I mostly work in ProRes422 for broadcast so 1920 x 1080 is fine.

    However the logical thing for me is to quarantine the Mac with FCP Legend still operational and start again with Resolve & CS6 on a Win box. So aside from benchmarks, issues of running software that can take advantage of NVIDIA CUDA makes me confident that CS6 and Resolve can live together. My other issue is the Mac has a Kona card and although I was able to add a Decklink to the MacPro it makes sense to not try to run too many apps and cards on one machine.

    On using R3D to grade, well I just love the goodness of being able to get in and adjust ISO and colour temp. Most RED work I do is short drama and we always relink to the R3D in Color to grade. I hope to do the same in Resolve as it gives so much more grade latitude and control.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy