Online Video Platform

Note: Our latest version of the online video platform is currently available for everyone, but customers with interactive videos can still use the old interface with Timeline by deselecting "Use new interface" on the login screen. After login, there is a switch button available in the top right menu on both interfaces.

If you experience any issues, please contact us at

Quick Start Guide

If you haven't used the Blue Billywig Online Video Platform (OVP) before, this is what you should know:

The OVP is a tool for publishing video and audio. You upload media files by simple drag-and-drop. While they are being processed, you do the bookkeeping, giving the media clips a name, a description, keywords, etc. Then, grabbing a playout -- a player customized to your needs --, you publish them on your website using an "embed code".

That -- in a nut shell -- is the basic workflow.

Of course, the next day, you think of a better title for your video clip. So you need to locate it in the OVP, perhaps among thousands of other clips uploaded by your peers. Luckily, typing a word from its title, or description, or keywords in the search box helps you out, and in an instant your changes can be online.

You can read more about searching in Media Clip Search.

But maybe we should take a step back. You might first have questions about the process of logging in. That is covered in the section Authentication and Login.

Then, as it all starts with content, the section Uploading and Encoding may be helpful. The system will transcode your media into several Assets.

After you've supplied the basic meta data (name, description, tags) you might need extra fields specifically tailored to your situation. The section Custom Meta Data Fields explains how.

Or you might directly want to publish the clip (Publishing and Status) and put it on your web site (Embedding) using a Playout.

Ad services

With our ad services proposition you can manage all (video) ads that are played through our platform.

Ad units

Ad units are at the base of our platform's ad services and define your inventory. They are the positions where you could show a (video) ad. The times that the player reaches the ad unit (with or without showing an ad) is called inventory.

The connection to the ad system through the VAST URL is managed in line items (more about these later), which you can target to one or more ad units. In our system there are three types of ad units.

By default all the player controls are turned off during commercials. With the options "Show Play/Pause button" and "Show Mute/Unmute button" you can allow these simple controls to be shown. Enter text in "Text Commercial Time Remaining" to show a countdown prefixed by this text. These ad unit settings can be overruled per line item by settings the "Disable controls" option in the line item.

When "Allow skipping" is enabled the user will be able to skip the ad after the specified amount of seconds. You can also alter the text that is displayed during the countdown and the text that is used in the button to skip the ad. Please note that our player respects the DfP setting "skippable" even when the "Allow skipping" setting is disabled in our system.

By default an ad unit code is generated from the title replacing any non-word characters with underscores. This code will be used in the embed tag (for embedding outstream formats) and in our analytics.

In-stream ad units

In-stream ad units define positions before or after media and are always linked to either a playout (all media playback through that playout) or a mediaclip (one on one advertising). In the position overview you can manage all the playouts (and soon mediaclips) which can run instream ads.

The various options for in-stream ad units are explained below.

Playout or mediaclip

Select either a playout or a mediaclip to define where the ad unit will run on. If there are two ad units targeted (one for a playout and one for a media clip), the media clip ad units will overrule the settings of the playout.

Commercial behaviour

The setting "Commercial behaviour" can be best understood imagining the player is started of with a playlist.

  • If you choose "Once per load", only the first clip in the playlist will show a pre-roll commercial. Then, if in the exitscreen a related clip is clicked, a new clip is loaded into the player. Hence, another pre-roll commercial will be shown.
  • If you choose "Once per session", only the first clip in the playlist will show a pre-roll commercial. Subsequent loads of clips or clip lists do not. (until you refresh the page)
  • If you choose "Once per clip", each clip in the playlist will show a pre-roll commercial. Subsequent loads of clips or clip lists will too.

Minimum clip duration

Enter a number in seconds. This allows you to set a minimum duration of the media clip in order for the ad unit to be allowed to run. Example: If you set this to 30 seconds, no ads will run on media clips shorter then 30 seconds.

Out-stream ad units

If the inventory from in-stream ad units is not sufficient or you want to increase your inventory you can make use of our out-stream formats. At the moment we support three different types of outstream formats: The inArticle (or inMenu), the inOverlay and the pre-content. Please refer to our outstream suite for more information about these.

The various options for out-stream ad units are explained below.

In and out view

The in and out view option plays or/and unmutes the video when the video player scrolls into or out of the current view. For example, a player is embedded halfway through an article but is not visible directly when the user arrives on a page. When the user scrolls down to read more of the article, the player comes into view and can start playing.

Force in and outview actions

Some mobile devices, like an iPhone, don't support inline playing of video by default. The configured in and out view actions are disabled by default on those devices. If you are sure you want to enable them, you can do so by enabling the "force in view actions" option. Exceptions are assets encoded using our "image sequence" profile, which can be player inline on an iPhone, and where view actions are not disabled by default.

Also see:

Block insecure HTML5 VPAID ads

If this setting is enabled in the line item or the ad unit, it will force ads to run in a secure iFrame disallowing page access using javascript.

Preload line items

This option allows you to start calling all VAST URL's in the line items at the first user interaction in order to enable faster playback once the user arrives at the player position. Without this option enabled the first VAST call will be done when the player is "InView".

Placement option

By default the player will be placed at the position of the script element. With this option you can place the script on the bottom of the page and find the proper place on the page using the "DOM Selector".

Placement DOM selector

The DOM Selector allows you to find an element that will be used by the placement option. This selector uses jQuery and can use anything jQuery can use. See for full documentation. The jQuery library is already included in our player.


  • #article-identifier p.paragraph (# is used for the id attribute of dom-elements, . (dot) for the classname. p can be used to select all <p> elements.)
  • div.article p:nth-child(4), div.article p:last (This will select the 4th <p> element within a <div class=”article”> element, and the last <p> element found within the <div class=”article”> element. When used with the Placement option afterSelector/first element the player will be placed after the first element found, so if there are less then 4 <p> elements found, it will be placed after the last <p> element.)

Attempt iFrame breakout

When the adunit is placed by another adsystem that places it within a friendly iFrame, this option will allow the player to break out of that iFrame in order to do proper "InView" calculations.1

Add (css) clear:both to player wrapper

