ÃÛ¶¹ÊÓƵ

Configure the Video component configure-the-video-component

The Video component lets you place a predefined, out-of-the-box video asset on your page.

For proper transcoding to occur, an administrator installs FFmpeg separately. See Install FFmpeg and configure AEM. Administrators also Configure Video Profiles for use with HTML5 elements.

CAUTION
This Foundation Component has been deprecated. ÃÛ¶¹ÊÓƵ recommends using the Core Components Embed Component instead.
CAUTION
This component is no longer expected to function out-of-the-box without extensive project-level customization.

Configure video profiles configure-video-profiles

For use of HTML5 elements, define video profiles. Those chosen here are used in order. To access, use Design Mode (Classic UI only) and select the Profiles tab:

chlimage_1-317

From this dialog, you can also configure the design of the Video component and parameters for Playback, Flash, and Advanced.

Install FFmpeg and configure AEM install-ffmpeg

The Video component relies on the third-party open-source product FFmpeg for transcoding of videos. Downloaded from . After installing FFmpeg, configure AEM to use a specific audio codec and specific runtime options.

To install FFmpeg on Windows, follow these steps:

  1. Download the compiled binary as ffmpeg.zip.
  2. Unarchive to a folder.
  3. Set the system environment variable PATH to <your-ffmpeg-location>\bin.
  4. Restart AEM.

To install FFmpeg on macOS X, follow these steps:

  1. Install Xcode available at .
  2. Install available at to get .
  3. Install MacPorts available at .
  4. In the console, run sudo port install ffmpeg command and follow the on-screen instructions. Ensure that the path of the FFmpeg executable is added to the PATH system variable.

To install FFmpeg on macOS X 10.6, using the pre-compiled version, follow these steps:

  1. Download the precompiled version.
  2. Unarchive it to the /usr/local directory.
  3. In the console, run sudo ln -s /usr/local/Cellar/ffmpeg/0.6/bin/ffmpeg /usr/bin/ffmpeg. Change the path as appropriate.

To configure AEM, follow these steps:

NOTE
These steps are only necessary if further customization of codecs is required.
  1. Open CRXDE Lite in your web browser. Access .

  2. Select the /libs/settings/dam/video/format_aac/jcr:content node and ensure that the node properties are as follows:

    • audioCodec is aac.
    • customArgs is -flags +loop -me_method umh -g 250 -qcomp 0.6 -qmin 10 -qmax 51 -qdiff 4 -bf 16 -b_strategy 1 -i_qfactor 0.71 -cmp chroma -subq 8 -me_range 16 -coder 1 -sc_threshold 40 -b-pyramid normal -wpredp 2 -mixed-refs 1 -8x8dct 1 -fast-pskip 1 -keyint_min 25 -refs 4 -trellis 1 -direct-pred 3 -partitions i8x8,i4x4,p8x8,b8x8.
  3. To customize the configuration, create an overlay in /apps/settings/ node and move the same structure under /conf/global/settings/ node. It cannot be edited in /libs node. For example, to overlay path /libs/settings/dam/video/fullhd-bp, create it at /conf/global/settings/dam/video/fullhd-bp.

    note note
    NOTE
    Overlay and edit the entire profile-node and not just the property that needs modification. Such resources are not resolved via SlingResourceMerger.
  4. If you changed either of the properties, click Save All.

NOTE
Changes to the default out-of-the-box workflow models are not preserved when you upgrade your AEM instance. ÃÛ¶¹ÊÓƵ recommends that you copy the modified workflow models before edit those. For example, copy the out-of-the-box DAM Update Asset model before editing the FFmpeg Transcoding step in the DAM Update Asset model to pick video-profile names that existed before the upgrade. Then, you can overlay the /apps node to let AEM retrieve the custom changes to the out-of-the-box model.
recommendation-more-help
19ffd973-7af2-44d0-84b5-d547b0dffee2