Render and Replace is Extremely Ineffecient
Given the prolific "GPU Render Error" bug affecting... most people, using "Render and Replace" on any AE-nested layers (something I use heavily) has become an important part of my workflow.
However, the "rendering" is... slow as ****. It doesn't use ANY system resources compared to actually rendering the file in AE or nesting the layer, rendering that nested sequence out, and bringing it back in - both of which are very inefficient approaches.
On any system I've used, CPU and GPU load stays extremely low and the render takes far longer than it would through other render methods.
This feature either needs to turn into a "background rendering" kind of scenario where you tell it to Render and Replace while you get to keep editing (currently it locks you out of the software while it crawls) or it needs to use your system resources as it should.
Jennifer Burton commented
Render and Replace has been a weird process for me. Some times it takes a couple seconds, other times, for the exact same clip, it'll take over 2 hours. I use render and replace when I have several dynamically linked sequences from an AE project, but its grossly unreliable