Additions:
Removed -p / password from parsers and help strings
Support for multiple TTML files in VOD slicing
Fixes:
Respect forceAR parameters in the slicer
Track PTS values of slices after discontinuities
Prevent inserting additional ad breaks
Clear 608 closed captioning at start of ad break
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
Additions:
Optimized to enable live 4k60p HDR ingest (requires -hwdec option with Pascal or better NVIDIA GPU).
Implemented faster than realtime HDR->SDR conversion for live 4k60p HDR ingest (requires -csp_xfrom clut with Pascal or better NVIDIA GPU).
Enabled debug overlay for video that has a source bit depth greater than 8-bits.
Fixes:
Fixed a regression slicing video with odd width/height.
When ingesting captions no longer strip out the extra space after italics.
The external_id set from /content_start API call was not set on new asset.
No longer drop some segments because of missing media.
Configuration Change:
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
Additions:
Store the apikey in the keychain for Mac GUI applications
RTMP configuration
Fixes:
Mac GUI will now use account’s DRM settings
Metadata passed in on content_start will display in /status call
Pasting of API key into API key field in Windows GUI slicer
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
We have made improvements to increase security, so password authorization on Slicer login will no longer be supported after March 25, 2019. Instead, we will require API key authentication.
On March 25th, 2019, we are planning a global change affecting all customers who have not implemented API keys. This change will impact the streaming service of those customers. After this change, there will no longer be support for the password entry on Slicer login and customers will be required to use API key authentication.
Please take the following action by March 24th to ensure your streaming service is not affected:
Update the Live Slicer to version 17111500 (11/22/2017) or higher, to have support for API keys. We recommend that you update to the latest Slicer release which can be downloaded from the Uplynk CMS.
Update your Slicer configuration to leverage API key authorization, instead of password authorization. Learn More
Note: Our original request to comply went out June 25, 2018. If you have already implemented API key authentication, you can disregard this request and you will not be affected.
For any questions or concerns please contact your Technical Account Manager or our support team at [email protected] or 1-877-334-3236.
Additions:
SCTE logging function
Allow for metadata to be supplied with boundary calls
Fixes:
Timecode flag crashes LiveSlicer
External ID not populating in CMS
Add_cc608 endpoint causing segfault
Slicer Improperly pre-ingests schedule on start up
Linear channel jitters / judders
Dropped_frame_usec does not reset on content start
Return values for bug timing in MS
Known Issues:
Image bugs do not display in Live Slicer with SDI mode
Windows GUI Slicer can’t login. Please use previous release for password authorization in Windows GUI Slicer.
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
We are making improvements to increase security, so password authorization on Slicer login will no longer be supported after March 25, 2019. Instead, we will require API key authentication.
On March 25th, 2019, we are planning a global change affecting all customers who have not implemented API keys. This change will impact the streaming service of those customers. After this change, there will no longer be support for the password entry on Slicer login and customers will be required to use API key authentication.
Please take the following action by March 24th to ensure your streaming service is not affected:
Update the Live Slicer to version 17111500 (11/22/2017) or higher, to have support for API keys. We recommend that you update to the latest Slicer release which can be downloaded from the Uplynk CMS.
Update your Slicer configuration to leverage API key authorization, instead of password authorization. Learn More
Note: Our original request to comply went out June 25, 2018. If you have already implemented API key authentication, you can disregard this request and you will not be affected.
For any questions or concerns please contact your Technical Account Manager or our support team at [email protected] or 1-877-334-3236.
Additions:
Upload queue depth to status API
cc1_on parameter to suppress individual 608 channels in LiveSlicer
Fixes:
An issue where the slicer would generate malformed slices
Regression causing "Slicer version doesn't support ad breaks in dash live stream. Upgrade slicer" errors on dash playback
Issue with FPS reduction
Errors in SliceBot job failure
Removed slicer failover group configuration (moved to services API)
Issue where a SCTE break was inserting two breaks instead of one
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
Additions:
Track additional information in slicer status for monitoring backend
Configuration example files for apikey usage
Fixes:
Slicer dropping frames periodically in DR mode
Unexpected ad breaks appearing
Recovering SCTE processing after slicer restart
Nielsen ID3 message box signaling in DASH
A SCTE segfault
Anamorphic video and image overlays
Stats reporting for NIC I/O bonded interfaces
max_no_signal_time configuration in linux
host NTP drift from server time automatically for apikey authentication
Ad break signaling for DASH
Python plugin dynamic linkage issue
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
Today we’ve added the following Test Player features to improve content security.
Prevent your account from auto creating test players in Settings > Test Player Restriction. This will be disabled by default.
New test player access permissions in Settings > Account Access let you specify who can create (write) and view (read) test players. All current users will have read & write permissions.
When creating new test players, you can restrict playback to only whitelisted IP addresses and set an expiry duration. Your whitelist can be configured in Settings > Test Player Restrictions.
