Changes to the Video Cloud Service

Product(s)
Video Cloud
Role(s)
Studio User
Player Developer
API Developer
Device SDK Developer
Topic(s)
General Info
Legacy Studio

This topic gives you advance notice of forthcoming and past changes to the behavior of the Video Cloud service, Video Cloud Studio, or players that may require you to change the way you work with Video Cloud.

Coming Service Changes

  • On May 31, all remaining support for the legacy Studio will be terminated.
  • As of July 1, 2018, the Brightcove Player will no longer support all versions of Microsoft Internet Explorer prior to version 11, including IE 8, 9, and 10. Versions of the Brightcove Player released before July 1 may continue to work on IE 10 and below but we will no longer test on any of those browsers or consider bug fixes specific to those versions.
  • As of July 1, 2018, we will no longer support version 5.9 of the Brightcove Player (and previous versions). Customers who want to make any changes to their players after that time will have to upgrade to a later version. If no changes or support are desired, however, version 5.9 and below will continue to be hosted and will continue to work unmodified.

Past Service Changes

  • On April 1, 2018, all support for the Smart Player was terminated.
  • On December 31, 2017, the read methods of the Media API were fully retired.
  • On June 30, 2017, Brightcove retired the write methods exposed by the Media API (e.g., update_video).
  • On June 30, 2017, Brightcove ceased supporting the FTP Batch Provisioning System and the content ingest methods of the Media API. The Aspera upload method ceased to be supported at the same time.
  • Deprecation of Media API read methods find_videos_by_user_id and find_videos_by_campaign_id. Effective January 31, 2012, Brightcove deprecated support for the Video Cloud Media API read methods find_videos_by_user_id and find_videos_by_campaign_id. These methods were used together with the old Consumer Generated Media module in Brightcove 2. For current best practices for managing user-generated content, see User Generated Content.
  • Deprecation of Media API read methods find_videos_by_text and find_videos_by_tag. Effective December 31, 2011, Brightcove deprecated support for the Video Cloud Media API read methods find_videos_by_tag and find_videos_by_text. We encourage you to use the search_videos method for video searches rather than using the find_video read methods. The search_videos method offers more flexible search and sorting options than the find_video methods, and is especially more flexible than the find_videos_by_text and find_videos_by_tags methods.
  • Flash Player Support. Effective May 15, 2011, Brightcove no longer supports Flash Player 9 for using the Video Cloud Studio or Video Cloud players. Video Cloud Studio users should upgrade to Flash Player 10. Read more about why we're doing this and what it means to you.
  • Content type for Media API responses. The content type for responses returned by the Video Cloud Media API is application/json and not text/html. Using the application/json content type should provide superior security. The change in content type should not affect how any JSON returned in a Media API method is parsed.
  • Error returned by Media API search_videos method for invalid sort_by arguments. If you call the search_videos method in the Media API with an invalid sort_by argument, the error returned currently includes the text of the invalid argument. Calls that include illegal characters (such as <, >, &, \, %, or +) in the sort_by argument will return an error message with the illegal characters escaped.