Connecting to the Player

CS Trigger talks to http://127.0.0.1:9036, the local HTTP API of the CS Player.

CS Trigger must run on the same machine as the player it drives.

Starting up

On start the app asks the player for its downloaded ads and shows a spinner while it waits.

  • If the player answers, the list appears and the Frame box fills with the frames the player reported.

  • If it does not, the app shows Failed to get data with the reason underneath and a Try again button.

The app waits for you to press Try again.

The usual reason for that screen is that the player is not up yet; press Try again once it is running.

Choosing a frame

Trigger events are addressed to a frame, so every list in CS Trigger belongs to one frame.

A frame is an independently playing region of a screen. A single-zone screen has one frame; a video wall or a multi-sided city format has several, and each of them plays — and is triggered — separately.

The Frame box lists the frames the player reported. Selecting a different one reloads the list. On start the app selects the first frame, and it falls back to the first one again if the frame you had selected is missing from the player’s next answer.

Refreshing the list

The list is a snapshot of the player’s answer. It is re-requested from the player when you:

  • press Reload;

  • switch frames;

  • change the sort field or the order;

  • change Settings → Video or Settings → Campaign filter.

Content delivered to the player after the last refresh does not appear until one of these happens.