Topic 1 of 5
#Choose an appropriate grid
Use the smallest grid that shows the required information clearly. Larger grids reduce detail and can create unnecessary remote-view load.
| Need | Suggested tile |
|---|---|
| Confirm visible playback | Liveview |
| Compare local times | Clock |
| Watch overall fleet state | Fleet health |
| Track one important screen | Large Liveview tile in a small grid |
Topic 2 of 5
#Build a layout
Click-by-clickOpen a saved monitoring wall
Multiview→Preset
- 1Preset
Choose the agreed site or event name. Do not edit the name.
- 2Selected / running
Check how many sources are configured and how many are already running.
- 3Start all
Press once only if the whole preset is required. Otherwise start one tile.
- 4Tiles
Wait for each tile to become ready or show a useful error.
- 5Stop all
Stop the views when monitoring is finished.

- 1Choose a grid size.
- 2Select a tile and assign its type.
- 3For player tiles, choose the player by its verified label.
- 4Repeat only for the tiles needed by this monitoring purpose.
- 5Give the layout a clear shared name and save it.
Topic 3 of 5
#Operate the grid
- Wait for tiles to establish before refreshing the whole page.
- Use tile status messages to identify one failed source.
- Open the player detail for investigation rather than troubleshooting inside the grid.
- Stop or leave the grid when continuous monitoring is no longer needed.
Topic 5 of 5
#If the grid becomes slow
- 1Reduce the number of continuous Liveview tiles.
- 2Replace visual tiles with clock or fleet-health tiles where possible.
- 3Check whether individual players are also slow in their detail views.
- 4Escalate a repeated site-wide issue with the layout name and time.