RBeddig

No. The network adaptor of your PC does not know it's IP address as long as the OS is not running. Therefore you need to send a "Magic Packet" as a broadcast (UDP) into the network. Usually it would look like this: FF FF FF FF FF FF 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 1C EE C9 01 52 11 0D This needs to be sent as hex code to either the IP address of the device or to the broadcast address of your network which would proabably be 192.168.100.254 in this case.

It would work inside and outside. On the outside of a dome you may run into issues with one camera only, due to the flat angles between camera and outer surface. If it is a sphere and the camera can "see" the area well enough it will work.

How do you build the loop? Using control cues or using the switches "free running" and "looping"?

Could be an EDID issue. Have you tried using a physical EDID minder behind the graphic card output? XVGA is not that common anymore today and the graphic card usually tries the highest and fastest EDID it can see. Ideally you'd use an EDID minder which you can set to only one frequency through dip-switches or software.

Since the OS of a WATCHPAX is write protected there are not many things to do to reset it to factory default. It looks as if the previous user has set it to a permanent IP address using the autostart script. You can access this script by connecting a mouse and keyboard to your WATCHPAX 2. Then press Ctrl+W to get access to the menus of WATCHPOINT. In the menu you can find a link to edit the autostart script. Look for all lines without a semicolon (;) at the beginning. These lines are active! All lines with a semicolon are comments only. The third part here is the one you need to set it back to DHCP. Hope it helps. Autostart.txt........... ; These are some examples on how to set a fixed IP number on the WATCHOUT computer. ; You only need to run this script once. After that the WATCHOUT computer remember the ; last set fixed IP number. The fixed IP numbers is shown in the start-up screen under ; the WATCHOUT 5 logo. The IP number inside the parentheses is the DHCP/link-local IP number. ; Remember that you always need to authenticate to level 2 before you try to set the IP number. ; ; Example: Set the fixed IP number to 192.168.0.100 ; ; authenticate 2 ; setIP 192.168.0.100 ; ; Example: Set the fixed IP number to 2.0.0.10 with the network mask 255.0.0.0 ; ; authenticate 2 ; setIP 2.0.0.10 255.0.0.0 ; ; Example: Remove the fixed IP number and restore the WATCHOUT computer to use the DHCP/link-local IP number. ; ; authenticate 2 ; setIP ;

You have the correct driver installed already. It's the one at the end of your list: Motu Audio ASIO. You will not see this in the audio settings of Windows since Windows does not see ASIO at all. But you will see it in WATCHOUT once selected.

You need to use the ASIO drivers, not the WASAPI driver. WASAPI only does 8 channels. Then you need to tell WATCHMAKER to use more than 8 channels. Preferences > Audio Out > Output Channel Limit...

Hi Quim, I have an installation where we run 18 channels and another one where we run 16 channels right now.

How many outputs on which resolutions are you using? Have you tried using an EDID minder in between the outputs and the LED processors. Since WATCHOUT does not resort the displays when it goes black and you see no error message it seems that the graphic card still receives a valid EDID and actually tries to send out data. I've seen some problems with standard EDID data sets and Novastar LED processors lately though.

The limitation Luca is referring to is only valid for AMD graphic cards and Windows 7 due to an AMD driver bug. There are quite a few postings on this forum about this issue. NVIDEA should work. The new WATCHPAX 60 series, the WATCHMAX SDI and the WATCHPAX 4 all use NVIDEA graphic cards. The first two run Windows 10, WATCHPAX 4 WIndows 7 embedded.

Yes, tweaking Windows 10 can be quite a task and it takes a long time to get the system stable and fast. WATCHMAX and WATCHPAX servers are more expensive than a self-built system but the price includes a warranty for a stable system which took months to set it up and for tests.

