Follow our specifications to ensure a seamless upload of video content.
Add a stream of video content by uploading an MRSS feed to MAZ. Get started here!
- Navigate to the Section you would like to add the MRSS feed.
- Click on +Content, +Feed, then +MRSS.
3. Enter the following metadata and Feed URL:
- Name (Internal facing)
- Feed URL
- Title (External)
- Subtitle (External)
- Description (External)
4. In the next form you see, fill in the metadata for the content menu you are adding to your app and save the form. For example, access, cover date, release date, etc.
Find our MRSS Specs below:
The following sample feed contains all of the elements required for the proper functionality of MRSS feeds in MAZ apps.
Please Note: MAZ recommends MRSS with UTF-8 Encoding.
<rss xmlns:media="http://search.yahoo.com/mrss/" version="2.0">
<title>Home video feed</title>
<description>Some description text for the feed</description>
<lastBuildDate>Mon, 23 Nov 2015 11:52:32 0800</lastBuildDate>
<title>A BIG Title for your Video</title>
<description> Description of the video </description>
<pubDate>Mon, 23 Nov 2015 09:29:47 0800</pubDate>
<media:content duration="123" medium="video" type="video/mp4" url="http://maz.com/samplevideourl/4mmaddgkad.m3u8"/>
Description of the elements -
<channel> describes the feed.
<title> The title of the channel.
<description> Description of the channel.
<link> The URL to the HTML website corresponding to the channel.
<lastBuildDate> - The most recent date/time the content of the channel was modified.
<item> Identifies a single video in the feed.
<title> The name of the video entry.
<description> Description of the video.
<pubDate> Identifies the date on which the content was published.
<guid > is an optional sub-element of <item>. It stands for globally unique identifier. A string that uniquely identifies the item.
<media:group> sub-element of <item>. It allows grouping of <media:content> elements that are effectively the same content, yet different representations.
<media:content> This element has attributes that provide useful metadata information, such as the source URL and duration.
<media:title> The title of the particular media object.
<media:thumbnail url=""/> Allows particular images to be used as representative images for the media object. It has one required attribute URL and other optional attributes such as height and width.
<maz:modified> Modified timestamp
This represents the timestamp of the last modification to the item. This should be in Epoch time format represented in seconds and it is stored as an integer. MAZ heavily relies on this value and in case of a change in the timestamp, will compare this value from its previous value and will reprocess the article if the newer timestamp is greater than the previous one, otherwise will ignore reprocessing. If this field is missing from the feed, the article will be processed only the first time.
<media:keywords> - Highly relevant keywords describing the media object. The keywords and phrases should be comma-delimited.
<media:subTitle> Optional element for subtitle/CC link to specify the subtitles of a media object.
- Titles truncated after roughly 49 characters
- Thumbnails minimum of 550 x 310 px
- Video full HD quality, 1080 x 1920
- The duration value within the <media:content> tag is optional.
Accepted file formats
- H.264 video up to 1080p, 60 frames per second, High or Main Profile level 4.2 or lower
- H.264 Baseline Profile level 3.0 or lower with AACLC audio up to 160 Kbps per channel, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats
- MPEG4 video up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second, Simple Profile with AACLC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats.
- Non-HLS/m3u8 format
The W3C provides a free RSS/ATOM feed validator, which can be found here: https://validator.w3.org/feed/. If you encounter any problems adding one of your feeds to our platform, try running it through this validator first to make sure it validates. This can be a great tool to pinpoint any errors that may be associated with your feed.
Important Note: We utilise etag and last-modified response headers for MRSS Feed's version validation, to update the apps with the newly added content in the MRSS Feed. Learn more about Feed version validation here.