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

2014-08-13 Release

2014-08-13 Release
Notable changes include information on the upgraded Android SDK and the release of the Android and iOS SDKs v.2.7.0.

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-09-08 Release

Adding 2014-09-08 Release Notable changes include the new Tinypass integration and the change in location of the documentation PDFs from the SDKs tab to the Documentation tabs.

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-09-16 Release

[ Edited ]

Adding 2014-09-16 Release Notable changes include the release of the Ooyala mobile SDK for iOS v.2.7.1 and a documentation update to Player V3 error handling.

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-09-22 Release

Adding: 2014-09-22 Release Notable changes include the Ooyala Chromecast HTML5 player and an update to what videos will appear in published Theme Builder playlists.

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-10-13 Release

[ Edited ]

Adding: 2014-10-13 Release Notable changes include the release of v.3.0.0 of the iOS and Android mobile SDKs.

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-10-27 Release

2014-10-27 Release

 

Notable changes include the release of anonymous proxy controls and the
adRequestTimeout Flash parameter.

 

Software Feature Releases

 

Anonymous Proxy Controls

 

Ooyala content protection now adds the capability of Anonymous Proxy Controls through
the detection and restriction of anonymous proxies used in accessing content. When
enabled for a specific account, anonymous proxies are detected and selectively
restricted through Syndication Controls in Backlot. This new Ooyala content
protection product offering supports:

  • Detection and identification of anonymous proxy connections.
  • Prevention of users with anonymous internet proxy service attempting to gain
    access to content by spoofing their IP addresses to explicitly circumvent
    blacklist and whitelist policies to change/obfuscate their geolocation.
  • Leveraging Neustar Anonymizer proxy identification and restriction
    methodologies, identify the level of risk associated with the user
    connecting via proxy service and based on that risk determine the decision
    to (not to) block/prevent the user from accessing video content.
  • Leveraging Neustar Anonymizer proxy identification and restriction
    methodologies enforcement of anonymous proxy detection/prevention is
    configurable within Backlot’s Syndication Rule. In an advanced mode,
    granular levels/statuses may be setup to allow for a specific status to be
    categorized for restriction:
    • Private
    • Active
    • Suspect
    • Inactive

Using Anonymous Proxy Controls you can devise a trusted party syndication
strategy where you add granular control over who accesses content and where it is
published from. This feature is available to all Ooyala customers as part of regular
Ooyala platform license for no additional cost.

You can set anonymous proxy
controls in Backlot:


http://support.ooyala.com/documentation/tasks/publishing_rules_create.html

 

adRequestTimeout Parameter

 

adReqeustTimeout is a new Flash parameter for Google IMA ads that enables the
customization of the time taken, in milliseconds, to make a timeout for the ad
request and continue the video playback.

 

Google IMA Ads Embedded Parameters

 

Documentation Release Items

 

 

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!
Community Manager
Posts: 88
Registered: ‎04-08-2014

2014-11-03 Release

2014-11-03 Release

 

Notable changes include the release of v.3.0.1 of the Ooyala mobile SDK for iOS.

 

Software Feature Releases

 

Ooyala Mobile SDK for iOS v.3.0.1

 

Bug Fixes

 

Release 3.0.1

  • The Learn More button rendered in the middle of the player, or duplicate Learn
    More buttons appeared.
  • Google IMA mid-roll ads did not play when the user forwarded the video using
    the scrubber.
  • Asset resume did not occur after a Freewheel mid-roll ad played.
  • Freewheel ads resume playback automatically, when the application is unlocked or
    resumed.
  • Console logs file are generated multiple times for the duration of the playing
    video content.
  • Video audio continued to play when the asset was dismissed via “Back” button
    navigation.

Release 3.0.0

  • Pre-roll ads did not appear in landscape view mode.
  • Playback crashed for some advertisements in Apple TV mode, using iOS 8.

 

Known Issues

 

