Jump to content
Dataton Forum


Dataton Partner
  • Content Count

  • Joined

  • Last visited

Everything posted by RBeddig

  1. I've seen H.264 files failing before and the reason was an unsupported encoding level. This could be your problem as well. Dataton has only limited options to cure this since it is a problem of the third party decoder used in the program. You can check this with software like MediaInfo or VideoSpec (both OS-X) or similar programs you might find for Windows OS.
  2. The production computer can be any computer capable of running Windows 7 or newer. I personally like using powerful notebooks since they are portable and flexible, can be taken back to the hotel room and have a UPS built in by design. The network can be any 1Gbit network, preferably using unmanaged switches. Managed switches are ok as well if you know how to set them up. If you have a lot of content in HAP or image sequences you'd rather select a desktop or 19" rack mount pc with 10Gbit network cards and a 10Gbit network infrastructure. The display units are the display computers, e.g. WATCHPAX, WATCHMAX or similar builds.
  3. Hmmmm.... start reading the manual from A-Z and all in this forum. Alternatively enroll into a WATCHOUT Certified Training session.
  4. I haven't done it with Nvidea for quite a while but maybe you can check the two pages under "video". If you come across something like 16-255 or the like, this is the place to change it.
  5. Have you checked the settings for the colour range. I remember NVidea cards used to go from 16-255 instead of 0-255. You can change this in the graphic card settings.
  6. This is the behavior if you change it in the preferences. Preference changes are something which works like a preparative preset for your show, not something you change during a presentation. You can though change the conditional layer status from outside through telnet at any time while the show is running, e.g. through a control system (WATCHNET, BLOCKS, Medialon, Universe,...). You could also send strings from a timeline to change the selection while the show is running.
  7. Simple answer, this feature was introduced in WATCHOUT 6. You can't export WATCHNET bundles in WATCHOUT 5.
  8. It very much looks like a network issue and probably it is not WATCHPOINT generating the issue but the underlying Windows OS. I found some hints on SSL on the web which does not make sense here, but you should check whether you only use one NIC on both the production side and the display computer. Are both computers running Windows 10? Have you been able to use the computer(s) with WATCHOUT before? Is the firewall turned off on both ends? We have seen cases with Windows 10 where you'd need to turn the firewall on at first, then connect WATCHOUT (online) and tell the firewall that you want those ports to be open and then turn the firewall off again. It wouldn't work when the firewall was off right from the beginning.
  9. Yes and no. It depends on the reading speed of the data drive in the production computer. In theory a 10 Gbit network can deliver appr. 1,280 MB/s. A standard SATA-III drive in a notebook will read maybe 500MB/s. If your production computer has a raid 0 of at least 3 SATA-III driver or a fast M.2 (NVMe) drive it will speed the transfer up. Of course, your display computers need a 10Gbit network card as well.
  10. The WATCHNET manual tells you how to use hex code: HINT: As in WATCHOUT, it is possible to send hexadecimal data bytes by using the prefix “$” followed by two characters that specify a byte. For example, “$0D” will send a carriage return. It is possible to mix text messages with hexadecimal bytes in any order. Any number of hexadecimal bytes may be sent but each two character sequence defining a byte must be prefixed with the “$” symbol. So use the form $FF$FF............$0D
  11. Yes. WATCHOUT can only work with one GPU. The onboard GPU needs to be disabled in bios or Windows drivers. Preferably bios.
  12. I'm not sure whether I really get your question. From your screenshots, you're using a computer with two different monitors with native resolutions of 1920x1200 (MIG) and 1920x1080 (mobile). If you want to use this computer as a display computer, you can use both outputs in WATCHOUT. Both have the same IP number but the output numbers differ (1, 2). Or do you use a computer with a graphic card (WX7100) and an onboard graphic card. In this case, you'll need to disable the onboard graphic card in your bios settings.
  13. Smooth playback depends mostly on file size, hardware specs and computer tweaking. I assume that your server is completely tweaked following the tweaking guidelines for Win 7!? Are your SSDs using RAID-0 configuration - and is WATCHOUT installed on this SSD raid? Is your OS on a separate SSD or at least on a separate partition? Have you checked the reading speed of your WATCHOUT SSD? Since you're using an 8-core CPU it might be a good idea to use chunks when encoding HAP.
  14. I've not seen WATCHOUT production crashing when too many videos had to be rendered. It usually slows down a lot and working with cues gets lagging. But the Windows protocols could show more information about the cause of your issues. Alex is pointing to an issue which usually happens when more than one NIC is active. In this case the production software will roll the timeline but the display computer will not react. In your case, the gui of the production software was blocked, wasn't it?
  15. It looks a bit like a fault on your production computer. Has it been tweaked (basic tweaks)? Which OS are you running?What sort of graphic card are you using on the production computer? Pre-loading 12 timelines can put some work on the production computer since it needs to render all the content of the stage window at the same time while usually the graphic power of notebooks is not the highest. If you have a lot of displays and maybe even more than one display computer, the display engine in WATCHMAKER has to do the work of the complete cluster to render the content. A good way to handle this is to switch the stage window to show thumbnails only instead of videos in highest possible quality. Once the show is programmed it is usually not necessary to see the videos running in the stage window. This reduces the load on the production computer quite a lot. The log files do not seem to show any information about the crash on April 12th. You could maybe check the events of the Windows log files. Maybe you'll find some hint in there.
  16. 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 in this case.
  17. 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.
  18. How do you build the loop? Using control cues or using the switches "free running" and "looping"?
  19. 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.
  20. 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 ; ; authenticate 2 ; setIP ; ; Example: Set the fixed IP number to with the network mask ; ; authenticate 2 ; setIP ; ; Example: Remove the fixed IP number and restore the WATCHOUT computer to use the DHCP/link-local IP number. ; ; authenticate 2 ; setIP ;
  21. 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.
  22. 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...
  23. Hi Quim, I have an installation where we run 18 channels and another one where we run 16 channels right now.
  24. 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.
  25. 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.
  • Create New...