Replies – Forums – Brian Carrigg

Forum Replies Created

Brian Carrigg
October 24, 2014 at 12:12 am in reply to: h264 encoding takes way longer than it should

I’ll definitely keep the pci accelerator option in mind. We won’t be getting rid of our current mac pro and it might not be bad to distribute the workload over both machines. I can let the old MP encode the h264 for one video and start the next video on the new machine.

I can’t help but feel there’s some underlying issue though. The fact that single pass encoding failed, and that I was able to transcode the same video in 30 minutes on a Windows machine tells me that something is wrong.
Brian Carrigg
October 23, 2014 at 8:30 pm in reply to: h264 encoding takes way longer than it should

if it’s really that simple, then this problem will be solved soon. As I mentioned we have the new Mac Pro on the way,so that will definitely speed things up. However, 70 hours for a 30 minute video seems way beyond the realm of normal processing speed. It seems that there is something else going on, as the processor never reaches full load even with two instances of compressor running and a third instance running on a Mac Mini in a cluster.
Brian Carrigg
September 23, 2014 at 4:16 pm in reply to: What types of corrections use the GPU to render and which use the CPU?

I avoid noise reduction, since that eats up resources in a hurry, but I was wondering about other functions. Like keying, or curves.

I have checked all my drive speeds, and there is no bottleneck there. Its a single video stream, from one SSD to another.

Playback happens in real time, strangely enough. I went through all of the optimizations in the Resolve manual for that though. So that may not give any indication of actual render performance.
Brian Carrigg
September 23, 2014 at 2:58 pm in reply to: What types of corrections use the GPU to render and which use the CPU?

What could be causing the huge disparity in render times for some of my projects then? They’re all just prores to prores workflows.