The following known issues will be resolved in a future release:

  • In some cases, when the user is watching a Freewheel served ad and clicks the
    Learn More button in horizontal orientation, and then returns to the video, the
    video is presented in portrait mode.
  • In some cases, when the user is watching a Freewheel served ad with the “Learn
    More” button in Landscape mode and switches to portrait mode, the “Learn More”
    disappears temporarily until the user changes the device orientation again.
  • The "Learn More" button is not clickable on Google IMA SDK Ads due to a bug with Google IMA SDK.

 

Documentation Release Items
 
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."
Posts: 1,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-11-10 Release

2014-11-10 Release

 

Notable changes include the release of v.3.1.0 of the Ooyala mobile SDKs for iOS and
Android.

 

Latest Release Notes: Mobile SDK for Android v3.1.0

 

New Features and Enhancements

 

This release includes the following updates:

 

  • Spanish language prompts are now supported for FreeWheel pre-roll and mid-roll
    ad prompts.
  • Japanese language prompts are now supported for FreeWheel pre-roll and mid-roll
    ad prompts.
  • The latest VisualOn release is now supported. This release supports Android 5.0,
    AKA Lollipop and includes new licensing. Make sure you follow the integration
    steps carefully to integrate the new license into your application.
  • FreeWheel SDK version 5.16 is now supported.
  • The Google IMA SDK sample application is updated.

 

Resolved Issues

 

This release includes the following resolved issues:

 

  • The native MediaPlayer sometimes throws the following error:

    "Media server died!", which is error(100, 0)
  • Google IMA SDK is logging too frequently.
  • When the player goes to fullscreen mode a new fullscreen controller is
    created.
  • Plays from an Android device are logged as "invalid host" in Backlot
    analytics.
  • The FreeWheel ad player lock and unlock features is not work properly.

 

Latest Release Notes: Mobile SDK for iOS v3.1.0

 

Updates and Enhancements

 

This release includes the following updates and enhancements:

 

  • This release includes support for armv7s architecture in the SDK
    library.
  • Spanish language prompts are now available for FreeWheel pre and mid-roll ad
    prompts.
  • Japanese language prompts are now supported for FreeWheel pre and mid-roll
    ad prompts.
  • The SDK libraries now support ARM64 architectures.
  • The Google IMA SDK sample app is updated.

 

Resolved Issues

 

This release resolves the following issues:

 

  • armv7s architecture support was not included in the SDK library.
  • When Rotating from landscape to portrait and calling
    [setFullscreen:NO] during an advertisement, the Learn
    More button sometimes disappears.
  • The Learn More button sometimes disappears after any device orientation
    change.
  • Google IMA SDK pre-roll, mid-roll, and post podded ads are not played when
    expected and the ad images do not appear correctly.
  • Airplay playback is paused when the device is locked.
  • Asset audio continues to play after the app Back button is activated.
  • The asset progress bar continued to appear in fullscreen mode for live
    assets.
  • FreeWheel mid-roll ads not playing properly.
  • Analytics are not accurate for plays from iOS devices.

 

Known Issues

 

This release resolves the following issues:

 

Apps sometimes crash when AirPlay is activated.

 

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-12-04 Release

2014-12-04 Release

 

Notable changes include the migration from Google IMA 1.x and 2.x to Google IMA v3,
new Flash player parameters, and a mobile SDK release.

 

Ooyala Mobile SDK for Android v3.2.0

Updates and Enhancements

 

This release includes the following updates and enhancements:

  • The SDK is now configurable for custom VisualOn library versions. For more
    information see Overriding the Default VisualOn Library.

  • The SDK now includes support for X86 libraries to improve performance with Intel
    based Android devices and the VisualOn integration libraries.

  • Player controls are now configurable for all ads, including
    Google IMA ads. For more information contact your CSM.

  • Freewheel ads cue points are now configurable for more information see
    FreeWheel Cuepoint Markers.

Resolved Issues

The following issues are resolved in this release:

  • The playAd method was missing from the SDK
    is now resolved.

  • The player continued to play an asset after the pause button
    was activated and shown as active in the player.

  • Google IMA SDK ads did not play in the proper sequence after
    a seek event.

  • IMA SDK ad asset list sometimes appeared on the screen when the scrubber bar is
    hidden.

  • Video playback reset if no pre-roll ads were configured for the asset.

  • The PlayAd method was not working properly as of SDK release
    3.0.0.

  • The setEmbedCode from a
    TIME_CHANGED_NOTIFICATION created an app crash
    issue in SDK release 3.1.0.

