- Administering User Guide overview
- Sites Features
- Website Administration
- Asynchronous Jobs
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- Troubleshooting MSM Issues and FAQ
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Audit Log Maintenance in AEM 6
- Configure the Rich Text Editor
- Configuring RTE for Producing Accessible Sites
- Configuring Undo for Page Editing
- Configure the Rich Text Editor plug-ins
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- The Link Checker
- Troubleshooting AEM
- Managing Access to Workflows
- Starting Workflows
- Administering Workflows
- Administering Workflow Instances
- Using cURL with AEM
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Configuring Search Forms
- Tools Consoles
- Reporting
- Configuring Layout Container and Layout Mode
- Editor
- Enabling Access to Classic UI
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Principal View for Permissions Management
- Content Disposition Filter
- Custom User Group Mapping in AEM 6.5
- Same Site Cookie Support
- Personalization
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Learning Manager
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- Integration with Adobe Analytics using IMS
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic (Scene7)
- AEM Livefyre Recipes
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Integration with Adobe Target using IMS
- Adobe Classifications
- Solutions Integration
- Exporting Experience Fragments to Adobe Target
- Best Practices for Email Templates
- Integrating with Livefyre
- Best Practices
- Content Management
Configure the Video component
The Video component lets you place a predefined, out-of-the-box (OOTB) 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.
This Foundation Component has been deprecated. Adobe recommends using the Core Components Embed Component instead.
This component is no longer expected to function out-of-the-box without extensive project-level customization.
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:
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
The Video component relies on the third-party open-source product FFmpeg for transcoding of videos. Downloaded from https://ffmpeg.org/. After installing FFmpeg, configure AEM to use a specific audio codec and specific runtime options.
To install FFmpeg on Windows, follow these steps:
- Download the compiled binary as
ffmpeg.zip. - Unarchive to a folder.
- Set the system environment variable
PATHto <your-ffmpeg-location>\bin. - Restart AEM.
To install FFmpeg on macOS X, follow these steps:
- Install Xcode available at developer.apple.com/xcode.
- Install available at XQuartz to get X11.
- Install MacPorts available at www.macports.org.
- In the console, run
sudo port install ffmpegcommand and follow the on-screen instructions. Ensure that the path of theFFmpegexecutable is added to thePATHsystem variable.
To install FFmpeg on macOS X 10.6, using the pre-compiled version, follow these steps:
- Download the precompiled version.
- Unarchive it to the
/usr/localdirectory. - 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:
These steps are only necessary if further customization of codecs is required.
-
Open CRXDE Lite in your web browser. Access http://localhost:4502/crx/de.
-
Select the
/libs/settings/dam/video/format_aac/jcr:contentnode and ensure that the node properties are as follows:audioCodecisaac.customArgsis-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.
-
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/libsnode. For example, to overlay path/libs/settings/dam/video/fullhd-bp, create it at/conf/global/settings/dam/video/fullhd-bp.NOTEOverlay and edit the entire profile-node and not just the property that needs modification. Such resources are not resolved via SlingResourceMerger.
-
If you changed either of the properties, click Save All.
Changes to the default out-of-the-box (OOTB) workflow models are not preserved when you upgrade your AEM instance. Adobe recommends that you copy the modified workflow models before edit those. For example, copy the OOTB 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 OOTB model.
Resources
Adobe Account
