One t runs the whole animation, but the camera, the section cut and the arrows should not all start and stop together. Event Timeline splits t into events, each with its own 0 to 1.
Events
An event is a range of the input t, such as 0.2 to 0.6. Before the range its output is 0, inside it rises from 0 to 1, and after it it stays at 1. Drag the slider:
Three events. The second starts before the first has finished, so the two overlap.
On the canvas, Event Timeline draws its events as bars. Drag a bar to move it, drag its ends to resize it, and use + and − to add or remove events; each event gets its own output, event 1, event 2… Hold Shift while dragging to turn off snapping.
Easing
Right-click the component to pick the easing for all its events: Linear, Ease In, Ease Out or Ease In-Out. Ease In-Out is the one to use for camera moves, because the camera starts and stops gently. The slider below drives the same events with Ease In-Out; compare the numbers with the diagram above.
The right-click menu has two more settings:
Outside Event: Hold outputs 0 before the event and 1 after it. Null Outside outputs nothing, which hides geometry that should only appear during its event.
Snap: snaps the bars to 0.1 s, 0.5 s, 1 s or one frame while you drag. It needs duration (the animation length in seconds), and fps for frame snapping. Both are only used to display and snap the bars; they do not change the outputs.
Nesting
Any event output is itself a 0 to 1, so it can feed another Event Timeline. Use this to split one part of the animation further, for example three arrows that appear one after another inside the "arrows" event. The eventSeconds output gives the length of each event in seconds, which you can wire into the nested timeline's duration so its snapping stays in seconds.
Preview in real time
A slider shows one moment at a time. To watch the animation play at its real speed, feed the t hub from Duration Counter. Set totalDuration to the same length as View Capture Driver, click Play, and the counter runs from 0 to 1 in that many seconds. Pause holds it, Reset goes back to the start.
A heavy definition may not keep up with 30 fps. The counter then skips values, so the preview looks choppier than the export will be. The exported frames are always complete, because View Capture Driver waits for every frame.