Jump to content
Dataton Forum

jfk

Moderator
  • Content Count

    1,516
  • Joined

  • Last visited

Everything posted by jfk

  1. It appears you are selecting Realtek Digital out. WATCHPAX have no built-in digital audio out. The 3.5mm jack is analog audio out, so the correct selection would be Speakers. (Would be more convenient if they just called it analog.) Timecode in requires a compatible USB audio interface (and you can only have one audio interface, so if you want to output audio and read timecode, a single interface must provide both). Current versions of WATCHOUT support ASIO for the audio input - i.e. ASIO for both output and input. (much older ASIO versions of 6 used a mix of ASIO output, but Di
  2. All WATCHPAX 2 include support for version 5.5.x. Most WATCHPAX 2 include support for any version 6 variant, up to and including the most recent version 6 release (6.6.5 as of today). There are some early production WATCHPAX 2 that only support v5.5.x. To be sure, use the License Manager in WATCHOUT 5.5.x Production to check supported versions. The reason you should check with 5.5.x if you are unsure of v6 support is you must go online to check the version. If you go online using v6 production on a v5 only WATCHPAX 2, you will “brick” the unit, requiring it to be returned for service to r
  3. Thank you for checking that Rainer. And to make things more confusing on AMD cards, those two legacy signal clocks can be dynamically assigned to any two of the four outputs. This is the anomalous behavior i referred to in the post above. i.e. AMD cards can only support two passive adaptors. And the ports supporting passive adaptors can dynamically change. As native DisplayPort output does not require the legacy clocks, using only active adaptors eliminates this concern.
  4. Isn’t that a link to only the current versions? Isn’t Windows Enterprise LTSB 2016 (1607) the ‘proper version’ for WATCHOUT?
  5. The cable you are using appears to be PASIVE and will only work on DisplayPort++ graphic card connections, not standard DisplayPort only graphic card connections. The fact that your cable works at some resoultions indicates that you do have a DisplayPort++ connection. A DisplayPort++ connection can be thought of as a dual mode connection. It is able to output either native DisplayPort -or- legacy signal type used by HDMI or DVI. I have found that the resolutions supported in legacy mode are a subset of the resolutions supported in native mode. For example, with a DisplayPort++ graphi
  6. You could avoid uncertainty and the considerable testing time to ensure stability by obtaining a WATCHPAX 60
  7. Are you trying to play the audio on Production (watchmaker) or Display (watchpoint). If watchmaker, have you set the correct audio device in watchmaker File - Preferences - audio out?
  8. A WATCHOUT Cube is a vague description, seems to describe hardware. First step is to determine the capabilities of your Dataton WATCHOUT License (USB key, reference https://knowledge.dataton.com/knowledge/the-difference-between-different-watchout-keys-and-versions) The best way to accurately determine the supported version is with the License Manager tool found in WATCHOUT Production v5.5.x or any v6 version (Window - License Manager). Once you * confirm your WATCHOUT License (USB key) supports v6 * confirm your “WATCHOUT Cube” Windows OS has been tuned for WATCHOUT
  9. jfk

    WP40 MST HUB

    Essentially that is true. However if you restrict resolution to 1920x1080 @ 60p, it is possible to achieve six outputs using MST hubs. The nVidia driver will present the MST hub outputs to WATCHOUT as normal outputs (up to six total).
  10. The wall physical measurements are incomplete information. Wall processors typically can scale an input to fill the space, although ideally you would want no scaling. What is important is the target resolution in pixels. The wall processors input resolution is also a factor in determining requirements. Pixel pitch, wall processor input capability and any wall processor scaling would determine how many pixels are needed to fill that physical measurement.
  11. No. This 2011 app no longer exists, it was outdated by iOS updates and therefore discontinued.
  12. I have been ghosting the ‘Dante Users Forum’ on Facebook for a while. Seems not all motherboard NICs are up to the task. Some are. i.e. ymmv. I have seen NIC settings tips for Dante in that forum as well. That forum may be a good place to seek that knowledge, there seems to be many helpful participants there.
  13. I suspect WATCHOUT version may make a difference for that. Used to be a live video / NDI set to less than 3% opacity would automatically optimise to ‘off’. I seem to recall that was changed, but i can not remember when. Ifyou are not using the standby function, an alternate method of opening a live video / NDI object is to place it on the main timeline from beginning (0.00) to end and make that layer standby. All standby media above 3% will be active all the time, but not visible while not in standby.
  14. One has to wonder what changed? WATCHOUT version, Windows update, DP driver version, DP firmware, ... ? Do you have the ability to restore to the state when it did work?
  15. Yes, there is. But the issue may not be the blend per se, it is more from misregistration of the overlap / double projection
  16. Try ... Quit WATCHOUT Production, move the backup .watch file to the same location as the original .watch file, open
  17. Never seen that one before. On what hardware does this error occur? WATCHPAX? User provided computer / Windows version? ... Where are you seeing that error? WATCHOUT Production error window? WATCHOUT Display error log? Windows 10 OS? ...
  18. Adding WATCHOUT audio playback to your WATCHOUT video output is strictly a matter of the graphics card driver’s audio support. WATCHOUT requires either ASIO or WASAPI audio support. On your display computer go to Window mode and check the audio out menu to determine if display output audio is an option.
  19. This most commonly occurs when there are multiple NICs on the production computer. If the WATCHOUT NIC is not the first NIC in Windows sort order, UDP traffic is lost to the first NIC, while TCP traffic still finds the correct NIC. play sent to the displays is a UDP command. To quickly confirm this is the cause, disable all NICs but the WATCHOUT NIC and normal operation should be restored. If you require multiple NICs (like WiFi and ethernet, etc), re-order the NICs in Windows so the WATCHOUT NIC is first.
  20. What timecode format are you using? Are you specifying the time code format or using automatic?
  21. So the issue is Windows problem. Did you look up the error as described in the knowledge base post?
  22. The Production computer error you observed indicates the production computer has lost communication with the display computer. The most LEAST likely cause is a network issue. The fault most likely occurred in the display computer. To obtain more information on its cause, you will need to look in the display computer’s error logs. On the display computer, go to the folder where WATCHOUT is installed. There you will find a folder named logs. In that folder, look for the most recent text files that begin with WATCHDOG... and WATCHPOINT... and ending in .txt . If the errors you find in t
  23. Depends on the WATCHPAX model. 3360 WATCHPAX were all v5.5.x only, but can be electronically upgraded to add v6 (and you must use v5.5x to upgrade the license to v6 BEFORE upgrading the WATCHOUT software to v6). 3362 WATCHPAX 2 depends on age, some were originally v5.5.x only and some were both v5.5.x and v6. All other WATCHPAX models (4, 20, 20A, 40, 60A, 60B, 60C) license are v6 only. Note, from a WATCHOUT software perspective, the version at time of the release of the hardware is the oldest version that will run on that model WATCHPAX. For example, WATCHPAX 60s require v6.5 o
  24. This seems to go beyond audio input. Video input for external devices require Microsoft Windows Driver Model (WDM) compliance. If the devices you mention are WDM compliant, then they should work.
  25. Already on the wish list ... De-embed audio from video streams containing embedded audio (NDI, capture cards, live streams), mix audio input into WATCHOUT’s audio output with WATCHOUT’s standard audio control (volume, input channel to output channel patching). Individual Programmable delay for for each input / de-embedded audio stream. Is there something you are looking for beyond that?
×
×
  • Create New...