-
Bug-report/Feature-request: Rendering Secondaries with handles
I’m not sure whether to file this as a bug-report or as a feature-request, but I’m finding that rendering clips with handles is only useful if you don’t have any secondaries enabled on your clips. Once you’ve added a Window or qualifier, if you try and render out clips from an FCP XML timeline import, the secondary corrections will “pop” off, or in the case of Windows, they’ll reset themselves to a different position when rendering through the handles.
I obviously don’t expect Resolve to read my mind and auto/track & animate Windows past the extents of the original edit points, but it would be nice if it could just continue whatever secondary setting was in effect at the point where the handles begin to render. So, for example, if I have a tracked Window on a clip, the movement of the Window would just stop at the point where it no longer has any tracking data, yet the color correction setting within that window would remain the same. At least this way, there wouldn’t be an obvious jump in any secondaries when you render the clip with handles.
In the case of Windows, an even better option would be to auto-interpolate the motion of the window past the last tracking keyframe, so if you just have a Window tracked to a simple camera pan, the Window would continue to move in the same direction and speed of the last point of the tracking data. If you’re familiar with Shake, it has an animation-curve editor function called “KeepSlope” which does exactly this (see this screengrab: https://img.skitch.com/20111129-myid1wmm59xqj7fpyd7uxnpx38.png), and is designed to continue tracked RotoShapes off-screen without having to actually generate the tracking data yourself.
But really, I’d just be happy if Resolve would just not snap Secondaries off when rendering with handles.