Outro duration

[imaretic]

When using OGrafs in an NLE, it's important for the NLE to know how long a graphic takes to animate out. This ensures the graphic animates out precisely at the end of its timeline piece, for example, rendering the final frame of the outro on the last frame of the OGraf piece on the timeline.

Since a graphic can be in different states during playback, the stop duration may not always be the same.

Potential solution to this problem could be making the outro duration a function in the web component rather than a static property in the manifest file. The OGraf client could then, after setting scheduled actions, call method like getOutroDuration(), or the outro duration could be returned as part of the response to setActionsSchedule().

[didikunz]

After today's (2025-10-29) discussion I try to summarize what I think would make sense in my opinion.

Add a property to the manifest with the duration of the outro animation (stopAction) in milliseconds and let it be -1 if it's unknown and varies that much, that it does not make sense to default it to anything (what should seldom be the case).

outroDuration: 500,

[nytamin]

Notes from Working Group meeting 2025-10-29:

We think that this is not limited to outros, as the animation between steps or other actions might be useful to know.
It is also relevant both for realtime and non-realtime applications.

We propose that a definition is added to the manifest that describes animation-times for different types of steps (such as intro/play, steps & outro/stop). If the animation time for a certain step is dynamic/unknown, it can be defined as "-1".
It is not a perfect solution, but having a statically defined animation-time allows for NLE's and automation software to predictably adjust action times.