Add the css style 'clear:both' to the player wrapper. Useful for situations in which our player can not detect the correct width to use.

Custom javascript code

It's possible to add custom javascript code that will be executed when the player is placed. You can use the references $$api (the player API) and $$wrapper (the player wrapper element) in your code. This option is not enabled by default. Contact support for more information.

Passback javascript code

Works similar to the custom javascript code, but will be executed only once all ads finished playing or no ad was found. You can use the references $$adPlayed (is true when an ad was played or false otherwise), $$api (the player API) and $$wrapper (the player wrapper element) in your code. This option is not enabled by default. Contact support for more information.

Allow Blue Billywig IMA

Allow usage of the Blue Billywig Interactive Media Ads component. This component is used to play inline video on devices which normally disable this like the iPhone. This setting is enabled by default. Please contact support for more information or if you want to alter this setting.

Display ad units

Display ad units are positions within our media player where display ads could be shown. Right now the different display positions are:

  • an overlay position displaying over the bottom of the video of 768x90px
  • a display position in the end screen of the video of 300x250px

Line items

In a line item you make the connection to your ad system through a VAST (Video Ad Serving Template) URL. Multiple line items can be targeted to an ad unit by priority. Each of the line items will be checked for a viable ad to play in our player and the first one that delivers a valid ad will run.

You can run a line item on one or more ad units. Please note that if you change the settings of a line item it will change for each of the ad units it is targeted to.

The various options for line items are explained below.


You can set a timeout on the line item which dictates the maximum time the line item gets to start an ad. If it does not deliver within this time the player will move on to the next line item if there is one available, or otherwise the main content.

VAST URL, macro's and custom targeting

Enter the full VAST URL to your ad system. You can use the following macro's which will be replaced by our player:

Macro Explanation Value
[url] The url the player is placed on. If the player is placed in an iFrame and the option "attempt iFrame breakout" is not used, the [url] will be the url of the iFrame. a URL encoded string
[deeplink] The deeplink of the mediaclip (is the same as [url] if not set) a URL encoded string
[timestamp] The timestamp that the VAST request was done. a number
[correlator] Same as [timestamp] a number
[playerwidth] The width of the player in pixels. When responsive sizing is used the width will return the width of the player at the moment of requesting the ad. a number (in pixels)
[playerheight] The width of the player in pixels. When responsive sizing is used the width will return the width of the player at the moment of requesting the ad. a number (in pixels)
[clipTitle] The title of the clip. Only available for in-stream the URL encoded title string
[clipID] The ID of the clip. Only available for in-stream the ID string
[playmode] The playmode selected by the player. Useful for example when using key/value targeting in combination with DfP "html5" or "flash"
[format] The format selected by the player. Almost the same as playmode, but returns another value. Useful in combination with liverail ( LR_FORMAT ). "application/x-shockwave-flash" or "application/javascript"

Furthermore you can add custom parameters to the embed code while embedding the player which will be passed to the VAST URL. By substituting %%<key>%% with the value part of the macro_<key>=<value> embed-code parameter.

An example: If you place %%foo%% in an ad tag url:
and book it in your line item, then embedding the player with:
results in the player requesting the VAST URL:


Here you can add conditions that need to be met before the line item will load.

Block insecure HTML5 VPAID ads

If this setting is enabled in the line item or the ad unit, it will force ads to run in a secure iFrame. When disabled, javascript VPAID ads will have access to the page they are running on.

Preferred playmode

The preferred playmode specifies the technique the player should try first to load and display the ad. Mobile devices do not support Flash, while old browsers like IE8 do not support HTML5 video. Some browsers support both techniques. This option specifies which technique is preferred when both are available. If you choose "Force Flash" then the process of loading the ad will only start when the user has Flash enabled.

Another thing to consider is if the ad system you are using supports HTML5/javascript VPAID or only Flash/SWF VPAID. For HTML5 to work there needs to be an mp4 or webm video file (normal VAST) or a javascript VPAID URL available. Please contact your ad provider to ensure you are using the right setting. Keep in mind that Flash is being phased out and browsers are slowing down the use of Flash components, so when possible use HTML5.

Minimum clip duration

Enter a number in seconds. This allows you to set a minimum duration of the media clip in order for the line item to be allowed to run. Example: If you set this to 30 seconds, no ads will run on media clips shorter then 30 seconds. This only applies to line items that are targetted to instream ad units.

Allow skipping

When enabled the user will be able to skip the ad after the specified amount of seconds. You can also alter the text that is displayed during the countdown and the text that is used in the button to skip the ad. Please note that our player respects the DfP setting "skippable" even when the "Allow skipping" setting is disabled in our system.

Disable controls

When using this option you will overrule the ad unit's settings to display controls. This can be useful if you know that the VAST URL that is booked on the line item will return a VPAID player which has it's own controls.


Every video or audio mediaclip that gets uploaded to the online video platform, automatically gets transcoded (or encoded) to different formats, in order to ensure playback on all devices and bandwidths. These formats are called assets and can be found in the assets tab in the mediaclip details. What specific assets are created by the online video platform can vary by specific publication settings, but we maintain a standard set that will be used in most publications.

Video assets

Video will be encoded to various asset types:


Our main asset type is MP4_MAIN and will be served to most of the users. It features a Standard Definition resolution along with an average bandwidth. There may be multiple MP4_MAIN assets using different resolutions and bandwidths in some publications.


Similar to the MP4_MAIN asset, with a High Definition resolution (above 720p). It features settings that ensure smooth playback and encoding that is more suited to high resolution video.


This asset type can be considered as the most basic asset, since it has great compatibility with a broad range of devices, including (hence the name) the iPod. However, file size and quality are sacrificed for this compatibility and the Blue Billywig player favours other assets if they can be played.


This asset will only be used within the Timeline Editor, and will never be served to the user.


An asset that is used to display interactive video on the iPhone. It will only be used on iPhone's when an interactive timeline is present.

Audio assets


This is the only asset type that will be encoded for audio mediaclips, and offers broad compatibility of devices and browsers. Depending on the setup we will add versions with different bitrate settings.

What asset will be used?

The Blue Billywig Player determines what asset to use on a number of factors, to ensure the best viewing experience.

