Known Issues

Brightcove Studio

• User roles. Not all Brightcove Console users can access the Brightcove Studio. Users with Financial or Production roles are denied access. A Brightcove Studio Admin user can change these users to the Standard or Admin roles to give them access to the Brightcove 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 Brightcove Studio. Please create all users you intend to access Brightcove in the Brightcove 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)

Brightcove Players

• 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 paramenter, playerTag, was intended for use in reports, to enable you to distinguish between separate instances of the same player in different pages. Brightcove 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. The most recent version of Microsoft Internet Explorer, IE8, allows users to set security settings that block Brightcove videos from loading. The problem arises from the new InPrivate filtering feature in IE8. 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 Brightcove player needs to communicate with Brightcove in order to load videos, this means IE8 users can configure their browsers in a way that prevents Brightcove videos from loading. This problem arises if an IE8 user sets the new 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 Brightcove JavaScript APIs in Brightcove, 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

• 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)
• 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.

Image capture

• Image capture for streaming FLV assets may fail intermittently with older Flash player versions, with the image capture tool failing to complete processing. If that happens to you, either upgrade to Flash Player 10 or upload your own images as video stills and/or thumbnails.
• Image capture for remote streaming assets is not supported. 
• Image capture for rtmpe and swf verified assets is not supported.
• 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.

Encoding

We do not currently support uploading files in the .mov DVCPRO HD video file format. (BC-14488)

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)

Publishing Module

Banner and ExpandingBanner components do not display in player preview or style editor

The Banner and ExpandingBanner BEML components do not display in the Publishing module. If you add one of these components to a custom player template, it will function correctly in a published player, but you cannot see the component when you preview the player or edit its styles in the Publishing module. (BC-16842)

Advertising Delivery

Ad Tag Translators

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

DFP Video and Rich Media Ad Tag Translator supports only one ad request per insertion point

The DFP Video and Rich Media Ad Tag Translator does not work properly with more than one ad request per insertion point. When you are setting your ad policies to work with an ad tag translator, set 'Number of ads to play' to 1. (BC-16888)

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 Brightcove 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 Brightcove 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.

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)

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.

Player API

loadVideo issue and new cueVideo Function

The Brightcove 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 Brightcove 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

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.