Region.Position versus Ruler.StartTime

Teetow wrote on 6/21/2007, 9:39 AM
I've written my own Batch Renderer, which basically uses regions and track names to export different parts of the project. Among other things, this renderer includes a preview window where you can check sample rate, target filename and various other things.

Usually, our projects are default projects; the Ruler StartTime is 0, and is set to show just "Time". We have, however, come across occasions where the rendered regions are incorrect, and I discovered that a Region.Position seems to always show the "true" time, regardless of what the Ruler.StartTime might be set at.

My question is: Is this by design? Wouldn't it make sense to have the Region.Position value reflect the actual timeline, including any offset? I've added a workaround, but it still feels a bit clunky.

Comments

SonyPJM wrote on 8/8/2007, 8:57 AM
Inconsistencies when the ruler start time is not zero stem from
oversimplification of the Timecode class and false assumptions
elsewhere. We hope to address these issues in an upcoming release.

One workaround for now is to set the ruler start time to zero at the
beginning of the script and reset it at the end.