Video

This section describes working with video in Dynamic Media.

Quick Start: Videos

The following step-by-step workflow description is designed to help you get up and running quickly with adaptive video sets in Dynamic Media. After each step is cross-references to topic headings where you can find more information.

1. Upload your Dynamic Media videos by doing the following:

   • Create your own video encoding profile. Or, you can simply use the predefined Adaptive Video Encoding profile that comes with Dynamic Media.

     • Create a video encoding profile.
     • Learn more about Best practices for video encoding.

   • Associate the video processing profile to one or more folders where you are going to upload your primary source videos.

     • Apply a video profile to folders.
     • Learn more about Organize digital assets.

   • Upload your primary source videos to the folders. When you add videos to the folder, they are encoded according to the video processing profile that you assigned to the folder.

     • Dynamic Media supports primarily short-form videos with a maximum length of 30 minutes and a minimum resolution that is greater than 25 x 25.
     • You can upload video files that are up to 15 GB each.
     • Upload your videos.
     • Learn more about Supported input file formats.

   • Monitor how video encoding is progressing either from the asset or workflow view.

2. Manage your Dynamic Media videos by doing any of the following:

   • Organize, browse, and search video assets

     • Organize digital assets
     • Search video assets or Searching assets

   • Preview and publish video assets

     • View the source video and encoded renditions of the video along with its associated thumbnails:
       Preview videos or Preview assets
       Manage video renditions

     • Manage viewer presets

     • Publishing assets

   • Work with video metadata

     • Edit the properties of video such as the title, description, and tags, custom metadata fields:
       Editing video properties

     • Managing metadata for digital assets

     • Metadata schemas

   • Review, approve, and annotate videos, and maintain full version control

     • Annotating videos or Annotating assets

     • Creating a version

     • Starting a workflow on an asset

     • Review folder assets

     • Projects

3. Publish your Dynamic Media videos by doing one of the following:

   • If you use Experience Manager as your WCM (Web Content Management) system, you can add videos directly to your web pages.

     • Add videos to your web pages.

   • If you are using a third-party web content management system, you can link or embed videos to your web pages.

     • Integrate video using URL:
       Link URLs to your web application.

     • Integrate video using embed code on web page:
       Embed the video viewer on a web page.

   • Publish videos to YouTube.

   • Generate video reports.

   • Add captions to video.

Work with video in Dynamic Media

Video in Dynamic Media is an end-to-end solution that makes it easy to publish high-quality Adaptive Video for streaming across multiple screens, including desktops, tablets, and mobile devices. An Adaptive Video Set groups versions of the same video that are encoded at different bit rates and formats such as 400 kbps, 800 kbps, and 1000 kbps. The desktop computer or mobile device detects the available bandwidth.

For example, on an iOS mobile device, it detects a bandwidth such as 3G, 4G, or Wi-Fi. Then, it automatically selects the right encoded video from among the various video bit rates within the Adaptive Video Set. The video is streamed to desktops, mobile devices, or tablets.

In addition, video quality is dynamically switched automatically if network conditions change on the desktop or on the mobile device. Also, if a customer enters full-screen mode on a desktop, the Adaptive Video Set responds by using a better resolution, improving the customer’s viewing experience. Using Adaptive Video Sets provides you with the best possible playback for customers playing Dynamic Media video on multiple screens and devices.

The logic that a video player uses to determine which encoded video to play or to select during playback is based on the following algorithm:

1. Video player loads the initial video fragment based on the bit rate that is closest to the value that is set for “initial bitrate” in the player itself.

2. Video player switches based on changes to the bandwidth speed using the following criteria:

   1. Player picks the highest bandwidth stream below or equal to the estimated bandwidth.
   2. Player considers only 80% of the available bandwidth. However, if it is switching up, it is more conservative at only 70% to avoid overestimating and immediately switching back.

For detailed technical information about the algorithm, see https://android.googlesource.com/platform/frameworks/av/+/master/media/libstagefright/httplive/LiveSession.cpp

For managing single video and Adaptive Video Sets, the following is supported:

• Uploading video from numerous supported video formats and audio formats and encoding video to MP4 H.264 format for playback across multiple screens. You can use predefined adaptive video presets, single video encoding presets, or customize your own encoding to control the quality and size of the video.

  • When an adaptive video set is generated, it includes MP4 videos.
  • Note: Primary/source videos are not added to an Adaptive Video Set.

• Video captioning in all HTML5 video viewers.

• Organize, browse, and search video with full metadata support for efficient management of video assets.

• Deliver Adaptive Video Sets to the web and desktops, tablets, and mobile devices.

Adaptive video streaming is supported on various iOS platforms. See Dynamic Media Viewers Reference Guide.

• Play back the video using Dynamic Media Video Viewer Presets, including the following:

  • Single video viewers.
  • Mixed Media viewers that combine both video and image content.

• Configure video players to meet your branding needs.

• Integrate video to your website, mobile site, or mobile application with a simple URL or embed code.

See Dynamic video playback sample.

See also Viewers for Experience Manager Assets and Dynamic Media Classic and Viewers for Experience Manager Assets only in the Dynamic Media Viewers Reference Guide.

Best practice: Using the HTML5 video viewer

The Dynamic Media HTML5 Video viewer presets are robust video players. You can use them to avoid many common issues that are associated with HTML5 video playback and issues associated with mobile devices. For example, a lack of adaptive streaming delivery and limited desktop browser reach.

