Hi David,
The "Render in Place" command allows you to pre-compute on a per-clip basis all of the effects you have applied to a piece of footage. This allows the rest of your editing timeline to work at real-time performance so you don't have any slowdowns caused by the system bogging down on an individual effect that isn't playing back at the native timeline FPS rate. This approach can be useful if you have things like OFX plugins, video denoisers, or other enhancements applied on specific footage, while the rest of your time timeline is mostly "cuts only" edits that run at full speed.
* * *
The timeline playing back at 1 FPS does seem a bit lower than anticipated. There are several possible sources that could lead to that. Off the top of my head the two most common issues would likely be:
Do you have a dual monitor setup that has a monitor connected to an internal integrated GPU chip on your system? This could cause Resolve to try and use that onboard graphics chipset for the GPU rendering operation.
If you open the Resolve preferences and navigate to the "System > Memory and GPU" section what do you see for the GPU configuration? Is anything else listed there besides your RTX 3060 GPU? The GPU configuration section in the preferences does have the option of toggling the compute from CUDA to OpenGL (or Metal on macOS) using the "GPU processing mode" control.
Do you have any background GPU based workloads that might be using any of the GPU compute capabilities? If you use a tool like "
GPU-Z" does it show much GPU activity on your system when playing footage in Resolve, and also when the system is sitting inactive?
Regards,
Andrew