--- title: Media RSS Feeds slug: technical/media-rss-feeds docTags: createdAt: 2025-03-11T07:10:25.852Z --- You can use any Media RSS (MRSS) feed that contains only RSS tags or MRSS feeds that contain images, videos, or a mix of both. BrightAuthor Classic doesn't support MRSS feeds that contain a mix of RSS and HTML tags. # Feed Sources ## Flickr You can subscribe to a Flickr Photostream using BrightAuthor Classic. Just [Add a Flickr Photostream](docId\:FGEFX7y8sCNSzRuEDh6p8) as an MRSS feed. Note that you cannot add individual Flickr sets*.* ## Screenfeed.com You can use feeds from [Digital Signage Content Service, Feeds, & Templates](http://www.screenfeed.com/) for weather info. They have a mix of basic and advanced weather feeds, including weather maps. They also offer international weather services.  ## BrightSign Network If you have a BrightSign Network (BSN) account, you can create MRSS feeds using the intuitive WebUI. Simply log in to your account at *brightsignnetwork.com*, click on the **Create** tab, select **Dynamic Playlist** and create a playlist. Media RSS feeds can be distributed to your BrightSign players or other networked clients. To learn more about Dynamic Playlists in BrightAuthor Classic, see [Dynamic Playlists](docId\:LfMkBxpUQwC5t2osx8GIx). ## Custom - Build Your Own An MRSS feed is normally an XML file served by any public web server that points to images or videos. If you are creating your own Media RSS feed, you can download the sample video .xml file and sample image .xml file here: ::File{src="https://api.archbee.com/api/presign/TYAqEnq_Txckpox4eAKHe-L_iu0Tq0TnACe7C5XyzT1-20250422-223215.xml" label="Video_Template.xml"} ::File{src="https://api.archbee.com/api/presign/TYAqEnq_Txckpox4eAKHe-QVtK5WcjW6a0GhbDJw61p-20250422-223233.xml" label="Media_RSS_Image_Template.xml"} The following list outlines the tags that should be included with each media `` in a BrightAuthor Classic presentation MRSS XML: - ``: The title of the media file. This text can be displayed on screen if the MRSS feed is used with a Live Text state. - `<link>`: A direct URL link to the media file. This attribute should be identical to the `<media:url>` attribute. - `<description>`:  A description of the media file. This text can be displayed on screen if the MRSS feed is used with a Live Text state. - `<guid>`: A unique identifier for the media file. If this attribute changes when the MRSS XML file updates, the cached file on the player will be updated as well (even if all other media item tags remain unchanged). - ispermalink: If this attribute is True, the unique identifier also represents a permanent link to the media file. - `<media>`: A tag containing several attributes related to the media file. - url: A direct URL link to the media file. This attribute should be identical to the \<link> attribute. - fileSize: The size (in bytes) of the media file. This attribute should always be specified to prevent duplicate file downloads. - type: The MIME type of the media file. With BrightAuthor Classic presentations, this should be either "image" (followed by "jpeg", "png", or "bmp") or "video" (followed by "ts", "mpg", "vob", "mov", or "mp4"). For example, a *.jpeg* image would be tagged as "image/jpeg" and a *.mov* video would be tagged as "video/mov". - medium: Either "image" or "video", depending on the MIME type of file. - duration: (Images Only) The length of time an image file is displayed on screen. # Caching Multiple Feeds If you are using multiple MRSS feeds with BrightSign Author, multiple feeds will be cached as long as the MRSS *.xml* file includes the size of the files being downloaded. If you have several MRSS feeds in the same zone and you change from one MRSS feed to another, the first feed will not be purged so long as the sizes are included for the downloaded files.  # Restrict the Cached Files Pool Media files that are no longer referenced by the MRSS feed(s) will remain on the storage until all available space is filled. The system will then begin removing files that are no longer referenced to make room for new MRSS content. If you want to ensure that free space is left on the card for other purposes, BrightSign Author allows you to define the maximum size allotted to dynamic data (MRSS feeds and Dynamic Playlists). To specify a dynamic data pool size: 1. Go to **Admin > Preferences > Storage**  2. Select the **Enable Limit Storage** box (see the image below). 3. Choose whether to restrict the **Dynamic Data** pool by either **Absolute** (absolute size in MB) or by **Percent** (the percentage of the total storage). When this pool is filled with cached MRSS files, the system will begin deleting files that are no longer referenced by the MRSS feed(s). HDR data, HLG, and other HDMI\*®\* capabilities are not passed through or ingested. The EDID that the BrightSign player advertises on the HDMI input claims 4K support for platforms which support 4K video output and have a 4K capable display attached. If the display doesn't support 4K or the platform doesn't support 4K video output, then the EDID reports modes only up to 1920x1080x60p. The EDIDs used as the basis for this can be found in the *sys:* drive on the players with the filenames *default-edid.bin* and *default-4k-edid.bin*. By default they report that the BrightSign player only supports stereo PCM audio. This is so that by default any audio coming in over the HDMI input can be mixed with audio from local playback. However, the values can be altered using *roVideoMode’s* *ConfigureHdmiInput* function which adjusts the EDID. ::Image[]{src="https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/hYG4cUPEXF693ataEPTRl_screenshot-2024-02-28-at-13455-pm.png" size="60" width="1620" height="1242" position="center" alt="Screenshot 2024-02-28 at 1.34.55 PM.png" darkWidth="1620" darkHeight="1242" showCaption="false"} ## # Control Image Duration You can control the length of time each image plays by editing the media RSS feed file.  For example, the script below sets the duration to 10 seconds In the `<media>` tag for an image in a MRSS feed file. The `fileSize` (in bytes) of each media file must be included to avoid multiple downloads of the same file even when it hasn't changed. ```text <item> <title>image1 https://brightsignnetwork.com/download/MRSS/image1.jpg image image1 is the best 0624 ```