On the design side of the player, you can design the video player’s functionality using standard web development tools. For example, you can design the buttons, controls, and custom poster image background using HTML5 and CSS to help you reach your customers with a customized appearance.

On the playback side of the viewer, it automatically detects the browser’s video capability. It then serves the video using HLS (HTTP Live Streaming), also known as adaptive video streaming. Or, if those delivery methods are not present then HTML5 progressive is used instead.

You can combine into a single player the ability to design the playback components using HTML5 and CSS. It can have embedded playback, and use adaptive and progressive streaming depending on the browser’s capability. All this functionality, means you can extend the reach of your rich media content to both desktop and mobile users and ensure a streamlined video experience.

See also Viewers for Experience Manager Assets only in the Dynamic Media Viewers Reference Guide.

Playback of video on desktop computers and mobile devices using the HTML5 video viewer

For desktop and mobile adaptive video streaming, the videos used for bit rate switching are based on all MP4 videos in the Adaptive Video Set.

Video playback occurs using either HLS or progressive video download. In prior versions of Experience Manager, such as 6.0, 6.1, and 6.2, videos were streamed over HTTP.

However, in Experience Manager 6.3 and on, videos are now streamed over HTTPS (that is, HLS) because the DM gateway service URL always uses HTTPS as well. There is no customer impact in this default behavior. That is, video streaming will always occur over HTTPS unless it is not supported by the browser. (see the following table). Therefore,

• If you have an HTTPS website with HTTPS video streaming, streaming is fine.
• If you have an HTTP website with HTTPS video streaming, streaming is fine and there are no mixed content issues from the web browser.

HLS is an Apple standard for adaptive video streaming that automatically adjusts playback based on network bandwidth capacity. It also lets the customer “seek” to any point in the video without the need to wait for the rest of the video to download.

Progressive video is delivered by downloading and storing the video locally on a user’s desktop system or mobile device.

The following table describes the device, browser, and playback method of videos on desktop computers and mobile devices using the Dynamic Media HTML5 Video Viewer.

Architecture of Dynamic Media video solution

The following graphic shows the overall authoring workflow of videos that are uploaded and encoded by way of DMGateway (in Dynamic Media Hybrid mode) and made available for public consumption.

Hybrid publishing architecture for videos

Best practices for encoding videos

The Dynamic Media Encode Video workflow encodes video if you have enabled Dynamic Media and set up video Cloud Services. This workflow captures workflow process history and failure information. See Monitor video encoding and YouTube publishing progress. If you have enabled Dynamic Media and set up video Cloud Services, the Dynamic Media Encode Video workflow automatically takes effect when you upload a video. (If you are not using Dynamic Media, the DAM Update Asset workflow takes effect.)

The following are best-practice tips for encoding source video files.

Source video files

When you encode a video file, use a source video file of the highest possible quality. Avoid using previously encoded video files because these files are already compressed, and further encoding creates a subpar quality video.

• Dynamic Media supports primarily short-form videos with a maximum length of 30 minutes and a minimum resolution that is greater than 25 x 25.
• You can upload primary source video files that are up to 15 GB each.

The following table describes the recommended size, aspect ratio, and minimum bit rate that your source video files must have before you encode them:

Obtain a file’s metadata

You can obtain a file’s metadata by viewing its metadata using a video editing tool, or using an application designed for obtaining metadata. Following are instructions for using MediaInfo, a third-party application, to obtain a video file’s metadata:

1. Go to MediaInfo Download.
2. Select and download the installer for the GUI version, and follow the installation instructions.
3. After installation, either right-click the video file (Windows® only) and select MediaInfo, or open MediaInfo and drag your video file into the application. You see all metadata associated with your video file, including its width, height, and fps.

Aspect ratio

When you choose or create a video encoding preset for your primary source video file, make sure that the preset has the same aspect ratio as the primary source video file. The aspect ratio is the ratio of the width to the height of the video.

To determine the aspect ratio of a video file, obtain the file’s metadata and note the file’s width and height (see Obtaining a file’s metadata above). Then use this formula to determine the aspect ratio:

width/height = aspect ratio

The following table describes how formula results translate to common aspect ratio choices:

For example, a video that is 1440 width x 1080 height has an aspect ratio of 1440/1080, or 1.33. In this case, you choose a video encoding preset with a 4:3 aspect ratio to encode the video file.

Bitrate

Bitrate is the amount of data that is encoded to make up a single second of video playback. The bitrate is measured in kilobits per second (Kbps).

When selecting a bitrate encoding, there are two types you can choose:

• Constant Bitrate Encoding (CBR) - During CBR encoding, the bitrate, or the number of bits per second is kept the same throughout the encoding process. CBR encoding persists the set data rate to your setting over the entire video. Also, CBR encoding does not optimize media files for quality but does save on storage space.
  Use CBR if your video contains a similar motion level throughout the entire video. CBR is most commonly used for streaming video content. See also Use custom-added video encoding parameters.

• Variable Bitrate Encoding (VBR) - VBR encoding adjusts the data rate down and to the upper limit you set, based on the data required by the compressor. This functionality means that during a VBR encoding process the bitrate of the media file dynamically increases or decreases depending on the media files bitrate needs.
  VBR takes longer to encode but produces the most favorable results; the quality of the media file is superior. VBR is most commonly used for http progressive delivery of video content.

