No picture from Master-computer
Posted 03 July 2012 - 07:41 AM
Let me start by saying that Watchout is all new to me.
Now to the problem that I have.
I have one master-computer and three slave-computers connected to four projectors. One computer to each projector.
For some reason all slave-computers start up nice and sends out the film but I don´t get any pictures from the projector connected to the master-computer.
The master-computer starts up but for some reason the Watchout program starts and then ends up in a Wait-mode.
If I restart the computer or restart Watchout everything works fine untill the next morning.
The computers are set to shot down at a pre set time every evening and are set to start at a pre set time every morning. I should not have to do this manually.
We use Watchout 4.
Can you please help me to solve this issue?
Posted 05 July 2012 - 08:57 AM
What do you mean here??
The Production computer (Master) is not supposed to give any playback image, only the Displays do. It's used to create & control.
Your autostart issue is solved by using a text-file based script for starting WATCHOUT, described in the manual's appendix section, Filebased control of Displays.
Posted 05 July 2012 - 10:06 AM
Yes, you are right. I did not explain myself that well.
The so called (Master) is a display computer, this is the computer running the start-up script.
For some reason it will not display the film. WO ends up in a Wait-state but if I restart the computer the film starts up and is displayed.
When I run the computer at my office there are no problems what so ever but connecting the computer where it is supposed to be, the problem occure every morning.
Posted 09 July 2012 - 03:07 PM
Is it a stand-alone installation?
No network switch onsite?
Posted 10 July 2012 - 01:18 PM
This is a networkconnected computer.
The only difference is the media used to display the film with. At my office I use a computer screen connected via VGA or HDMI, this works fine. The problem occure when I connect the computer to a projector via HDMI. The film will not start in the morning. Computer starts up correct but it will not display the film. If I restart the computer the film is displayed via the projector and it works all day long and the computer shuts down correct in the evening. Next morning problem occures again.
What might be the problem? I am out of ideas now.
Thanks in advance.
Posted 10 July 2012 - 09:45 PM
Focus on differences!
Posted 11 July 2012 - 06:57 AM
Could it be that in the morning startup, at least one of the Slave Display PCs is slow in its startup readiness, and therefore the Master waits, and waits...and does not get a return signal from the slow Slave that it is now ready. On the manual re-start, all Slaves are ready, so it all runs thereon without a hitch, until the next morning startup?
Is such is the case, put in a longer delay on the Master startup to allow the slow Slave to get ready.
my 2 cents,
Posted 11 July 2012 - 10:25 AM
This is the only difference. How ever, we have 15 more units that are connected like this and they all work just fine.
The equipment is configured like this:
- One computer connected to a projector running the start-up script.
- Three other computers connected to one projector each.
I think there must be some issues with our show files, some settings or with the Watchout software. These are the only things that I can think of and that is causing us this problem.
For some reason the computer works when I use it at my office, it starts and shuts down as it is set to do. In the show room there is no picture from the computer with the start up script. I do get pictures from the other three computers connected to this show. If we restart the computer with the start up script we get pictures from all four projectors.
What to do and how to do it?
Posted 14 July 2012 - 04:40 PM
If necessary, you could transfer the show you are having problems with, to the other cluster of PCs which have shown no problems, and run it there. Does the problem transfer over? What about the show on the 'no problem cluster' of equipment transferred over to this problem cluster? Does the problem repeat on this cluster? Working this way, narrows down the problem area, and eventually should nail down the cause.
Posted 16 July 2012 - 06:56 AM
I think that I will be able to narrow down the cause to this problem but I might not be able to sort it out entirely. I can only try my very best to get it to work until the staff gets back from their hollidays.
Thanks for your information and help to solve this issue.