When you upload a video to the DAM and add it your channel, you might encounter issues that video might not play in Screens player.
The following sections describe how to debug and troubleshoot video playing in your channel.
Once you upload the video to the channel, AEM should start creating some renditions for it. You can view your videos under Assets.
To view the video:
http://localhost:4502/assets.html/content/dam/we-retail/en/videos
.There should be different renditions (a MP4 or M4V).
If there is no rendition, make sure you have ffmpeg installed on the OS where AEM is running.
If there is no rendition, make sure you have ffmpeg installed on the OS where AEM is running.
Click here to install ffmpeg.
If you do not see a source attribute under video, it could be that the video did not get trans-coded. If the video is trans-coded properly, it will appear in the dashboard, as shown in the figure below.
Check ffmpeg is installed and the video profiles.
Navigate to the Video Profile, that is, http://localhost:4502/etc/dam/video.html
and click Upload Test Video.
Upload a test video and click Ok to begin the transcoding.
If the transcode fails, expand the ffmpeg output to understand any errors in the console output of ffmpeg.
Also, if the video transcodes successfully can download the transcoded file.
Make sure you give sufficient time for the video to transcode (it should show the tag new instead of processing) before you add it to any channel.
Check the list of profiles from the page design if the video component is not configured properly.
Navigate to your channel and select the Design mode.
Select the video and open the Edit dialog. Open the Profiles tab.
Select different profiles (at least “High Quality H.264” profile should be there).
Use the Web Player http://localhost:4502/content/mobileapps/cq-screens-player/firmware.html/content/screens/we-retail/locations/demo/flagship/single/device0
to validate playback in browsers (Chrome and Safari). Chrome is used on Android devices while Safari is the OSX and iOS browser.
If the video does not run on Safari, it will not run in the OSX and iOS players. This is probably an encoding issue and the video must be re-encoded.
Follow these steps to use a DAM workflow to create FullHD renditions:
Navigate to the workflow model admin, that is http://localhost:4502/libs/cq/workflow/admin/console/content/models.html/etc/workflow/models
.
Select the Screens Update Asset model.
click Start Workflow from the action bar to open the Run Workflow dialog box.
Select your video asset in the Payload.
Click Run.
Allow some time to create the renditions, but after a few seconds/minutes (depends on video size), reload the web player on Safari.
In case, AEM Screens player picks up the video but does not display, you need to troubleshoot the Autoplay Policy flag.
Follow the steps below to troubleshoot google’s autoplay policy flag issue:
Navigate to chrome://flags/#autoplay-policy
Change Autoplay policy from Default to no user gesture is required
Relaunch your web browser and update the player
To learn more about the best practices for good user experiences with the new autoplay policies in Chrome, please see documentation for Autoplay Policy Changes, that is, https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio
.
To play videos synchronously across multiple devices, you should use the absolute strategy for the sequence the video is part of.
The absolute strategy:
Follow the steps below to set up an absolute strategy:
Navigate to your channel author and select the sequence component as shown in the figure below.
Open its configuration dialog.
Edit the Strategy and add absolute.
The OS of the players must have the same clock.
Aligning Clocks on OS X Follow the steps below to align the clocks on OSX:
It may take some time before the players start a new aligned sequence.