event_state

SCTE 35 Part 2

Enumerated values

Value	Dec	Name	Description
0x00	0	start	The event begins at the point indicated by the parent time_signal, which may carry a PTS or signal immediate timing. Any cueing or arming of a downstream splice should happen before that point.
0x01	1	active	The event is in progress. The elapsed and remain times are normally updated as it runs.
0x02	2	paused	The event is paused. It can enter this state from start or active, and can later move to active or resume.
0x03	3	resume	A signal to re-evaluate the event and decide whether service delivery should change.
0x04	4	fetch	Announces a future event so a downstream process can acquire it early, for example fetching an ad decision ahead of time for just-in-time transcoding and packaging. Standards note SCTE 35 Part 2's zero-elapsed rule and its fetch example are in tension; for a fetch (a future event) elapsed is typically the sentinel 0xFFFFFFFFFF because the event has not started.
0x05-0xFF		Reserved	Reserved for future use. Not currently assigned a meaning. Standards note SCTE 35 Part 2 p.51 mentions an 'end' event_state in prose that is absent from Table 12. We treat Table 12 as authoritative (there is no 'end' state); an event ends when its remain time reaches zero. Ending an event by simply omitting further descriptors appears only in an example, not as a general state-transition rule.