jfk

You could provide a scan code to send them to the URL found the in the shortcut

Check to see if there is a hidden piece of media triggering the error. As for the "extension", are you referring to the indicator for the the manual pre-roll option? That normally would not appear unless requested. reference: Cues - CUE SPECIFICATIONS

??? Sure, you setup a shortcut to the panel url that is defined by the WATCHNET server. How you make the shortcut depends on the operating system you are using. More info for iOS: Using a Panel starting at time 1:26 The process is the same for any OS, the steps to get there vary in detail.

Turn off live update and use it the old way

You might try downloading and installing WATCHOUT v6.0.2

watchout version means a lot on this one, what you describe is a known bug in v6.0, since corrected in the next release.

I can not answer all your questions, but here is a start ... If the only way the device will work is via virtual com ports, then no, it can not be used. Yes, if the virtual com ports existed, they would confuse WATCHOUT. This needs to be done in a different, standalone TCP/IP mode, completely indepenent of Windows com ports.

Epic thread resurrection. Very cool, thanks for the report. Props for using search.

If you see no activity on the first connection, then I suspect those devices also may also be using the generic driver already installed. Good enough

Not sure what I am missing here. You do not capture anything. Go to the Window menu, select Output, create a new output for TCP/IP. Define the IP address and port number you used in puTTY. Drag the listing from the output window to a timeline to create a string cue. Open that cue and type in the string you used in puTTY. Note, un-typable character and hex values must be entered as a dollar sign and two hex digits. For example, a carriage return is typed as $0D

No. It precedes Windows 10 by a long time. It may be possible to get it to work if you replace the license key driver with a newer version that supports Win 10. But you will still encounter other issues that are unique to Win 10. Not recommended for any version of WATCHOUT at this time, but Dataton is working on a new version 6 variant to address that. i.e. coming soon .... BTW Microsoft does provide downgrades rights to Windows 10 Pro owners. So a Windows 10 Pro license owner may use Windows 7 Professional or Windows 8.1 Pro in lieu of Windows 10. Since proper tuning and OS preparation dictates the drives be reformatted and the OS installed from scratch, switching to a more compatible OS is no different amout of work.

Thomas, since a WATCHPAX is locked Windows embedded and it clears any installed driver on shut down, does that mean the Korg has to auto-install the custom driver every time the WATCHPAX boots? I suppose that would work, would make me a bit nervous in an unattended install starting up on a daily basis. Not so much concern for live shows when an operator is always present. ---- FYI There are also much simpler low cost USB - MIDI interfaces that work with the generic MIDI driver included in Windows. i.e. no driver needs to be installed, needed support is already available from a standard windows install. These type of interfaces are always straightforward and simple, i.e. they simply provide a MIDI In and MIDI out jack and nothing more. That is all WATCHOUT supports anyway - one MIDI connection only. As soon as they start getting fancier than that (multiple MIDI ports, etc), the need to install drivers come into play. I know the USB-MIDI interface that Show Sage sells has immediately worked without further driver install with every computer I have ever plugged it into, including WATCHPAX and WATCHPAX 2. I know of a few examples of these running trouble free daily in museums for multiple years now. (In conjunction with MIDI Solutions F8 switch interfaces providing connections for push to start and language selection pushbuttons).

The DP graphics card does not support accelerated Microsoft DirectX 3D rendering, the advanced Windows rendering mode required by WATCHOUT. That is why WATCHOUT software will not open, the needed rendering mode is not available. You should be looking at AMD/ATi or nVidia based graphics cards that support the needed rendering modes.

No, for 4k use, WATCHMAX is not overkill. There is no limit in the WATCHOUT software other than those defined (maximum six outputs from only one graphics card, all outputs from one graphics card must the same resolution and refresh rate.) , All other limitations will derive from the hardware chosen. From a practical perspective, when outputting 4K resolution, the WATCHMAX will only provide two useable 4K outputs.

WATCHMAX will provide 3840 x 2160 output at either 60p or 30p quite well. For 4k use, depending on movie encoding you intend to use, you might consider the WATCHMAX enhanced RAID option that increases disk storage throughput about twofold.

Here is a good instructional video from AMD, the differences between passive and active adaptors is explained (among other things). https://www.youtube.com/watch?v=Jf0X0lNFmgw&feature=youtu.be From what they say there, seems to be a good argument for only using active adaptors. Mixing passive and active adaptors results in two different signal paths. i.e. Passive adaptors pass through legacy DVI/HDMI/VGA native signals generated directly from the graphics card (up to maximum of two). Even though these legacy signals are output on a DisplayPort connector, they are not DisplayPort signals, the graphics card detects the passive adaptor and adjusts to generate the legacy signal types. Active adaptors accept native DisplayPort signals from the graphics card and then externally adapts them to DVI/HDMI, adding the signals not normally supplied by native DisplayPort. So to ensure no differences in timing, it would make sense to keep all the signal paths the same. Note 3360 WATCHPAX (one output) requires an active adaptor when needed, passive is not supported. 3362 WATCHPAX 2 (two outputs) on the other hand supports passive adaptors on both ports.

BTW If you do already own WATCHPAX, you will need a device to accept the live signal and convert it to an RTSP MPEG 2 mulit-cast stream. In WATCHOUT, use Network Video media type to place the stream on the displays. Expect delay in such a system. Normally your integrator can provide products to perform the conversion. Just ran a google search, there seems to be lots of products out there for this, both hardware and software based. Sounds like a great research project for ISE early next month ;-) Not having tried it, just looking at specs, something like this looks appropriate: Marshall Electronics VS-103E-3GSDI 1080p60 Full HD Video Encoder with Embedded Audio Anyone out there with firsthand experience integrating live sources into WATCHOUT's Network Video object willing to share?

That is simply not true. All WATCHPAX and WATCHMAX are Windows 7, and I assure you they run all WATCHOUT 6 variants. With regular' PCs, there are numerous successful systems running Windows 7 and WATCHOUT 6. More likely newer drivers optimized for Win 8 at the expense of Win 7 proper function. You may have to investigate using older drivers with some hardware as a result.

WATCHOUT and WATCHPAX encoding guidelines

WATCHOUT Display & Production computer Tweaking list Just wanted to create a more direct link to information near the end of the first post

Been away on holiday. If you don't already own it, you really do not want to purchase a WATCHPAX for live capture applications. WATCHMAX on the other hand is well suited to that task, as it can accommodate up to twelve live HD-SDI inputs. Be sure to specify quantity and signal type desired for capture options when ordering / requesting a quote. for example, live feed -> one SL DVI or live feed-> four HD-SDI, etc.

v5.5.1+ suppresses the logo on startup with the -NoLogo switch in use. With both 5.5.1+ and v6, the information text is still displayed (on a back background) until a show is loaded. (information text = version, WATCHOUT computer name and cluster and IP address) reference: http://forum.dataton.com/topic/56-hide-watchout-logo-progress-bar-while-updating-show/?p=288

reference: watchpoint = WATCHOUT Display Is this occurring during computer power up with the watchpoint software loaded by a shortcut in the autostart folder? What you describe typically occurs in that scenario when a background item starts up after watchpoint and interferes with watchpoint's operation. i.e. your computer tuning is not complete, this should be caught and fixed during tuning / testing before the computer is put in service. BTW I have even seen something as innocuous as a keyboard with programmable macro keys and without its correct driver cause such issues.

Well, since Live Update is one of the areas addressed by v6.0.1, it would make sense if you try that version to see if it addresses your Live Update issue.

Since there were changes in Live Update between the two - which version - v6.0 or v6.0.1 ?