Xibo showing half screen
After some time our portrait display is showing content only at the upper 50% of the screen. Below that the Windows desktop is visible. Xibo version 1.63. What can cause this? Thanks in advance!
Question information
- Language:
- English Edit question
- Status:
- Needs information
- For:
- Xibo Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Related FAQ:
None Link to a FAQ
Revision history for this message
|
#1 |
Hi,
same Problem here,
after some time (more then a day) a 16:9 (1920x1080) display is showing content only at the upper left of the screen.
Below that the Windows desktop is visible.
Xibo version 1.64 Windows
Layout with 4 Regions
After changing the layout to a Layout with 1 Region, the problem still exists.
How can this be fixed ?
Best regards, Hubert
Revision history for this message
|
#2 |
Unfortunately we have no idea what can cause this.
It sounds like Xibo is running in Windowed mode (meaning the clientX, Y, width and height have been specified) - but that would have required a change to the settings, etc.
If you restart the player without doing anything else - does it jump back to full screen?
Revision history for this message
|
#3 |
When restarted it shows xibo fullscreen normally. After some time the problem reappears. Tested it with aswel 1.63 as 1.64.
Revision history for this message
|
#4 |
Stop and start without changing settings, Xibo shows again the whole screen. It is as it should be.
Revision history for this message
|
#5 |
Sorry to be perdantic - when it is showing half the screen, is the content cut, or is it sized to fit the smaller screen size?
I'm trying to work out whether the client still thinks it is full screen, or whether it things is it in windowed mode.
Revision history for this message
|
#6 |
Hi Dan,
No problem, happy to see that we are trying to figure it out!
Is the problem occurs, the content is cut.
Revision history for this message
|
#8 |
Sorry guys, but we will don't know what the problem can be - i've created a bug for it... if you notice anything extra that might help it would be much appreciated.
Revision history for this message
|
#9 |
Another note!
The original area was before the problem occurred 1920x1080. After that, the area has shrunk to 1024x768.
Revision history for this message
|
#10 |
Last night the error occurred again.
Here is the log file from the client.
ScheduleAgentTh
Fehler bei der Anforderung mit folgender Fehlermeldung:
--
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=ltr>
<STYLE id=L_64r_1>A:link {
FONT: 8pt/11pt verdana; COLOR: #ff0000
}
A:visited {
FONT: 8pt/11pt verdana; COLOR: #4e4e4e
}
</STYLE>
<META content=NOINDEX name=ROBOTS>
<META http-equiv=
<META content="MSHTML 5.50.4522.1800" name=GENERATOR>
<BODY bgColor=#ffffff>
<TABLE cellSpacing=5 cellPadding=3 width=410>
<TBODY>
<TR>
<TD vAlign=center align=left width=360>
<H1 id=L_64r_2 style="FONT: 13pt/15pt verdana; COLOR: #000000"><ID id=L_64r_
</ID></
<TR>
<TD width=400 colSpan=2><FONT id=L_64r_4
style="FONT: 8pt/11pt verdana; COLOR: #000000"><ID id=L_64r_
<TR>
<TD width=400 colSpan=2><FONT id=L_64r_6
style="FONT: 8pt/11pt verdana; COLOR: #000000">
<HR color=#c0c0c0 noShade>
<P id=L_64r_7><B>Try the following:</B></P>
<UL>
<LI id=L_64r_
<LI id=L_64r_9><B>Check spelling:</B> Check that you typed the Web page address correctly. The address may have been mistyped.
<LI id=L_64r_
<LI id=L_64r_
</UL>
<HR color=#c0c0c0 noShade>
<P id=L_64r_
<UL>
<LI id=L_64r_13>Error Code 64: Host not available
<LI id=L_64r_
--.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
|29.12.2014 03:12:54|
Fehler: Leere Antwort auf Anforderung.
|29.12.2014 03:12:56|
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
|29.12.2014 03:12:58|
Fehler: Leere Antwort auf Anforderung.
RequiredFilesAg
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
Fehler: Leere Antwort auf Anforderung.
ScheduleAgentTh
ScheduleAgentTh
RequiredFilesAg
ScheduleAgentTh
RequiredFilesAg
Revision history for this message
|
#11 |
The exact time when the error occurred is not known.
The client is restarted at 2:00 last night. The error was detected at 12.30
Somewhere between these times it occurred.
Revision history for this message
|
#12 |
Those error messages would indicate that the player (and device) lost connection to the CMS during the outage - I would be surprised if this was related to the issue.
I wonder if 1024x768 is the native resolution of the graphics card...
Revision history for this message
|
#13 |
Perhaps an important clue!
After the resolution was 1920x1080 firmly set in the client options, the problem has not occurred for a few days.
Revision history for this message
|
#14 |
Problem back again:
After many days it happened again
1920x1080 firmly set in the client options is not the solution.
Can you help with this problem?
Provide an answer of your own, or ask Nick ten Berge for more information if necessary.