The Live Streaming Statistics API is now available to our customers. This version includes statistics on Live Events as well as Channels, making it easy for our customers to monitor all live streaming playback with one API. Review the User Documentation to learn more. Prior versions of Channel Stats API will be supported for a period of time, but will be EOL at a future date.

X-Device-IP fields in ad request headers will now contain the IP address specified by the ad.vip parameter.

A new metric has been added to Slicer Monitoring, SCTE Last Seen. SCTE triggers are critical to operating a Live Slicer. Primarily, SCTE instructs slicers on when programs begin and end, and when ads should be inserted. SCTE Last Seen determines the length of time that may elapse since the Live Slicer last received a SCTE 35/104 signal before triggering a warning or critical status. Please review the User Documentation to learn more.

Slicer Monitoring 2.0 is now available for all Streaming customers. Version 2.0 introduces new features, more customization, and an updated interface. Please review the User Documentation to learn more. The current version of Slicer Monitoring will continue to be supported until the end of July, to allow customers to maintain oversight of their slicer data, while they setup version 2.0. We ask that all customers migrate to version 2.0 before we end of life version 1.0. We plan to deprecate Slicer Monitoring 1.0 on July 20, 2020. Please contact your account manager with any questions.

The latest version of Channel Stats API is now available for all customers. This API provides statistics for your live channels, including counts of new and concurrent sessions, count of sessions experiencing slate, and the duration that slate was inserted for those sessions. Please review the User Documentation to learn more.

Today we deployed an enhanced set of Analytics tools. The new UI and underlying data platform provides customers with improved access to your analytical data and paves the way for new capabilities coming to the platform in the near future. You'll notice the following changes in the Control Center:

• A new Services tab that contains:

• New and legacy analytics tools

• Monitoring

• The Billing tab will be replaced by the “Billing Usage Report” in the new analytics tool for customers who receive invoices

• Data through March 31st will be stored in the legacy tool and data from April 1st onward will be in the new tool

For more information, view the updated documentation here

Fixes:

• -encwait now functions as expected

• dropped frames when input signal has timeline gaps

• -prog N argument no longer causes a crash

• Slicebot will wait for caption files

• Video stuttering issues with 4K RTP input

Additions:

• Python 3 support for SCTE python plugin

Download the latest

• Windows

• Linux

• Mac

Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay

On April 1st, we will be deploying an enhanced set of Analytics tools. The new UI and underlying data platform will provide customers with improved access to your analytical data and pave the way for new capabilities coming to the platform in the near future. Here's what you'll notice:

• A new Services tab that will contain both the legacy and new analytics tools

• Monitoring and Billing will be accessed through the Services tab

• Billing tab will be replaced by the "Billing Usage Report" in the new analytics tool for customers who receive invoices

• Data through March 31st will be stored in the legacy tool and data from April 1st onward will be in the new tool

For more information, view the updated documentation here.

On April 1st, we will be updating our Log Delivery system. The new and old logs will be pushed simultaneously to customers' S3 buckets until the old logs are deprecated on June 30th. This three month period should be used to test and integrate format changes. The new logs differ in the following ways:

• Logs will be prefixed in an easily identifiable manner in your S3 buckets

• Custom log fields will be replaced by an enhanced log schema, which includes asset, event or channel metadata

• A default log schema will be in place for those customers not using custom fields

For more information, view the updated documentation here.

We released enhancements to the Asset Search API, to provide advanced search capabilities on asset libraries, such as metadata search, date range filtering, asset type filtering and multi-faceted searches. Please review the user documentation to learn more.