Skip to content
All updates

Output Player v2

The brand-new broadcast player, rebuilt from the ground up. Released as version 4.4.0.

4.4.0Release archive

New configurator

A new way to map broadcast signals

New formats

Up to 4K60P

1080p50, 2K, 4K50P or custom.

Pixel formats

Customize pixel formats

BGRA or UYVY.

New engine

High-performance parallel render engine

GPU performance

Advanced hardware encoding and decoding

New preview

On-machine output preview

New live system

Cloud Live in seconds, not minutes

What changed in v2.

Rebuilt from the ground up
The new application provides a natively timed video pipeline for the most accurate and stable framerate.
Live output preview on the machine
A separate window to check whether an output has the correct signal, without tuning into SDI or NDI.
Resilient SDI output pipeline
A new, production-proven system to bring frames to the physical card.
Faster Cloud Live booting
From waiting 5 to 10 seconds, to a live signal within 2 seconds.
GPU decoding detection
Advanced use of NVIDIA CUDA, AMD or macOS VideoToolbox for fast decoding of common formats.
New UI for single player client mapping
A clear overview of the mapping setup per player.
40% less CPU usage
With multi-output setups, the new parallel processing pipelines cut CPU usage by 30 to 40%.
Standalone automation controller
Your configured rundowns can run by themselves without the Core connection. The player queues itself to keep running.
Faster synchronisation
With deeper control over frame playback, synchronisation is up to 10 frames faster and can be applied more safely.
Improved framerate conversion
From 25 to 50, from 23.976 to 25: input framerates are accurately converted to your output rate.
Seamless migration
All output mappings from the previous configuration are used by the new player without extra action.

Migrate to v2 in five steps.

A complete walkthrough of how to move from the old Output Player to the stable new version.

Update the other apps first

Only apps at these versions or later speak the protocols Output Player 4.4 needs.

Core 4.3.6 Audio Manager 4.3.4 Media Server 4.3.6
  1. Take a note of your old output mappings. The new version should re-use the old mappings automatically.

  2. Download the installer for version 4.4.0. A next generation app, from the Download Center.

  3. Check the new Output Player configurator. Look for inconsistencies and correct them in the new configurator.

  4. Shut down the old version and install the new one. The downtime should be minimal, but make sure your output sources are not on air. After installation the new version starts automatically.

  5. Verify the new player's outputs. The old mappings are re-used in the new player. Adjust missing outputs or formats in the new configurator.

Output settings in the new configurator, with SDI, NDI and Cloud Live mapped per output

Migration FAQ.

What is the expected downtime for the migration? +

The downtime is equal to other updates of the Output Player. You close the app and start the newly installed one. How long the Output Player takes to load depends on the complexity and size of your outputs configuration.

I don't see a version 2 to download? +

Output Player version 2 is included in the 4.4.0 release of the software and is officially labeled as version 4.4.0.

My new output configuration misses mappings. +

The background migration of the old mappings to the new configurator could be incomplete for your specific setup. Add the mappings from the old player manually, or contact support through a ticket or email.

The old mappings didn't include a "pixel format". How is this mapped in v2? +

The old system did a "smart mapping" when an output channel (NDI or SDI) used an alpha-capable format: with NDI Alpha Support or SDI Keying selected, the player converted to BGRA in the background. To give broadcast professionals more flexibility, this mapping is now customizable. For the best performance with large non-alpha files and high framerates choose UYVY422, for transparent alpha graphics choose BGRA.

The new player feels buggy. +

Building the new player from the ground up, we may have made a mistake. Sorry for the broadcast inconvenience. Create a support ticket or email us, so we can fix the issue with the highest priority.

How do I roll back? +

Keep the old Output Player installed to roll back instantly: close the new application and open the old one. Uninstall the new one so the Core doesn't start it automatically. Let us know what went wrong, so we can improve the new version and help with the migration.

I have multiple Output Player client instances. How do I merge them? +

The new Output Player no longer requires multiple processes on the same machine, which makes app lifecycle management a lot more stable. As a result, you manage a single Output Player config per machine. Contact us if you need help bringing the existing configuration back to a single client mapping in the new configurator.