Well, usually a warning would pop up in Windows 7 as well but maybe it was sort of half-way registered in the OS. Normally it would also work with an activated firewall but WATCHOUT uses more ports, some of them being dynamically selected by Windows. BTW, we have seen the firewall of Win 10 blocking WATCHOUT although it was turned off. Here, we needed to turn it on, accept the rules for WATCHOUT and then turn it off again.

LTSB 2016 is the 1607 version of Windows 10. The tweaking document is based on this version!

Are you sure that you only use ONE active NIC (network port) on the production computer, all others DISABLED? Have you tried swapping the switch or using a direct cable between both computers to rule out problems on the switch? Have you tried other media codecs? While it usually works, WMV is not officially supported. See: https://www.dataton.com/watchout-overview-supported-media-images-sound-and-video

WATCHOUT will still use 8bit colour depth, even if the graphic card supports 10bit.

I've seen this in very early versions of WATCHOUT 6. Which version are you using? Have you tried to rebuild the cache on both sides?

Hmmm.... What is "that problem" and what did you clean and remove? If you installed WATCHOUT under the programs folder of Windows on drive C, you should de-install it and then re-install it using the correct folder on your fast WATCHOUT drive.

LTSC is the successor of LTSB. They changed the name in 2018 and now call it LTSC. LTSC versions are newer and are not tested in Sweden yet. The tweaking guide is for the 2016 LTSB version only. Might work with LTSC but there is no guarantee. The update files mentioned for LTSB 2016 will most probably not work with LTSC.

This is a different problem and should probably moved to a new separate thread. There are many reasons why you could see a network error and the loss of the connection. Pls. elaborate a bit what you are doing and how the error messages look like more specifically. Which version of WATCHOUT are you using? What Windows version? Are you using WATCHMAX or WATCHPAX or your own builds? How does your network look like and are there other devices inside the network? Reasons could be hardware related, software related (not only WATCHOUT!), tweaking, codecs....

Hi Chris, Just tried with two such cards on our servers and all six inputs appear and work fine. Which driver are you using? I've just installed 7.19.0 but had no issue with older drivers before. Maybe you should de-install the driver and re-install it again. https://www.datapath.co.uk/datapath-current-downloads/vision-capture-card-downloads/vision-drivers/vision-drivers-1 BTW, older drivers had an option to install the driver in kernel mode or custom mode. We need custom mode now.

Since it is a webpage, trying a different browser or deleting the cache might also help.

Hi, If the timeline length is shorter than the timecode received, you will see strange timecode values and flickering in images. I would not turn the timecode listening mode on and off all the time as long as you have control over the timecode itself (Medialon). It's recommended to not only turn the timecode listening mode on but to also tell WATCHOUT what sort of timecode it should expect (25fps, 30fps,...) You should also allow for a little pre-roll since timecode readers need to analyze the complete timecode string first to adjust the correct position. This hasn't changed much since the times of tape based media. Last but not least, the timecode value is only half of the story. If in doubt, you should check the signal with a scope. LTC is a rectangular signal and should look like rectangles on a scope. Some audio devices have problems with rectangular signals and if the shoulders look too much like a sine-wave or even worse, the timecode reader has problems to synchronize to it, even if the signal strength is fine.

Hi Jim, I just tried three DMX values in a formula for opacity and position. Both worked fine for me. Actually, since the limitation for one universe in/out has been dropped, DMX values are quite a good work-around for in-out-variables. BR Rainer

mai pen rai, If you want to check the real performance, always use all outputs which you plan to use later. Do not just connect one monitor and do your testing while later you might want to output a signal to 4 screens. Makes a difference!

Kai, First of all, it really depends on your server hardware. Do you have the server available already or are you using a supplier who will deliver the hardware at a later stage? We get similar questions from rental clients very often and the safest way is to test, test and test. We ask for samples or render our heavy demo content to the sizes needed and then run it on the proposed system. HAP depends a lot on the speed of the SSD. The load on the CPU is quite low but it also needs more support from the graphic card than the other codecs.