Known Issues

Please review the following known issues:

 

  • Google IMA SDK ad assets sometimes to not play properly when
    the skippable ad option is invoked.

  • The sequence of Freewheel ad assets changes on Android Nexus
    5.

  • VisualOn integration videos restart when switching between
    fullscreen and normal view.

  • When a pre-roll ad is played the
    AdStartedevent occurs before the
    PlayStartedevent.

  • VisualOn integration videos sometimes do not resume after a
    seek even in fullscreen mode.

  • Users are unable to seek after switching to fullscreen mode
    for VisualOn integration videos.

  • Freewheel ads continue to play after a pause event is
    triggered.

Ooyala Mobile SDK for iOS v3.2.0

 

Updates and Enhancements

 

This release includes the following updates and enhancements:

  • The Getting Started sample app is updated for the ARM64
    architecture.

  • The PlayAd method is now exposed to allow dynamic ad insertion during playback.
    For more information contact your CSM.

  • Player controls are now configurable for all ads, including
    Google IMA ads.

  • Freewheel ads cue points are now configurable.

  • The iOS Mobile SDK is updated to support the Freewheel 5.18
    libraries.

Resolved Issues

The following issues are resolved in this release:

  • Post-roll ads did not play properly on AirPlay.

  • The video gravity could not be changed for ads.

  • Freewheel ad overlays appeared but did not persist as expected.

  • Post-roll ads did not play properly after the app was closed
    and restarted.

  • Google IMA SDK poddable ads sometimes did not play properly
    after a device lock event during a previous ad.

  • Google IMA SDK ads did not play in the proper sequence after
    a seek event.

  • Video casting display presented unexpected behavior on Chromecast after wireless
    connectivity stalled or failed.

  • Files were missing from the SDK DefaultControlSource folder.

Known Issues

Please review the following known issues:

 

  • Google IMA SDK assets continue to play on iOS 8 devices
    after the app is closed.

  • Google IMA SDK asset audio (no video) continues to play on
    iOS 8.1 devices after the scrubber is pushed to the end.

  • Freewheel ads are sometimes distorted in landscape
    mode.

Google IMA Migration

 

We are deprecating and deactivating versions of the
Google IMA SDK prior to IMA3.

 

Deactivation of deprecated Google IMA SDKs

The current supported IMA SDK version is IMA3 for both Flash and HTML5. The IMA2 Flash
and IMA1 HTML5 SDKs not only do not support the current full DFP and AdX feature set,
but are also officially deprecated and no longer actively maintained or supported by
Google's engineering team. As such, the IMA2 and IMA1 SDKs are no longer recommended for
use by any publishers. After 12/31, the IMA2 and IMA1 SDKs are planned to be fully
deactivated; Google will remove the IMA2 and IMA1 SDK files from hosting, and all
players integrated with the deactivated SDKs will cease to request or render ads. To
continue serving ads uninterrupted, all players with IMA2 Flash or IMA1 HTML5 SDK must
be upgraded to IMA3 SDK prior to the deactivation date.

 

Note: This does not affect the
HTML5 player and Ooyala iOS and Android SDK apps.
 

Where is IMA SDK version assigned?

 

The version of IMA SDK integrated with
players is determined by the following settings in Backlot.

Backlot → MONETIZE → Ad
Sets → Ad Source.

 

An older version of IMA SDK is loaded on the Flash and HTML5
players when the following Ad Sources under Ad Sets is selected in Backlot:

  1. DoubleClick
  2. DoubleClick Overlay
  3. AdSense For Video Instream
  4. AdSense For Video Endcap
  5. AdSense For Video Overlay

The correct version, IMA SDK3, is loaded on the players when the following Ad
Source under Ad Sets is selected in Backlot:

  • Google IMA V3

