When a domain or geo location is ‘unknown’ the benefit is currently given to the viewer, allowing the media to play. For example, this occurs when the viewer has disabled JavaScript, or another instance is when there is no IP record for the geo location. Publishers that require strict enforcement now have the ability to enable ‘Strict Enforcement’ to ensure their content will only be viewed where they want it.

This can be enabled under the ‘Settings’ tab followed by selecting the ‘Content Restriction’ tab. Publishers can now specify ‘Strict Enforcement’ when declaring their restriction rules.  

Most recently released is a new set of analytics reports that provide granular data on viewership’s Operating System, Browser, and Device platform. Now LVP publishers can easily determine how videos are being accessed and watched. 

 With our HTML5 Player, effortlessly deliver video to your mobile audience, reaching iOS, Android and Blackberry devices without any additional work. With our device detection technology, you can use one embed code to automatically deliver content across multiple devices; our players selects the correct file format based on the viewers device. 

 Now videos can be displayed in a playlist player on mobile devices. This means better aesthetics for your website and more content available for your mobile audience to browse through. 

Let’s get down to the basics-according to comScore there are currently about 13.5 million people watching online video with an average of 17 hours each per month. Granted, this is a pretty broad statistic, but now you know you have the opportunity to reach millions of viewers with your online video. Now you just need to figure out how to target the right audience for you.

Getting to know your audience is like dating. You have to go out a few times before you can determine whether they like what you have to offer. Vice-versa, you have to gather info from them to determine if they are a good fit for you. It’s the same process with publishing online video, but unlike dating you can’t meet every person watching your content to determine what content is appealing to your audience.

More and more of you publishing online videos face the same problem of not really knowing whether your audience is even watching your content. Fret no more my friends-LVP has a fully comprehensive solution to help you gather the data and information to determine what content is most effective.

With LVP analytics you can really start to understand the extent of your reach to your audience. By having the ability to evaluate your performance you can really start to extend your scope and delve into strengthening your viewership.

 Even knowing what devices your audience is using to watch online video is important. Having this knowledge will help you determine what devices you need to push your content out to.

Reelseo conducted a survey of 1000 people and found that 68 percent of people watch online video on their laptops, 52 percent on their desktops, and 17 percent on a mobile device such as iPhone, Droid, Blackberry, etc. They also said that over the course of the next year to expect the mobile video consumption to increase by at least 20 percent.

With the growing trend of mobile video consumption also comes the need to have the right set of tools to accomplish this. With that being said, LVP offers a complete mobile solution to optimize transcoding for mobile devices along with many other video publishing features. You can also use our open APIs to create mobile apps and sites. Another great feature is the smart device detection utilities. As you get to know your audience, you can fine-tune your delivery using our tools.

Knowledge is power. The more you know about your audience, the more success you’ll have with your online video publishing. Let us help you keep it simple and stress free! You have enough on your plate-LVP provides all the tools to help you target the right audience for you.

Closed Captioning Guide

Audience and Overview

This guide is intended for all publishers that wish to enable closed captioning or subtitles in the LVP player. Closed captioning is the display of text on the video screen in order to communicate spoken dialogue. The audience for closed captioning is typically those individuals that are hard of hearing. However, they can also be used to display a translation (AKA ’subtitles’) to non-native speakers of the video language. Closed captioning can be enabled by simply uploading a caption file for each of your media.

1.0 Enabling Closed Captions

The workflow to enable captioning is quite simple. Once a caption file is uploaded for a media the LVP player will automatically display a caption-control on the screen. The steps below walk you through this process.

1. Create a DFXP formatted caption file for each of your media. See Section 2.0 for information on creating DFXP files.
2. Login to your LVP account and select a media. In the ‘Media Properties’ upload your caption file. Only files with an extension of ‘dfxp’ or ‘xml’ will be recognized.



3. Once a file has been uploaded for a media the embedded players will display a caption-control. If the control does not appear after approximately ten minutes, double check your DFXP file for errors. See Section 2.2 for troubleshooting suggestions.

1.1 Disabling Captions on a Player

By default, if closed captions are associated with the media the caption-control will automatically show in the player. However, if you would like to disable closed captions on a specific player or tweak the appearance/location of the captions you may do so by adjusting the controls in the Player Builder.

Note: The player preview within the Player Builder will not display a sample of your caption settings. You must generate an embed code for your player to evaluate the result of the settings.

2.0 DFXP Caption Files

The Distribution Format Exchange Profile (DFXP) is an XML-based standard developed by W3C for the representation of time-based text, or captions. The LVP player reads the XML, outputting each line of text on the screen in accordance with the ‘begin’ and ‘end’ time. An example of a properly formatted DFXP file is below. See Appendix A for an example of a DFXP file for captions in multiple languages. If multiple languages are represented, the LVP player will automatically display the list of languages in the player caption-control.

