Rendering Video
Google AMP provides a standard element for rendering video called
amp-video,
which is used by the
Widget Framework's
amp content profile. When using the
amp content profile, you can use both the
Teaser
and
Media
widgets to render video as you would using the
default content profile. The
amp-video element does, however, impose a number of
requirements and limitations that you must take account of:
- HTTPS only
-
The
amp-videoelement requires video sources to be available over HTTPS, so your servers must be configured to serve content over HTTPS. If you use the Escenic Video plug-in to transcode video then you must make sure it is configured to serve video over HTTPS (see http://docs.escenic.com/video-guide/3.1/awsclientconfig_properties.html for details). - Cue point settings ignored
-
The
amp-videoelement cannot render cue points. The Media widget's Cue point settings are therefore ignored. - Video player settings ignored
-
The
amp-videoelement always renders video using the HTML 5videoelement. Any alternative video player settings specified either in Using a Custom Media Configuration or in the Media Players configuration file are therefore ignored. - Pre-roll ad settings ignored
-
The
amp-videoelement does not support pre-roll ads. Any settings related to pre-roll advertising are therefore ignored. - Gallery settings ignored
-
The
amp-videoelement does not support video galleries. All gallery-related settings (Link behavior/On click=select from gallery and Media play mode settings=select from gallery in the Teaser widget, Auto-advance videos in the gallery in the Media widget) are therefore ignored. If Media play mode settings is set to select from gallery, then it falls back to the default setting (Content page). - Pop-up video settings ignored
-
The
amp-videoelement does not support pop-up video players. Media play mode settings=Pop up box in the Teaser widget is therefore ignored and the (Embedded media player) mode is used instead.