If you don't find an answer, please click here to post your question.
Reply
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-01-29

2016-01-29 Release

 

Notable contents of this release include an updated Watchlist REST API design.

 

 

Software Feature Releases

 

Streamlined Watchlist APIs

The design of the Watchlist APIs has been optimized, with the same functionality, same version (v3), and minor changes to the request syntax.

 

 

Documentation Releases

Watchlist REST APIs: Updated the Watchlist REST API documentation to reflect the optimized design.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-02-10

2016-02-10 Release

 

Notable contents of this release include updated and new Ooyala IQ functionality.

 

 

Software Feature Releases

 

Ooyala IQ Metrics Supported for Backlot Assets Played in Third-Party Players

Ooyala IQ can now provide metrics for:
  • An Ooyala player playing Ooyala assets (hosted in Backlot)
  • (NEW) A third-party player playing Ooyala assets (hosted in Backlot)
  • A third-party player playing third-party assets (hosted in a third-party CMS)

 

You can configure if you want to use the third-party player to play a Backlot asset or play a third-party CMS-hosted asset. The following examples show how to specify content type with the Ooyala-JW Player adapter.
 
  • OOYALA_CONTENT: Indicates that the mediaid is an Ooyala embed code. You must use type: 'mp4'. To get the value for file, make the Backlot API query: /assets/<ASSET EMBED CODE>/streams for the asset and copy the encoding with "muxing format" == mp4. See Getting Started with a Third-Party Player and Ooyala Assets for full enablement details.
  • <script type="text/javascript">
        var jwPlayer = jwplayer("video").setup({
            file: 'pathToYourOoyalaMp4VideoAsset',
            mediaid: 'yourOoyalaEmbedCode',
            type: 'mp4'
        });
        var jwOoyalaReporter = Ooyala.Analytics.JWReporter("<pcode>", jwPlayer, {
            contentType: Ooyala.Analytics.MediaContentType.OOYALA_CONTENT
        });
    </script>
  • EXTERNAL_CONTENT: Indicates that the mediaid is not an Ooyala embed code (and is customer-defined media ID from a non-Ooyala CMS).
  • <script type="text/javascript">
        var jwPlayer = jwplayer("video").setup({
        file: 'pathToYourVideoAsset',
        mediaid: 'yourMediaID'
        });
        });
        var jwOoyalaReporter = Ooyala.Analytics.JWReporter("<pcode>", jwPlayer, {
            contentType: Ooyala.Analytics.MediaContentType.EXTERNAL_CONTENT
        });
    </script>
 
For Ooyala assets (hosted in Backlot), you can now view Ooyala IQ analytics metrics for video assets played in third-party video players, such as JW Player. The key steps for enabling IQ analytics metrics for video assets played in third-party video players are:
 
  1. Enable your third-party player to communicate player events to Ooyala IQ by integrating the Ooyala IQ JavaScript SDK with your non-Ooyala video players by using one of the Ooyala out-of-the-box adapters or by building your own adapter.
  2. Make sure that your Ooyala assets are playable on third-party players by checking that your video assets are .mp4 files and that you have the correct encoding profile to allow .mp4 files to be encoded.
  3. Create your third-party player, making sure to reference the URL to your .mp4 video asset, the asset's embed code, and to specify the asset type as mp4.

 

See Getting Started with a Third-Party Player and Ooyala Assets for details on how to get started.
 

Mixed Player Support in Ooyala IQ

If you are using Ooyala players and third-party players to play Ooyala video assets (hosted in Backlot), you can now use one Backlot account to stream video to an Ooyala player and a third-party player. You can view consolidated IQ analytics metrics in one dashboard (through one user account) for both types of players.

 

analytics_v3_mixed_player.png
 

Please note that for third-party assets (hosted in a third-party CMS), you will still need to set up a separate Backlot provider account to ingest asset metadata.

 

 

Infinite Label Scrolling in Ooyala IQ

The Business Intelligence page of Ooyala IQ now supports infinite label scrolling with the "filter by label" feature. We have also enhanced the Business Intelligence page load response time when you have a large number of labels.

 

analytics_v3_infinite_label_scroll.png
 

New Preset Time Ranges in Ooyala IQ

Ooyala IQ now supports the following new preset time range selections:
  • This Year
  • Last Year
  • Last 12 Months

 

