Jump to content

RBeddig

Dataton Partner
  • Posts

    597
  • Joined

  • Last visited

Contact Methods

  • Website URL
    http://www.presentation-technologies.de

Profile Information

  • Gender
    Not Telling
  • Location
    Berlin - Germany

Recent Profile Visitors

2,370 profile views

RBeddig's Achievements

(3/3)

  1. The update procedure is correct. Since the encrypting mechanism of the wibu keys has changed, old keys need to be physically swapped if they are not small plastic keys with a serial number of 3-344xxxx or newer. So basically you would pay for both steps and receive a new key with version 6 and 7. Since you're in Amsterdam, contact Walter of AVtrade for details.
  2. And another important question: do you have a WATCHOUT 7 license key or are you testing without a dongle?
  3. Which version of WATCHOUT are you using? Are you using a notebook with one (?) or two (?) monitors connected? Which open processes / windows do you see when pressing the Windows key? Do you then see two WATCHOUT icons in the taskbar?
  4. In WATCHOUT 6, virtual displays unfortunately can't be warped at all. This will be different in WATCHOUT 7.
  5. It's actually the numpad "0" key starting the timeline. You could also take a look at the free version of Universe Control. It should be able to generate a control page as a web page and can control up to three devices. Universe has a very good driver for WATCHOUT.
  6. This error usually shows up when the resolution set in the WATCHOUT production software does not match the EDID received from the image. Very often it is the case if you set 50fps in WATCHOUT and the display EDID wants 60fps but it can also be the resolution itself which is not supported by the display.
  7. Hi Kai, To calculate the conditional layer, you need to add all the conditions... To turn all conditions on is 1073741823. If you then add another "1", you'll turn all conditions off. enableLayerCond 1073741824$0D condLayer.watch
  8. Did someone say so? The HAP family of codecs is widely used on media servers - not only WATCHOUT - as it allows for very large videos in a reasonable to good quality, depending on which flavour of HAP and encoder you're using. With HAP files you can probably play 20+ FHD@60 videos over 4 outputs at the same time if you have a powerful server. The HAP codec compresses videos! The difference to other codecs, e.g. H.264, is that you'll see very little load on the CPU when playing back such files. HAP is actually more compressed than HAPQ. HAP uses less color depth which may lead to banding best visible when using computer generated gradients. HAPQ is a codec with 8bit color depth and better on gradients but it takes quite some space on your SSD and you'll need pretty fast ones too. Never embed audio in HAP files! H.264 is rendered using the CPU and you'll see that the CPU load will be pretty high when playing larger H.264 files. There is also a limit of the actual pixel size when using H.264. With some experience and following the numerous tips on encoder settings (no b-frames, fastdecode,...) you can create high quality H.264 files to be used on WATCHOUT servers. You can even encode H.264 files with very little compression using an i-frame only setting. Then your files will get bigger of course. As Jim said, you should pack your H.264 files in a MP4 container. But be aware, the load on the CPU will be much higher than playing HAP or HAPQ files. MOV and MP4 unfortunately say nothing about the actual encoding. It's just an envelope for your encoded video. Important is, what's inside, like HAP, H.264, H.265, ProRes, Animation,...
  9. What you are referring to are Artnet values, not strings sent via TCP/UDP. Different kind of control but also doable with WATCHOUT. Generate DMX outputs, connect a WATCHOUT dongle and send the values on the Artnet universe and channel which is probably explained in your manual. Note, that Artnet control can lead to false commands since Artnet usually uses a ramp to the value you want to send. This means, if you want to send the value 200 from the current value 0, it may also send some of the values in between before reaching 200.
  10. Their may be two reasons for this: a) you have installed a third-party codec set on your computer which then can "steal" the playback capability from WATCHOUT b) your MP4 files are actually H.265 files which are not supported by WATCHOUT 6. They are supported in WATCHOUT 7.
  11. Maybe rather $24(PVC:muteState)$0D$0A As Jim explained, the dollar sign "$" is a reserved letter inside WATCHOUT. It defines that the next to numbers/letters following a "$" sign are the hex-code for an ASCII letter or a non-printable ASCII code. Other software use other letters to describe a hex-code. The hex-code for the letter "$" is often defined as "x24" (you can find many lists and pictures on www to show you the relation between ASCII and hex-values) where "x" in this case also just tells you that the number is a hex-code. So if you need to send the letter "$" as the first byte of your string, you have to send the hex-code instead. $ > $24 (for WATCHOUT).
  12. There is no command to change display cluster names or such things in the protocol and there are quite a few reasons for that. A way to solve your issues would be to take a closer look at conditional layers and maybe at virtual displays and tiers. Conditional layers can be used to turn layers on or off on-the-fly. You can send those commands from inside WATCHOUT as described by Mickey but a better way would probably be to get yourself a small Elgato Stream Deck or some easy to program control software to send those commands from the outside. In your backup scenario you could route your content through virtual displays before it reaches the "real" display and you could of course route the backup servers to the displays in the same way. As you don't want to show both instances at the same time on the outputs, you'd use conditional layers to make those virtual screens visible which you want to see on the projectors. BTW, there is a video on the Dataton website about backup strategies and this also explains an installation where this approach was used in a fully automated way. https://www.dataton.com/techtalk-video-building-fully-automated-redundancy-for-watchout-in-advanced-fixed-installations Hope it helps!
  13. Can you send some screen shot of your project and how you defined the control cues? I've never seen such issue and we have programmed quite a few projects which work the way you want ti to work.
  14. This message clearly doesn't come from WATCHOUT. If you say, it plays WATCHOUT 5, how old is the display computer? Wrong boot volumes etc. is something I have noticed in the past when the display computer has a RAID set of drives and the RAID got lost in BIOS. This can happen when the CMOS battery is dead.
×
×
  • Create New...