defining the play/render timings

[Ichthyostega]

• what are the play/render timings ?
• how to derive that information at the point when building a new PlayProcess

[Ichthyostega]

Meanwhile I've found out a lot regarding the first question.
The timings are a strategy and an abstracted frame grid; they expose an interface to determine the nominal time of a frame number and they provide a foundation for attaching this to real wall clock time (and actually performing this attachment is the purpose of the TimeAnchor). The point to stress here is the abstraction. While all this functionality is "basically" or "somehow" available in the Session/Timeline, we introduced the Timings record to be able to reason about playback and rendering without having to understand the inner workings of the session.

Thus the work to be done for this ticket is as follows

• find out how a Timings record is initially set up when a new playback connection is prepared. That is: how to connect to the session and extract the information necessary for driving the implementation of the timings record
• find how how a Timings record can act as constraint and can be combine with further timing constraints -- especially those provided by the OutputSlot (i.e. the limitations inherent for the given output sink). This second part of the task will be quite involved and it is sufficient just to come up with an initial draft how to solve this requirement.

[Undercover Agent]

Migration MasterTickets ⟼ Subtickets-plugin