Note: For 2016, This Year means 2016-01-01 to today in the provider's time zone, Last Year means 2015-01-01 to 2015-12-31, and Last 12 Months means a date range from 12 months ago to today in the provider's time zone. For example, using 2015-02-10 as "today", This Year means 2016-01-01 to 2016-02-10, Last Year means 2015-01-01 to 2015-12-31, and Last 12 months means 2015-02-10 to 2016-02-10.
 
analytics_v3_year_time_presets.png
 
 

Ooyala Analytics Chrome Extension

The Ooyala Analytics Chrome extension is now available in the Chrome Webstore at https://chrome.google.com/webstore/detail/ooyala-analytics-plugin/kgkibeopmmkehaijmmfhldeclmgbmgnp. You can use this debugging tool to help you to build your own third-party player adapter to work with Ooyala IQ.

 

Ooyala IQ Support for Chromecast Devices

Ooyala IQ now tracks Chromecast device plays. You can monitor Chromecast receiver analytics with the Ooyala IQ API by looking at data for browser=chrome, deviceOs=chromecast, and deviceType=settop. In the Ooyala IQ UI this will be under Device Type > settop > other - Chromecast. In the Player panel, you will see "Chromecast_player" for Chromecast players. Analytics results will vary depending on which cast/play scenario the end user initiates.

This feature was released in January. See Chromecast Integration Analytics for details.

 

Player V3 Bug Fix

We have released a fix for a Player V3 bug where on Android devices, Nexus 5 and Galaxy Note 4, after a pre-roll ad finished, the scroll bar on the video would jump back and forth, blocking a user from seeking through the video.

 

Updated NPAW Desktop Plugin

We have updated the Desktop Plugin of the Ooyala QoS Solution powered by NPAW's YOUBORA Analytics. This release adds support for custom parameters so you can display QoS data filtering on Backlot labels and custom metadata.

 

 

Documentation Releases

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-02-17

2016-02-17 Release

 

Notable contents of this release include version 4.11.0 of the mobile SDKs for iOS and Android and Live bug fixes.

 

 

Software Feature Releases

 

Mobile SDK for Android v.4.11.0

 

New Features and Enhancements

  • The OoyalaPlayer now emits Observable events differently than in the past. Previously, the OoyalaPlayer would emit String objects from the OoyalaPlayer's Observer Notifications. There are now additional notifications that emit the OoyalaNotification class. This will not likely affect your existing code, but if it does, you will need to modify the way you handle the update() method to determine the class of the notification.
  • A new OoyalaPlayer.getPCode() method has been added to the Mobile SDK.
  • Upon reaching the end of playback on a video, the Discovery tray will automatically load the next video.
  • A new OoyalaPlayer.ClickAd() has been added to the Mobile SDK. This method runs the Learn More feature, opening up the browser based on the advertisement being played.
  • The Skin Sample App now includes FreeWheel and IMA functionality.

Resolved Issues

  • There was an issue in which the Nexus 9 Android M would crash while running the player. This issues has been resolved.
  • When using the new Skin SDK, there was an issue in which clicking the Share button resulted in the Share Panel popup, which would continue to pop up even after clicking the back button or elsewhere on the screen. This issue has been resolved.

Known Issues

  • When using the IMA SDK, there is an issue in which an ad will not pause when the user taps the pause button.
  • When using the new Skin SDK, there is an issue in which tapping the volume button causes the scrubber bar and video to play from beginning. In addition, attempting to scrub forward and back causes the scrubber to jump around inconsistently.
  • There is an issue in which loss of connectivity during the playback of an ad causes the player to crash.
  • When using the new Skin SDK, there is an issue in the CC CC On/Off button may not appear.
  • There is an issue in which the Discovery Up Next message covers the Play/Pause button.
  • When using the new Skin SDK, on the Discovery menu, if you click many videos in rapid succession you may crash the application.

 

Mobile SDK for iOS v.4.11.0

 

Resolved Issues

  • There was an issue in which the sharing a link on Facebook or Twitter from fullscreen mode failed to produce a popup to post the link. This issue has been resolved.
  • In the new Skin SDK, there was an issue in which IMA ads occasionally would not play. This issue has been resolved.
  • In the new Skin SDK, there was an issue in which the controls would become unresponsive in fullscreen mode after rotating the device twice. This issue has been resolved.
