Starting today, you can create clipping profiles in Uplynk to speed up the clip creation process. When the clipping tool is launched, you have the ability to select a clip profile which pre-populates all clip settings, such as overlays, bumpers and exports. With profiles, only in/out points and titles are required so you can get clips out to your audiences much faster.

Clipping profiles also support multiple accounts per publishing integration. For example, if you manage content for multiple brands within a single Uplynk account, you can now publish to different Facebook pages based on the selected profile.

Clip profiles are created in your clip settings page. You will notice that current clip settings have been migrated into a default profile. When you launch the clipping tool, your default profile will be pre-populated, when you create new profiles they will be available in the profile dropdown.

Additions

• Full support for Live Events 2.0

Fixes:

• Multiple ad breaks being entered for a single request

Download the latest

• Windows

• Linux

Live Events 2.0 is now live and available in your Uplynk account. With an all new workflow and dashboard, Live Events via Uplynk are more powerful than ever.

Things to remember

• Update any API integrations to call the new set of live event APIs via new API Documentation

• Check out the new Live events tab

• Read up on new workflow and functionality via Live Events Documentation

• Look in the All Content tab post event for assets

• Download the newest Camera Slicer

Camera Slicer Release 17041700

Additions

• Full support for Live Events 2.0

• SlicerID field of Login UI will now have a default value of 'cameraslicer1'

Fixes

• Multiple ad breaks being entered for a single request

Download the latest

• Mac

If you have any questions please contact Support or your account representative.

A new version of Live Events, that introduces an improved workflow, will be released on April 18th. The current workflow will be replaced and action needs to be taken for current Live Event users.

What to do:

• Download the new Camera Slicer, which will be available on April 18th

• Update any API integration to call the new set of live event APIs for events after the release date

• Updated APIs can be found here: API Documentation

• If you have events scheduled on or around the launch date and would like to temporarily opt out of the upgrade, please contact support.

• Visit our support site to get more information on the new Live Event features: Live Events Documentation

What to expect:

• Older versions of the Camera Slicer will not work after April 18th

• Any event assets currently in your Live Event tab will be moved to your "all content" tab

If you have any questions or concerns regarding this transition please contact Support or your account representative.

We have added the ability to block playback by domain in the upLynk CMS. You can edit the list of blocked domains by accessing Blacklisted Domains on the Advanced Settings tab. This functionality will allow you to quickly add or remove domains to which playback will be disallowed.

Additions:

• Automatic SSL Cert and DNS configuration

• ignore_scte_preroll option for SCTE 104

• TTML parsing stores ttm:desc as subtitle description

• noaudio flag to suppress audio from UDP input

Fixes:

• splitscreen issue on Black Magic Duo 2 cards

• Caption parsing

• Invalid characters no longer crash slicebot

• Various SCTE python plugin integer casting issues

Download the latest:

• Mac

• Linux

• Windows

We've added a new Notification Method for Slicer Monitoring Alerts. For those that want slicer alerts to be delivered in a simple, consumable format so that they can be integrated with other tools in your workflow, Push Notifications is for you.

With our Push Notifications, you can easily receive notifications in SNS, and build scripts to the tools that need that information, such as ticketing systems, chat tools, or 3rd party monitoring tools.

Provides an immediate notification when an alert is triggered
With Push Notifications, our alerts are sent to a customer endpoint immediately, allowing customers to know the moment something happens

Provides a secure, consistent message type
Our goal is to simplify and secure our delivery of notifications to customers. Utilizing AWS, we are able to send data to a secure endpoint that you configure and manage. Our messages are simple to consume and parse for downstream services.

Allows for customizations and easy integration into your third party tools
Flexible configuration gives you the options to chose what to send and where to send. There are 12 alerts that are available for configuration. All alerts are sent immediately. Once this data is in your account, it’s easy to setup integrations into other tools, such as Slack, PagerDuty, Splunk, or JIRA for example.

Read more about this feature here

Additions:

• Custom SDI channel configurations

• SDI mono channel audio support

• Parse region textAlign property in TTML

Fixes:

• Segfault under certain conditions when running multiple Live Event 2.0 dashboards

• SCTE-104 UPID parsing

• Various other SCTE and baseline python plugin fixes

• Asset metadata for initial content_start calls

Download the latest:

• Mac

• Linux

• Windows

Additions:

• SDI ingest performance enhancements

Fixes:

• Live Events 2.0 functionality

• Status API consistency

• Linux install script updated to work with systemd (in addition to upstart)

Download the latest:

• Mac

• Linux

• Windows

We've expanded our monitoring capabilities with the inclusion of four new alerts for Slicer Monitoring

• Static Video: This alert will inform you when the slicer is receiving static video from the source signal. This could be a green screen, color bars, a frozen frame, or any other instance where the video luminosity is not changing for an extended period of time. Customers control the amount of time that static video is present before an alert is triggered.

• Static Audio: This alert will detect when the audio feed is sending a static audio track to the slicer. This will help catch when end-users hear any audio tone that is irregular and unintended. Customers control the duration of when the system will trigger a warning or critical alert.

• Extended Ad Break: This metric will identify when a slicer stays in the an ad break state for longer than expected. Customers can be alerted when a slicer stays in an ad break state for longer than expected.

• Nielsen Tags Last Seen: This metric will check that Nielsen tags are being received and inserted into the stream as expected by the customer. The customer can configure the slicer to detect nielsen watermarks, and insert tags in the stream. This metric will allow customers to be alerted if nielsen watermarks are not being identified by the slicer.