I was tinkering with Batch Rendering and would love to have the option to set a START and END 'camera' position, and have the 'camera' evenly navigate between the two points.
This could be accomplished as follows:
1) In batch render menu, you would have an optional check box for START and END frame position
2) once checked, you could manually set in the viewport what you want the start view to be for the 1st frame of the sequence, and click 'RECORD START POSITION' button, which would record the position values into the Batch Rendering menu as the START position.
3) likewise, then nav to end view in viewport and click 'RECORD END POSITION' button. (You could also allow user to export the position as a general 'position' data file or something...)
4) then, have a mathematical transition take place via a formula which would divide the difference from START to END's parameters by the # of frames, where each frame is evenly & incrementally moved from START position to END position. That way, you could have smooth transition of panning or zooming as frames are batch rendered, as opposed to a fixed camera position.
I know you can Alembically import another application's camera movements into Batch Render via connection to the render target, but I want to bypass that part and do it all in Octane Standalone. Would be interested to import the objects' animations and movements from the alembic file, but then handle the camerawork in the standalone via batch rendering.
And if I want, I could, say with a render of 200 frames, have 1-100 be done separately from 101-200, that way I could create 2 'cameras'. And if I had a ping ponging conversation back and forth, I could import again the position file I want to START and END with.
Come on....
COME OOOOONNNNNN....!