RSS feed in single mode advances too slow

Asked by Roel Vliegen

I have a RSS related question.

First some details:
Xibo Server 1.2.2 on Windows XP SP3 machine
Xibo client on Windows XP SP3 machine

Situation:
I'm using different lay-outs with different sources for RSS feeds, sources are internal (file://) and external (http://).
Each lay-out consists of a region with a scrolling (single) RSS feed with title and description. Scroll speed is 10 (for test purpose).
On the bottom of that same lay-out there's a scrolling (left) ticker, only title, with scroll speed 40.
Both RSS feeds direct to the same file.

Problem:
On the lay-outs with the external RSS feeds over HTTP no problem.
On the lay-outs with the internal RSS feed the ticker feed runs fine. But the region with title and description which runs in single mode advances too slow.

I started out at an scroll speed of 50, the feed advances in some minutes. When setting the scroll speed to a lower value (tried 30, 20, 10 and 1) the time it takes to advance doesn't really speed up, it still takes minutes.

Question information

Language:
English Edit question
Status:
Solved
For:
Xibo Edit question
Assignee:
No assignee Edit question
Solved by:
Dan Garner
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Alex Harrington (alexharrington) said :
#1

Because the 1.2.2 client is single threaded, the client is too busy scrolling your other feeds to advance the region in single mode.

You could double all your values for scrolling speed and double your value for scroll step amount in the client options. That would halve the number of scroll events the client would need to generate to move all your feeds at the expense of making them slightly more jumpy.

1.3.3 offloads this work to individual browser threads so shouldn't suffer so badly.

Alex

Revision history for this message
Roel Vliegen (r-vliegen) said :
#2

Extra info: I timed the moment of advancing and it takes exactly 2 minutes, regardless of the scroll speed I set.
It looks like a bug to me, but it's strange that the timing is so precise at 2min.

Revision history for this message
Roel Vliegen (r-vliegen) said :
#3

So Alex, what you're saying is upgrade to the 1.3.3 version?
Is it stable enough to be used in production environments?

Revision history for this message
Alex Harrington (alexharrington) said :
#4

I'm telling you it's a limitation of the current architecture of that client.

1.3.3 is a development preview and has some known bugs, so I wouldn't recommend you upgrade to it if you have a production environment.

Alex

Revision history for this message
Roel Vliegen (r-vliegen) said :
#5

OK, that's clear.
The scrolling speed set to 1, this doesn't fix the problem.
I'll give adjusting the scroll step ammount a try.

Fortunatly the Xibo implementation isn't live yet, so it gives me a couple of weeks time to address the problem.

Revision history for this message
Roel Vliegen (r-vliegen) said :
#6

Thanks Alex Harrington, that solved my question.

Revision history for this message
Alex Harrington (alexharrington) said :
#7

Setting very low numbers (ie < 10 or so) will cause you problems with the old client.

Use higher numbers and increase the scroll step amount for better results.

Alex

Revision history for this message
Dan Garner (dangarner) said :
#8

I'm not sure 1.3.3 would help - unfortunately it is still single threaded with regards to what gets shown on the screen. There is certainly more CPU time available to that one thread (due to threading other things), but the single UI thread limitation is still present.

Just to be clear, scrolling speed will not directly effect the Single Ticker - but adjusting its value may reduce the load of running the bottom ticker.

Tickers in 1.3.3 are slightly more efficient, which also helps reduce the load.

I think the best thing to do is remove the bottom ticker in a test layout, and see if the Single one speeds up (at least you know if the two are related then!).

Revision history for this message
Roel Vliegen (r-vliegen) said :
#9

Dan, I tried your suggestion to remove the bottom ticker.
There's no time difference when reloading, I even cleaned up the local library.

Is 't possible that the problem is in the feed?
Would you please take a look at the feed? I uploaded it on-line: http://www.sbportal.nl/rss/adelante_mededelingen.rss.

For your information; I also tried the external location above, so it's not in the fact that the feed is on the LAN.

Revision history for this message
Roel Vliegen (r-vliegen) said :
#10

Hey there all,

With the system going live in a couple of days I wondered if someone can tell me what's wrong with my RSS feed.
I've tried a couple of RSS/XML feed build applications and even pasted my content in an working feed model.

Conclusion is that it isn't Xibo's timing; the problem relies in the RSS/XML feed.
But I just can't figure out the exact problem.

It doesn't look like that the HTML tags I use (<br> <p> </p>) are the problem because Xibo can handle them.
But is it possible that it takes more time to advance by the use of tags?
Suggestions? TiA

Revision history for this message
Roel Vliegen (r-vliegen) said :
#11

For your information: in the RSS/XML feed, there is a <![CDATA[ tag used by the program.
Is it possible that this causes the problems?

Example: http://www.sbportal.nl/rss/adelante_mededelingen.rss

Revision history for this message
Best Dan Garner (dangarner) said :
#12

If your feed is loading and being displayed, then I don't think there will be a problem with the feed itself.

The duration of a single ticker is dependant on the number of items in the feed - if your feed only has a few items, then each one will display for a long time before switching to the next.

Your feed has only 4 items - to make things simple, if your feed was set to display for 40 seconds, then each item would take 10 seconds before you could advance.

In 1.3.3 you can specify the duration of the media items is "per feed item" or "for entire media item"... which allows you to control this.

For you - try reducing the overall duration of the feed item... if it is the only media item in the region it will carry on until all other regions are expired anyway.

Revision history for this message
Roel Vliegen (r-vliegen) said :
#13

Thanks Dan Garner, that solved my question.

Revision history for this message
Roel Vliegen (r-vliegen) said :
#14

Thanks Dan,

The overall feed duration was exactly the problem.
When I adjusted it to: <feed> x <seconds_to_display>, the effect is like I wished for.

With this problem solved we can go live this week.
A really big thanks to you!

Revision history for this message
Dan Garner (dangarner) said :
#15

Great! Glad that worked...