We’re excited to announce that our new Syndication workflow will go live on Monday, July 21.

This update introduces a new way to manage Syndication jobs through job templates. When you create a target, you will be able to pre-configure job settings that will automatically apply whenever a job is added to a live channel or event. This makes the setup process faster and simpler - especially if you need to reuse the same configuration for different live events.

What’s Changing?

• Job templates are now part of each target.
• New unified Syndication page replaces the old Settings > Publishing location.
• Streamlined UI for creating and managing targets and jobs.

Check out our updated Syndication docs here, and reach out to our Support team if you have any questions.

The LVP Player has been updated to support auto-height (with a fixed width) and auto-width (with a fixed height). In addition, the LVP Player now supports auto-title where the player title will automatically be set to the title of the asset being played.

You can read more on how to use these enhancements here.

Contact Support or your Technical Account Manager with any questions.

The Uplynk Slicer family of applications runs on select Linux, MacOS, and Windows hosts in customer-managed deployments. The Slicer applications are required to perform certain communications tasks with the Uplynk Cloud infrastructure, such as logging in and reporting status.

Since the slicer's very early days, we have bundled Root Certificate Authority Certificates with the application to manage our TLS/SSL trust chain. In the June 2023 release, we upgraded the bundled Root CA Certificates to align with our cloud hosting platform requirements.

The Uplynk Cloud infrastructure provides TLS certificate security based on a certificate signed by a trusted Root CA. Slicer versions released prior to June 2023 do not contain the updated Root CA certificate required for validating future TLS certificates. As a result, these versions must be updated to maintain connectivity and functionality.

Starting August 1, 2025, the cloud management system will only support slicers released in June 2023 or later. Slicers older than this date will log an error message stating that they do not meet the system’s minimum requirements, and content will not be processed. To resume content processing, the slicer must be updated. This change does not impact VoD or linear content already processed and stored in the library using older versions.

Customers with Recent Activity:

Even if your slicers are inactive, we recommend reviewing your live and VoD slicer versions and upgrading any version dated before June 2023. Please ensure any inactive workflows are prepared to go live when needed. You will also see a CMS news item confirming this message.

If you need to upgrade your slicers, we strongly recommend using the most recent slicer version. We also advise testing in a staging environment to ensure workflow compatibility.

Customers without Recent Activity:

Even if your slicers are inactive, we recommend reviewing your live and VoD slicer versions and upgrading any version dated before June 2023. Please ensure any inactive workflows are prepared to go live when needed. You will also see a CMS news item confirming this message.

We strongly recommend using the most recent slicer version if you need to upgrade your slicers. We also advise testing in a staging environment to ensure workflow compatibility.

Important exception:

If you are running Python 2.0 plugins (used for SCTE ad marker detection), do not upgrade beyond version 23062600. Slicers released after that version only support Python 3.0 or later. While not required, we recommend rewriting any Python 2.0 plugins in a current version of Python and using them on the latest supported Slicer version.

We value your business and apologize for any inconvenience this may cause. If you have questions, please get in touch with your account team or our support team.

Launched four years ago, the CSL V1 platform was our first CMS-integrated live-streaming solution via hosted slicer ingest into Uplynk. Many customers now deliver high-quality encoded source streams to Uplynk using newer protocols like SRT—and have successfully leveraged CSL V1. Conceptually, the platform established ingest points (URL’s and expected protocols) that could be streamed to. When a new cloud slicer was created, it would effectively be linked to the ingest point as part of that process.

Over the past six months, our development team has built a new version of the platform—CSL V2—with a re-architected design to improve scalability, reliability, cost-efficiency, and launch speed. From a usage perspective, we eliminated ingest points being separate from the slicer. Instead of deleting a slicer to free up the resource when not being used, we implemented a stop and start capability in CSL V2.

Due to the architectural differences, CSL V1 slicers cannot be directly migrated to V2. Existing V1 endpoints are not reusable, and customers must create new V2 slicers for their workflows.

Recommended Migration Process:

