0

MRSS Minimum Duration?

JRB Technical

July 08, 2012 23:33

None

Follow

Hello:

What is the minimum duration for a MRSS item (with a BrightSign)?

It seems that anything below 5 seconds is ignored for images, I was trying to do a 1 second delay for a short animation, but no matter what number less than 5 I declare  for duration, the images always show for 5 seconds.  Any number 5 and above and the player displays the image for the correct number of seconds.

I know I can do a Image List in BA with 1 second frame times, so the player can changes images that quickly with out issues, so why can't I do anything less than 5 seconds as part of a MRSS feed list?  The images are cached, so they should play the same as if they placed on the card as part of a presentation.

Anyone at BrightSign know?

Thanks!

John

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Lyndon July 09, 2012 21:42

  MRSS playlists are processed differently, different part of the playback code. Depending on how your playlist is setup, your images when in a normal playlist might be cached if they're small enough. In a list there's next image is always known, so in a list, the next image is cached in memory so it can play very quickly. If you weren't using a list, your image playback would be slower. 

• 0
  
  Lyndon July 09, 2012 21:43

  Wasn't sure if I was clear. I don't know of a way currently to modify the mrss code to cache images in memory so you can get fast playback like you do with lists. 

• 0
  
  JRB Technical July 09, 2012 23:50

  The MRSS images are always cached, that was the other problem that I solved last week, as I would update the images in the MRSS Feed, but the player would keep playing the cached images.  I had to change the guid element for each of the images in the MRSS feed every time I update the images, so the player would access and download the revised images.

  See my post: http://support.brightsign.biz/entries/21670947-mrss-image-caching-demystified

  I checked the play logs for the unit, the image playlist is reading the files from /storage/sd/pool/ every time they play, and the MRSS images are playing from /storage/sd/cache/ every time they play; both using "BSPLAY". So the only real difference is the directory on the SD card, which shouldn't make a difference.

  The images in both cases are identical in resolution and file size, just being stored in different folders on the SD card.

  It is really frustrating, as the player doesn't handle M-JPEG, animated GIF, or MNG (animated PNG), so in the case of trying to do something simple like animated weather radar images, the only route now seems to be to see if I can do some sort of conversion to MPEG-2 or MP4 server side, which is a waste of resources for something that the player is capable of doing, but for some reason I guess it was programmed not to.