Known Issues
  • In the new Skin SDK, there is an issue in which the Up Next message may overlap with the Play button.

 

Bug Fixes for the Live Platform

 

The following bugs were fixed in the Live Platform:
  • There was an issue where if there were two users for the same pcode, the second user was unable to start a channel created by the first user. Any users of the same account (pcode) can now log in and start any created channel.
  • There was an issue where starting a channel while impersonating another user caused channels started on that deployment to fail. You can now impersonate (log in) to an account and perform all actions.
Note: These fixes will only work for any channels using the "Ooyala Package" created since the latest deployment. All existing old channels with "Ooyala Package" will not work and should be deleted.
Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-03-04

2016-03-04 Release

 

Notable contents of this release include updates to the Watchlist API documentation and new documentation for stopping unauthorized streams.

 

 

Software Feature Releases

 

Unauthorized Stream Takedown Service

 

Your Ooyala Backlot provider account can be configured to allow you to stop unauthorized streaming in realtime. Then, to stop unauthorized access to an asset as it is streaming, use Rights Locker to delete the entitlement or contact your Ooyala Customer Support Manager to do it for you. The deletion of the entitlement causes stream takedown to occur immediately. See Stopping Unauthorized Streams for details on how this works.
 
 

Documentation Releases

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-03-09

2016-03-09 Release

 

Notable contents of this release include the ability to set presets in Ooyala IQ and a fix to Ooyala IQ metrics for Live assets.

 

 

Software Feature Releases

 

Ability to Save Preset Filters to your Ooyala IQ Account

 

If you save a preset filter in Ooyala IQ, the saved preset will be available to you any time you log into your user account (even if you access your account from another device).

 

 

Ability to Add All Assets when Filtering by Name in Ooyala IQ

 

In the Ooyala IQ Asset panel, when filtering by asset name, you can now select all assets that appear in the search results by simply clicking Add all search results.

 

analytics_v3_filter_name.png

 

 

New Legend for Ooyala IQ Segments Watched

 

In the Segments Watched section on the Ooyala IQ Video Details page, when you hover your mouse over a specific section on the graph, you can now see a legend that displays the time of the video in HH:MM:SS format with a play count.

 

analytics_v3_live_segment_watched.png

 

Fix to Hours Watched Ooyala IQ Metric for Live Assets

 

We have implemented a fix for a bug where the hours watched metric was not reported correctly for live assets in Ooyala IQ for the Flash player. Ooyala IQ currently captures all of the Ooyala IQ metrics and content metadata for live assets except for the following:
  • Playthrough (25%, 50%, 75%, 100%)
  • Average playthrough
  • Segments watched
  • Live asset length

 

 

Documentation Releases

 

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-03-17

2016-03-17 Release

 

Notable contents of this release include new features for Ooyala Live and the release of v.4.12.0 of the mobile SDKs for iOS and Android.

 

 

Ooyala Live v.1.1.0

 

New Features and Enhancements

 

  • The Ooyala Live REST API Reference is now available. This will allow external services to perform create, read update, delete (CRUD) actions for events, channels and schedules.
  • Support has been added for eHLS with a key rotation option.
  • Support has been added for multiple network inputs for a single channel, providing input redundancy.
  • Channel stream versioning is now available, allowing you to use multiple encoders at different times but for the same channel.
  • Every time a channel is started it fetches the profile data. This allows you to update the profile for a channel without creating a new one. This applies to all channels created with Ooyala Live v.1.1.0 and later.

 

Ooyala Live Resolved Issues

 

  • There have been adjustments to the user interface for greater consistency and improved look and feel.
  • The 2GB file size limitation has been changed to 9 EB.
  • There was an issue in which DVR duration for events set by users was not propagating correctly. This issue has been resolved.

Known Issues

  • DVR does not work for HDS event streams.
  • Event lengths have a 4-hour maximum if Live to VOD enabled, and are limited to 8 hrs when Live to VOD is disabled.

 

 

Mobile SDK for Android v.4.12.0

 

