I've seen similar posts, but none with a clear answer. When/how often does the MRSS Feed refresh if I'm using a Local Network? The user guide says:
Note: Text feeds are static, whereas RSS and Media RSS feeds are updated each time the BrightSign player connects to the server. RSS feeds are ideal for instant updates from sources such as Twitter.
When does the "BrightSign" player 'connect to the server'?
The ttl tag in mrss feed determines how often will the unit check for new files in the feed.
ttl is measured in minutes.
Here is a sample video xml and a sample image xml for reference.
I have ttl set to 1 but mrss feed is not refreshed!
Is this issue happening after a longer period and / or after a network drop / time out?
It does not refresh at all. I have set the feed interval from brightsign author under presentation properties. It displays the content and then does not refresh after the interval I set up. what is the difference between ttl and the feed interval that is setup under brightsign author ?
It’s very similar / related.
In the Brightsign you can set the Interval for a player to check the feed.
During the interval check, as we interpret it, it check the feed time stamp (LastBuildDate and the TTL value (TTL = Time To Live).
It has to do with cashing the feed and it’s related items.
So if a feed has a 5 min TTL the player should only cache this ones every 5 minutes.
Any change in the contents in the feed should force a new LastBuildDate in the head of the feed.
The player should first look if a Timestamp has changed prior to looking into the feed itself for changed items.
No change in Timestamp and the player should do nothing.
Change in Timestamp and player should look into feed items differences.
Does it make a difference if the mrss feed is not a physical file location but an url endpoint that is serving up text/xml content? I'm Serving the mrss file through an url that constructs the feed and serves to the device directly without creating the file.
Indeed. But text would be in the feed I presume and content items should be mentioned including complete url and correct tags.
Do you have an example?
text/xml is a mime type that I'm serving to player.
I have set my Update Interval to "Every 5 minutes" but the content is not refreshed during that interval. When I re-published the presentation, it refreshed the content.
Here is my feed: {mysite} is redacted for security reasons here
Well I cannot test your file but I don’t see a last build date or pubdate.
If your server does not do a so called HEAD call response you should leave it opt out in the data feed preference.
I’ve read somewhere in the BrightAuthor manual that the player that has this on, and he does not see a change in the feed head he does not do future request any more.
We experience also feed update issues.
I didn't include those because I did not see build date or pubdate properties on their examples http://support.brightsign.biz/hc/en-us/articles/218067267-Supported-Media-RSS-feeds
Should I include those properties on my mrss feed?
So, are you suggesting to uncheck the "Optimize Feed Updates"?
If the server does not support HEAD call request I would leave it out; See page 112 from the manual.
I received very recently a sample from Brightsign as an example for the HEAD call and PubDates in it; http://bsnm.s3.amazonaws.com/romeo/ed8b2f4196932f1559db3f837ee8e4c5
That link gives me an error. Can you paste its content here?
Yes I noticed. I re-build the link but here are also the contents;
Thanks for the help. One last question. The "Optime Feed Update" checkbox can be checked as long as the last-Modified is in HEAD and pubDate is a field in the Feed?
Yes. But also the server should give a proper HTTP HEAD call response.
The LastBuildDate we use was always in prior to the new HEAD call function. This HEAD call is new since BrightAuthor 4.6.
And here is an example from me and I replace confidential part wit {domain-url};
<rss xmlns:media="http://search.yahoo.com/mrss/" version="2.0">
<channel>
<title>
<![CDATA[ Brightsign tests ]]>
</title>
<link>https://{domain-url}</link>
<description>
<![CDATA[ Brightsign test MRSS ]]>
</description>
<generator>SigncastFeeds</generator>
<lastBuildDate>Fri, 17 Mar 2017 11:38:53 GMT</lastBuildDate>
<ttl>5</ttl>
<item>
<title>
<![CDATA[ ]]>
</title>
<link>
https://{domain-url}/331/
</link>
<guid isPermaLink="false">1489747135</guid>
<pubDate>Fri, 17 Mar 2017 11:38:55 GMT</pubDate>
<media:content url="https://{domain-url}/" type="image/png" duration="10" fileSize="2971988"/>
</item>
<item>
<title>
<![CDATA[ Brightsign test MRSS 1-3 ]]>
</title>
<link>
https://{domain-url}/7067.mov
</link>
<category>
<![CDATA[ video ]]>
</category>
<description>
<![CDATA[ BrightSignBranding_192060p.mov ]]>
</description>
<guid isPermaLink="false">106210</guid>
<pubDate>Thu, 16 Mar 2017 10:05:39 GMT</pubDate>
<media:content url="{domain-url}/7067.mov" type="video/mpeg" fileSize="26832260"/>
</item>
</channel>
</rss>
