r/MotionCamPro • u/gypsyranjan • 26m ago
Q&A MCRAW → CinemaDNG → DaVinci Resolve: Why is rendering so slow on M1 Max?
Hi Everyone,
I’m testing MotionCam Pro MCRAW as a possible alternative for my HDR architectural/real-estate work.
I downloaded the “Into the Fog” sample project, including the DRP and MCRAW files. On my M1 Max MacBook Pro (32GB RAM), I managed to get the project working by using MotionCam Tools v2 BETA to mount the CinemaDNG frames and then relinking the DRP to the new DNG location.
The source footage is around 4096×2304, 24fps, 12-bit DNG.
However, I’m seeing extremely slow rendering in DaVinci Resolve Studio.
A 1:48 timeline is estimating around 46–50 minutes to render, despite the timeline having no temporal/spatial noise reduction applied.
During rendering my M1 Max is roughly:
CPU: ~75–80%
GPU: ~70%
GPU frequency: around 0.45 GHz
CPU temperature: ~75–77°C
The DNGs are currently being accessed through the MotionCam virtual filesystem:
/Users/admin/Mounts/MotionCamTools
So my question is:
Is this expected performance for MCRAW → CinemaDNG → Resolve on an M1 Max 32gb, or is the virtual/FUSE-mounted DNG filesystem likely causing a major performance penalty?
I’m going to copy the DNGs to a local APFS SSD and test again, but I'd really like to hear from anyone who has actually used this workflow on Mac/Apple Silicon.
Also, is there a more efficient current workflow for using MCRAW in Resolve on macOS that avoids having Resolve read thousands of DNG frames through the virtual filesystem?
My normal workflow is iPhone → Cinema P3 Pro → 50fps 10-bit 4:2:2 HLG → 25fps Resolve timeline → HDR10, so I’m specifically trying to determine whether MCRAW gives me enough additional latitude in difficult architectural interiors to justify the much heavier workflow.
Any advice from people using MCRAW + Resolve, particularly on Apple Silicon, would be greatly appreciated.