PyClient : Problem retrive scheduled layouts

Is the clock correct on the client machine and in the same timezone as the server?

If you press i then n once it's past the start of one of the layouts does it then skip to the new layout?

Alex

yes, server and client are both on the same machine. So the same "date" and "time".
OS Ubuntu 10.04 32bit

after press "n", the default layout is simply "refreshed". No switching to other layouts.

strange thing is that I've "deleted" default layouts.. but it always show :|

Andy's problem was very specific to him, but you may as well upgrade as a next step.

The latest is in a branch at lp:~alexharrington/xibo/pyclient-1.2.1a1

Alex

nothing..

I tried to:
bzr branch lp:~alexharrington/xibo/pyclient-1.2.1a1

but nothing, it doen't wont to display the layouts scheduled..

Switching to new logger
Rsplash-2 has expired
Rsplash-5 has expired
Rsplash-8 has expired
Rsplash-11 has expired
Rsplash-14 has expired
Rsplash-17 has expired
Rsplash-20 has expired
Rsplash-23 has expired

Ok. Can I have a debug level 10 log please. Instructions are in the client installation docs.

Alex

Well the situations is:

To get working "n key" to change layout, every layouts need to have an "home area" (an image, a text.. something).
But, scheduled layouts continue to not works.

Now, I'll try to produce a log for you.. give me some minutes :]

thanks in advance!

I don't understand what you mean by a home area. Do you mean a region? All layouts need to have at least one region to be shown.

Alex

And that region must have at least one media item in it.

Yes, I mean region, sorry (italian translation for region is "home area", I don't know why)

Anyway, here the file log:
http://www.megaupload.com/?d=37361FDT

Can you check in the console (where you ran the client) that there's no exceptions being thrown.

Alex

Xibo Client v1.2.1a1
Reading default configuration
Reading user configuration
LOG: 1295275569.84 2 info XiboLogScreen logger started at level 10
LOG: 1295275569.84 2 info Set socket timeout to: 20
Log Level is: 10
Logging will be handled by: XiboLogFile
Switching to new logger
Rsplash-2 has expired

I don't think it will cause any problem, but is there any reason you've got all your schedules setup as priority schedules?

That feature is only generally used when you want to make a special exception to a long-running series of scheduled events.

Alex

No, there isn't a specific reason.

Now I'll try without "priority".

Looking more closely, it's correctly loading layout ID 5 on priority schedule and on that layout is an image.

What duration have you set on that image. It appears to be set to "2147483647000" seconds. That means that the SHORTEST time that layout 5 will EVER run for will be just over 68000 years.

The python client won't cut the layout short when it's running just because another layout has become available in the schedule

Alex

omg.. I don't know that "duration" of inside images can be the problem.
Give me some minutes, I'll try with short durations.

thanks in advance.

Oh my god.. that was the problem!!!

THANKS!

No problem.

That's nothing new to any version of Xibo. The duration of any given item is the minimum amount of time you want it to remain on the screen for. In some scenarios (for example where you have multiple regions) then it may remain for longer but it will never be shown for less than that time.

Alex