When do you use VBR versus CRB?
When selecting VBR versus CBR, it is almost always recommended that you use VBR for your media files. VBR provides higher-quality files at competitive bitrates. When you use VBR, be sure you use with two-pass encoding, and set the maximum bitrate to be 1.5x the target video bitrate.

When you choose a video encoding preset, be sure you account for the target end user’s connection speed. Choose a preset with a data rate that is 80 percent of that speed. For example, if the target end user’s connection speed is 1000 Kbps, the best preset is one with a video data rate of 800 Kbps.

This table describes the data rate of typical connection speeds.

Resolution

Resolution describes a video file’s height and width in pixels. Most source video is stored at a high resolution (for example, 1920 x 1080). For streaming purposes, source video is compressed to a smaller resolution (640 x 480 or smaller).

Resolution and data rate are two integrally linked factors that determine video quality. To maintain the same video quality, the higher the number of pixels in a video file (the higher the resolution), the higher the data rate must be. For example, consider the number of pixels per frame in a 320 x 240 resolution and a 640 x 480 resolution video file:

The 640 x 480 file has four times more pixels per frame. To achieve the same data rate for these two example resolutions, you apply four times the compression to the 640 x 480 file, which can reduce the quality of the video. Therefore, a video data rate of 250 Kbps produces high-quality viewing at a 320 x 240 resolution, but not at a 640 x 480 resolution.

In general, the higher data rate you use, the better your video appears, and the higher resolution you use, the higher data rate you must maintain viewing quality (compared to lower resolutions).

Because resolution and data rate are linked, you have two options when encoding video:

• Choose a data rate and then encode at the highest resolution that appears good at the data rate you chose.
• Choose a resolution and then encode at the data rate necessary to achieve high-quality video at the resolution you chose.

When you choose (or create) a video encoding preset for your primary source video file, use this table to target the correct resolution:

Fps (Frames per second)

In the United States and Japan, most video is shot at 29.97 frames per second (fps); in Europe, most video is shot at 25 fps. Film is shot at 24 fps.

Choose a video encoding preset that matches the fps rate of your primary source video file. For example, if your primary source video is 25 fps, choose an encoding preset with 25 fps. By default, all custom encoding uses the primary source video file’s fps. For this reason, you do not need to explicitly specify the fps setting when you create a video encoding preset.

Video encoding dimensions

For optimal results, select encoding dimensions such that the source video is a whole multiple of all your encoded videos.

To calculate this ratio, you divide source width by encoded width to get the width ratio. Then, you divide source height by encoded height to get the height ratio.

If the resulting ratio is a whole integer, it means that the video is optimally scaled. If the resulting ratio is not a whole integer, it impacts video quality by leaving leftover pixel artifacts on the display. This effect is most noticeable when the video has text.

As an example, suppose that your source video is 1920 x 1080. In the following table, the three encoded videos provide the optimal encoding settings to use.

Encoded video file format

Dynamic Media recommends using MP4 H.264 video encoding presets. Because MP4 files use the H.264 video codec, it provides high-quality video but in a compressed file size.

Publish videos to YouTube

You can publish video assets managed in Experience Manager Assets directly to a YouTube channel that you have previously created.

To publish video assets to YouTube, you tag video assets in Experience Manager Assets with tags. You associate these tags with a YouTube channel. If a video asset’s tag matches the tag of a YouTube channel, then the video is published to YouTube. Publish to YouTube occurs along with a normal publish of the video as long as an associated tag is used.

YouTube does its own encoding. As such, the original video file that was uploaded into Experience Manager is published to YouTube instead of any video rendition that Dynamic Media’s encoding has created. While it is not required to process videos using Dynamic Media, it is expected that they do so in case a viewer preset is needed for playback.

When you bypass the video processing profile and publish directly to YouTube, it simply means that your video asset in Experience Manager Asset does not get a viewable thumbnail. It also means that videos that are not encoded do not work with any of the Dynamic Media asset types.

Publishing video assets to YouTube servers involves completing the following tasks to ensure safe and secure server-to-server verification with YouTube:

1. Configure Google Cloud settings
2. Create a YouTube channel
3. Add tags for publishing
4. Set up YouTube in Experience Manager
5. (Optional) Automate the setting of default YouTube properties for your uploaded videos
6. Publish videos to your YouTube channel
7. (Optional) Verify the published video on YouTube
8. Link YouTube URLs to your Web Application

You can also unpublish videos to remove them from YouTube.

Configure Google Cloud settings

To publish to YouTube, you need a Google account. If you have a GMAIL account, then you already have a Google account; if you do not have a Google account, you can easily create one. You need the account because you need credentials to publish video assets to YouTube.

The account used with Google Cloud and the Google account used for YouTube do not need to be the same.

Google periodically changes their user interface. As such, the steps to publish videos to YouTube can vary slightly from what is documented below. This caveat also applies to YouTube when you try to check if videos are uploaded to it.

To configure Google Cloud settings:

1. Create a Google account.
   https://accounts.google.com/signup/v2?service=mail&flowName=GlifWebSignIn&flowEntry=SignUp

   If you already have a Google account, you can skip to the next step.

2. Go to https://cloud.google.com/.

3. On the Google Cloud page, near the upper-right corner, select Console.

   If necessary, Sign in using your Google account credentials to see the Console option.

