Jump to content

RBeddig

Dataton Partner
 View Profile  See their activity

  • Posts

    627

  • Joined

  • Last visited

 Content Type 

Everything posted by RBeddig

  1. RBeddig
    If you're using a WATCHPAX, the unit's C drive is locked which means that you can't install anything or alter Windows. From my understanding, to be able to shut down a server from remote you need to be either connected as a user e.g. through ssh or have an application running in the background of your WATCHPAX which listens to incoming commands. This is to protect your computer since otherwise everybody could shut down any computer in a network.
  2. RBeddig
    No. If you can wake the device through a defined time in your bios, it just takes a timeline with a cue to turn the player off before you restart it from your bios again. In your autostart.txt file you would write something like: authenticate 1 setLogoString "The show will begin shortly" (optional) delay 5000 load "MyShow" wait run "your show timeline" run "reboot" The "reboot timeline will then run for 23h 50m until it restarts your player. The important thing is that your player supports wakeup at time.
  3. RBeddig
    Does your bios support wake on time? If so, you can set the start time here. Then you use an autostart.txt script to run a timeline which runs for maybe 23 h 50 m and then sends the command to power the player down. The player will go down and the bios will wake it up again.
  4. RBeddig
    Do you want to run your WP4 in cluster mode or with the production computer connected? If you want to learn MIDI channels you need to do this when the device is connected to the production computer. Furthermore, in the latest versions of WATCHOUT you need to select the MIDI input in the control tab of the preferences. If you then want to run the WP4 stand alone in cluster mode, you need to select the MIDI device in the menu of WATCHPOINT on the WP4 as well. You can reach this by building a remote connection from WATCHMAKER to your WP4 or you can connect a mouse and keyboard directly to your WP4 and press ctrl+W to make the menu visible. After selecting the MIDI device here - which at this point needs to be connected to the WP4! - you need to use an autostart.txt script to take control of the initial loading of your show and restart the unit.
  5. RBeddig
    Well, you can send a command to yourself from within WATCHOUT to power your device down. powerDown to 127.0.0.1:3039 if sent from a player to itself. If your player supports wake on time in BIOS, it would be easy to wake it up at a certain time again.
  6. RBeddig
    I assume that you're running your system in a proven and known infrastructure (switch, displays, server hardware...)!? We've used WATCHOUT 6.5 in installations and I imported all of our 10+ shows of our Academy Training program into WATCHOUT 6.5 yesterday without any issues at all. Those shows consists of many different files and formats. I've seen one case which sounds a littlebit like your problem where the Microsoft Defender (Win 10) on the production computer blocked the transfer of files to the display computers. Have you tweaked your computers?
  7. RBeddig
    The display servers send out strings every now and then into the network on UDP. If the physical network of all servers is in the same ip set they should all appear in the network window inside WATCHMAKER.
  8. RBeddig
    You can use cluster name and display name instead of ip addresses. See the manual on page 43 for more details. ADDRESSING BY IP NUMBER OR BY NAME Display computers may be addressed either by name or by IP number (see “Computer”). In most cases, addressing by name is preferable, since it allows IP numbers to be dynamically assigned, thereby reducing the need for manual configuration.
  9. RBeddig
    Can you try naming the computers instead of using fixed IP addresses?
  10. RBeddig
    Yes, the "WATCHOUT dongle actually acts as a general key for all software products which need a dongle, i.e. WATCHNET, WATCHMAKER, WATCHPOINT or the Dynamic Image Server.
  11. RBeddig
    This trick requires a WATCHOUT dongle in your computer and you need to go online, even if you have no displays connected for your test.
  12. RBeddig
    Can you try to transcode some of the videos to e.g. HAP or MPEG-2 and try again? We have seen issues when a certain number of MP4 files tried to play at the same time. You're loading files around that time while others are still playing.
  13. RBeddig
    Could be a broken file. What happens if you leave the 2GB file out? And just out of curiosity, what is the format of the drive on which the show folder resides (on the display computer)?
  14. RBeddig
    We usually leave our servers running at trade shows once they're set up. Doesn't matter whether it's a big server or a small one. WP4 doesn't have a power switch and you can actually power it down by cutting the power (or, if you want to be nice to the device, send a powerDown command). To power on, just plug the power cable back in. It will boot into WATCHOUT. To automatically run your show follow the instructions in the manual p. 172ff. There is a script in the autostart file which can start your servers. Important!!! Only apply this script to one of your two servers if they're in the same show (cluster).
  15. RBeddig
    The log files are in a folder logs inside the WATCHOUT folder. If you talk about google and amd driver update tasks, are you sure that you've applied the tweaking list from A-Z??? It sounds very much like a tweaking issue where some component tries to push into the foreground pushing WO into the background.
  16. RBeddig
    OK, this was my guess. Thanks for sharing.
  17. RBeddig
    May I ask which codec you used?
  18. RBeddig
    If you overlay two screens in WATCHOUT the default behaviour is that WATCHOUT creates a soft edge mask. You can turn this off per display in the tabs of the display settings dialogue.
  19. RBeddig
    I'd swap the images and (not at the same time) swap cables to see whether it is related to some disturbance or bound to a specific input. What happens if you change the resolution of the input? The dark part on the top actually looks as if you had a mask applied (display settings) or an automatic soft edge mask. Are your screens overlapping?
  20. RBeddig
    I don't know whether you're using the main timeline for your show or an aux timeline. My standard workflow with virtual screens is to use the main timeline for the virtual screen mapping where I place the various virtual screens at 0:00, a pause cue at maybe 5 sec and a loop cue back to this pause cue to make sure that an accidental run command on the main timeline does not loose the mapping. The main timeline is always active! My actual content is then using one or more aux timelines.
  21. RBeddig
    The commands look ok but are you sure that the cluster is actually fully connected to WATCHNET? A way to find out would be to go into the script part of WATCHNET, to select the scripts and then to execute them form there by pressing Shift+E (if I remember right - don't have an open WATCHNET running right now to check) or to use the command from the menu. If it doesn't work from here either you need to check whether WATCHNET is registered correctly as the controlling head of the system.
  22. RBeddig
    I've not seen anything like this but just out of curiosity, why are you looping the timeline with the virtual displays in the first place? Are they animated in any way?
  23. RBeddig
    All you need to do is to put a circular mask on top of all the rest of your content.
  24. RBeddig
    This of course works as long as the underlying layer remains in the memory of the graphic card. I thought that you needed a much tighter loop, similar to what you get from free running and looping.
  25. RBeddig
    If you jump out at the middle of a frame and back into the middle of a frame two halves of the runtime of the frame is lost. Therefore doubling the frame can help to prevent a visible effect in this case. If everything is rather slow you'll probably can do without this.
×
×
  • Create New...