The account information and management tools in the Brightcove Studio are linked from the Home page in the Studio. From any page in the Studio, click the Home icon, then click the link for the tool you want to use:
In reports, you may get entries like: UNKNOWN PLAYER (ID: -2) -2. An entry like this in the reports means that the player ID parameter was not sent in the tracking event. This can happen if assets are getting played back outside Brightcove players, using a direct URL to the asset. UNKNOWN PLAYER (ID: 265188xxxx)
An entry like this in the reports will occur in a report if:
No. Ad tag translator SWFs that were developed for AS2 players do not work with AS3 players. We've developed
many ad tag translators and many more are available from our partners. For more information, see Integrating your ad server.
Yes; Brightcove can set the Ad Translator at the account level, in which case it is enabled for all of your players, or you can set it at the individual player level.
Yes, but only if your Ad Translator transforms the custom ad into one of Brightcove's supported XML ad formats.
The player ID is sent to the ad server when a default Brightcove DFP ad call is made. You may have been using the player ID previously to target ads in your ad serving system. Now that you have created your own Ad Translator, during ad calls, you can pass any key/value pairs you like to your ad server, and interpret them accordingly. For example, you can add key/value pairs in the advertising settings for a player and then those key/value pairs can be accessed by the Ad Translator. This means you could enter plid=123456 as a key/value pair in a certain player's ad settings in the Advertising module. You could also choose to use a more meaningful key name, now that you have full control, such as player=musicvideos, for example.
You can set cue points using the cue point editor in the Brightcove Studio Advertising module, the Media APIs, or FTP batch provisioning.
Edit your player in the Brightcove Studio Advertising module. Select the Ad Source that matches your ad server or, if you're using a custom Ad Translator, input the URL to your Ad Translator in the appropriate field and save your changes.
Video ad, video pods, banners, and ad SWFs in the VAST formats, and video ad, video pods, banners, overlays, overlay pods, and ad SWFs in the Brightcove formats. Takeovers are not yet supported. See Supported Ad Formats for more details.
Brightcove is not an ad server, however we have heard from our customers that they would like an easier way to host video ads in general.
Unfortunately, all ad servers have not caught up to video yet, and some of them do not support hosting of video. Those that do host video are sometimes costly.
While Brightcove does not provide the comprehensive tracking and reporting that an ad server or network can provide, there are a few ways that you can leverage your Brightcove account to deliver video ads if you are looking for a simple and quick solution:
You can use the Advertising module to:
The Advertising module is a user-interface module that provides ad policy management features. It is designed for advertising operations users in your organization who need to manage advertising policies and ad requests for your Internet TV content.
You can set the ad server URL at the account level, at the player level, or in a config parameter in the player's publishing code. The value set in the publishing code will override the value set at the player level, which in turn overrides the value set at the account level.
There is no single listing of uploaded assets in the Media module, as there was in the Brightcove Console. You can, however, access thumbnails, video stills, logo overlays and bumper videos that you created in the Console. When you edit a video's properties, you can access lists of the appropriate asset type to assign as images, bumpers or logo overlays to your videos.
Yes, you can view and edit titles you create through batch upload as videos in the Media Library in the Media module. You can also manage videos you add using the Media API create_video method.
Reporting on dynamic delivery renditions is not available in this release of Brightcove. You can get reports by video, but these are not broken down by rendition.
In this release of Brightcove Studio, you can view a video's dynamic delivery renditions in the Details pane of the Media module and you can replace all renditions with a single video file, but you cannot replace multiple renditions using the Media module. You can do so using batch provisioning.
Brightcove offers three different methods for uploading videos to your Brightcove media library:
You can use the Media module to bookmark your most-used playlists as favorites in your account. You should use favorites for playlists that you edit frequently, so that you can drag and drop videos from your media library into these playlists. This is an account-wide setting, so other users in your account can have an impact on your favorites list.
A playlist is an ordered group of videos. A playlist can be a manual playlist, to which you explicitly assign videos, or a smart playlist, which is constructed automatically based on video tags or other video properties.The term playlist replaces the term lineup, as used in the Brightcove Console.
A video is composed of a video file, some metadata (such as a name, short description, tags, scheduling information, etc), and potentially some images (such as thumbnail or video still) or a bumper. The term video replaces the term title, as used in the Brightcove Console. In the Brightcove Studio workflow model, you no longer need to create a set of assets and assemble them into a title, as you did in the Brightcove Console.
Multi-bitrate streaming improves a viewer's experience by enabling you to deliver videos with the resolution and bit rate that best matches the viewer's connection speed. When you upload a non-VP6 video file, you can choose for Brightcove to transcode your master video file into six different VP6 or H.264 files, each with a different bit rate and size. The Brightcove player automatically selects the highest quality rendition that the viewer's download connection speed can support, taking into account the rendition's resolution and bit rate. In previous releases, we referred to as "dynamic delivery."
The maximum file size for videos you upload with the Media module is 2 GB. To upload larger files, use FTP batch upload.
Brightcove players can play back VP6 (FLV) or H.264 (MP4) format files. When you upload a non-VP6, non-H.264 source file, Brightcove transcodes the file into your choice of VP6 or H.264. When you upload an H.264 file, you can choose to leave it as H.264 or have Brightcove transcode it to VP6.
You can upload video files in these formats: 3g2, 3gp, asf (streaming for Windows Media Player), avi, dv, flv (VP6), mov (QuickTime multimedia), mp4 (H.264), mpeg, mpg (MPEG-1 and MPEG-2), qt (QuickTime), wmv (Windows Media Video). Video files must be no larger than 2 GB.
You can use the Quick Video Publish feature in the Media module to quickly publish a single video. Using Quick Video Publish, you select a video in the Media module, click a link, and immediately get the publishing code you need to publish the video in a single-video player in a web page.
Changes you make to your playlists details in the Media module go live immediately after saving your playlist. If you are adding or removing videos from existing playlists using drag-and-drop, then the changes go live immediately.
Anamorphic widescreen uses rectangular pixels to store a widescreen image to standard 4:3 aspect ratio. So, while the image looks like a widescreen 16:9 video, its true aspect ratio is 4:3. When Brightcove transcodes your videos, we maintain the same aspect ratio as the source file. However, if you want a 16:9 aspect ratio, you need to make sure that your source video uses a true 16:9 aspect ratio, and not an anamorphic 16:9 aspect ratio, which will be transcoded as 4:3.
The preview feature in the Media module is strictly a preview of the video file. The video preview does not include the logo overlay or bumper applied to the video.
We no longer offer the iFrame publishing code option for AS3 players. Please choose from one of the other more robust publishing code types, like JavaScript.
You cannot access the AS3 Players you create in the Brightcove Console.
If you were a Brightcove customer before the release of Brightcove 3, you can access your Brightcove AS2 players in the Console. Your AS2 players will not appear in the Publishing module.
No, your default viral player must be an AS3 player.
Once you've created a player, you can assign one or more playlists to it, using the Media module. See Assigning Content to Players. If your player template doesn't accept playlists, you can assign a video to it using Quick Video Publish or assign content to the player programmatically by editing parameters in the publishing code for the player and specifying the video ID property of the video you want to play. See Assigning Content to Players Programmatically.
You can use the Brightcove Studio to select a single-video AS3 player to be the player used when a virally syndicated video from your account is played back. Set the default viral player in the Account Settings page of the Brightcove Studio.
You can use the style editor in the Publishing module to change the look and feel of every visual component of a Brightcove player. In addition, if you are a Brightcove Pro or Enterprise customer, you can create custom player templates, which offers you a much richer, more powerful scope for customizing players. A custom player template can let you create a player with an enormous variety of combinations of layouts, usiing standard or custom-developed components.
The Brightcove Studio Publishing module is a user-interface module that improves and replaces the video player design and management features of the Brightcove Console. The Publishing module gives you the ability to style the out-of-the-box or custom player templates in a highly interactive and user friendly model. Players created in the Publishing module leverage the AS3 technology to achieve faster performance and a richer, more flexible viewer experience. Using pre-defined components or custom components you develop, you can assemble unique player templates with powerful features.
You can use the Publishing module to choose one of the many standard player templates for your players. In addition, if you are a Brightcove Pro or Enterprise customer, you can create custom player templates and add them your account.
Media API method calls are made by HTTP requests, similar to web services calls.
To get started with the Media API, you need the API tokens that authenticate your requests. If your Brightcove account was created after the Brightcove 3.3.2 release (August 27, 2009), a read token and a read token with URL access were automatically generated for you when your account was created. If your account was created before that, or if you need a write token or other additional tokens issued to you, contact Brightcove customer support.
Media sharing is a feature available only to Brightcove Enterprise publishers. Media sharing enables you to take videos in your Brightcove Media Library and add them to the Brightcove Media Library of your affiliates. You can use media sharing either with the share_video method in the Media API or with the batch provisioning feature.
The Media API methods can deliver their output in JSON or Yahoo's Media RSS (MRSS) format.
Because Media API method calls are made in the form of HTTP requests, you can use the Media API with any language, client-side or server-side, that supports making HTTP requests. And what language doesn't? This release provides examples of how to use the Media API with Java, JavaScript, ActionScript, and PHP. Brightcove-savvy developers have created SDKs for Java, PHP, and .NET, which will make the Media API even easier to use. Search the Forum for more information.
The Media API is a REST-based set of functionality for interacting with your Brightcove Media Library. It provides read methods that let you access the metadata of your videos and playlists, and write methods that let you create, modify, or delete videos or playlists.
Yes, contact us via the feedback form and we can discuss the options available from our professional services team.
BEML is a Brightcove feature that enables development of custom player templates. BEML stands for Brightcove Experience Markup Language. It uses XML to specify a player template. Using BEML, you can combine standard and custom player components into practically infinite different possible layouts and customize the colors, themes, and behavior of each component. After you add a BEML player template to your account, you can use the Publishing module to create and configure instances of your custom players.
Players are collections of components, like video displays, navigation and advertising units. The Publishing module is a UI tool for creating players for you to publish on your site. The Player API allows you to extend your players and customize them further, integrating them with other services like reporting and ad servers, and adding your own UI.
The Player API is an ActionScript 3-based set of functionality for building player UI on your websites. The framework allows for more flexibility in UI by allowing you to assemble modules, like navigation and consumer tools, to your specifications. And because it's built using ActionScript 3, the performance is greatly improved.