<?xml version=”1.0″ encoding=”UTF-8″?>

<tt xml:lang=”en” xmlns=”http://www.w3.org/ns/ttml” xmlns:tts=”http://www.w3.org/ns/ttml#styling”>

  <body>

    <div xml:lang=”en”>

      <p begin=”00:01.7″ end=”00:05.0″>Narrator:  Someone watching a car<br/>accelerate toward light speed</p>

      <p begin=”00:05.0″ end=”00:07.4″>would see something<br/>very strange.</p>

      <p begin=”00:07.4″ end=”00:10.5″>It would seem as though the<br/>car itself were getting shorter</p>

      <p begin=”00:10.5″ end=”00:14.4″>and that time for the person<br/>in the car was slowing down.</p>

      <p begin=”00:14.4″ end=”00:17.3″>However, you wouldn’t<br/>see these effects</p>

      <p begin=”00:17.3″ end=”00:20.6″>until the car began to<br/>approach the speed of light.</p>

      <p begin=”00:20.6″ end=”00:23.0″>At 90% of the speed of light</p>

      <p begin=”00:23.0″ end=”00:28.6″>the car would appear to shrink<br/>to 44% of its usual length.</p>

      <p begin=”00:28.6″ end=”00:30.2″>This thought experiment</p>

      <p begin=”00:30.2″ end=”00:32.5″>answered Einstein’s<br/>old question</p>

      <p begin=”00:32.5″ end=”00:33.9″>about what he would see</p>

      <p begin=”00:33.9″ end=”00:36.3″>if he traveled along<br/>with a beam of light.</p>

      <p begin=”00:36.3″ end=”00:38.4″>He simply couldn’t<br/>make the trip</p>

      <p begin=”00:38.4″ end=”00:42.1″>for at the speed of light,<br/>length would contract to zero</p>

      <p begin=”00:42.1″ end=”00:44.5″>and time would stop.</p>

    </div>

  </body>

</tt>

2.1 Creating Caption Files

If you are familiar with the DFXP standard or feel comfortable with the example above, you can easily use a text editor to create the caption files yourself. However, it is extremely important that you use an editor that saves your file with UTF-8 encoding or some of your characters may not display properly. If you do not want to create these files we recommend the following companies that offer creation services:

• 3PlayMedia (website)
• SubPLY (website)
• dotSub (website)

2.2 Troubleshooting

This section provides troubleshooting information for DFXP files. If you are experiencing problems with your captions, see the suggestions below.

Captions are Not Showing

• Caching Time – The addition of caption files may take up to ten minutes to reflect.
• Player Builder Settings – Verify that you have not inadvertently disabled captions on your player.
• Verify XML Format – Verify that your XML is properly formatted. See here for an XML validator.
• Verify Namespace Declarations – Your captions will not show if you are missing the required namespace declarations. Make sure that your DFXP file contains the following in the header:
• <?xml version=”1.0″ encoding=”UTF-8″?>
• <tt xml:lang=”en” xmlns=”http://www.w3.org/ns/ttml” xmlns:tts=”http://www.w3.org/ns/ttml#styling”>

List of Languages are Missing

• Make sure your file contains an XML language declaration for each language in the body. Even if you have only one language, you must still include the language declaration.
• <?xml version=”1.0″ encoding=”UTF-8″?>
• <tt xml:lang=”en” xmlns=”http://www.w3.org/ns/ttml” xmlns:tts=”http://www.w3.org/ns/ttml#styling”>
•   <body>
•     <div xml:lang=”en”>
•             <p begin=”00:01.7″ end=”00:05.0″>Narrator:  Someone watching a car<br/>accelerate toward light speed</p>
•     </div>
•     <div xml:lang=”es”>
•             <p begin=”00:01.7″ end=”00:05.0″>Narrador:  Si se observara a un auto<br/>acelerando a la velocidad de la luz</p>
•     </div>
•     <div xml:lang=”de”>
•             <p begin=”00:01.7″ end=”00:03.4″>Sprecher:<br/>Wer ein Auto beobachtet</p>
•     </div>
•   </body>
• </tt>

Appendix A

The following is an example of a properly formatted DFXP file containing multiple languages:

<?xml version=”1.0″ encoding=”UTF-8″?>

