Adobe Experience Manager Assets provides for centralized video asset management where you can upload videos directly to Assets for auto-encoding to Dynamic Media Classic and access Dynamic Media Classic videos directly from Assets for page authoring.
Dynamic Media Classic video integration extends the reach of optimized video to all screens (auto device and bandwidth detection).
The default video encoding process is based on using the FFMPEG-based integration with video profiles. Therefore, the out-of-the-box DAM ingestion workflow contains the following two ffmpeg-based workflow steps:
Enabling and configuring the Dynamic Media Classic integration does not automatically remove or deactivate these two workflow steps from the out-of-the-box DAM ingestion workflow. If you already use the FFMPEG-based video encoding in Adobe Experience Manager, it is likely that you have FFMPEG installed on your authoring environments. In this case, a new video ingested using DAM would be encoded twice: once from the FFMPEG encoder and once from Dynamic Media Classic integration.
If you have the FFMPEG-based video encoding in Experience Manager configured and FFMPEG installed, Adobe recommends that you remove the two FFMPEG workflows from your DAM ingestion workflows.
The following formats are supported for the Scene7 Video component:
Deciding where to upload your video assets depends on the following:
If the answer is “yes” to either or both of these questions, then upload your video directly to Adobe DAM. If the answer is “no” to both questions, then upload your video directly to Dynamic Media Classic. The workflow for each scenario is described in the following section.
If you need a workflow or versioning for your assets, upload to Adobe DAM first. The following is the recommended workflow:
If you do not need a workflow or versioning for your assets, upload your assets to Scene7. The following is the recommended workflow:
To configure universal presets:
In Cloud Services, navigate to your Scene7 configuration and click Edit.
Select the Video tab.
The Video tab does not appear if the page does not have a cloud configuration.
Select the adaptive video encoding profile, an out-of-the-box single video encoding profile, or a custom video encoding profile.
For more information about what the video presets mean, see the Dynamic Media Classic documentation.
Adobe recommends that you select either both adaptive video sets when configuring the universal presets or select the Adaptive Video Encoding option.
The selected encoding profiles are automatically applied to all videos uploaded to the CQ DAM target folder you set up for this Scene7 cloud configuration. You can set up multiple Scene7 cloud configurations with different target folders to apply different encoding profiles as needed.
To update the viewer and encoding presets for video because the presets were updated in Scene7, navigate to the Scene7 configuration in the Cloud Configuration and tap Update the viewer and encoding presets.
Navigate to the CQ DAM target folder where you have set up your cloud configuration with Scene7 encoding profiles.
Click Upload to upload primary source video. Video uploading and encoding is complete after the DAM Update Asset workflow is complete and Publish to Scene7 has a checkmark.
It takes time for the video thumbnails to be generated.
Dragging the DAM primary source video onto the video component accesses all Scene7 encoded proxy renditions for delivery.
When using Experience Manager, you have access to both the Video component available in Sites and the Scene7 video component. These components are not interchangeable.
The Scene7 video component only works for Scene7 videos. The foundation component works with videos stored from Experience Manager (using ffmpeg) and Scene7 videos.
The following matrix explains when to use which component:
Out of the box, the S7 video component uses the universal video profile. You can, however, obtain the HTML5-based video player for use by Experience Manager. In Scene7, copy the embed code of the out-of-box HTML5 video player and put it in your Experience Manager page.
Even if using the Scene7 video component is recommended for viewing Scene7 videos, this section describes using Scene7 videos with the Foundation Video Component in Experience Manager, for the sake of completeness.
The following table provides a high-level comparison of supported capabilities between the Experience Manager Foundation Video component and the Scene7 Video component:
|Experience Manager Foundation Video||Scene7 Video|
|Approach||HTML5 first approach. Flash is only used for non-HTML5 fallback.||Flash on most desktops. HTML5 is used for mobile and tablets.|
The various video encodings are created according to the S7 encoding presets selected in the S7 cloud config. For the foundation video component to use them, a video profile must be created for each S7 encoding preset selected. This method allows the video component to select the DAM renditions accordingly.
New video profiles and changes to them must be activated to publish.
In Experience Manager, tap Tools > Configuration Console.
In the Configuration Console, navigate to Tools > DAM > Video Profiles in the navigation tree.
Create a S7 Video Profile. In the New. menu, select Create Page and then select the Scene7 Video Profile template. Give the new video profile page a name and click Create.
Edit the new video profile. Select the cloud config first. Then select the same encoding preset as selected in the cloud config.
|Scene7 Cloud Config||The cloud config to use for the encoding presets.|
|Scene7 Encoding Preset||The encoding preset to map this video profile with.|
|HTML5 video type||This property lets you set the value of the type property of the HTML5 video source element. This information is not provided by the S7 encoding presets, but required for properly rendering the videos using HTML5 video element. A list for common formats is provided, but can be overwritten for other formats.|
Repeat this step for all encoding presets selected in the cloud config that you want to use in the video component.
The Foundation Video component must know about what video profiles to use in order to build the video sources list. Open the video components design dialog box and configure the components design for using the new video profiles.
If you use the Foundation Video component on a mobile page, repeat these steps on the design of the mobile page.
Changes made to the design require activation of the design in order to take effect on publish.