4. On the Dashboard page, to the right of Google Cloud Platform, select the Project drop-down list to open the Select a project dialog box.

5. In the Select a project dialog box, select New Project.

6. In the New Project dialog box, in the Project name field, type the name of your new project.

   Your Project ID is based on your project name. As such, choose the project name carefully; it cannot be changed after it is created. Also, you must enter the same Project ID again when you set up YouTube in Experience Manager later on. Therefore, write it down.

7. Select Create.

8. Do either one of the following:

   • On your project’s Dashboard, in the Getting Started card, select Explore and enable APIs.
   • On your project’s Dashboard, in the APIs card, select Go to APIs overview.

9. Near the top middle of the APIs & Services page, select ENABLE APIS AND SERVICES.

10. On the API Library page, on the left side, under Category, select YouTube. On the right side of the page, select YouTube.

11. On the YouTube page, select YouTube Data API v3.

12. On the YouTube Data API v3 page, select MANAGE.

    

13. To use the API, you need credentials. If necessary, on the left side of the APIs & Services page, select Credentials.

14. On the Credentials page, near the top, select CREATE CREDENTIALS, then select OAuth client ID.

15. On the Create OAuth client ID page, in the Application type drop-down list, select Web application.

    

16. Do one of the following:

    • In the Name field, enter a unique name for your OAuth 2.0 client.
    • Use the default name that Google already provided in the Name field.

17. Under the Authorized JavaScript origins heading, select ADD URI.

    

18. In the URIs text field, enter the following path, substituting your own domain and port number in the path, then press Enter to add the path to the list:

    https://<servername.domain>:<port_number>

    For example, https://1a2b3c.mycompany.com:4321

    NOTE

    The URI path example above is hypothetical and for explanation purposes only.

19. Under the Authorized redirect URIs heading, select ADD URI.

20. In the URIs text field, enter the following path, substituting your own domain and port number in the path, then press Enter to add the path to the list:

    https://<servername.domain>:<port_number>/etc/cloudservices/youtube.youtubecredentialcallback.json

    For example, https://1a2b3c.mycompany.com:4321/etc/cloudservices/youtube.youtubecredentialcallback.json

    NOTE

    The URI path example above is hypothetical and for explanation purposes only.

21. Near the bottom of the Create OAuth client ID page, select Create.

22. On the OAuth client created dialog box, do the following:

    • (Optional) Copy the values in the Your Client ID and Your Client Secret fields, and save.
    • Select DOWNLOAD JSON, then save the JSON file.

    You need this downloaded JSON file when you set up YouTube in Adobe Experience Manager later on.

    

23. On the OAuth client created dialog box, select OK.

24. Log out of your Google account. Now create a YouTube channel.

Create a YouTube channel

Publishing videos to YouTube requires that you have one or more channels. If you have already created a YouTube channel, you can skip this task and go to Add tags for publishing.

To create a YouTube channel:

1. Go to https://www.youtube.com and sign in using your Google account credentials.

2. In the upper-right corner of the YouTube page, select your profile picture (it can also appear as a letter within a solid colored circle), then select YouTube settings (round gear icon).

3. On the Overview page, under the Additional Features heading, select See all my channels or create a channel.

4. On the Channels page, select Create a new channel.

5. On the Brand Account page, in the Brand Account Name field, enter a company name or any other channel name you choose where you want to publish your video assets, then select Create.

   Remember the name that you enter here; you must enter it again when you have to set up YouTube in Experience Manager.

6. (Optional) If necessary, add more channels.

   Now you add tags for publishing.

Add tags for publishing

To publish to your videos to YouTube, Experience Manager associates tags to one or more YouTube channels. To add tags for publishing, see Administer Tags.

Or, if you intend to use the default tags in Experience Manager, you can skip this task and go to Set up YouTube in Experience Manager.

Set up YouTube in Experience Manager

Starting with Experience Manager 6.4, a new touch user interface method was introduced to set up YouTube publishing in Experience Manager. Based on the installed instance of Experience Manager that you are using, do one of the following:

• To configure YouTube in Experience Manager before 6.4, see Set up YouTube in Experience Manager before 6.4.
• To configure YouTube in Experience Manager 6.4 or later, see Set up YouTube in Experience Manager 6.4 and later.

Set up YouTube in Experience Manager 6.4 and later

1. Be sure you log in to your instance of Dynamic Media as an Administrator.

2. In the upper-left corner of Experience Manager, select the Experience Manager logo, then in the left rail, navigate to Tools(hammer icon) > Cloud Services > YouTube Publishing Configuration.

3. Select global (do not select it).

4. Near the upper-right corner of the global page, select Create.

5. On the Create YouTube Configuration page, under Google Cloud Platform Settings, in the Application Name field, enter the Google Project ID.

   You specified the project ID when you initially configured Google Cloud settings earlier.
   Leave the Create YouTube Configuration page open; you are returning to it in a moment.

   

6. Using a plain text editor, open the JSON file that you downloaded and saved earlier in the task Configure Google Cloud settings.

7. Select and copy the entire JSON text.

8. Return to the YouTube Account Settings dialog box. In the JSON Config field, paste the JSON text.

9. Near the upper-right corner of the page, select Save.

   Now set up YouTube channels in Experience Manager.

10. Select Add Channel.

