The standard HTML template for video in Asset fields looks like this:
<iframe width="100%" height="100%" scrolling="no" allowfullscreen="true" frameborder="0" src="{stampvalue-config:baseaddress}dmm3bwsv3/embedplayer/play.aspx?accesskey={stampvalue-access:accesskey}&aid={stampvalue-asset:assetid}&autostart=0&width=auto&height=auto&videoquality=video{stampvalue-selected:quality}&fs=1" style="" siloid="{stampvalue-asset:assetsiloid}"></iframe>
What this does is it uses an iframe with a source to the connected Digizuite. This source returns an HTML section which embeds the Digizuite video player with a poster and source.
This means that Video is streamed directly from Digizuite. The reasoning behind this, is that video potentially can take up a lot of disk space and hence we do not want to cache it in the Sitecore server (as we do with other asset types).
Furthermore, Digizuite utilizes a video player called Flowplayer. This is an extension built on-top of the standard HTML5 video player. The main reason for this is it has the same styling across all browsers.
Using the standard HTML5 video player
The HTML template can also be customized to use the standard HTML5 video player if that is preferred. An example of such a template could look like this:
HTML5 Video player template
<video controls poster="{stampvalue-config:baseaddress}dmm3bwsv3/{stampvalue-asset:assetid}_2_11_1_11_0_{stampvalue-access:accesskey}_False.jpg">
<source type="video/mp4" src="{stampvalue-config:baseaddress}dmm3bwsv3/{stampvalue-asset:assetid}_10079_11_1_11_0_{stampvalue-access:accesskey}_False.mp4">
</video>
Native browser video playback
This player uses the native browser video playback. The drawback of this solution, is that the player controls looks different for each browser vendor.Example
<div style="width:640px; height:360px;">
<video controls="controls" width="640" height="360" poster="/{stampvalue-config:mediapipeline}/9c60ffb4e919412ab924c6b925612774/774-50045" >
<source type="video/mp4" src="https://[DAM URL]/dmm3bwsv3/assetstream.aspx?accesskey=a9402f36-039d-43ba-9109-ac599b6335b7&destinationid=10010&assetid=774&mediaformatid=50050">
</video>
</div>- Custom video playback through API (code behind)
The video streaming URL is retrieved from the API, see this guide DFS 9.2.0 - 4 Accessing metadata through API, and using this a custom video player is constructable.
Configuration
To configure the html for the video asset, navigate to sitecore → Templates → Branches → DFS → AssetTypeOutputRoot → AssetTypeOutputRoot and select the 01 - Video item.
The Html section contains the html template for the different content areas. The two important fields for video playback is Rich Text Editor Media and Asset Field Type. This is rendered when inserting a video asset into RTE or when using the DAM for Sitecore asset field.The stampvalues in the html are tags that are replaced through a pipeline. Read more about the stampvalues in section 3.6. Whenever changes to these fields are made, then the silo has to be synchronized in order for the changes to work.