I’m trying to set up a workflow where a Rhino camera animation can be compared against an early previsualization pass generated outside Rhino, and I’d like input from anyone who has tackled something similar.
Context: I have a Named Views sequence that defines a camera path through a model, and I export a rendered still sequence from that path. Separately, I’ve been experimenting with Muse Video, which is a prompt-led external browser tool for describing a subject, motion, camera treatment, and framing in text form. It’s not a Rhino plugin or integration, and the underlying model is explicitly preview-stage, so I’m only using it as a loose visual reference, not a finished output.
My actual questions:
Camera data
When exporting Named Views for reuse elsewhere, is there a reliable way to log target point, lens length, and rotation per frame without manually reading the Properties panel each time? A CSV or text log per keyframe would be ideal.
Frame sequence export
Is there a preferred approach for exporting a still sequence that keeps consistent frame numbering and resolution so the timing lines up cleanly with an external reference clip, even a rough one?
Scale and timing
If the external reference has no real-world scale reference, how do you usually anchor comparisons - fixed focal length, matched frame count, or something else?
I’m not expecting a plugin-level integration here, just trying to keep my Rhino export disciplined enough that any external comparison, however preliminary, stays meaningful rather than approximate. Curious how others structure this without over-engineering it.