11. In the Channel Name field, enter the name of the channel that you created in the task Adding one or more channels to YouTube earlier.

    You can optionally add a description, if desired.

12. Select Add.

13. YouTube/Google verification is displayed. If you are not already logged into the Google Cloud account, then skip this step.

    • Enter the Google username and password associated with the Google Project ID and the JSON text above.
    • Depending on how many channels your account has you see two or more items. Select a channel. Do not select the e-mail address; it is not a channel.
    • On the next page, select Accept to allow access to this channel.

14. Select Allow.

    Now set up tags for publishing.

15. Setting up tags for publishing - On the Cloud Services > YouTube page, select the pencil icon to edit the list of tags that you want to use.

16. To display the list of available tags in Experience Manager, select the drop-down list icon (upside-down caret).

17. To add them, select one or more tags.

    To delete a tag you have added, select the tag, and select X.

18. When you are finished adding the tags you want, select Save.

    Now you publish videos to your YouTube channel.

Set up YouTube in Experience Manager before 6.4

1. Be sure you log in to your instance of Dynamic Media as an Administrator.

2. In the upper-left corner of Experience Manager, select the Experience Manager logo, then in the left rail, navigate to Tools (hammer icon) > Deployment > Cloud Services.

3. Under the Third-Party Services heading, under YouTube, select Configure now.

4. In the Create Configuration dialog box, enter a title (mandatory) and name (optional) in the respective fields.

5. Select Create.

6. In the YouTube Account Settings dialog box, in the Application Name field, enter the Google Project ID.

   You specified the project ID when you initially configured Google Cloud settings earlier.
   Leave the YouTube Account Setting dialog box open; you are returning to it in a moment.

7. Using a plain text editor, open the JSON file that you downloaded and saved earlier in the task Configuring Google Cloud settings.

8. Select and copy the entire JSON text.

9. Return to the YouTube Account Settings dialog box. In the JSON Config field, paste the JSON text.

10. Select OK.

    Now set up YouTube channels in Experience Manager.

11. To the right of Available Channels, select + (plus sign icon).

12. In the YouTube Channel Settings dialog box, in the Title field, enter the name of the channel that you created in the task Adding one or more channels to YouTube earlier.

    You can optionally add a description, if desired.

13. Select OK.

14. YouTube/Google verification is displayed. If you are not already logged into the Google Cloud account, then skip this step.

    • Enter the Google username and password associated with the Google Project ID and the JSON text above.
    • Depending on how many channels your account has you see two or more items. Select a channel. Do not select the e-mail address; it is not a channel.
    • On the next page, select Accept to allow access to this channel.

15. Select Allow.

    Now set up tags for publishing.

16. Setting up tags for publishing - On the Cloud Services > YouTube page, select the pencil icon to edit the list of tags that you want to use.

17. To display the list of available tags in Experience Manager, select the drop-down list icon (upside-down caret).

18. To add them, select one or more tags.

    To delete a tag you have added, select the tag, and select X.

19. When you are finished adding the tags you want, select OK.

    Now you publish videos to your YouTube channel.

(Optional) Automate the setting of default YouTube properties for your uploaded videos

You can optionally automate the setting of YouTube properties on upload of your videos. Create a metadata processing profile in Experience Manager.

To create the metadata processing profile, you are first going to copy values from the Field Label, Map to property, and Choices fields, all found in Metadata Schemas for video. Then, you build your YouTube video metadata processing profile by adding those values to it.

To automate the setting of default YouTube properties for your uploaded videos:

1. In the upper-left corner of Experience Manager, select the Experience Manager logo, then in the left rail, navigate to Tools (hammer icon) > Assets > Metadata Schemas.

2. Select default. (Do not add a checkmark to the selection box to the left of “default”.)

3. On the default page, check the box to the left of video, then select Edit.

4. On the Metadata Schema Editor page, select the Advanced tab.

5. Under the YouTube Publishing heading, select YouTube Category.

6. On the right side of the page, under the Settings tab, do the following:

   • In the Map to property text field, select and copy the value.
     Paste the copied value into the open text editor. You are going to need this value later when you create your metadata processing profile. Leave the text editor open.

   • Under Choices, select and copy the default value that you want to use (such as People & Blogs or Science & Technology).
     Paste the copied value into the open text editor. You are going to need this value later when you create your metadata processing profile. Leave the text editor open.

7. Under the YouTube Publishing heading, select YouTube Privacy.

8. On the right side of the page, under the Settings tab, do the following:

   • In the Map to property text field, select and copy the value.
     Paste the copied value into the open text editor. You are going to need this value later when you create your metadata processing profile. Leave the text editor open.

   • Under Choices, select and copy the default value that you want to use. Notice that the Choices are grouped in pairs of two. The bottom field in the pair is the default value that you want to copy, such as public, unlisted, or private.
     Paste the copied value into the open text editor. You are going to need this value later when you create your metadata processing profile. Leave the text editor open.

9. Near the upper-right corner of the Metadata Schema Editor page, select Cancel.

10. In the upper-left corner of Experience Manager, select the Experience Manager logo, then in the left rail, select Tools (hammer icon) > Assets > Metadata Profiles.

11. On the Metadata Profiles page, near the upper-right corner of the page, select Create.

12. In the Add Metadata Profile dialog box, in the Profile title text field, enter the name YouTube Video then select Create.

