Jump to content
Dataton Forum


Dataton Partner
  • Content Count

  • Joined

  • Last visited


About RBeddig

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location
    Berlin - Germany

Recent Profile Visitors

1,187 profile views
  1. No, but running WATCHOUT on WIndows 10 Pro takes the risk of updates. Normally Windows updates are a good thing if we talk about security in office or private use cases. WATCHOUT servers are not so much under threat since we don't usually store private data and important documents on WATCHOUT servers. On the other hand, we have seen several updates which caused a Windows server to stop working at all. The update forced the system to go into an indefenite boot loop or deleted all user data and software from a computer. We also had clients who prepared a show on site for days on their Windows 10 Pro notebooks and when the CEO entered the stage for the big opening of the event, the notebook showed the message that Windows thought it would be an ideal time to shut down the computer to install all updates. If you run WATCHOUT on servers in a fixed installation and the client calls you one morning to tell you that nothing is working anymore it can also be a bit uncomfortable for you. Yes, you can delay updates on a Windows 10 Pro system but we also know that sometimes updates lead to performance and stability issues and then you don't have too many options to repair your system on the long run. Windows 10 Enterprise or IoT (used on all WATCHMAX and WATCHPAX servers) can be installed in a way that it NEVER updates anything keeping the system in a tested and stable state. It's up to you whether you love the thrill of update surprises or be more conservative, staying with a tested system on the long run.
  2. You can record one universe at a time. You can also program DMX cues inside WATCHOUT but usually it is more convenient to use a software or hardware meant to control lighting equipment. As stated above, you can send DMX into 256 universes with the limitations described above. Usually you would use WATCHOUT to program a couple of lamps or lighting circuits while you'd use different hardware and software and probably a separated network for more complex projects.
  3. In theory 256 universes, BUT DMX is constantly sending quite a bit of data, not only for those channels which change. It constantly updates the status of all channels and when using 256 universes with 512ch. each you can easiyl see that this would bring your network to a stand still.
  4. Hi, I created a link to the driver version 2017Q4 I use with Windows 7 servers. You'll need a pw to connect to this. Contact me in a private message for this. The link is valid for three days only!! https://msb95.myqnapcloud.com:4433/share.cgi?ssid=0HJzite
  5. To control a cluster, you have to send authenticate 1<CR> <CR> = Carriage return, fromWATCHOUT usually $0D. See page 177 of the manual! when you open the connection. The command "online" is only valid if you control the production software. WATCHPOINT does not know this command and does not need it. See page 181 of the manual!
  6. Do you have more than one network connection open on your production computer? It is recommended to use only one NIC!. In today's Academy training I have used a DMX input to trigger timelines without any issues (WO 6.5). Maybe you could share some pictures of your settings in the preferences and your inputs.
  7. Have you checked the universe settings in the preferences - control page? WATCHOUT can use Artnet on any network. If you're sender can't use standard networks like 192.168.xxx.xxxx, you'd need to set WATCHOUT to the Artnet network. Be aware that some Artnet software starts counting universes at 0 while other start at 1. Also important!!! WATCHMAKER will only see Artnet when it is online.
  8. You normally don't have to set anything on the advanced tab. The input number on the basic tab has to be the same as the one set in WATCHPOINT on your display computer. Blackmagic drivers are a real mess and their support is even worse. That's why we stopped using their cards for quite a while. They are cheaper but you compensate this by spending a lot of time to make them work. Have you tried to set the input to 1080 p 30 or p 29.97? This often helped us when we still used BM cards.
  9. We have seen bad playback performance with HAP codecs with all driver versions newer than 2017 Q4. AMD introduced some energy saving mechanism which seems to throttle the performance of the graphic card. Secondly you could try to use chunks when encoding the media. Without chunks, a HAP file will use only one core. I'd try with two chunks here.
  10. Usually, if one out of 4 servers shows a problem like this, it points to the installation or other server related problems. I would try to re-image the server or at least re-install WATCHOUT.
  11. I've seen something like this before and my solution was to change the colour space. Otherwise, are you on the same switch or is the signal going through various switches in a network? Have you tried to "catch" the signal on a second computer running the NDI monitor, preferably on the same switch as the WATCHOUT display computer?
  12. If you want to feed a large LED wall with more than one output from your graphic card and more than one LED processor, you will need the S400 card. For soft-edge from within WATCHOUT it is often not needed.
  13. Try this one. Windows_7_Tweaking_list_2.1.pdf
  14. My cues work like this: The name can be any name. Does not have to be the name of the file. The path is the name of the file or, if it is in a subfolder: subfolder\filename.jpg Does this work?
  15. If you really want to hide an upload you should look into using the old "standby layer" feature.
  • Create New...