Known Issues

Video Cloud Studio

• Modules not loading in Chrome. Due to a recent update in the Chrome browser and the built-in version of Flash, publishers using Google Chrome may experience issues with loading modules of Video Cloud Studio, and the Studio may display a "Missing Plugin" error.  
  Workaround. Disable the built-in version of Flash that Chrome, or simply use an alternate browser. For instructions or further information, please submit a support case. 

• User roles. Not all Brightcove Console users can access the Video Cloud Studio. Users with Financial or Production roles are denied access. A Video Cloud Studio Admin user can change these users to the Standard or Admin roles to give them access to the Video Cloud Studio. If you do so, however, the Brightcove Console roles for these users will be changed to either Programmer or Administrator.
  
  If you create a new user in the Brightcove Console, this user will not be enabled for the Video Cloud Studio. Please create all users you intend to access Video Cloud in the Video Cloud Studio.
• Custom domain name with no default viral player. If you try to set a custom domain name for your account, but there is no default viral player for your account, the custom domain name setting will not be saved.
  Workaround: Set a default viral title player for your account first. Then, you will be able to save your new custom domain name succesfully. (BC-17620)
• Japanese and Spanish versions of Video Cloud Studio may conflict with Google Toolbar. If you are using either the Japanese or the Spanish version of Video Cloud Studio while the Google Toolbar is active in your browser, and you switch from the Studio Homepage to a Studio module, the screen may blink and freeze. This seems to result from a conflict with Google Toolbar, which is trying to translate the page, causing the page to continuously refresh.
  Workaround: Disable the Google Toolbar while you use Video Cloud Studio. (BC-20979)
• IE8 Compatibility View required for Search. Searching in the Media and Advertising modules requires Compatibility View to be enabled when using Internet Explorer 8. (BC-22910)

Video Cloud Players

• With Flash Player 11.2, some anamorphic videos and live streams will display with an incorrect aspect ratio. Not known to affect videos that have been transcoded by Brightcove; only source videos used as a rendition and live streams have been affected. The problem appears to be in the Flash Player runtime, and is resolved in the Flash 11.3 beta
• Videos with DRM applied will not play on some versions of Chrome. Viewers using Chrome on Windows 7 will see the video player load, but videos will not load or play. This applies to videos with DRM applied only. This is an issue with Chrome that cannot be resolved by Brightcove. Workaround: use a different browser.
• Users of Google Public DNS and other DNS servers not provided by their ISP may experience slower player loads.  Google Public DNS interferes with the regional IP information that under normal circumstances would resolve to a regional ISP provider when the request is handled by Brightcove's servers.  Brightcove, as well as many of the content delivery networks we work with  (Akamai, etc.), depend on the regional ISP information to direct users to servers closest to their location for ideal performance.  Brightcove has added the Google Public DNS server locations to our system so that we can make a more educated guess at the end users location but, as Google acknowledges, this may not be the closest server they would have resolved to otherwise.
• HEX characters prevent videos from playing HTML5 players. Avoid using HEX characters in the short or long description of their video title because it will break HTML5 and cause the Video Cloud player to not render on non-flash supported devices. (BC-30439)
• autoStart configuration parameter disabled in HTML5 mode. The autoStart configuration parameter is ignored for players in HTML5 mode. (BC-25554)
  
• get code option for LiveJournal does not work. When a viewer clicks the get code option in the viewer and selects the LiveJournal option, the player rejects the viewer's username and password, even if they are valid. (BC-21495)
• playerTag player configuration parameter is not used in reports. A player configuration parameter, playerTag, was intended for use in reports, to enable you to distinguish between separate instances of the same player in different pages. Video Cloud reports do not currently use the playerTag configuration parameter, so this parameter can't be used for that intended purpose.
  
• InPrivate filtering setting in IE8 can be set by users to block videos from loading. Microsoft Internet Explorer, version IE8 and later, allows users to set security settings that block Video Cloud videos from loading. The problem arises from the InPrivate filtering feature in IE. This feature detects and provides the option to block communication between the website a user is viewing and third-party websites. Since a web page that hosts a Video Cloud player needs to communicate with Video Cloud in order to load videos, this means IE users can configure their browsers in a way that prevents Video Cloud videos from loading. This problem arises if an IE user sets the InPrivate filtering setting to  "Automatically Block".
• Full screen issue with wmode. If you add the wmode configuration parameter to a player, and the browser is using Flash Player 9.0.45.0 or lower, Full Screen does not function correctly. Instead of maximizing up to Full Screen, it will only maximize the size of the player template, and upon clicking the 'Exit Full Screen' button, nothing will happen. Workaround: Either omit the wmode configuration parameter or require your viewers to use Flash Player 9.0.115 or later. (BC-15292)
• Spurious Flash 10 upgrade prompt with incorrect JavaScript configuration. If a viewer is using Flash 10 and if the player's JavaScript publishing code contains incorrect code, the player prompts the viewer to upgrade to Flash 9 or later. For a player to use Video Cloud JavaScript APIs, its JavaScript publishing code must include this line:
  <script language="JavaScript" type="text/javascript" src="http://admin.brightcove.com/js/BrightcoveExperiences.js"></script>
  Earlier beta versions of Brightcove 3 used BrightcoveWidgets.js in the JavaScript URL instead of BrightcoveExperiences.js; if you use the correct JavaScript URL in your publishing code, this Flash upgrade prompt does not occur. (BC-14086)