<tt xml:lang=”en” xmlns=”http://www.w3.org/ns/ttml” xmlns:tts=”http://www.w3.org/ns/ttml#styling”>

  <body>

     <div xml:lang=”en”>

            <p begin=”00:01.7″ end=”00:05.0″>Narrator:  Someone watching a car<br/>accelerate toward light speed</p>

            <p begin=”00:05.0″ end=”00:07.4″>would see something<br/>very strange.</p>

            <p begin=”00:07.4″ end=”00:10.5″>It would seem as though the<br/>car itself were getting shorter</p>

            <p begin=”00:10.5″ end=”00:14.4″>and that time for the person<br/>in the car was slowing down.</p>

            <p begin=”00:14.4″ end=”00:17.3″>However, you wouldn’t<br/>see these effects</p>

            <p begin=”00:17.3″ end=”00:20.6″>until the car began to<br/>approach the speed of light.</p>

            <p begin=”00:20.6″ end=”00:23.0″>At 90% of the speed of light</p>

            <p begin=”00:23.0″ end=”00:28.6″>the car would appear to shrink<br/>to 44% of its usual length.</p>

            <p begin=”00:28.6″ end=”00:30.2″>This thought experiment</p>

            <p begin=”00:30.2″ end=”00:32.5″>answered Einstein’s<br/>old question</p>

            <p begin=”00:32.5″ end=”00:33.9″>about what he would see</p>

            <p begin=”00:33.9″ end=”00:36.3″>if he traveled along<br/>with a beam of light.</p>

            <p begin=”00:36.3″ end=”00:38.4″>He simply couldn’t<br/>make the trip</p>

            <p begin=”00:38.4″ end=”00:42.1″>for at the speed of light,<br/>length would contract to zero</p>

            <p begin=”00:42.1″ end=”00:44.5″>and time would stop.</p>

    </div>

    <div xml:lang=”es”>

            <p begin=”00:01.7″ end=”00:05.0″>Narrador:  Si se observara a un auto<br/>acelerando a la velocidad de la luz</p>

            <p begin=”00:05.0″ end=”00:07.4″>se vería algo muy extraño.</p>

            <p begin=”00:07.4″ end=”00:10.5″>Parecería como si el mismo<br/>auto estuviera encogiendo</p>

            <p begin=”00:10.5″ end=”00:14.4″>y como si el tiempo pasase más<br/>lento para la persona del auto.</p>

            <p begin=”00:14.4″ end=”00:17.3″>Pero no vería estos efectos</p>

            <p begin=”00:17.3″ end=”00:20.6″>hasta que el auto empezase a<br/>acercarse a la velocidad de la luz.</p>

            <p begin=”00:20.6″ end=”00:23.0″>Al 90% de la velocidad de la luz,</p>

            <p begin=”00:23.0″ end=”00:28.6″>el auto parecería encogerse hasta<br/>el 44% de su longitud normal.</p>

            <p begin=”00:28.6″ end=”00:30.2″>Este experimento fue la respuesta</p>

            <p begin=”00:30.2″ end=”00:32.5″>a una vieja pregunta de Einstein</p>

            <p begin=”00:32.5″ end=”00:33.9″>sobre lo que vería</p>

            <p begin=”00:33.9″ end=”00:36.3″>si viajase a la velocidad de<br/>un rayo de luz.</p>

            <p begin=”00:36.3″ end=”00:38.4″>Simplemente no podría<br/>hacer el viaje</p>

            <p begin=”00:38.4″ end=”00:42.1″>porque a la velocidad de la luz, <br/>la longitud se reduciría a cero,</p>

            <p begin=”00:42.1″ end=”00:44.5″>y se detendría el tiempo.</p>

    </div>

    <div xml:lang=”de”>

            <p begin=”00:01.7″ end=”00:03.4″>Sprecher:<br/>Wer ein Auto beobachtet</p>

            <p begin=”00:03.4″ end=”00:05.9″>das bis fast Licht -<br/>geschwindigkeit beschleunigt</p>

            <p begin=”00:05.9″ end=”00:07.4″>würde etwas<br/>sehr seltsames sehen.</p>

            <p begin=”00:07.4″ end=”00:10.5″>Es würde ihm vorkommen,<br/>als ob das Auto kürzer wird</p>

            <p begin=”00:10.5″ end=”00:12.2″>dem Autofahrer dagegen<br/>schiene es</p>

            <p begin=”00:12.2″ end=”00:14.4″>daß die Zeit langsamer ablauft.</p>

            <p begin=”00:14.4″ end=”00:17.7″>Dieses würde sich aber<br/>erst dann bemerkbar machen</p>

            <p begin=”00:17.7″ end=”00:20.6″>wenn das Auto in die Nähe<br/>der Lichtgeschwindigkeit kommt.</p>

            <p begin=”00:20.6″ end=”00:23.0″>Bei 90% der<br/>Lichtgeschwindigkeit</p>

            <p begin=”00:23.0″ end=”00:28.0″>würde das Auto bis auf 44% seiner normalen Länge schrumpfen.</p>

            <p begin=”00:28.0″ end=”00:30.2″>Dieses Gedankenexperiment<br/>antwortete</p>

            <p begin=”00:30.2″ end=”00:33.9″>auf Einsteins alte Frage<br/>was er wohl sehen würde</p>

            <p begin=”00:33.9″ end=”00:36.3″>wenn er auf einem<br/>Lichtstrahl mitreiste.</p>

            <p begin=”00:36.3″ end=”00:38.4″>Doch solch eine Reise<br/>ist unmöglich</p>

            <p begin=”00:38.4″ end=”00:40.1″>denn bei<br/>Lichtgeschwindigkeit</p>

            <p begin=”00:40.1″ end=”00:42.0″>würde die Länge<br/>auf Null schrumpfen</p>

            <p begin=”00:42.0″ end=”00:44.5″>und die Zeit<br/>würde stille stehen.</p>

    </div>

  </body>