13. On the Metadata Profile Editor page, select the Advance tab.

14. Add the copied YouTube Publishing values to the profile by doing the following:

    • On the right side of the page, select the Build Form tab.

    • (Optional) Drag the component labeled Section Header to the left and drop it in the form area.

    • (Optional) Select Field Label to select the component.

    • (Optional) On the right side of the page, under the Settings tab, in the Field Label text field, enter YouTube Publishing.

    • Select the Build Form tab, then drag the component labeled Multi Value Text and drop it below the YouTube Publishing heading that you created.

    • To select the component, select Field Label.

    • On the right side of the page, under the Settings tab, paste the YouTube Publishing values (Field Label value and Map to property value) that you copied earlier, into their respective fields on the form. Paste the Choices value into the Default Value field.

15. Add the copied YouTube Privacy values to the profile by doing the following:

    • On the right side of the page, select the Build Form tab.

    • (Optional) Drag the component labeled Section Header to the left and drop it in the form area.

    • (Optional) Select Field Label to select the component.

    • (Optional) On the right side of the page, under the Settings tab, in the Field Label text field, enter YouTube Privacy.

    • Select the Build Form tab, then drag the component labeled Multi Value Text and drop it below the YouTube Privacy heading you created.

    • To select the component, select Field Label.

    • On the right side of the page, under the Settings tab, paste the YouTube Publishing values (Field Label value and Map to property value) that you copied earlier, into their respective fields on the form. Paste the Choices value into the Default Value field.

16. Near the upper-right corner of the page, select Save.

17. Apply the YouTube Publishing metadata profile to the folders where you are going to upload videos. You must have both the Metadata Profile and the Video Profile set.

    See Metadata Profiles and Video Profiles.

Publish videos to your YouTube channel

Now you associate the tags that you added earlier to video assets. This process lets Experience Manager know which assets to publish to your YouTube channel.

To publish videos to your YouTube channel:

1. In Experience Manager, navigate to a video asset that you want to publish to your YouTube channel.

2. Select the video asset (the adaptive video set).

3. On the toolbar, select Properties.

4. In the Basic tab, under the Metadata heading, select Open Selection Dialog to the right of the Tags field.

5. On the Select Tags page, navigate to the tags you want to use, and then select one or more tags.

   Remember that the tags must be associated with the YouTube channel.

6. In the upper-right corner of the page, select Select.

7. In the upper-right corner of the video’s properties page, select Save and Close.

8. On the toolbar, select Quick Publish.

   See also Use Publication Management with Experience Manager Sites.

   You can optionally verify the published video on your YouTube channel.

(Optional) Verify the published video on YouTube

You can optionally monitor progress of your YouTube publishing (or unpublishing).

See Monitor video encoding and YouTube publishing progress.

Publishing times can vary greatly depending on numerous factors that include the format of your primary source video, file size, and upload traffic. The publishing process can take anywhere from a few minutes to several hours. Also, higher resolution formats are rendered much more slowly. For example, 720p and 1080p take longer to appear than 480p.

After eight hours, if you still see a status message that says Uploaded (processing, please wait), try removing the video from your site and uploading it again.

Link YouTube URLs to your Web Application

You can obtain a YouTube URL string that is generated by Dynamic Media after you publish the video. When you copy the YouTube URL, it lands on the Clipboard so you can paste it as necessary to pages in your website or application.

To link YouTube URLs to your web application:

1. Navigate to the YouTube published video asset whose URL you want to copy, then select it.

   Remember that YouTube URLs are only available to copy after you have first published the video assets to YouTube.

2. On the toolbar, select Properties.

3. Select the Advanced tab.

4. Under the YouTube Publishing heading, in the YouTube URL List, select, and copy the URL text to your web browser to preview the asset or to add to your web content page.

Unpublish videos so you can remove them from YouTube

When you unpublish a video asset in Experience Manager, the video is removed from YouTube.

To unpublish videos to remove them from YouTube:

1. Navigate to the video assets that you want to unpublish from your YouTube channel.
2. In an asset selection mode, select one or more published video assets.
3. On the toolbar, select Manage Publication. If necessary, select the three dots icon (. . .) on the toolbar to see Manage Publication.
4. On the Manage Publication page, select Unpublish.
5. In the upper-right corner of the page, select Next.
6. In the upper-right corner of the page, select Unpublish.

Monitor video encoding and YouTube publishing progress

When you upload a new video to a folder that has video encoding applied or, you publish your video to YouTube, monitor how your video encoding/Youtube publishing is progressing (or failing). Actual YouTube publishing progress is only available by way of the logs. But whether it fails or succeeds, it is listed in other ways described in the following procedure. In addition, you receive email notifications when a YouTube publish workflow or video encoding completes or is interrupted.

Monitor progress

You can monitor progress, including failed encoding/YouTube publish.

1. View video encoding progress in your assets folder:

   • In card view, video encoding progress displays on the asset by percent. If there is an error, this information also displays on the asset.

   

   • In list view, video encoding progress displays in the Processing Status column. If there is an error, this message displays in that same column.

   

   This column does not display by default. To enable the column, select View Settings from the views drop-down menu, and add the Processing Status column and select Update.

   