DoubleClick and AdSense ads will still be supported via the Google IMA V3 Ad
Source using the ad tag.

 

How to change IMA SDK to latest version?

Please contact your Customer Success Manager and Ooyala Technical Support for migration
instructions. You need to migrate all of your Ad Sets to use the latest and correct Ad
Source, Google IMA V3, to avoid playback problems from using deprecated or non-supported
versions of Google IMA.

 

This migration cannot be done programmatically on the player
because we will not be able to test or validate all customer specific integrations
and edge cases. The player is designed to automatically load the latest IMA V3 SDK.
However the setting via Ad Sets in Backlot overrides the player version. Hence, the
change needs to be made on Backlot to ensure that correct version of IMA module is
loaded on the players.

 

Our recommendation is for you to work with Technical
Support to make the switch on a test player, verify the change across their ad sets
and ad rules, and then make the switch to the correct Ad Source in production. The
Technical Support team will be able to help migrate large ad sets for customers.
This process is automated to ensure accuracy and efficiency.

 

Other Deprecations

We no longer support cuepoints for Google IMA.

 

Ad Rules for Flash

Note: Ad rules are only available for Flash.
 

Youcan set ad positions for Google IMA though DFP ad rules, which can be enabled to
correctly render for an ad with the Backlot UI or Backlot API. The steps
to integrate with DFP can be found at Monetizing Your Ooyala Content with DFP

 

Feature Release Items

 

New Flash Player Parameters

 

  • showAdMarquee - specifies whether to show or hide the ad marquee
    during ad playback. If showAdMarquee is missing or set to true, the ad marquee
    will appear while an ad is playing on your player. This global parameter works
    for all ad types supported by Ooyala. For more information, see Embedded Parameters
    Note: This parameter is for Flash only.
  • Another parameter you can set is useStyledNonLinearAds, which shows
    a close button for non-linear ads when set to true. This parameter is optional -
    by default the button to close an ad is shown for non-linear ads. For more
    information, see Google IMA Ads Embedded Parameters
    or Google IMA Ads Integration Guide.
    Note: This
    parameter is for Flash only.

Documentation Release Items

 

  • Support Site Reorganization
    • The MRSS validator link is moved from the SDK Mobile and Client SDK
      support page. The link is now included in the “Validating MRSS Feeds”
      topic.
    • The SDK Mobile and Client SDK support page is updated. The page now
      includes links to the release notes and the supporting documentation.
    • Removed Social Integrations links from the SDKs tab. Twitter
      and Facebook documentation can be found on the DEVELOPERS tab in
      the Social Integrations Developer Guide.
    • Removed the Scratchpad link from the SDKstab. Links to the scratchpad can be found
      at The Scratchpad.
    • The Integration Guide on the DEVELOPERS tab has been broken apart into
      individual guides, including Ooyala Mobile SDK Developer Guides, Ads
      Integration Guide
      , Device
      Integration
      Guide, Third Party Paywall Integrations, and Social Media Integration Guide. These guides are now shown
      at the top level of the navigation of the DEVELOPERS tab for increased
      clarity.
  • Google IMA Migration to V3
    • Embedded Parameters--
      Removed reference to the “google” AdSense parameter. AdSense ads can be
      used by inserting an AdSense ad tag url into the Google IMA V3 ad source
      when creating an ad set.
    • Monetizing Your Ooyala Content with DFP -- Added
      instructions on how to enable DFP ad rules for an ad set via Backlot UI
      and API.
    • Creating Ad Sets for Integrating with Ad Sources -- Updated Google AdSense ad source to Google IMA
      V3.
    • Supported Ad Networks -- Updated the
      supported ad networks to show that AdSense and DoubleClick are supported
      via the Google IMA V3 ad source.
    • Ad Set Fields for Google IMA V3 --
      Updated the topic to note that you can use AdSense and DoubleClick ads
      through the Google IMA V3 ad source with the ad tag url. Added caveat
      that ads that use Backlot settings will be loaded dynamically before the
      ad position as determined in Backlot. Google IMA does not provide
      functionality in IMA v3 that allows us to queue ads for pre-fetch.
    • Ad Sets -- Added a note that the
      ad_type cuepoint is no longer a valid value for the Google IMA V3 ad
      source. Removed DoubleClick and AdSense from valid ad source values in
      Backlot API. Added a new ad_type “rules” (Google IMA V3 only).
    • Google IMA Ads Integration
      -- Added information about the Google IMA migration to V3.
    • Google IMA Ads Integration Guide -- Added
      information about using ad rules via DFP because cuepoints for Google
      IMA are deprecated. Removed cuepoint section, added note about using ad
      rules instead via DFP. Added instructions on how to enable DFP ad rules
      for an ad set via Backlot UI and API.
  • VAST Ad Set Integration Guide
    -- Added instructions on how to implement VAST companion ads.
  • New Flash Player Parameters
  • Localization--Added a
    list of valid inputs for the "locale" player parameter for Flash and HTML5.
  • Debugging/Troubleshooting Extension for Chrome--Added
    content regarding the modes of operation in the debugger and how to debug your
    own site.

 

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,224
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2014-12-17 Release