</tt>

TV isn’t going just anywhere; it’s going everywhere. Which is why we at Adobe are launching Adobe Pass®, a new authentication service for TV content providers looking to reach more viewers on more connected devices. As a long-time partner with Limelight Networks, we’re also working with the Limelight Video Platform to present content owners and distributors with a comprehensive solution offering everything from video player options and user authentication, to web acceleration services and secure delivery across laptops, smartphones, tablets, connected televisions and more.

TV Everywhere is still a relatively new concept, but one that broadcasters and pay-TV providers are aggressively pursuing in order to meet consumer demand, realize new revenue opportunities, and remain competitive in the market. Authentication is perhaps the biggest challenge with new deployments. How do you get content to new devices quickly and easily while ensuring it remains protected? Approaches in the industry have varied significantly so far, with providers testing a wide range of technologies. This experimentation has made it clear what is most important in a solution – namely flexibility, ease of use, and secure authorization – all of which we can deliver with Adobe Pass.  Once an authentication system is in place, providers can not only deliver content everywhere, but also begin to offer cross-platform services, and take advantage of new monetization opportunities available online.

Meanwhile, the Limelight Video Platform has some great capabilities that fit with Adobe Pass, and with our mission to keep things simple, but also customizable in the online video world. Open APIs, optional integrated delivery services, and flexible content management all contribute to an experience that is effectively streamlined for video providers, and easy and enjoyable for online TV viewers.

For detailed information on Adobe Pass, take a look at www.adobe.com/go/adobepass. Adobe Pass is fully deployed and available today. Highlights include:

• Leverages the Flash Platform and HTML5
• Player and DRM platform agnostic
• Flexible business rules
• Easy integration with multiple Pay tv providers
• Leverages the latest security capabilities in the Adobe Flash® Player runtime
• Single log-in for consumers; no additional download required

Limelight Video Platform Universal Embed Codes now have intelligence built into them that ensures video delivery to all devices including mobile. With video consumption on mobile phones growing rapidly, you will want to be sure that your customers are getting access to your site’s videos regardless of device. Once LVP Mobile Delivery is enabled, all a user has to do is drop the Universal Embed Code onto a web page. When a visitor comes to that page the Universal Embed Code will automatically detect and deliver the proper transcoded video file based on the visitor’s hardware environment regardless if it’s a PC or a Smartphone including Blackberrys, Androids, HTML5 or iDevices.

LVP Mobile Delivery is standard on the Enterprise Edition, but is also available for a monthly fee on the Professional and Premier Editions. If you have questions or would like to enable Mobile Delivery on your account, click here to contact us.

The VPS product and development team built the player by using a standard live player template that was then custom-skinned with the NFL’s logo and other branding elements. The player also included a playlist that enabled the viewer to switch to different cameras that were covering the event. Naturally the NFL wanted to monetize the live content so the VPS live player trafficked ads from DART/Double Click for pre-roll and companion ads as viewers joined the event. To ensure the best possible viewing experience the player delivered adaptive bit-rate streams.

NFL Superbowl XLV Media Day Player

Online publishers that want to deliver a large number of videos on their website will need to rely heavily on metadata properties. The ability to filter, sort and search metadata greatly simplifies and accelerates the process of organizing and delivering video libraries that contain hundreds or even thousands of titles. While most online video platforms offer some basic meta tags like Title, Description, Keywords and Genre’, the Limelight Video Platform (LVP) is the most sophisticated with customizable metadata properties. Not only does LVP allow the creation of customized metadata fields but LVP stands alone in the ability to easily sort and search custom fields.

These customizable metadata fields can be text, numeric or a pick list of pre-determined values. For example, a music video publisher may want to add some custom metadata fields for Artist, Record Label and SKU data. These fields would be ideal as pick lists. The text field would work best if you want to allow free form text.

The custom metadata properties are only available in the premier and enterprise versions of LVP.

Searchable Custom Metadata Properties