jfk

Not possible / recommended. It would defeat the purpose of a locked down predictable / repeatable configuration. At the very least, if you were to figure a way to hack it, it would void all warranty and support.

Possibly put them in a composition?

The error code is from Windows, not WATCHOUT. As you can not install drivers on a WATCHPAX, it may indicate the lack of a driver needed for that device. Most people would use an HDMI to NDI Ethernet adaptor when using a WATCHPAX to bring in a live signal.

i am not sure if simply creating the DMX output at address 512 is enough. If its status does not change, it may still optimize out. Just to be sure, for the purpose of testing, create an aux timeline 2 seconds long with a DMX cue fade up 1 second, fade down 1 second, run it and loop it.

Understood, but that is a valid transmission and that device is not fully compliant with the standard if it is refusing to accept that Sequence byte.

i am no expert, but could it be that particular lighting device considers any transmission not containing the full 512 addresses as a flawed transmission and ignores it? The standard does not require all addresses be transmitted. Yet sending the full range is the norm for most consoles, etc. WATCHOUT is the outlier. Still, as you can see other devices deal with it. Easy enough to check. Add a DMX Output in the same universe and set it to address 512. This forces WATCHOUT to transmit the entire range.

Slingle key jump - no. You can hit Ctrl-F and then type any control cue name (case sensitive) followed by Enter key to jump to that cue.

Thanks for reporting back your r success. Sorry i did not provide the known good version number in my previous response. As you correctly indicate, nVidia driver version 460.89 is the recommended version for best results with WATCHOUT.

There is an issue with recent nVidia drivers, you may need to go back to an older nVidia driver version.

I see you have cross posted this in the Facebook WATCHOUT User Group. So i will duplicate my response from that thread. It is true, Dataton does not support specific vendors products. Dataton supports standards. Prior to v6.3, Dante was supported via the Microsoft WDM standard. v6.3 and later changed audio support to the more modern profesional standard ASIO (and the newer Microsoft standard WASAPI). Dante Virtual Sound card offers support for both WDM & ASIO standards. So when migrating from versions before 6.3 to 6.3 and later you may very well need to reinstall audio drivers. Also, with 6.3+ make sure that WO output sample rate is identical to Dante’s output rate. Those values have to match. In WATCHOUT 6.2.2 this is something out of user control(and setup automatically), but with WO 6.3. and higher this has to be set up manually. DVS has been a topic of conversation among the support team earlier this week and they assure me that current WATCHOUT versions are tested and confirmed working with Dante Virtual Sound card. And no, there has been no recent changes related to Dante in ASIO WATCHOUT versions, if it works with 6.6.5 it should work with any 6.3+ version.

The speaker selection should work for the 3.5mm output. Might check the connections and impedance match. What build is your WATCHPAX 4? The Focusrite 3rd gen driver is in the latest WATCHPAX 4 build (r38) only, you may need to update the build.

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 DirectX for input.)

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 restore. v5.5.x only WATCHPAX 2 can be electronically upgraded to v6 in the field for the standard upgrade fee. For more information on this see: https://knowledge.dataton.com/knowledge/how-to-upgrade-a-watchpax-server-from-watchout-version-5-to-version-6 For future searches that may hit this topic, information on the oldest version you may use in WATCHPAX (all models) https://knowledge.dataton.com/knowledge/watchout-versions-for-different-watchpaxes-watchmaxes

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.

Isn’t that a link to only the current versions? Isn’t Windows Enterprise LTSB 2016 (1607) the ‘proper version’ for WATCHOUT?

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++ graphics card connection, a passive cable would not work at 1400x1050. An alternative is to use an ACTIVE DisplayPort to HDMI adaptor. They are only slightly more expensive than passive adaptors. Active are typically two piece connections (active adaptor & patch cable) where passive cable often are single cable solutions. An active adaptor will work with all DisplayPort types. It connects via native DisplayPort and circuitry typically embedded in one of the adaptor’s connector housings converts native DisplayPort to legacy HDMI signals. This opens up all available resolutions the graphics card provides in native mode. i.e. the same graphics card that would not work at 1400x1050 with a passive cable will work with an active adaptor. When choosing an active adaptor, be sure it supports the maximum resolution you require. Not all active adaptors support 3840x2160 at 60p, but adaptors capable of that resolution are available. Also, AMD graphics cards have an unusual support of DisplayPort++. With AMD cards, it is recommended to never use passive adaptors and only use active adaptors so you do not have to concern yourself with their anomalies.

You could avoid uncertainty and the considerable testing time to ensure stability by obtaining a WATCHPAX 60

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?

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 (reference either https://forum.dataton.com/topic/3235-windows-10-tweaking-guide/ or https://cdn.dataton.com/Files-PDF-etc/misc/Windows_7_Tweaking_list_2.1.pdf?mtime=20180319104650) Then all you need to do is uninstall the old version and install the new version. ______________ There are many ways to externally trigger WATCHOUT. The live show community leans toward using MIDI controllers to trigger events. There are also WATCHOUT dedicated controllers designed for the live show market that are quite powerful. The installation market leans toward control systems (Dataton WATCHNET, PixiLab, Medialon, Crestron, etc). Other methods exist like time timecode chase. Even DMX (via ArtNet) can be set up to trigger events although it is cumbersome to configure.

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).

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.

No. This 2011 app no longer exists, it was outdated by iOS updates and therefore discontinued.

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.

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.

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?