Assets provides for centralized video asset management where you can upload videos directly to Assets for auto-encoding to Scene7 and access Scene7 videos directly from Assets for page authoring.
Scene7 video integration extends the reach of optimized video to all screens (auto device and bandwidth detection).
- The Scene7 video component automatically performs device and bandwidth detection to play the right format and right quality video across desktop, tablets and mobile.
- Assets - You can include adaptive video sets rather than only single video assets. An adaptive video set is a container for all video renditions required to playback video seamlessly across multiple screens. 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. You use an Adaptive Video Set, along with S7 video component, for adaptive video streaming across multiple screens including desktop, iOS, Android, Blackberry, and Windows mobile devices. See Scene7 documentation about adaptive video sets for more information.
The default video encoding process is based on using the FFMPEG-based integration with video profiles. Therefore, the out-of-the-box DAM Update Asset workflow contains the following two ffmpeg-based workflow steps:
- FFMPEG thumbnails
- FFMPEG encoding
Be aware that enabling and configuring the Scene7 integration does not automatically remove or deactivate these two workflow steps from the out-of-the-box DAM Update Asset ingestion workflow. If you already make use of the FFMPEG-based video encoding in AEM, it is likely that you have FFMPEG installed on your authoring environments. In this case, a new video ingested using Assets would be encoded twice: once from the FFMPEG encoder and once from Scene7 integration.
If you have the FFMPEG-based video encoding in AEM configured and FFMPEG installed, Adobe recommends that you remove the two FFMPEG workflows from your DAM Update Asset workflows.
Deciding where to upload your video assets depends on the following:
- Do you need a workflow for the video asset?
- Do you need version control for the video asset?
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 Scene7. The workflow for each scenario is described in the following section.
If you need a workflow or versioning for your assets, you should upload to Adobe Assets first. The following is the recommended workflow:
- Upload the video asset to Adobe Assets and automatically encode and publish to Scene7.
- In AEM, access video assets in WCM in the Movies tab of the Content Finder.
- Author with Scene7 video or foundation video component.
If you do not need a workflow or versioning for your assets, you should upload your assets to Scene7. The following is the recommended workflow:
- In Scene7, set up a scheduled FTP uploading and encoding to Scene7 (system automated).
- In AEM, access video assets in WCM in the Scene7 tab of the Content Finder.
- Author with the Scene7 video component.
The Video tab does not appear if the page does not have a cloud configuration. See Enabling Scene7 for WCM.
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 Scene7 documentation.
Adobe recommends that you select either both adaptive video sets when configuring the universal presets or select the Adaptive Video Encoding option.
If you need to update the viewer and encoding presets for video in AEM because the presets have been updated in Scene7, navigate to the Scene7 configuration in the cloud configuration and click Update the viewer and encoding presets.
When using AEM, 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 AEM (using ffmpeg) and Scene7 videos.
The following matrix explains when you should 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 AEM by doing one of the following:
- In Scene7, copy the embed code of the out-of-box HTML5 video player and put it in your AEM page.
- Use the Scene7 HTML5 viewer SDK to create a custom player and then create a custom AEM component.
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 AEM, for the sake of completeness.
The following table provides a high level comparison of supported capabilties between the AEM Foundation Video component and the Scene7 Video component:
|es||AEM 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.|
|Extensibility||Yes||Yes (with Scene7 viewer SDK)|
The various video encodings are created according to the S7 encoding presets selected in the S7 cloud config. In order for the foundation video component to make use of them, a video profile must be created for each S7 encoding preset selected. This allows the video component to select the DAM renditions accordingly.
New video profiles and changes to them must be activated to publish.
Edit the new video profile. Select the cloud config first. Then select the same encoding preset as selected in the cloud config.
Property Description 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 allows to 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.
The foundation video component must know about what video profiles to use in order to build the video sources list. You must open the video components design dialog and configure the components design for using the new video profiles.
If you use the foundation video component on a mobile page, you might need to 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.
- Create a S7 cloud config. Make sure the video encoding presets are set and the importer is running.
- Create a S7 video profile for each video encoding preset selected in the cloud config.
- The video profiles must be activated.
- Configure the design of the foundation video component on your page.
- Activate the design after you are done with your design changes.