TVSDK for Desktop HLS Release Notes describe what is new or changed, the resolved, and known issues in TVSDK DHLS.
1.4.31
Multi-CDN Support for CRS Ads
1.4.30
To accommodate customers who want to pay only for what they use, rather than a fixed rate regardless of actual use, Adobe collects usage metrics and uses these metrics to determine how much to bill the customers.
1.4.24
Important: You must have at least Adobe Flash Player version 22 or later installed.
Persistent network connections create and store an internal list of network connections that can be reused for multiple requests, instead of opening a new connection for each network request. Persistent network connections should increase efficiency and decrease latency in your networking code.
In this release, this feature is not supported in Apple Safari and Mozilla Firefox on a Mac.
1.4.19
1.4.18
1.4.10
For more information, see Ad fallback for VAST and VMAP ads.
1.4.8
Video Heartbeats Library (VHL) updated to version 1.5
1.4.7
Support for on-premise installations of the Adobe Individualization Server to customize the client’s individualization request to go to a different endpoint.
1.4.6
Sample-based AES encryption is now supported.
1.4.2
Video Heartbeats Library (VHL) update to version 1.4.0.1
1.4.0
Blackout Signaling With Alternate Content Replacement As part of the 1.4 TVSDK update, the TVSDK also now supports going into and returning from regional blackouts against linear content. The TVSDK can now process two manifest files in parallel, main and alternate, to monitor for blackout signals even when alternate programming is being shown in place of the original programming.
Remove/Replace C3 Ads Now, no additional prep work is needed to dynamically insert new ads into video-on-demand (VOD) assets that are coming out of the C3 window. The TVSDK now provides an API to remove custom content ranges and dynamically insert new ads. This powerful new functionality is also useful in cases where live/linear content airs during broadcast and is immediately pulled down for use as on demand content without proper time to “clean” the asset.
All TVSDK customers who use CRS are strongly encouraged to upgrade to at least TVSDK 1.4.32 on iOS, Android, and Desktop HLS. This upgrade will be a drop-in replacement to the existing app implementation. After the upgrade, check for the CRS creative URL requests in a proxy tool (for example, Charles) to verify that the version in the path reflects version 3.1. For example,
https://adunit.cdn.auditude.com/assets/3p/v3.1/218747/94b/c1b/94bc1b964cc67e115a5a6781c7329b90_ee92607938ffff46b083121f044c2746.m3u8
Version 1.4.41
Zendesk #33777 - Localhost token SWF for DHLS distribution build expired.
Updating the localhost token for PMP demo on DHLS.
Version 1.4.38 (891)
Zendesk #30731 - TVSDK does not playing multiple VPAID ads in an AdBreak.
Fixed Multiple VPAID ads playback in an AdBreak.
Zendesk #29968 - Double Billboard.
The video player can repeat the last segment of a period when an ABR switch happens. Due to this, at times, last segment of preroll repeated. This has been fixed.
Version 1.4.35 (879)
Version 1.4.33 (873)
Zendesk #21701 - Send the original creative URL for 1401 CRS request instead of the normalized url.
The issue where already repackaged URLs are being requested for transcoding has been fixed, as per the required by the CRS back end.
Zendesk #26197 - Anamorphic Compression not replayed in desired Display Resolution.
Note: This issue requires Flash player 24.0.0.194 or later.
The issue where missing entries in the aspect ratio tables were used to calculate the output width has been fixed.
Zendesk #26840 - HDCP detection failing on IE11 + Windows7 after second attempt.
Note: This issue requires Flash player 24.0.0.218 or later.
This issue was resolved by modifying AdobeCP’s main message queue processing to iterate through the whole queue, instead of just blocking on the very first message.
Zendesk #27460 - The new Akamai account is unable to handle a POST CDN request.
The new CDN account is unable to handle a POST CDN request. This issue was resolved by updating the code to make the cdn.auditude.com ad request be GET instead of POST.
Zendesk #27619 - Flash crash on Windows 10
Note: This issue requires Flash player 24.0.0.218 or later.
This issue was resolved by preventing a fault as the result of long URLs.
Zendesk #28218 - Tracking event does not fire while the plackback from the resume point
This issue is the same issue as in Zendesk #26592. The issue where seek operations were allowed when the media player is in the PREPARED state for VOD streams has been fixed.
Version 1.4.32 (867)
The code was not updating the pre-roll ad break item when the resume point was not zero. This issue was resolved by adding logic to refresh the code when the range start times do not match.
The exceptions with the array methods have been fixed.
Version 1.4.30 (855)
The following issues were resolved for TVSDK in this release:
Note: This issue requires Flash player 23.0.0.185 or later.
This issue was resolved by allowing TVSDK to continue the playback, even if the manifest is missing the WebVTT M3U8, and just register a warning.
This issue was resolved by handling of VPAID ads correctly based on content IDs rather than time ranges.
Important: This issue requires Flash player 23.0.0.185 or later.
Important: This issue requires Flash player 23.0.0.185 or later.
The caption display texture map code has been fixed to properly handle the coordinates during the player resizing.
The Video Heartbeat Library (VHL) has been updated to version 1.5.9 to resolve the following issues:
This issue was resolved by tracking the bitrate changes in VideoAnalyticsTracker.
Version 1.4.28 (848)
This issue was resolved by adding the code to check the AUDITUDE_METADATA_KEY and by making the AUDITUDE_METADATA_KEY and ADVERTISING_METADATA_KEY interchangeable.
This issue was resolved by taking into account that when there is no ad setup, TVSDK can speed up processing by eliminating the pre-roll ad hold and live reservation hold on the timeline that is designed to synchronize ad insertion.
Note: This issue requires Flash player 23 or later.
This issue was resolved by loading the WebVTT files only when captions are required to be displayed.
Note: This issue requires Flash player 23 or later.
The spurious EOC code caused the caption display to disappear. This issue was resolved by forcing the 608 captions codes RU2, RU3 and RU4 to provide the correct visibility in the current active window.
Version 1.4.27 (844)
This issue was resolved by enabling TVSDK to ping the correct error tracking URLs on invalid asset formats.
Note: This issue requires Flash player 23 or later.
After getting a 404 error on certain requests, a crash might occur. This issue has been resolved by ensuring that the connection does not shut down while the response is being handled. The resolution ensures that the VPAID ad files are not counted incorrectly, so they do not get released while they are downloading.
Note: This issue requires Flash player 23 or later.
Fixed the issue that caused a DRM metadata corruption when switching between different profiles.
Note: This issue requires Flash player 23 or later.
This issue is the same issue as in Zendesk #23621.
Note: This issue requires Flash player 23 or later.
The Windows native networking code has been fixed to ensure that connections do not close handles that are currently being used by other connections.
This issue was resolved by allowing clients to set custom parameters separately on Opportunity instance so that clients do not have to override OpportunityGenerator.
Version 1.4.26 (839)
Zendesk #18854 - Update creative selection logic based on CRS rules
Zendesk #22725 - playbackManager.beginPlayback() implementation in the sample application for Desktop
Zendesk #22807 - SeekManager null reference exception
Zendesk #22822 - Frequent buffering when using TVSDK to play a clear HLS
Zendesk #23378 - Stream integrity blocks rules.xml
Version 1.4.24 (817)
Note: This issue requires Flash player 22.0.0.175 or later.
The issue where the DRM adapter is reset after downloading a small fraction of a segment does not get restored properly has been resolved.
This issue was resolved by adding an API (trackVideoComplete) to manually trigger the completion of content during a LINEAR/LIVE video tracking session.
The following libraries were updated:
Zendesk #21643 - VPAID ads do not play in full
This issue was resolved by using a zero-height viewport to fill the stage when a VPAID ad is playing.
The SSL-related issues were fixed, and the VHL library that is used in TVSDK has been updated to the latest version.
During adaptive bitrate, with the max bitrate limit, the reloading of the video intermittently shows a black screen even though the client sees updates to position, and the client behaves as though it is playing content.
Version 1.4.23 (809)
Note: This issue requires Flash player 21.0.0.240 or later.
The issue where the post-roll ads were being skipped when the ad rule logic was applied to the TVSDK has been fixed.
If a vast inline ad has multiple media files with a VPAID ad being the first ad, the inline ad is not played for live streams. This issue was resolved by picking up a different media file instead.
Note: This issue requires Flash player 21.0.0.240 or later.
The audio repeating issue has been fixed.
Note: This issue requires Flash player 21.0.0.240 or later.
This release provides support for returning from an ad break early before the ad break is played to completion. Early return is indicated through a custom manifest tag.
Note: This issue requires Flash player 21.0.0.240 or later.
The audio repeating issue that was fixed has also fixed this issue.
Note: This issue requires Flash player 21.0.0.240 or later.
The audio repeating issue was fixed.
The issue where the reference player not playing any stream and was throwing an exception at start up has been fixed.
Version 1.4.22 (791)
Note: This issue requires Flash player 21.0.0.197 or later.
The random 3357 errors that occurred by properly initializing the deviceID when storeVoucher() is called has been fixed.
In this release, global ad request timeout has been added.
Version 1.4.21 (782)
PTTimedMetadataChangedNotification
notificationsNote: This issue requires Flash player 21.0.0.182 or later.
This issue was resolved in the Desktop Reference Player by providing the ability to set Ad tags and adding a custom opportunity generator that shows how to subscribe to custom cues and how to process these cues in a VOD file.
Note: This issue requires Flash player 21.0.0.182 or later.
This issue was resolved by updating the app to set _resource.metadata.setValue(DefaultMetadataKeys.ENABLE_LIVE_PREROLL, “false”) to disable pre-roll ad insertion in a PIP swap and, as a result, no pre-roll opportunity is generated.
A sorting functionality was introduced to fix the out-of-sequence ad placement that resulted in a negative main content duration.
Note: This issue requires Flash player 21.0.0.182 or later.
This issue was resolved to behave correctly and not dispatch events when ad break is skipped.
Note: This issue requires Flash player 21.0.0.182 or later.
The Auditude Request parses the AuditudeSettings for custom parameters when creating an ad unit for advertising requests.
This behavior was changed to include custom parameters from the Opportunity object in the request. Also, multiple opportunities with different custom parameters cannot be packed in one Auditude request.
Note: This issue requires Flash player 21.0.0.211 or later.
This issue was resolved by allowing the TVSDK to ignore the manifest (HLS sub profiles) that contains the AC3 codec that the TVSDK does not support (surround).
Version 1.4.20 (762)
Note: This issue requires Flash player 20.0.0.306 or later.
Note: This issue requires Flash player 20.0.0.306 or later.
The occasional hangs that occurred when seeking in Google Chrome were resolved by shutting down the queries, if the queries take too long to get a response or if the socket is being shut down.
Note: This issue requires Flash player 20.0.0.306 or later.
This issue was resolved by reporting a warning.
This issue was resolved when #EXT-X-FAXS-CM tag appears at the top playlist before individual bitrate or segments in the playlist.
This issue is the same as Zendesk #19181.
This issue was resolved by making the player dump and reload the manifest when a track changes and by correcting the UTF8 string conversion problem that affected the double-byte WebVTT caption track names.
Version 1.4.19 (1.4.19.738)
This issue requires Flash Player FP 20.0.0.267 or later and was resolved by handling the Unicode string correctly.
This feature requires Flash Player FP 20.0.0.267 or later and was introduced in release 1.4.19.
This feature requires Flash Player FP 20.0.0.267 or later and was fixed by correctly handling the Unicode string.
This issue requires Flash Player FP 20.0.0.235 or later and is the same issue as Zendesk #18723.
This issue requires Flash Player FP 20.0.0.235 or higher and is the same as Zendesk #18723.
This issue was resolved by ignoring the gap between timestamps and just playing the downloaded content.
In Primetime’s default adPolicy selector, if a mid-roll ad is watched, the adBreak is not moved to the seeked position when you complete a seek. To play the ad again, after the seek, the application needs to override the selectAdBreaksToPlay() function.
This issue was resolved by allowing the player to update the playbackMetrics time, the minimumOpportunityTime, and the Timeline.
This issue requires Flash Player FP 20.0.0.267 or later and was resolved by setting the advertisingMetadata.adSignalingMode correctly.
This issue was resolved by adding a new API, adRequestTimeout, to the AuditudeSettings for an ad request timeout. Users can now override the default 10s ad request timeout.
Version 1.4.18 (1.4.18.722)
When an ad break is empty, the ad break start and complete tracking events were not being pinged. This issue was resolved by sending ad break start pings on empty ad breaks, such as VMAP AdBreak, with a valid AdSource nod.
Version 1.4.17 (1.4.17.702)
This issue was resolved by providing support for the EXT-X-MEDIA-TIME tag for vtt caption files.
Note: You must have at least Flash Player FP 19.0.0.245 or higher.
When sometimes playing live content, there might be invalid keys in the manifest (for example, for blackout periods), but other time ranges might have valid keys and will still play. Previously, when a key that was listed in a manifest could not be downloaded, the entire manifest failed. Now, the manifest fails only when all of the listed keys cannot be downloaded. If some keys are valid, but some of these keys could not be downloaded, content will play. We will still fail if we try to play a segment that requires a key that we do not have.
Note: You must have at least Flash Player FP 19.0.0.245 or higher.
A bug in the cookie manipulation code that might truncate cookie values was fixed.
Version 1.4.16 (1.4.16.684)
This is an enhancement.
This issue was resolved by detecting rollover and managing the discontinuity per payload type and not generically.
This issue was resolved by re-initializing video heartbeat tracker during a linear stream playback session.
Note: The resolution requires Flash Player FP 19.0.0.207 or greater.
This issue is the same as Zendesk #3732.
Note: The resolution requires Flash Player FP 19.0.0.207 or greater.
This issue was resolved by handling the live streams where the domains of the TS files change when reloading the live manifest, and the files were downloaded twice.
Note: The resolution requires Flash Player FP 19.0.0.207 or greater.
The issue was resolved by handling streams with no audio in the first 2 seconds of the first TS file.
Note: The resolution requires Flash Player FP 19.0.0.207 or greater.
The issue was resolved by handling live streams with time interleaving between audio and video frames on segment boundaries.
Note: The resolution requires Flash Player FP 19.0.0.207 or greater.
The issue was resolved by handling unmuxed audio with mid-roll ad insertion. (The parser switch occurs, and at any point in playback, the content transitions to the mid-roll ad, or in middle of ad playback, and so on.)
This issue is the same as Zendesk #17973.
Version 1.4.15 (1.4.15.678)
The fix was to add AD_BREAK_SKIPPED if an ad is skipped.
The fix was to add support for setting the AVNetworkConfiguration property useCookieHeaderForAllRequests through the TVSDK.
A crash during playback of some encrypted content was fixed.
Note: The fix requires Flash Player 19.0.0.200 or higher.
Added a type to AdBreakTimelineItem (AdBreakTimelineItem.placementType) so that AdPolicySelector can return a different policy for pre-roll, mid-roll, and post-roll content.
The fix was to remove the logic to change the target buffer size to the initial buffer size when buffering begins.
Version 1.14.14 (1.4.14.771)
Zendesk #17363 - Fix README documentation for reference player
Zendesk #17471 - Player Freezes
Partial fix for an issue where an ad does not play from the beginning after seeking.
Provide custom parameters for each ad break.
Version 1.4.13 (1.4.13.660)
fix url parsing problem when query paramer contains “http”
Fixed a crash when playing video in fullscreen mode with IE11
Fixed a crash when playing video in fullscreen mode with FireFox on Windows.
Fixed an issue where a URL was not getting its type recognized correctly because it had no extension
Fixed a crash when playing video in fullscreen mode on Windows.
**1.4.12 **(1.4.12.656)
Updated Creative Repackaging Service to properly handle ads with dynamic creative URLs.
Basic playback of MP4 content is now supported including play, pause and seek.
The following require Flash Player 18.0.0.225 or greater:
TrickPlay now accepts rates higher than 16x: +/- 32, +/-64 and +/-128.
Fixed crash when attempting to play a redirect ad on Mac Firefox.
Fixed crashed in Windows Firefox during playback in fullscreen.
Version 1.4.11 (1.4.11.648)
Allow caption sizes to be used in WebVTT caption code.
Fix stage video bug.
InvalidateProfiles in ThreadSeek when new period is detected.
Fixed crash in native networking mode in pepper
Fixed issues finding wildcard token when the pageDomain is different from the swf domain.
Version 1.4.10 (1.4.10.642)
Fixed a occasional Flash Player crash with Firefox on Mac when a stream, playing on an external monitor, would switch to a higher bitrate stream.(requires Flash Player 18.0.0.160)
+-
40/50 seconds and starts going black after +-
90 secondsFixed an issue on Mac Chrome where stream would start to flicker an eventually go black. (requires Flash Player 18.0.0.161)
Zendesk #3304 - VAST 3.0 [ERRORCODE]
macro not being populated
[ERRORCODE]
macro will be URL encodedZendesk #3601 - Enhancement request: Wrapper companion management
Version 1.4.9
Added clearVideo() method to MediaPlayer. Clears the displayed video frame by clearing the AVStream from the StageVideo object. Should only be called if the video is paused, and replaceCurrentResource or replaceCurrentItem must be called before play() can be called again.
Reference player has been updated with Adobe Analytics integration
mime types for HLS format had been case sensitive, this was incorrect and has been changed so they are no longer case sensitive
Version 1.4.8
Version 1.4.7
Version 1.4.6
Version 1.4.5
Version 1.4.4
[Adobe Primetime]
Update: HLS client based failover support for PROGRAM-DATE-TIME in Desktop PSDK (requires Flash Player version 16.0.0.305 or greater)[Ads]
Tracking ad errorsVersion 1.4.2
[VPAID]
Player not responding when seeking past ad break[Analytics]
Incorrect chapter dataVersion 1.4.1
Version 1.4.0
ReferenceCore.as
by changing the contents of onPlaybackManagerPrepared
:if (_playbackManager.autoPlay) {
_playbackManager.play();
} else {
_playbackManager.play();
_playbackManager.pause();
}
Version 1.4.13 PTPLAY-8501 - When VMAP returns two direct MP4 non transcoded ads, the same fall back ad plays twice.
Version 1.4.2 In the Flash Player version 16 release, an issue was identified with the ABR “switching down” logic, after the player gets into an empty buffering event. The issue prevents the bitrate from switching down in bad bandwidth environments once the player gets into a buffering state. To work around the issue, have your app set the BufferControlParameters.initialBufferTime
to be the same as BufferControlParameters.playbackBufferTime
temporarily during the buffering state (that is, on a BufferEvent.BUFFERING_BEGIN
event) then reset it back to the set values on BufferEvent.BUFFERING_END
event. The fix for this issue will be available in the next patch release of Flash Player verison 16.
Version 1.4.0