[ Edited ]

2014-12-17 Release

 

Notable changes include Google IMA improvements for the HTML5 player and the release
of the mobile SDK v.3.2.1 for iOS and Android.

 

Mobile SDK for Android 3.2.1 Released

 

Updates and Enhancements

 

  • The SDK now includes new SecurePlayer libraries for Playready
    playback on Android L devices.
  • The SDK API documentation in now found in the SDK APIDocs
    directory.

Google IMA Improvements for HTML5

 

We now have increased support for Google IMA for desktop and mobile.

 

New Parameters for HTML5

adRequestTimeout, showInAdControlBar, and showAdMarquee are now supported for
Flash and HTML5 for the Google IMA module.

 

 

Ad Rules

Ad rules are now available for Flash and HTML5. To view what ad positions are now
supported per platform and browser, see Google IMA Ads Integration.

 

You can set ad positions for Google IMA though DFP ad rules, which can be enabled
to correctly render for an ad with the Backlot UI or Backlot API.
 
The steps to integrate with DFP can be found at Monetizing Your Ooyala Content with DFP.

Note:
Google IMA's AdRules feature supports ad-breaks without additional code. Do not use
AdRules with other types of ads. We highly discourage you from mixing other
adTagUrls with an AdRule adTag as it may lead to unexpected behavior. For
example, we recommend against using an AdRule adTag along with a mid-roll ad
position set via Backlot.
 

Known Issues

  • The rewind button is disabled for iOS8. We are aware of this
    issue and are working on a solution. In the meantime, please seek using the
    progress bar to “rewind” a video.
  • For iPhone with iOS7, after completely finishing a video if
    you select a second video to play the player will crash. The issue will
    manifest if you change the video stream type outside of iOS native player.
    This is due to an underlying iPhone iOS7 issue. We will not be fixing this
    issue.

 

Reminder: Google IMA Migration

 

This is a follow up to our previous messaging regarding Google’s plans to deactivate
IMA v1 and IMA v2 SDKs.

 

Deactivation of deprecated Google IMA SDKs

Google will be deactivating IMA v1 and IMA v2 on December 31, 2014. On this date,
all players integrated with IMA v1 or IMA v2 will cease to request or render
video ads, and may fail to play content.

 

We recommend you begin your migration to Google IMA v3 immediately, especially if
you are a heavy user of IMA Ads and Ad Sets. This will provide adequate time to
perform the necessary testing and validation to ensure a successful migration
before Google deactivates IMA v1 and IMA v2 at the end of this month.

 

Please don’t hesitate to contact us at http://support.ooyala.com/contact if you have any questions or concerns.

 

How can I change the IMA SDK to the latest version?

Please contact your Customer Success Manager and Ooyala Technical Support for
migration instructions. You need to migrate all of your Ad Sets to use the
latest Ad Source, Google IMA V3, to avoid playback problems from using
deprecated or non-supported versions of Google IMA.

 

Discovery Updates

 

The Discovery API is updated to identify the bucket_info version.

 

Documentation Release Items

 

 

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!