2. View progress in the asset details. When you select an asset, open the drop-down menu and select Timeline. To narrow it down to workflow activities like encoding or YouTube publishing, select Workflows.

   

   Any workflow information–such as encoding–displays in the timeline. For YouTube publish, the Workflow timeline also includes the name of the YouTube channel and the YouTube video URL. In addition, you see any failure notifications in the Workflow timeline after the publish is complete.

   NOTE

   It can take a long time for failure/error messages to finally be recorded due to multiple workflow configurations on retries, retry delay, and timeout from https://localhost:4502/system/console/configMgr, for example:

   • Apache Sling Job Queue Configuration
   • Adobe Granite Workflow External Process Job Handler
   • Granite Workflow Timeout Queue

   You can adjust the retries, retry delay, and timeout properties in these configurations.

3. For workflows in progress, see Workflow Instances available from Tools > Workflow > Instances.

   NOTE

   You need administrative rights to access the Tools menu.

   

   Select the instance and select Open History.

   

   From the Workflow Instances area, you can also suspend, terminate, or rename workflows. See Administer workflows for more information.

4. For failed jobs, see Workflow Failures available from Tools > Workflow > Failures. The Workflow Failure lists all failed workflow activities.

   NOTE

   You need administrative rights to access the Tools menu.

   

   NOTE

   It can take a long time for the error message to finally be recorded due to multiple workflow configurations on retries, retry delay, and timeout from https://localhost:4502/system/console/configMgr, for example:

   • Apache Sling Job Queue Configuration
   • Adobe Granite Workflow External Process Job Handler
   • Granite Workflow Timeout Queue

   You can adjust the retries, retry delay, and timeout properties in these configurations.

5. For completed workflows, see Workflow Archive available from Tools > Workflow > Archive. The Workflow Archive lists all completed workflow activities.

   NOTE

   You need administrative rights to access the Tools menu.

   

6. You receive email notifications about aborted or failed workflow jobs. These email notifications are configurable by an administrator. See Configure email notifications.

View video reports

Video Reports display several aggregate metrics across a specified period to help you monitor that published individual and aggregate videos are performing as expected. The following top metrics data are aggregated for all published videos across your entire website:

• Video Starts
• Completion Rate
• Average time on video
• Total time on video
• Videos per visit

A table of all published videos is also listed so you can track the top viewed videos on your website based on total video starts.

When you select a video name in the list, it shows you the video’s audience retention (drop-off) report in the form of a line chart. The chart displays the number of views for any given moment of time during video playback. When you play the video, the vertical bar tracks in synchronization with the time indicator in the player. Drops in the line chart data indicate where your audience drops off from disinterest.

If the video was encoded outside of Adobe Experience Manager Dynamic Media, the audience retention (drop-off) chart and the Play Percentage data in the table are not available.

By default, the first time you enter Video Reports, the report displays video data starting at the first of the current month and ends with the current month’s date. However, you can override the default date range by specifying your own date range. The next time you enter Video Reports, the date range you specified is used.

For video reports to work correctly, a Report Suite ID is automatically created when Dynamic Media Cloud Services is configured. At the same time, the Report Suite ID is pushed to the Publish server so that it is available for the Copy URL feature when you preview assets. However, this functionality requires the Publish server be already set up. If the Publish server is not set up, you can still publish to see the video report. However, you must return to the Dynamic Media Cloud Configuration and select OK.

To view video reports:

1. In the upper-left corner of Experience Manager, select the Experience Manager logo, then in the left rail, navigate to Tools (hammer icon) > Assets > Video Reports.

2. On the Video Reports page, do one of the following:

   • Near the upper-right corner, select the Refresh Video Report icon.
     You use Refresh only if the end date of the report is the current day. This feature ensures that you see the video tracking that has occurred since the last time you ran the report.

   • Near the upper-right corner, select the Date Picker icon.
     Specify the beginning and end date range for which you want video data, and then select Run Report.

   The Top Metrics group box identifies various aggregate measurements for all published videos across your site.

3. In the table that lists the top published videos, select a video name to play the video and also see the video’s audience retention (drop-off) report.

Add closed captions or subtitles to video

You can extend the reach of your videos to global markets by adding closed captioning to single videos or to Adaptive Video Sets. By adding closed captioning you avoid the need to dub the audio, or the need to use native speakers to rerecord the audio for each different language. The video is played in the language that it was recorded. Foreign language subtitles appear so that people of different languages can still understand the audio portion.

Closed captioning also allows for greater accessibility for people who are deaf or hard of hearing.

See also Accessibility in Dynamic Media.

Dynamic Media can convert caption files to JSON (JavaScript Object Notation) format. This conversion means you can embed the JSON text into a web page as a hidden but complete transcript of the video. Search engines can then crawl/index the content to make the videos more easily discoverable and give customers more details about the video content.

See Serving static (non-image) contents for more information about using the JSON function in a URL.

To add captions or subtitles to video:

