Resolve 16b1 doesn't use RR-X on iMac Pro OSX 10.14.3

Resolve 16b1 is not using my RR-X for decode. When I use Red Cine-X Pro, I can clearly see that CPU usage (800%) and GPU history (25%), plus disk buffering, is able to run 24fps all day with 8K footage at 1/4 debayer resolution. When I raise the quality level to 1/2 resolution, the CPU utilization rises to over 900% (my 10-core CPU suggests that 1000% is max limit), the GPU utilization rises somewhat, and RCX cannot keep up.

With Resolve 16b1, the GPU history shows the GPU (Vega 64 with 16GB VRAM) completely pegged at 100% and CPU utilization below 200%. It plays back at about 14 fps +/- 1 fps. It would be nice if the next beta of Resolve can remember how to do performance with an RR-X installed!

Edit: I fixed my empty /etc/hosts file and I no longer get the error message about failing to initialize DPDecoder processes.

[Dwaine Maggart]

The Red Rocket-X cannot debayer that footage. So it has to be done in GPU space.

But the Rocket-X can and should be decompressing the footage, and that should not be putting a load on the CPUs. Your comment about CPU utilization being so high with RedCineX makes no sense, unless the Rocket-X isn't doing anything.

RR-X cannot debayer Helium nor Monstro clips, only decode. And possibly, though I don't know, the deciding step is equally heavy despite debayer resolution.

In RCX I definitely see fps performance changes as I change the debayer resolution. In 16b1 I see no fps difference between full debayer and 1/16th. I do see a huge quality difference, however.

In any case 16b1 is unable to play 8K R3D media at 23.976 at any debayer resolution. RCX works at 1/4, and flies at 1/8 and 1/16.

I don't remember for sure whether I restarted 16b1 since I submitted this report, but I went back to try to re-baseline my results before attempting to disable the RR-X card so I could do a true A/B comparison. And as of 5 minutes ago, 16b1 is ripping through R3D footage as expected. I don't know what caused the miserable performance reported the other day. Will update if I see another performance drop.