• Choose a time when the live channel or event can be briefly interrupted.
• Stop the source stream to the existing V1 slicer.
• Note the transport protocol, name, configuration, and profile of the current V1 slicer.
• Delete the V1 slicer.
• Create a new V2 slicer with the same parameters (name, protocol, profile, configuration).
• Copy the new V2 slicer URL and passkey (if applicable) into the source stream device.
• Start the new V2 slicer.
• Restart the source stream.
• Verify that the V2 slicer is slicing the stream successfully.
• Confirm that the live event or channel is operating as expected.

Alternate Option:

You may pre-create the V2 slicer (with a different name/ID) before stopping the V1 slicer. Once ready, simply point the source stream to the new V2 slicer and add it to your desired channel or event.

For Uninterrupted Channels:

If your channel cannot be interrupted, duplicate the feed, send a copy to a V2 slicer, configure a failover group, and then remove the V1 slicer.

If You No Longer Need a Slicer:

Simply delete it. Should you require one in the future, use CSL V2. The CSL V2 User Guide offers step-by-step instructions:
https://docs.uplynk.com/docs/cloud-slicer-live

We value your business and appreciate your understanding during this transition. If you have questions, please contact your account manager or our support team.

You can now upload TS captures and other troubleshooting files directly through the new Support page in the Uplynk UI. Files are stored securely and automatically deleted after 14 days. Visit the Support section to get started.

You can read more about this new enhancement here.

Contact Support or your Technical Account Manager with any questions.

When setting up a new ad server with "Universal Ad Configuration", you often receive an "Ad Tag" - a template URL from your ad provider that includes server information and required parameters. With this enhancement, you can simply paste your Ad Tag URL, and the system will automatically parse it and populate the configuration with all the relevant values. This makes setup faster, easier, and helps reduce the risk of manual errors.

You can read more about this new enhancement here.

Contact Support or your Technical Account Manager with any questions.

The following update of the Dolby ID names in the Dash manifest only has changed as follows:

The following is an example of this portion of a current Dash Manifest and change: Dolby 5.1 previous:

<Representation bandwidth="129741" codecs="ec-3" id="maindolby6">

Has changed to:

<Representation bandwidth="129741" codecs="ec-3" id="mdolby6">

The other Dolby codecs would change as the example above.

Contact Support or your Technical Account Manager with any questions.

The original Slicer Failover (pre-2020) found under the Channels->Playback tab is being discontinued on about June 30, 2025. On that tab, the Enable Automatic Failover checkbox should be unchecked to work with the current Failover, introduced in 2020, which is under the Ingest tab.

The Slicer Failover going forward is described at https://docs.uplynk.com/docs/failover.

Contact Support or your Technical Account Manager with any questions.

The Legacy 'Hosted Slicers' Cloud Slicer Live V1 platform will be shut down on June 30th, 2025. We recently launched our 'Cloud Slicers' Cloud Slicer Live (CSL) V2 platform. If you have any existing Hosted Cloud Slicers in the V1 environment, please create new ones in the V2 environment and move your streams to them. The CSL V2 offering brings improvements to resource management, failover handling, and usability. These updates make CSL lighter, more flexible, and cost-effective, ensuring a smoother workflow experience. CSL V2 also offers a simplified UI and adds the ability to Start and Stop slicers to keep costs down and simplify the business process

Link to the CSL User GuideIf you have any questions, please reach out to Support.

Uplynk has traditionally secured their APIs with a user-generated token that utilized API keys that are viewable in the Uplynk CMS. This technique is not very flexible, meaning that any API key generated by a user could access all Uplynk functionality, regardless of whether the user of the API key needs this access.

Scoped API Keys allows specific API functionality to be limited to those individuals or systems that need it. Uplynk's traditional API integration keys and the new Scoped API Keys will coexist for the foreseeable future.

Information on Scoped API Keys can be found at https://docs.uplynk.com/reference/scoped-api-keys.

Contact Support or your Technical Account Manager with any questions.