GLMedia · Conversion, transport and confidence
Using processor and video-wall splicer outputs for monitors
Count content feeds and logical destinations before counting connectors. A free port helps only when the device can generate the feed and the monitor accepts its signal.
Required feed source → Processor logical destination with verified resources → Output configuration → identified physical connector → Compatible conversion/transport → monitor
From the need to the connector
| Content | Specify program, preview, AUX, multiview or Presenter View. |
|---|---|
| Logical destination | Identify an independent composition, routed source or copy of another output. |
| Resources | Check card, connector grouping, layers/scalers and available resources for the exact model. |
| Physical output | Record port, complete format, transport and monitor input. |
Why the distinction matters
Event Master documents output configurations assigned to Screen and AUX destinations with capacity rules. That does not turn any connector on any splicer into AUX. The exact device must provide that function; a monitoring output should not be assumed to carry clean program.
Two monitors: the same image or different content
If two confidence monitors need the same image, consider compatible distribution from an already prepared output. Each branch still has its own link and monitor requirements.
If one needs program and the other notes, generate both images at the source and use paths that keep them separate. An AUX output may suit the task when its function, format and resources allow it; a program copy will continue to show program.
| The confidence image changes unexpectedly | Compare the source, destination and parameters included in the scene or preset. Repeat the change off program. |
|---|---|
| There is an image, but text is cropped | Check aspect ratio and cropping at the source, processor and monitor without changing everything at once. |
| The pattern arrives, but notes do not | The pattern confirms part of the output path; the actual source still needs generation and selection checks. |
Proposed setup and test
- Save the show and complete one row per feed: content → source → logical destination → card/port → monitor.
- Create or select the destination according to its manual and verify resources before changing the show. Identify groupings that use several connectors for one signal.
- Test a pattern on each physical output, then real content. Confirm received format, aspect ratio and which connectors share an image.
- Rehearse an audience scene and a confidence scene: record what changes, what stays fixed and who calls each change.
Alternatives when outputs run short
If every monitor needs the same image, evaluate distribution of one compatible output. Different content needs independent capacity or a separate source path. A scaler can adapt format, but does not create the next slide or replace composition resources.
Frequently asked questions
Are program, preview, AUX and multiview interchangeable?
No. Program is the audience image; preview prepares changes; AUX depends on system routing; multiview combines views for supervision. Check actual behavior.
Can two monitors use different resolutions?
Only when the paths provide documented independent adaptation or both accept a common format. Two connectors alone do not prove it.
What should I check if a scene change also changes confidence?
Compare the affected destinations and transition/preset selection with the feed table. Save the state and repeat the change off program before editing.
Official documentation
- Barco Event Master R5905948/15 — Destination Configuration — 6.16: Destination formats; Rules; More about AUX Destinations
- Microsoft — Use Presenter View in PowerPoint — Presenter View: current slide, next slide, speaker notes and monitor selection
Accessed October 25, 2026