Media Module

Video editing and deleting

• Videos that appear in a manual playlist cannot be deleted. You must first remove a video from any playlists it is associated with before you can delete it. This is the designed behavior.

Playlist editing

• Playlists in the Media module are not required to have unique names. Lineups in the Brightcove Console, however, are required to have unique names. If you create a playlist in the Media module that has the same name as an existing playlist or lineup, you will be unable to edit the playlist as a lineup in the Console.
  Workarounds: Rename the playlist to give it a unique name, or edit it in the Media module rather than in the Brightcove Console. (BC-11369)

Uploading

• 
  When Publishers use the Retain source as a rendition encoding option it may not be compatible with DRM.  Brightcove utilizes Adobes Flash Access to implement our DRM feature, and Flash Access is not compatible with all video source file formats that Brightcove allows customers to use. If an incompatible videos source is uploaded into a DRM enabled Publisher, the symptom would show as the highest rendition remaining in processing.
• Flash Player 10.1 Beta release is not stable for Studio use. The beta versions of Flash Player 10.1, released by Adobe, causes some unpredictable behavior in the Video Cloud Studio.
  Workaround: Do not install the Beta versions of Flash Player 10.1 on a production machine that you want to use to access the Studio. 
• The maximum size for video files you can upload using the Media module is 2 GB.
• If you are uploading files and lose your network connection, the Media module doesn't report back an error. The file that was in the process of being uploaded will not resume uploading if you reconnect to the network. You must cancel the currently uploading file and then the rest of the files in the upload queue will continue to upload normally. (BC-12692)
• If you are uploading a very large file from a network shared drive, your upload may time out before it is complete.
  Workaround: Copy your file to a local drive and start your upload again. (BC-16759)
• Mac OS upload failures with large video files. If you are uploading from a Mac, you should make sure that your machine has at least twice as much available system memory size as the size of the video you are uploading. For example, if you are uploading a 1 GB video file, your Mac should have at least 2 GB of available system memory. (BC-19989)
• If you choose to upload a new Video but the OS file picker does not appear automatically, check to see if your machine is allowed access to the "file selection box". In some organizations where security levels are high, this permission may be disabled. Please contact your internal IT department for assistance enabling this option for your machine.
• Updating FLV files of videos in the Video Files tab of the Media module's Video Editor can result in unexpected failures when using Firefox 3.5.8 and Flash version 10.1.51.95.
  Workaround: Use a different browser or upgrade to a later version of Firefox. (BC-23900)

Image capture

• If you are not able to capture a specific image from your video, you may be experiencing limitations of image capture and flash. The capture functionality can only retrieve a key frame. Normally, this is not an issue, as a key frame is often provided every second or two. When attempting to capture an image from the end of the video, this issue can be more noticeable as there may not be a nearby key frame for the last second or two of the video. You can attempt to go back to a slightly earlier time within the video, say for example five seconds before the end to see if the image capture functionality works.

Adding Playlists to a Player

If you add the same playlist more than once to a tabbed player, additional tabs are added for the duplicated playlists, but these tabs have no content. Workaround: Avoid adding the same playlist to a player more than once. (BC-16014)

Previewing fails with some Macintosh OSX 10.5.x configurations

In certain Macintosh OSX 10.5.x computer configurations, an operating system service appends port 80 to certain requests, which causes those requests to fail. This can cause attempts to preview videos in the Media module to fail. In some cases, upgrading the Macintosh system software to version 10.5.5 has solved this problem.

Previewing may fail with Internet Explorer in full screen mode

Some users may experience issues while using the preview in the Media module with Internet Explorer and in full screen mode.

Workaround: Disable hardware acceleration in the Flash player.
To turn off hardware acceleration, bring the preview player up in the Media module. Right click the player and select settings. At the bottom of the settings dialogue, select the screen icon, which will enable you to uncheck the hardware acceleration. (BC-19718)

Previewing bandwidth is categorized as "Unknown Video"