New Features and Enhancements
 
  • The OoyalaPlayer now uses the new OoyalaNotification class in Observable events, which work differently than in the past. Previously, the OoyalaPlayer would emit String objects from the OoyalaPlayer's Observer Notifications:
    public void update(Observable arg0, Object argN){ ... }

    In such cases, argN was a String. This has changed, and argN is now an object of type OoyalaNotification. If you would like to maintain the same functionality you have had with strings up till now, you can now use OoyalaNotifcation.getNameOrUnknown(argN), which returns the string that was originally passed:

    public void update(Observable arg0, Object argN) {
        if (arg0 != player) {
          return;
        }
    
        final String arg1 = OoyalaNotification.getNameOrUnknown(argN);
        if (arg1 == OoyalaPlayer.TIME_CHANGED_NOTIFICATION_NAME) {
          ... your code here ...
        }
        ...
    }        
  • The Mobile SDK for Android now provides support for the following types of VAST 3.0 ads:
    • Ads with Icons
    • Skippable Ads
    • Podded Ads with Sequence

 

Resolved Issues

  • When you click Up Next, the UI will display Loading until the video begins to play.
  • There were issues in which the thumb scrubber for the volume and CC On/Off button did not display properly. These issues have been resolved.
  • There were issues in which the Learn More button and Up Next video did not respond to clicks. These issues have been resolved.
  • There was an issue in which the Share panel would pop up after click the back button or somewhere in the screen. This issue has been resolved.
  • When using the new Skin SDK, there was an issue in which tapping the volume button causes the scrubber bar and video to seek. This issue has been resolved.
  • There was an issue in which Up Next did not provide descriptions of upcoming videos. This issue has been resolved.

 

Known Issues

  • There is an issue in which loss of connectivity during the playback of an ad causes the player to crash.
  • NPAW Integration does not currently work with Ooyala SDKs 4.12.0. We are working to resolve this immediately.
  • In the new Skin SDK, Android Fullscreen does not work correctly.
  • In the new Skin SDK, Up Next does not display the title or description on small playback screens.

 

 

Mobile SDK for iOS v.4.12.0

 

New Features and Enhancements

 

  • The Mobile SDK for iOS now provides support for the following types of VAST 3.0 ads:
    • Ads with Icons
    • Skippable Ads
    • Podded Ads with Sequence
  • The default CC On/Off button color has been changed to blue, and is now configurable.

 

Resolved Issues

  • There was an issue in which Up Next did not provide descriptions of upcoming videos. This issue has been resolved.
  • There was an issue in which Freewheel ads and their controls were not properly rendered with the Ooyala player skin. This issue has been resolved.
  • There was an issue in which cue points did not display for all assets and ads would not play. This issue has been resolved.

 

Known Issues
  • In the new Skin SDK, Up Next does not display the title or description on small playback screens.

 

 

Documentation Releases

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-03-25

2016-03-25 Release

 

Notable contents of this release include new documentation for Ooyala Account Token generation.

 

 

Software Feature Releases

 

Ooyala Account Token Generation

 

Access to certain Ooyala services, such as eCommerce and Watchlist, is controlled using an Ooyala Account Token. The Ooyala Account Token API generates an account token to authenticate a user. When calling these APIs, the client is required to provide the account token for authentication. After your application has logged in a user, it calls the Ooyala Account Token API route to get the account token. The account token is valid for a specific amount of time, 15 minutes by default. See Ooyala Account Token API for details on how this works.
 

Ooyala Live Platform version 1.1.1

The following new features and enhancements have been implemented in this release of the Live Platform

  • For channels, support had been added for characters from additional language alphabets.
  • The user interface for the test channel page has been enhanced.
  • There was an issue in which channel creation was blocked. This issue has been resolved.
  • There was an issue in which ingest URLs for channels created before version 1.0.4 were not displayed. This issue has been resolved.

 

Documentation Releases

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-03-31

This release includes the new ability to enforce per-studio limits on concurrent streams and support for Apple FairPlay: http://support.ooyala.com/developers/documentation/relnotes/2016-03-31.html

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-04-04

2016-04-04 Release


Notable contents of this release include added support in Ooyala Live for HLS with Discretix PlayReady DRM.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,250
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

Ooyala Release Notes 2016-04-12

[ Edited ]

 

2016-04-12 Release


Notable contents of this release include a new release of Player V4 and Player V4 documentation updates.

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!