Define the relationship between the pictures
Several screens do not necessarily require several independent playback machines. If they show the same picture, a suitable distribution arrangement may deliver one source to multiple destinations. Different pictures need independent content paths or a system that divides a larger canvas into outputs. A scene continuing across screens also needs a defined timing relationship.
Write down the audience result before discussing ports. “Three screens” is incomplete. “Three separate product stories” and “one animation moving from the left screen to the right” describe very different requirements, even with identical display hardware.
Three common arrangements
| Audience result | Content arrangement | What needs testing |
|---|---|---|
| The same picture in several places | One programme distributed to multiple screens | Format compatibility, image treatment and sound at each destination |
| Different information at each position | Independent outputs or independent player jobs | Correct content, orientation, update method and restart behaviour |
| One scene across several screens | A mapped canvas or coordinated media segments | Spatial alignment, matching timing, loop boundaries and recovery |
| Different pictures changing on one cue | A coordinated state change with defined content per screen | What “together” means for the creative effect and how each destination responds |
A splitter repeats a signal; it does not independently choose a different film for each screen. Conversely, multiple outputs do not by themselves establish the required synchronisation. Confirm both the content routing and the method used to coordinate it.
Be precise about “in sync”
Starting on one command, staying on corresponding video frames and drawing those frames at coordinated output timing are different aspects of synchronisation. BrightSign's technical documentation distinguishes these mechanisms and specifies a supported network and player arrangement. It is a useful reminder to ask for the chosen system's actual method, rather than assume that clicking Play on several machines is enough.
The viewer sees the entire chain, including processing inside each display. Ask for the visible result to be tested after the actual screens are configured. If screens use different processing settings or products, the technical team should assess whether that affects the intended effect. A rehearsal on three nearby computer windows cannot confirm the final room result.
Hypothetical example: a three-screen panorama
Assume three landscape displays, each assigned a 1920 × 1080 image, are arranged side by side. For this simplified example, ignore bezel and physical-gap compensation. The combined content canvas is 5760 × 1080 pixels. One way to specify its regions is:
| Destination | Region on the canvas | Assigned picture size |
|---|---|---|
| Left screen | Starts at x = 0, y = 0 | 1920 × 1080 |
| Centre screen | Starts at x = 1920, y = 0 | 1920 × 1080 |
| Right screen | Starts at x = 3840, y = 0 | 1920 × 1080 |
This map describes the content, not proof that a particular laptop can output or play it. The team could evaluate a capable multi-output system or coordinated players with prepared segments. BrightSign's multi-output documentation demonstrates that output position, resolution and rotation are explicit configuration choices on supported hardware.
Suppose the animation contains a moving line that crosses both joins. Use that moment as a rehearsal test, then watch several loop boundaries. Next, test the agreed recovery procedure after one destination restarts. Confirm whether the returning screen rejoins the current scene, waits for a common restart or requires operator action.
Keep audio and content changes deliberate
Specify where the soundtrack plays. Three local screen speakers reproducing a shared soundtrack may not be the intended listening experience. Tell the audio team whether the screens form one audience zone or separate stations, and have them plan the corresponding sound path.
For updates, maintain one approved package listing the files and destination of each. Replacing only one segment of a panorama can create mismatched duration or content, even if the file opens correctly. Agree who checks the complete set and when it becomes the show version.
What to send the technical team
A numbered screen plan with size, orientation and intended picture for each destination.
A sample of the most timing-sensitive content, including transitions and the end of the loop.
The required cue, soundtrack location and behaviour after the sequence ends.
The expected operating period and the method for approved content updates.
A rehearsal plan covering the final chain and the agreed restart scenario.
Use control computer planning and technical support to turn that content map into an output plan. The number of physical screens should be a consequence of the visual design; the number of playback devices should follow the actual output, timing and operating requirements.
Further reading
BrightSign video synchronisation and multi-output configuration describe specific supported implementations. Verify the system proposed for your event.