If you preview a video in the Media, Advertising, or Analytics modules, the bandwidth usage is not tracked under the name of that video. If you run a report in the Video Cloud Studio for Video Bandwidth usage, you will see that bandwidth incurred while playing back video files in preview mode is tracked against a video named 'unknown'. This is the desired behavior, since it helps you separate "real" viewers from internal testing or administration views of your videos. (BC-22916)

Publishing Module

None.

Advertising Delivery

VAST Ad Duration Format

The ad duration returned in a VAST response must be specified in the hh:mm:ss format, as indicated in the VAST specification. If you return the duration as XX, instead of 00:XX:00, then your tracking URLs will not fire at the right time. (BC-25811)

Ad Tag Translators

Ad tag translator SWFs that were developed for AS2 players do not work with AS3 players.

Banner BEML component can cause video ad to play over video content

When a custom BEML player with a Banner component gets a VAST response with a video ad and a banner, the video and the video ad may play simultaneously, with the ad over the video content.

Workaround: A custom BEML player that will be used for advertising with banners should use the ExpandingBanner component rather than the Banner component. (BC-28214)

ExpandingBanner doesn't support fade mode

The ExpandingBanner BEML component has an animationType attribute. The fade value for animationType does not work correctly.

Workaround: Use animationType="expand" instead. (BC-19816)

Ad SWFs should not be used across videos or playlists

Full screen events are not seen by the ad SWF.

Workaround: Use the Flash full screen events instead of using the Video Cloud player's events. (BC-17274)

Click Tag does not work in Flash 9 ad creatives compiled with ActionScript 3

Flash ad creatives written and compiled with ActionScript 3 / Flash 9 will play back in the Video Cloud player. However, the click tag functionality won't work. As such, we don't fully support ActionScript 3 in Flash ad creatives. We do support Flash 9 ad creatives compiled with ActionScript 2.

Internal redirect tag issue in Overlay ads

Do not use redirect tags for creative URLs for the Overlay and Synched Overlay ad formats (BC-24699)

Media API

Error when passing an empty array of videoIDs in update_playlist

If you try to clear all contents from a playlist by passing an empty array of videoIDs in the update_playlist method, the method returns code 100: UnknownServerError (instead of something more informative) and the playlist will not be modified. (BC-17725)

Changed Value for total_count property where get_item_count=false

Previously, in the methods find_related_videos, find_videos_by_user_id and find_videos_by_campaign_id, if you passed null or false for the get_item_count argument, the value returned for the total_count property would be 0. This behavior was inconsistent with the behavior of other related methods. Now, in this circumstance, the value returned for the total_count property is -1. (BC-13332)

MRSS Read methods do not return paths to videos

Universal delivery service enables calling Media Read API methods to retrieve a video's FLVURL field, which is the path to the video itself. However, if you call the Media API to return in MRSS format (using the output=mrss argument), the FLVURL field may not be returned. The FLVURL field will always be returned if you call a Media Read method to return in JSON format (using the output=json argument). (BC-23681)

Using both output=MRSS and fields causes error

In Media API read methods, if you use both the output=MRSS and fields (or video_fields or playlist_fields) parameters in your method call, the method returns a code 100: unknown error. If you want your output in MRSS format, you cannot use the fields parameter to limit the fields returned in the MRSS. (BC-17039)

Read methods returning lists have problems with commas in reference IDs

The find_videos_by_reference_ids and find_playlists_by_reference_ids methods cannot handle reference IDs that contain commas.

Workaround: Avoid using commas in reference IDs for videos and playlists.

Distribution and Feeds

Creating a YouTube distribution channel with a name that is too long fails silently

When you configure a YouTube channel on the Account Settings: Distribution Settings page, the maximum channel name length is 255 characters. If you create a channel with a name longer than this, the channel is not created, but you do not receive a warning message or any other indication of what went wrong. (BC-27522)

Player API

loadVideo issue and new cueVideo Function

The Video Cloud Player API has a function named loadVideo. The intention of this function is to play a video in the video display window of a player. This function allows a developer to initiate playback of a specific video using the custom code. Currently the loadVideo function has a known bug where a video is queued but not played back under certain conditions. We have been made aware that some of our partners may be relying upon this broken behavior to present the video to the user, but not initiate automatic playback. In response, we have added a new API function named cueVideo. This function is nearly identical to loadVideo; however, when you invoke cueVideo the video is presented to the user, but will not automatically play.

The bug in loadVideo has been fixed and as a result, calling loadVideo should in all cases cause the video to begin playback immediately. If you want instead to have the video cued and have the user initiate playback, use the cueVideo instead. If you have existing code that was relying on the bug in loadVideo, you should update your code to use the cueVideo function.

