Nodes: Sequence

Sequence:ActionOn allows Actions (Strings) to be output when a certain input is received.

The 1st input is compared to the 3rd input.

If they match the string defined by the 2nd input is sent out on the 1st output

and a Bang is sent out of the 2nd output.

Sequence:Announcer gives you some Meta information about Sequences,

on this machine and advertised ones in the same Network

Sequence:BroadcastScheduler is the node-graph interface to a show-control

broadcast scheduler entity (created in the Broadcast Scheduler window). It

forwards its pin inputs to the entity and emits the entity's state on its outputs.

Sequence:FrameServer allows a Sequence to fluently follow a

Timecode or Nomalized Target position, the progress gets faster

if the Target is further away and slower the closer it gets.

Sequence:GetSequence gives you a list of all available Sequences in the current Project.

It also allows you to convert between Sequence index, ResourceID and Name.

Sequence:GetSequenceStatus provides Sequence information as JSON or Pack.

Sequence:GetStepper resolves a show-control stepper entity (by dropdown,

resource id or name) and emits its resource id and name - the stepper

counterpart of GetSequence.

Sequence:NMux converts an input Instance into one or more actions

that can be executed by the Sequence Node.

Sequence:Observer shows all advertised Sequences in the Network

and makes a connected Sequence follow everything the selected one does.

Sequence:ObserverRegistry is a Node used in the System Graph to enable the Advertise/Observer logic

used to synchronize Sequences between multiple Videoservers in a Cluster, and with Conductor Software.

It can not really provide worth outside of that.

Asset:Properties

Sequence:Sequence references and controls a Sequence

created in the Sequencer window.

Sequence:SequenceCommander provides you with many commands

ready to use for controlling any Sequence you have in your Project

Sequence:Stepper is a powerful tool that allows you to control/automate multiple Sequences,

Transitions between them and can even be expanded with other nodes.

After adding one or more Sequences via the Add sequences you can use the Grid to add

Steps that will run through from left to right.

If the Box for a Sequence is active in the Step it will be started, if not it will be stopped

Sequence:StepperCommander gives you access to many commands to control a conneced

Sequence:Stepper node via the string input or UDP

Sequence:StepperFeedback converts the information a connected

Sequence:Stepper provides into easily parseable Strings for Feedback

to a central processing unit.