1. Use a third-party application or service to create your video caption/subtitle file.

   Ensure that the file you create follows the WebVTT (Web Video Text Tracks) standard. The captioning filename extension is .VTT. You can learn more information about the WebVTT captioning standard.

   See WebVTT: The Web Video Text Tracks format.

   There are both free and premium tools and services that you can use to author caption/subtitle files outside Dynamic Media. For example, to create a simple video caption file with no styling, you can use the following free online caption authoring and editing tool:

   WebVTT Caption Maker

   For best results, use the tool in Internet Explorer 9 or above, Google Chrome, or Safari.

   In the tool, in the Enter URL of video file field, paste the copied URL of your video file and then select Load. See Obtain a URL for an Asset to get the URL to the video file itself which you can then paste into the Enter URL of video file field. Internet Explorer, Chrome, or Safari can then natively play back the video.

   Now follow the onscreen instructions from the site to author and save your WebVTT file. When you have finished, copy the caption file contents and paste it into a plain text editor and save it with a VTT filename extension.

   NOTE

   For global support of video subtitles in multiple languages, the WebVTT standard requires that you create separate .vtt files and calls for each language you want to support.

   Generally, you want to name the caption VTT file the same name as the video file, and append it with the language locale, such as -EN, or -FR, or -DE. By doing so, it can help you with automating the generation of the video URLs using your existing web content management system.

2. In Experience Manager, upload your WebVTT caption file into DAM.

3. Navigate to the published video asset that you want to associate with the caption file that you uploaded.

   Remember that URLs are only available to copy after you have first published the assets.

   See Publish assets.

4. Do one of the following:

   • For a pop-up video viewer experience, select URL. In the URL dialog box, select and copy the URL to the Clipboard and then past the URL into a simple text editor. Append the copied URL of the video with the following syntax:

     &caption=<server_path>/is/content/<path_to_caption.vtt_file,1>

     Note the ,1 at the end of the caption path. Immediately following the VTT filename extension in the path, you can optionally enable (turn on) or disable (turn off) the closed caption button on the video player bar by setting to ,1 or ,0, respectively.

   • For an embedded video viewer experience, select Embed Code. In the Embed Code dialog box, select, and copy the embed code to the Clipboard and then paste the code into a simple text editor. Append the copied embed code with the following syntax:

     videoViewer.setParam("caption","<path_to_caption.vtt_file,1>");

     Note the ,1 at the end of the caption path. Immediately following the VTT filename extension in the path, you can optionally enable (turn on) or disable (turn off) the closed caption button on the video player bar by setting to ,1 or ,0, respectively.

Add chapter markers to video

You can make your long form videos easier to watch and navigate by adding chapter markers to single videos or to Adaptive Video Sets. When a user plays the video, they can select the chapter markers on the video timeline (also known as the video scrubber). They can easily navigate to their point of interest, or immediately jump to new content, training, and demonstrations.

You create a chapter list for your video in much the same way that you create captions. That is, you create a WebVTT file. Note, however, that this file must be separate from any WebVTT caption file. You cannot combine captions and chapters into one WebVTT file.

You can use the following sample as an example of the format you use to create a WebVTT file with chapter navigation:

WebVTT file with video chapter navigation

WEBVTT
Chapter 1
00:00.000 --> 01:04.364
The bicycle store behind it all.
Chapter 2
01:04.364 --> 02:00.944
Creative Cloud.
Chapter 3
02:00.944 --> 03:02.937
Ease of management for a working solution.
Chapter 4
03:02.937 --> 03:35.000
Cost-efficient access to rapidly evolving technology.

In the example above, Chapter 1 is the cue identifier and is optional. The cue time of 00:00:000 --> 01:04:364 specifies the start time and end time of the chapter, in 00:00:000 format. That last three digits are milliseconds and can be left as 000, if preferred. The chapter title of The bicycle store behind it all is the actual description of the chapter’s contents. The cue identifier, the starting cue time, and the chapter title all appear in a pop-up in the video player when a user hovers their mouse pointer over a visual cue point in the timeline.

Because you are using an HTML5 video viewer, ensure that the chapter file you create follows the WebVTT (Web Video Text Tracks) standard. The chapter filename extension is .VTT. You can learn more information about the WebVTT captioning standard.

See WebVTT: The Web Video Text Tracks format.

To add chapter markers to video:

1. Save the VTT file in UTF8 encoding so you avoid problems with character rendition in the chapter title text.

   Generally, you want to name the chapter VTT file the same name as the video file, and append it with chapters. By doing so, it can help you with automating the generation of the video URLs using your existing web content management system.

2. In Experience Manager, upload your WebVTT chapter file.

   See Upload assets.

3. Do one of the following:

   For a pop-up video viewer experience

   Navigate to the published video asset that you want to associate with the chapter file that you uploaded. Remember that URLs are only available to copy after you have first published the assets. See Publishing Assets. From the drop-down menu, then select Viewers. In the left rail, select the video viewer preset name. A preview of the video is opened in a separate page. In the left rail, at the bottom, select URL. In the URL dialog box, select and copy the URL to the Clipboard, then past the URL into a simple text editor. Append the copied URL of the video with the following syntax so you can associate it with the copied URL to your chapter file: &navigation=<full_copied_URL_path_to_chapter_file.vtt>

   For an embedded video viewer experience

   Navigate to the published video asset that you want to associate with the chapter file that you uploaded. Remember that URLs are only available to copy after you have first published the assets. See Publishing Assets. From the drop-down menu, then select Viewers. In the left rail, select the video viewer preset name. A preview of the video is opened in a separate page. In the left rail, at the bottom, select Embed. In the Embed Code dialog box, select, and copy the entire code to the Clipboard, then paste it into a simple text editor. Append the embed code of the video with the following syntax so you can associate it with the copied URL to your chapter file: videoViewer.setParam("navigation","<full_copied_URL_path_to_chapter_file.vtt>"