Using system fonts with setRotation and setAlpha

Using setRotation along with system fonts causes any text in the rotated component to disappear. TextLinks using system fonts cannot have their opacity set with setAlpha. (BC-12947)

videoChange event in VideoPlayer Module removed

The videoChange event in the VideoPlayer Module has been removed. For most purposes, the streamStart event can be used instead. (BC-14359)

showIconMenu function in Menu Module replaced by showMenuPage

The showIconMenu function in the Menu Module no longer has any effect, since Video Cloud players no longer have an icon menu. Use showMenuPage instead, specifying the menu you want to display.

Custom Players and BEML (Brightcove Experience Markup Language)

Auto-advance in multi-video player templates

Auto-advance is a player setting that causes a player to begin playing the next video in a playlist immediately after the preceding video completes. If you duplicate one of the standard player templates that supports one or more playlists, the new player template will have auto-advance turned on, and you will not be able to turn auto-advance off in the Publishing module for players made with that template. This issue affects player templates duplicated from the following standard player templates:

• Widescreen with Horizontal List
• Widescreen with Vertical Video List
• Widescreen with Video Text List
• Video Player with Horizontal Video List
• Tabbed Navigation 3.0
• Compact Tabbed Navigation 3.0
• Thumbnail Navigation
• Video Player with Dropdown Navigation
• Widescreen with Dropdown Navigation
• Chromeless Video Player with Tabbed Playlists

To avoid this problem, remove the following text from the List or TileList element in the new player template:

automaticAdvance="true"

(BC-21330)

Embedded fonts do not work in player templates

If you use an embedded font in a player template, the player will not load. Do not use embedded fonts in a player template. (BC-18487)

Avoid white space in XML attributes

In BEML player templates, be sure not to include extra white space in XML attributes. For example, do this:

<element id="foo" />

and not this:

<element id = "foo" />

The extra white space before and after the equals sign in this example prevents the player template from being styled in the Publishing module. 

FTP Batch Provisioning

Deleting Cue Points. When you delete cue points using FTP batch provisioning, you need to provide the cue point's id; providing the cue point's name (as documented) does not suffice and is not necessary. To get the cue point ids of a video, you can use a Media API call like this:

http://api.brightcove.com/services/library?command=find_video_by_reference_id&video_fields=cuepoints&reference_id=[VALUE FOR VIDEO]&token=[READ TOKEN FOR YOUR ACCOUNT]

With the cue point id you retrieve, submit an FTP batch manifest with a line like this:

<delete-cuepoint id="[VALUE FOR CUE POINT]" video-refid="[VALUE FOR VIDEO]"/>

As an alternative, you can delete a cue point using the Media module or Advertising module. (BC-27079)

Video Cloud App SDK for iOS

• Currently searchForRenditionWithLowBitRate() will not work for HLS renditions.
• Unsupported protocols.  The Apple media services do not support all protocols.  For example, the RTMP protocol is not recognized by the Apple player and will throw an NSInvalidArgumentException that must be handled by the application developer.
  Workaround:  If you wish to use streaming videos with RTMP URLs, configure Universal Delivery Service on your CDN, and add the argument media_delivery=HTTP to your Media API calls. Read more about Universal Delivery Service.  (BC-22314)
  
• Incoming calls.  Incoming calls are sent directly to voicemail if a video is in the process of being downloaded.  In addition, declining an incoming call during video playback occasionally causes the screen to go blank.  This is consistent with other iPhone video applications, and may be related to the Apple media framework. (BC-21799, BC-21642)
• Geo-filtered videos.  Geo-filtering settings on videos are not honored in the Video Cloud iPhone player; geo-restricted videos will always play on the device, regardless of the viewers location. (BC-22397)
• findPlaylist* calls from the Video Cloud App SDK for iOS.  You must include videos in the playlist_fields argument to get video fields returned from findPlaylist* calls to the Video Cloud Media API. (BC-22403)

Video Cloud SDK for Android

• Layout issue has been fixed; please download version 1.1.0.

Live Video

If your video stream source is H.264 encoded and you set the video-codec parameter in your FTP batch manifest to H264, viewers receive a unplayable stream. This occurs because "mp4:" gets prepended to the stream name.

Workaround: Set the video-codec parameter to "ON2". (BC-22105)

Media Sharing

Universal delivery service. If the sharer and sharee do not have the same settings for Universal Delivery Service, problems can arise with videos shared with media sharing. If a sharee has UDS enabled but the sharer doesn't, the content will not be available. If the sharer has UDS enabled and the sharee doesn't, the Media API requests for UDS will fail.

Workaround: Enable universal delivery service for both accounts.