Compatible assets

First, the player determines what assets can be played on device and browser that the user is using. The resulting list is also featured in the quality selection list in the player.

Determining the 'best' asset

Next, the player measures the internet connection speed that is available. The asset with highest bandwidth that is not higher than the internet connection speed, will be chosen. This way, the user will get the best quality media without stuttering.

Note that a user can still manually select an asset that has a higher bandwidth than the available internet connection speed, via the quality selector.

Deleting assets

We strongly discourage deleting assets, since this can result in an unplayable media on some devices. However, when an asset is deleted, the player will try to select one of the remaining assets.

When replacing a media clip's source file, deleted assets will again be transcoded. An accidentally deleted asset can be recovered by re-uploading the source file.

Previewing assets

Although the Online Video Platform allows every asset to be previewed, it may occur that some assets are unplayable in the OVP depending on the device, browser and whether Flash is installed or not.

Authentication and login

Signing into the Online Video Platform generally happens through <your environment>, for example: Before you are able to log in to the OVP, an account has to be created.

Creating an account

New accounts can be created by anyone who has an account with the permission user management. Alternatively, the Blue Billywig support team can help you with setting up new accounts (

Every account has the following information:

  • Email address -- has to be unique platform wide
  • First name
  • Last name
  • Username -- has to be unique publication wide. By default, the username will be composed of the first letter of the first name, followed by a dot (.) and the last name.
  • Gender (male or female)
  • Password -- case sensitive
  • One or more user roles (see Roles and permissions)

Setting a password

When an account is created, an email will be sent to the specified email address with further instructions to activate the account by setting a password that will be used to log in.

Logging in

Both your email address and username can be used to log in to the OVP, along with the password you set earlier. When you were already logged in in the past 20 minutes (in OVP5 or OVP6), you will be automatically logged in. After around 20 minutes of not using the OVP, you will be logged out for security reasons and will need to log in again.

Resetting your password

When you have forgotten your password, it is possible to reset your password by providing the email address that is linked to your account. You can do this at the login screen, by clicking the Forgot password? text.

An email will be sent to your email address with a link to set a new password. After setting a new password, you are able to log in again using the password you set earlier.

Note: The password is case sensitive.

Roles and permissions

In order to access the OVP, a user is required to have different roles. A user can have multiple roles which will be combined to give broader access to the OVP. A detailed list describing all roles is listed below.

  • Editor

    • Upload files
    • View and edit clips (Note: An editor can not publish clips!)
    • Export clips to a third party system (Youtube, Facebook)
    • Manage playouts
    • Import clips from other publications (please refer to !!PUBLICATIONS!!)
    • Manage creatives
    • Edit Zones (requires Zone Editor module)
    • Get embedcodes for clips
  • Publisher

    • Upload files
    • View and edit clips
    • Publish clips
    • Export clips to a third party system (Youtube, Facebook)
    • Manage playouts
    • Import clips from other publications (please refer to !!PUBLICATIONS!!)
    • Manage creatives
    • View statistics
    • Get embedcodes for clips
  • Read only

    • View
  • Stats

  • Timeline
  • Timeline advanced
  • Commercials
  • Commercials advanced
  • 1 on 1 advertiser
  • External uploader
  • Traffic Manager
  • iPhone only user
  • User manager
  • Restricted user
  • Readonly

Custom meta data fields

Custom meta data fields can be added to media clips. Please contact Blue Billywig if you want to add or change any meta data fields. The following field types can be added:

text field

single line text field

text area

multi line text field


yes/no toggle


There are two versions of this field type

  • a fixed list of options / values, you can choose from
  • an extendable list of values, where you can choose of on of the existing values, or add new ones

List fields can be configured to be single or multi select, meaning either one value can be selected, or multiple.


A field where you can create a relation to one or more (other) media clips. The media clips that can be chosen can be limited to clips of a specific media type (e.g. video, audio and/or images) or of a specific use type (editorial / creative)


date field (without time)


color picker


If you want retrieve the code to embed a video in your website, you can generate code which will play your media clip using the selected playout's settings. There are various types of embed codes.


This is the default embed code that delivers players and content on websites or in apps.


This Standalone/HTML embed code wraps around the Javascript embed code and can be used to link straight to a OVP video, or to include a OVP video in an iframe.


This option returns the oEmbed URL which can be used to embed a video using oEmbed code.


This Scriptless HTML embed code can be used to include a OVP video or a fallback screenshot of the video in an email. When the HTML5 video tag is supported the video will be embedded. When the video tag is not supported by the email client a fallback screenshot of the player is automatically generated and linked to either the deeplink provided in the OVP or the default player presentation page when no deeplink is available. The OVP deeplink can also be overruled using the query string deeplink=directplay in which case the fallback image will link to the default player presentation page where the video will automatically start to play. When the clip contains a timeline, the fallbackimage output will automatically be chosen as interactive videos are not supported in email clients.

Fallback image

This Scriptless HTML embed code can be used in situations where just the fallback screenshot is needed. The screenshot links to the video in the same way as the email the screenshot does in the email situation above.

Live Streams

Live streams can be added using the live streams tab in the upload & encode settings screen. Here, a source URL can be added along with more information about the stream, which the Blue Billywig player uses to properly present the stream to the end user.

In order to support multiple devices and bandwidths, more streams can be added to a live stream clip in the Streams tab in the media clip details.

Note: We do not distribute streams from our platform, which means that viewers will receive the video directly from the source entered in the OVP. If you require live stream distribution, please contact support.

Media clip search

When entering text in the search field, you search through various properties of the available media clips. For instance, if a title, description or one of the tags matches your search query, the media clip is returned.

smart search

If you wait a moment after typing a list with results will appear below the search field. Here you can choose from various options:

  • Media types, statuses, or tags matching your search. When choosing one of these options, you are searching for all media clips containing the selected media type, status or tag.

  • Mediaclips matching your search. By selecting one of these options, you are directly going to the details page for this media clip.

  • Options to (only) search in the title or description fields.

combining searches

You can combine multiple terms to filter the results displayed below the search field. When searching in multiple properties, a "AND" search is performed. When doing multiple searches for a specific property, an "OR" search is performed.


  • [media type:video] [title:bird] will be interpreted as "media clips of type video, having bird in the title".
  • [media type:video] [media type:audio] [title:bird] will be interpreted as "media clips of type video or audio, having bird in the title".


Playlists are an ordered collection of mediaclips in the online video platform publication. Mediaclips in a regular playlist can be added, removed and ordered manually.

Smart playlists

In addition to playlists that contain a number of manually added clips, the OVP features smart playlists. These playlists contain mediaclips that are dynamically added to the playlist via a set of filters. It is possible to filter on media type, tags, title, and many more. The maximum length of a smart playlist can be adjusted, along with a sorting criteria.

Smart playlists are automatically updated when new or changed mediaclips match (or don't match) the filters, thus will always provide an up-to-date list.

Solr query filter

For expert users, the OVP features the ability to use a custom Solr query. A detailed description regarding available fields in the Solr query is provided in the interface itself. The official Solr documentation can be found here.


It is possible to play a playlist in the Blue Billywig Player. The first mediaclip will be played, followed by the next mediaclip in order. Another use for playlists is the related items list that appears in the player when a mediaclip has finished. When a playlist is selected in the specific playout settings, the clips from that playlist are used in the related items, with an option to randomise the order.


A Vodcast URL can be generated for all playlists. The vodcast URL is created using the playlist ID:

http://<your environment><playlist id>


By embedding a mediaclip using a playout, you can customize the player to your specific needs. The following configuration options are available:


The playout is rendered in the specified width and height. These values can be absolute numbers (in pixels), or percentages.

Absolute dimensions

A non-percentage value will always result in a player with a static width and height as specified. This is the most basic configuration and is recommended for novice users.

Relative dimensions

Using a percentage for the width and height, it is possible to create a responsive player. A player with the size in percentages will act like any other HTML element with the size in percentages. A player with 100% width and 100% height will fill its containing element. This way, a web developer can control the player dynamicly by adjusting its parent container. Please make sure your containing element has a height set. By default, a div element without a height set with a 100% player in will not be visible since it's height will be 0.

Responsive sizing

This option makes the player overwrite height values in the playout settings. It sets the width of the player to 100% and calculates the height with it's width and the aspect ratio of the video. This feature is useful for responsive websites where the width of the player is variable.

Although this feature is very powerful in responsive websites, we recommend it only to expert users.


The player and its skin can be configured in any color. There are 4 colors that can be adjusted:

  • Background color / opacity controls the color and opacity of the control bar, popup windows and the title display background
  • Foreground color, controls the color of text and icons
  • Widget color, controls the accent color of widgets, like the progress in the progress bar
  • Player background color, controls the background color of the player


An overlay for a logo can be created, by uploading an image, or selecting a previously uploaded one. The you can specify the alignment of the logo, and optionally make it clickable by supplying an url.

Control bar

The control bar has three options (autohide, show and hide) which control the visibility of the entire control bar. The visibility of the seperate elements in the control bar can be individually controlled:


  • Should the player show the time, and if so in which format
  • Should the player show a progress bar


  • Should the player show a mute button
  • Should the player show a volume slider, and if so, in what orientation

Note: The volume control / mute button is not supported on the iPad and most other mobile devices.


You can specify if the player should display the following buttons:

  • Language select: When subtitles or captions are available this button will allow the user to select a different language
  • Playback quality selector: This allows the user to select a different playback quality
  • Audio track selector: When multiple audio tracks are available this button will allow the user to select a different audio track
  • Full screen button: Will show a button which will attempt to go fullscreen when pressed. If fullscreen is not supported by the browser it will fill up the browser space (full browser)
  • Share button, this enables the viewer to share the video on social web sites

Start and end screen

Every video has an end screen and (if autoplay has not been enabled) a start screen

Start screen

The start screen can be customised to show a big play button, and the media clip's meta data (like the title, author and copyright information)

End Screen

The end screen can display a list of related items. The following options are available

  • Randomize related items
  • Related clips will be instantly loaded inside the current player, but it is possible to link these clip to a specific deeplink page
  • The related clips can be further controlled with a custom clip list for related items. You can select a (dynamic) cliplist which will be displayed, randomly if wanted.


The following options are available for sharing the video

  • Use deep link for social links: the viewer will share the specified deep link instead of the current URL the user is watching the video on. This allows the creation of a specific video page with corresponding OG Graphs for Facebook embedding
  • Share Twitter text: this text will be placed before the video URL when clicking the Twitter share button
  • Playout used for sharing: optionally, you can specifiy a different playout to use when the viewer shares the video

Auto options

The player can be customized to certain behaviour, like autoplay (automatically play the video when the player loads), automute (mute the player when loaded) and autoloop (loop the clip or entire cliplist).

In and out view

The in and out view option plays or/and unmutes the video when the video player scrolls into our of of the current view. For example, a player is embedded halfway through an article but is not visible directly when the user arrives on a page. When the user scrolls down to read more of the article, the player comes into view and can start playing.

Some mobile devices, like an iPhone, don't support inline playing of video by default. The configured in and out view actions are disabled by default on those devices. If you are sure you want to enable them, you can do so by enabling the "force in and out view actions" option. Exceptions are assets encoded using our "image sequence" profile, which can be player inline on an iPhone, and where view actions are not disabled by default.


By default, the player will react to keyboard controls. You can disable these controls by checking the "Disable keyboard controls" option.

You can see which keys you can use to control the player here


The Mouse options utilize the mouse interaction with the player. When the user hovers the mouse over or away from the player, it can mute/unmute and/or start/stop playing. When the user clicks the player, a link can be opened in the current window, or a new one.

Placement options

You can specify the location on your web site the player should be placed. The following options are available:

  • Default: Place the player directly after the position of the embed script.
  • Place the player directly after the first element matching the specified DOM-Selector
  • Place the player after the number of items matching the DOM-Selector divided by two, rounded down. Example: When 7 elements match the selector, the banner will be placed after the 3rd element.
  • Below the webpage “fold”. This means it will place the player after the first element that is not completely visible without scrolling. If none of the elements is below the fold, the player will not be placed.
  • Below the fold, with the exception that it will be placed after the last element found, if none of the matching elements is under the fold.

No sound influence

On some devices the player will be unable to influence the sound/volume settings of the device. Mobile devices that currently do not support sound influence are:

  • All iOS devices including iPad, iPhone and iPod Touch
  • Most Android devices running Android 2.x
  • Devices running on Windows Mobile Phone

Mobile devices that currently do support sound influence are:

  • Windows Surface RT
  • Most Android devices running Android 4.x or higher

For devices with "no sound influence" we introduced options which come in handy when using ad services

  • Disable autoplay and inview actions: this will disable the player from automatically start playing from any situation, i.e. autoplay is turned on, or inview/mouse hover is set to start the player.
  • Disable player placement entirely: this will not place the player at all.

Custom code

You can specify custom Javascript code which will be executed when the player is displayed. References you can use * $$api, the player's api * $$wrapper, the DOM node the player is rendered in


The fitmode specifies how the video is rendered in the available space

  • Smart: the recommended and default option, a smart combination of stretching and letterboxing
  • Native: play the video in the exact dimensions of the videofile
  • Fit vertical: fit in the vertical direction
  • Fit horizontal: fit in the horizontal direction
  • Fit both: fit in both horizontal and vertical direction
  • Stretch: stretch in both horizontal and vertical direction
  • Cover (overscan): cover both horizontal and vertical direction with overscan

Playback preferences

You can configure various settings which influence the skin behaviour. By default, not all of these options are available. For more information, please contact our support team.

  • Use Blue Billywig skin
    • Auto: Skin is disabled when inline playback is not supported
    • Disable on touch: skin is disabled for mobile touch devices
    • Always disable: skin is disabled for all devices.

Note: when the skin is disabled, all timeline interactions are disabled too, unless the "Blue Billywig skin for timeline clips" is enabled

You can choose to use the native browser controls when the skin is disabled

When you have imported or exported your content to YouTube, you can turn on Enable YouTube playback to play the content from YouTube in our player.

Our player tries to select the best asset based on the user's bandwith and previously selected playback quality. To do this we will do a bandwith check before playing content. When the bandwidth is not yet determined (often the case when autoplay is turned on) you can use the setting Prefer HD to let the player to start with an asset which is at least 720p.

Developer options

You can enable comScore logging by supplying an URL for comScore logging.

You can enable Google Analytics or Piwik logging by supplying the appropiate information. Please contact our support team for more information on this option.

If you require a cookieless player, you can control the cookies set by the player with Disable Cookies. Tracking cookies are cookies which allows the tracking of a user through different videos. Other cookies are for player functinality, like remembering the volume a user sets.


The Blue Billywig Viewpage is used to display a mediaclip in a player on a single webpage. The page is hosted by the Online Video Platform, is publicly accessible and can be customised with a background image, logos and colors. In addition, this page is also used as the fallback deeplink for the related playout.

The viewpage contains all the necessary tags and markup that is needed for proper search engine indexing, as described in the external metadata generator page.

Accessing the viewpage

The viewpage is created using a combination of a playout and a mediaclip in a specific URL scheme:

http://{publication}{playout name}/{mediaclip id}.html

The viewpage link can also be found in the embed tab in the mediaclip edit screen.

Customising the viewpage

There are a number of customisations available to adjust the page to your liking. It is possible to show or hide the title and description of a mediaclip, use custom player dimensions, horizontally align the video and text, and adjust the text color.


The default background of the page is plain white, however it is possible to adjust the background color and even upload an image. The background image must be uploaded to the OVP and has a number of sizing options:

  • Original size: keep the original image size.
  • Cover: keep original aspect ratio, but cover the whole background.
  • Contain: Keep the original aspect ratio, but fit the whole image in the background (creating horizontal or vertical bars).
  • Stretch: Stretches the background image to the whole background.

It is also possible to specify the position, especially useful when selecting original size.

In case of contain or original size, the background image may sometimes not cover the available space. The color of the background behind the image can be specified using background color.


Up to four different logos can be specified to fill all four corners of the page. The logos will be displayed at the original size, but will not exceed 50% of the width and height of the page. This allows the page to correctly display on mobile devices.

Design documents

In order to aid designers with the customisation of the page, we have created a set of guideline PNGs displaying the various margins and alignments available. These are available for download here.


Clips or individual assets can be previewed in the preview player. For convenience, you can toggle between a large and a small display. If the clip has subtitles or an Interactive Timeline, these will be shown too.

Publishing, status and deleting

The status indicates the public availability of the mediaclip. There are two status values: 'draft' and 'published'. By default, all mediaclips uploaded to the VMS get the status 'draft'.


Mediaclips which are draft are mediaclips that are not ready to be viewed publically, in other words: have restricted access. Only users that are logged into Blue Billywig and have the correct user permissions have the ability to view the mediaclip. Draft mediaclips will never show up in searches without a valid session.

Embedding a draft mediaclip will result in an 'Unable to play media' message.


Published mediaclips are visible to anyone, they can be embedded and viewed on any website by anyone and will also show up in searches.

Note: Geographical restrictions may apply.

Scheduled publishing / embargo

If it is desired that a certain mediaclip has to be published at a later date, a 'scheduled publication' can be set (which is located at the top right, near the draft / published switch). A date and time can be selected from which the mediaclip should be publically visible. Alternatively, it's also possible to specify a date and time from which mediaclip should not be public anymore.

Deleting clips

Clips that are deleted end up in the trash. From the trash, they can be permanently deleted, or can be put back (with status 'draft'). Deleted clips will not show up anywhere in the OVP, other than the trash.

Uploading and encoding


Uploading files can be done on the [Upload & Encode] page, Blue Billywig supports a number of file types:

  • Video

    All common types of video can be uploaded, including MP4, WMV, MOV, MKV and AVI. However, we do recommend specific settings when exporting from your video editing program.

    Video will, when completely uploaded, be encoded to different formats depending on the uploaded file. Videos with a resolution lower than 720p will not be encoded to 720p and above, just like 1080p will not be encoded to 1080p and above.

  • Audio

    Audio can also be uploaded in all common file types like MP3, WAV, OGG and WMA. However, we do recommend specific settings when exporting from your audio editing program.

    Just like video, audio will also be encoded to different formats directly after completing the upload.

  • Images

    Images can be uploaded to Blue Billywig for use in timeline or logo's in playouts. Images will not be encoded but can (and will) be requested in optimal dimensions.

  • Documents

    For timeline download options, documents can also be uploaded to Blue Billywig. File types include PDF, doc and docx.

Containers, codecs and file types

For a complete list of supported file types, container formats and codecs, please refer to the supported file types page.


All video files uploaded to Blue Billywig will be encoded automatically to multiple different formats to ensure playback on every device and maintain a good user experience on fast and slow connections. Encoding happens automaticly after a clip has been uploaded, this process can be monitored on the [Upload & Encode] page for recently uploaded clips, and on the individual clip edit page.

Please not that a video might not be available on every device, before encoding has finished. It is thus advised that clips are only published after encoding has finished.


It's possible to import videos from a number of sources, by using the "url import" field. The following are some of the sites which are supported:

  • Apple Trailers
  • Bandcamp
  • BBC
  • BBC iPlayer
  • BuzzFeed
  • Comedy Central
  • Daily Motion
  • Discovery
  • Dropbox
  • Facebook
  • Instagram
  • MTV
  • NPO
  • Periscope
  • Soundcloud
  • Twitch
  • Vimeo
  • Vine
  • YouTube

Recommended upload encoding settings

Container: MP4

Video codec: H.264

  • Main profile for standard definition (lower than 720p)
  • High profile for high definition (720p and higher).
  • Progressive scanning

    Transcoding to web video formats always results in progressive video output files. Although Blue Billywig will suppress artifacts resulting from an interlaced source file, best results are obtained when the video source file is progressive instead of interlaced.

  • Aspect ratio: Preferably 16:9, but any will work. Do not letterbox.
  • Framerate: 24 to 60, original framerate will be maintained.

    Most video source file format use constants frame rates, for example 25 frames per second. Some file format make use of variable frame rate. Use of variable frame rate is not recommended, as this can be a cause for audio sync issues.

  • Bitrate
    • 480p: 2.5 to 5 Mbps
    • 720p: 5 to 10 Mbps
    • 1080p: 10 to 20 Mbps

Audio codec: AAC (Advanced Audio Codec)

  • Sample rate: 48 kHz
  • Bitrate
    • Mono: 192 kbps
    • Stereo: 320 kbps
    • 5.1: 512 kbps

Supported video- and audio codecs, file formats and containers

Blue Billywig offers broad support for all kinds of video codecs, audio codecs, file formats and containers. Everything that is supported is listed below. For the best results when uploading your video, please refer to our recommended upload encoding settings.

File formats

  • 4xm
  • 8088flex TMV
  • ACT Voice
  • Adobe Filmstrip
  • Audio IFF (AIFF)
  • American Laser Games MM
  • 3GPP AMR
  • Amazing Studio Packed Animation File
  • Apple HTTP Live Streaming
  • Artworx Data Format
  • ADP
  • AFC
  • APNG
  • ASF
  • AST
  • AVI
  • AviSynth
  • AVR
  • AVS
  • Beam Software SIFF
  • Bethesda Softworks VID
  • Binary text
  • Bink
  • Bitmap Brothers JV
  • Brute Force & Ignorance
  • BWF
  • Discworld II BMV
  • Interplay C93
  • Delphine Software International CIN
  • Digital Speech Standard (DSS)
  • Canopus HQ
  • Canopus HQA
  • Canopus HQX
  • CD+G
  • Phantom Cine
  • Commodore CDXL
  • Core Audio Format
  • CRC testing format
  • Creative Voice
  • D-Cinema audio
  • Deluxe Paint Animation
  • DFA
  • DSD Stream File (DSF)
  • DV video
  • DXA
  • Electronic Arts cdata
  • Electronic Arts Multimedia
  • Ensoniq Paris Audio File
  • FFM (FFserver live feed)
  • Flash (SWF)
  • Flash 9 (AVM2)
  • FLI/FLC/FLX animation
  • Flash Video (FLV)
  • framecrc testing format
  • FunCom ISS
  • G.723.1
  • G.729 BIT
  • G.729 raw
  • GIF Animation
  • GXF
  • HNM
  • iCEDraw File
  • ICO
  • id Quake II CIN video
  • id RoQ
  • IEC61937 encapsulation
  • IFF
  • iLBC
  • Interplay MVE
  • IV8
  • IVF (On2)
  • LATM
  • LMLM4
  • LOAS
  • LRC
  • LVF
  • LXF
  • Magic Lantern Video (MLV)
  • Matroska
  • Matroska audio
  • FFmpeg metadata
  • MD Studio
  • Metal Gear Solid: The Twin Snakes
  • Megalux Frame
  • Mobotix .mxg
  • Monkey’s Audio
  • Motion Pixels MVI
  • MOV/QuickTime/MP4
  • MP2
  • MP3
  • MPEG-1 System
  • MPEG-PS (program stream)
  • MPEG-TS (transport stream)
  • MPEG-4
  • Mirillis FIC video
  • MIME multipart JPEG
  • MSN TCP webcam
  • MTV
  • Musepack
  • Musepack SV8
  • Material eXchange Format (MXF)
  • Material eXchange Format (MXF), D-10 Mapping
  • NC camera feed
  • NIST SPeech HEader REsources
  • NTT TwinVQ (VQF)
  • Nullsoft Streaming Video
  • NuppelVideo
  • NUT
  • Ogg
  • Playstation Portable PMP
  • Portable Voice Format
  • TechnoTrend PVA
  • QCP
  • raw ADTS (AAC)
  • raw AC-3
  • raw Chinese AVS video
  • raw CRI ADX
  • raw Dirac
  • raw DNxHD
  • raw DTS
  • raw DTS-HD
  • raw E-AC-3
  • raw FLAC
  • raw GSM
  • raw H.261
  • raw H.263
  • raw H.264
  • raw HEVC
  • raw Ingenient MJPEG
  • raw MJPEG
  • raw MLP
  • raw MPEG
  • raw MPEG-1
  • raw MPEG-2
  • raw MPEG-4
  • raw NULL
  • raw video
  • raw id RoQ
  • raw Shorten
  • raw TAK
  • raw TrueHD
  • raw VC-1
  • raw PCM
  • RDT
  • RealMedia
  • Redirector
  • RedSpark
  • Renderware TeXture Dictionary
  • RL2
  • RPL/ARMovie
  • Lego Mindstorms RSO
  • RSD
  • RTMP
  • RTP
  • RTSP
  • SAP
  • SBG
  • SDP
  • Sega FILM/CPK
  • Silicon Graphics Movie
  • Sierra SOL
  • Sierra VMD
  • Smacker
  • Smush
  • Sony OpenMG (OMA)
  • Sony PlayStation STR
  • Sony Wave64 (W64)
  • SoX native format
  • SUN AU format
  • SUP raw PGS subtitles
  • TDSC
  • Text files
  • THP
  • Tiertex Limited SEQ
  • True Audio
  • VC-1 test bitstream
  • Vivo
  • WAV
  • WavPack
  • WebM
  • Windows Televison (WTV)
  • Wing Commander III movie
  • Westwood Studios audio
  • Westwood Studios VQA
  • XMV
  • xWMA
  • eXtended BINary text (XBIN)
  • YUV4MPEG pipe
  • Psygnosis YOP

Video codecs

  • 4X Movie
  • 8088flex TMV
  • A64 multicolor
  • Amazing Studio PAF Video
  • American Laser Games MM
  • AMV Video
  • ANSI/ASCII art
  • Apple Intermediate Codec
  • Apple MJPEG-B
  • Apple ProRes
  • Apple QuickDraw
  • Asus v1
  • Asus v2
  • ATI VCR1
  • ATI VCR2
  • Auravision Aura
  • Auravision Aura 2
  • Autodesk Animator Flic video
  • Autodesk RLE
  • Avid 1:1 10-bit RGB Packer
  • AVS (Audio Video Standard) video
  • AYUV
  • Beam Software VB
  • Bethesda VID video
  • Bink Video
  • Bitmap Brothers JV video
  • y41p Brooktree uncompressed 4:1:1 12-bit
  • Brute Force & Ignorance
  • C93 video
  • CamStudio
  • CD+G
  • CDXL
  • Chinese AVS video
  • Delphine Software International CIN video
  • Discworld II BMV Video
  • Canopus Lossless Codec
  • Cinepak
  • Cirrus Logic AccuPak
  • CPiA Video Format
  • Creative YUV (CYUV)
  • DFA
  • Dirac
  • Deluxe Paint Animation
  • DNxHD
  • Duck TrueMotion 1.0
  • Duck TrueMotion 2.0
  • DV (Digital Video)
  • Dxtory capture format
  • Feeble Files/ScummVM DXA
  • Electronic Arts CMV video
  • Electronic Arts Madcow video
  • Electronic Arts TGV video
  • Electronic Arts TGQ video
  • Electronic Arts TQI video
  • Escape 124
  • Escape 130
  • FFmpeg video codec #1
  • Flash Screen Video v1
  • Flash Screen Video v2
  • Flash Video (FLV)
  • Forward Uncompressed
  • Fraps
  • Go2Webinar
  • H.261
  • H.263 / H.263-1996
  • H.263+ / H.263-1998 / H.263 version 2
  • H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
  • HEVC
  • HNM version 4
  • HuffYUV
  • HuffYUV FFmpeg variant
  • IBM Ultimotion
  • id Cinematic video
  • id RoQ video
  • IFF ByteRun1
  • Intel H.263
  • Intel Indeo 2
  • Intel Indeo 3
  • Intel Indeo 4
  • Intel Indeo 5
  • Interplay C93
  • Interplay MVE video
  • J2K
  • Karl Morton’s video codec
  • Kega Game Video (KGV1)
  • Lagarith
  • LCL (LossLess Codec Library) MSZH
  • LCL (LossLess Codec Library) ZLIB
  • LOCO
  • LucasArts SANM/Smush
  • lossless MJPEG
  • Microsoft ATC Screen
  • Microsoft Expression Encoder Screen
  • Microsoft RLE
  • Microsoft Screen 1
  • Microsoft Screen 2
  • Microsoft Video 1
  • Mimic
  • Miro VideoXL
  • MJPEG (Motion JPEG)
  • Mobotix MxPEG video
  • Motion Pixels video
  • MPEG-1 video
  • MPEG-2 video
  • MPEG-4 part 2
  • MPEG-4 part 2 Microsoft variant version 1
  • MPEG-4 part 2 Microsoft variant version 2
  • MPEG-4 part 2 Microsoft variant version 3
  • Nintendo Gamecube THP video
  • NuppelVideo/RTjpeg
  • On2 VP3
  • On2 VP5
  • On2 VP6
  • On2 VP7
  • VP8
  • VP9
  • Pinnacle TARGA CineWave YUV16
  • Prores
  • Q-team QPEG
  • QuickTime 8BPS video
  • QuickTime Animation (RLE) video
  • QuickTime Graphics (SMC)
  • QuickTime video (RPZA)
  • R10K AJA Kona 10-bit RGB Codec
  • R210 Quicktime Uncompressed RGB 10-bit
  • Raw Video
  • RealVideo 1.0
  • RealVideo 2.0
  • RealVideo 3.0
  • RealVideo 4.0
  • Renderware TXD (TeXture Dictionary)
  • RL2 video
  • Sierra VMD video
  • Silicon Graphics Motion Video Compressor 1 (MVC1)
  • Silicon Graphics Motion Video Compressor 2 (MVC2)
  • Silicon Graphics RLE 8-bit video
  • Smacker video
  • SMPTE VC-1
  • Snow
  • Sony PlayStation MDEC (Motion DECoder)
  • Sorenson Vector Quantizer 1
  • Sorenson Vector Quantizer 3
  • Sunplus JPEG (SP5X)
  • TechSmith Screen Capture Codec
  • TechSmith Screen Capture Codec 2
  • Theora
  • Tiertex Limited SEQ video
  • Ut Video
  • v210 QuickTime uncompressed 4:2:2 10-bit
  • v308 QuickTime uncompressed 4:4:4
  • v408 QuickTime uncompressed 4:4:4:4
  • v410 QuickTime uncompressed 4:4:4 10-bit
  • VBLE Lossless Codec
  • VMware Screen Codec / VMware Video
  • Westwood Studios VQA (Vector Quantized Animation) video
  • Windows Media Image
  • Windows Media Video 7
  • Windows Media Video 8
  • Windows Media Video 9
  • Wing Commander III / Xan
  • Wing Commander IV / Xan
  • Winnov WNV1
  • WMV7
  • Psygnosis YOP Video
  • yuv4
  • ZeroCodec Lossless Video
  • ZLIB
  • Zip Motion Blocks Video

Audio codecs

  • 8SVX exponential
  • 8SVX fibonacci
  • AAC+
  • AAC
  • AC-3
  • ADPCM 4X Movie
  • ADPCM Creative Technology
  • ADPCM Electronic Arts
  • ADPCM Electronic Arts Maxis CDROM XS
  • ADPCM Electronic Arts R1
  • ADPCM Electronic Arts R2
  • ADPCM Electronic Arts R3
  • ADPCM Electronic Arts XAS
  • ADPCM G.722
  • ADPCM G.726
  • ADPCM IMA Electronic Arts EACS
  • ADPCM IMA Electronic Arts SEAD
  • ADPCM IMA Funcom
  • ADPCM IMA QuickTime
  • ADPCM IMA Westwood
  • ADPCM IMA Dialogic
  • ADPCM IMA Duck DK3
  • ADPCM IMA Duck DK4
  • ADPCM IMA Radical
  • ADPCM Microsoft
  • ADPCM Nintendo Gamecube AFC
  • ADPCM Nintendo Gamecube DTK
  • ADPCM Nintendo Gamecube THP
  • ADPCM Shockwave Flash
  • ADPCM Sound Blaster Pro 2-bit
  • ADPCM Sound Blaster Pro 2.6-bit
  • ADPCM Sound Blaster Pro 4-bit
  • ADPCM Westwood Studios IMA
  • ADPCM Yamaha
  • AMR-NB
  • AMR-WB
  • Amazing Studio PAF Audio
  • Apple lossless audio
  • ATRAC1
  • ATRAC3
  • ATRAC3+
  • Bink Audio
  • CELT
  • Delphine Software International CIN audio
  • Digital Speech Standard - Standard Play mode (DSS SP)
  • Discworld II BMV Audio
  • COOK
  • DCA (DTS Coherent Acoustics)
  • DPCM id RoQ
  • DPCM Interplay
  • DPCM Sierra Online
  • DPCM Sol
  • DPCM Xan
  • DSD (Direct Stream Digitial), least significant bit first
  • DSD (Direct Stream Digitial), most significant bit first
  • DSD (Direct Stream Digitial), least significant bit first, planar
  • DSD (Direct Stream Digitial), most significant bit first, planar
  • DSP Group TrueSpeech
  • DV audio
  • Enhanced AC-3
  • EVRC (Enhanced Variable Rate Codec)
  • FLAC (Free Lossless Audio Codec)
  • G.723.1
  • G.729
  • GSM
  • GSM Microsoft variant
  • IAC (Indeo Audio Coder)
  • iLBC (Internet Low Bitrate Codec)
  • IMC (Intel Music Coder)
  • MACE (Macintosh Audio Compression/Expansion) 3:1
  • MACE (Macintosh Audio Compression/Expansion) 6:1
  • MLP (Meridian Lossless Packing)
  • Monkey’s Audio
  • MP1 (MPEG audio layer 1)
  • MP2 (MPEG audio layer 2)
  • MP3 (MPEG audio layer 3)
  • MPEG-4 Audio Lossless Coding (ALS)
  • Musepack SV7
  • Musepack SV8
  • Nellymoser Asao
  • On2 AVC (Audio for Video Codec)
  • Opus
  • PCM A-law
  • PCM mu-law
  • PCM signed 8-bit planar
  • PCM signed 16-bit big-endian planar
  • PCM signed 16-bit little-endian planar
  • PCM signed 24-bit little-endian planar
  • PCM signed 32-bit little-endian planar
  • PCM 32-bit floating point big-endian
  • PCM 32-bit floating point little-endian
  • PCM 64-bit floating point big-endian
  • PCM 64-bit floating point little-endian
  • PCM D-Cinema audio signed 24-bit
  • PCM signed 8-bit
  • PCM signed 16-bit big-endian
  • PCM signed 16-bit little-endian
  • PCM signed 24-bit big-endian
  • PCM signed 24-bit little-endian
  • PCM signed 32-bit big-endian
  • PCM signed 32-bit little-endian
  • PCM signed 16/20/24-bit big-endian in MPEG-TS
  • PCM unsigned 8-bit
  • PCM unsigned 16-bit big-endian
  • PCM unsigned 16-bit little-endian
  • PCM unsigned 24-bit big-endian
  • PCM unsigned 24-bit little-endian
  • PCM unsigned 32-bit big-endian
  • PCM unsigned 32-bit little-endian
  • PCM Zork
  • QCELP / PureVoice
  • QDesign Music Codec 2
  • RealAudio 1.0 (14.4K)
  • RealAudio 2.0 (28.8K)
  • RealAudio 3.0 (dnet)
  • RealAudio Lossless
  • RealAudio SIPR / ACELP.NET
  • Shorten
  • Sierra VMD audio
  • Smacker audio
  • SMPTE 302M AES3 audio
  • Sonic
  • Sonic lossless
  • Speex
  • TAK (Tom’s lossless Audio Kompressor)
  • True Audio (TTA)
  • TrueHD
  • TwinVQ (VQF flavor)
  • VIMA
  • Vorbis
  • Voxware MetaSound
  • WavPack
  • Westwood Audio (SND1)
  • Windows Media Audio 1
  • Windows Media Audio 2
  • Windows Media Audio Lossless
  • Windows Media Audio Pro
  • Windows Media Audio Voice