jfk

It is pretty impressive that the Surface Pro supports accelerated DirectX 3D graphics and all the other sub-systems are DirectX compliant. Still that is a very high demand for such compact hardware. Now the question is just how well it supports DirectX. i.e. this really sounds like a hardware / driver issue, and memory leaks in immature drivers are not all that unusual. Yes, we have encountered bugs in WATCHOUT 6, but nothing that looks like a memory leak. Sounds like WATCHOUT is exercising portions of Windows on your hardware that are not commonly encountered with other applications, and that is bringing the hardware / driver issues to the forefront. Have you done any web searching on issues other users encounter with your chosen hardware?

Did you check the obvious, i.e. is the Play Audio Media item checked in the WATCHOUT Production Preview menu? Probably does not matter here, but it is usually useful to indicate the WATCHOUT version you are using.

and yet your graphics card is outputting at 30 - that will cause the issues you describe. Try changing WATCHOUT Preferences to 30 to match what the computer is actually doing. (BTW do not use the Windows control panel to make your display settings, use the card specific utility), Well that is a red flag right there, pointing at exactly what Mike warns about - EDID issues. Do what Mike told you, substitute a standard display connected directly to rule out WATCHOUT issues, then focus on the real issue which is your display chain. Disconnect all other display connections for the test (if you have multiple 1080p monitors, hook them all up direct, but eliminate the display connections that are already causing issues for the purpose of testing. The 30 Hz restriction is most likely is a side effect of an EDID issue.

As long as the timecode is present on the input and timecode is enabled, you could move the timeline, and timecode will pull it right back. If timecode has ceased at the input -or- if timecode is disabled, then yes, you can manually control the timeline.

Without the information from the tween's formula dialog it is hard to tell what is going on there.

You may exchange a failed or failing key for a new one of the same version for a core fee (≈ USD $300 + shipping charges). Contact your local WATCHOUT Premium Partner for assistance. BTW The license key is not specific to version 5.1, it is a version 5 license and will work with any version 5 variant. You are welcome and encouraged to upgrade from v5.1 to v5.5.2, which is at no charge. i.e. the same license will work with the latest v5 version. That would not be an option anyway. You do not need proof of purchase when an exchange fee is charged (out of warranty), the old license USB key is adequate proof of license ownership, you must exchange that old license key anyway.

Break the 16 channel audio into two 8 channel multi-channel .wav files. Assign each file to the display PC that will play it, by placing the anchor point of the audio speaker icon for each file inside a display rectangle assigned to the computer you want it to play on.

I would suggest you make that argument with Microsoft. Dataton works within the confines of Windows built-in support.

A USB device without MID IN, MIDI OUT and MIDI Thru connections is not a real MIDI device. So yes, external hardware would be needed to turn those USB devices masqueardaing as MIDI devices over USB, into real MIDI devices with standard MIDI connections. Makes more sense to purchase real / true MIDI devices and avoid all that nonsense. Supporting multiple USB connections as MIDI interfaces is beyond the built-in Windows support for MIDI, and is unnecessary when using true MIDI devices. Yes, the low cost USB device manufacturers provide drivers to allow Windows applications to support multiple USB devices masquerading as MIDI, but those are proprietary solutions and not available through generic Windows methods. There is more than enough MIDI address space available through the single MIDI connection to address any imaginable need. Adding proprietary software interface to support pseudo devices just seems unnecessary to me.

Does seem to be a change. Now your shortcut for aux timelines becomes Cntrl-J, Tab, I do not know if it is intentional, but I prefer that. But I am renaming timelines more than jumping the timeline in that dialog, I respect your method just the same.

Update. Came up with a customer today. Yes, the -NoLogo command line switch in Version 6 continues to function in the same manner as v5.5.1 & v5.5.2 Just tested and reconfirmed on all three of those versions today (v5.5.1, v5.5.2, v6.0).

With a generic HID driver and a mouse not acting as expected, you should look for a windows 10 driver from the mouse vendor.

3840x2160 capture works with WATCHOUT 5 and there is no reason to believe any different with WATCHOUT 6. We used DataPath capture cards when testing this with WATCHOUT 5, DataPath VisionSC-DP2 at up to 3840x2160 60p via DisplayPort 1.2 and the DataPath VisionDVI-DL up to 3840x2160 30p via DL-DVI-D. There are a few WATCHOUT 5 systems in regular use for the purpose of accepting a 4K signal and delivering it as four 1080p outputs. Do not know about the BMD product.

did not see any smilies - damned if I can find that, search does not seem to work for groups, but Facebook is always a bit confusing to me. Is it not possible to provide a link for such a reference?

No there is no WATCHOUT Windows 10 tweak list. If it is anything like 8, someday 10.1 should come closer to the mark. From what I have read in other lists, you might want to be conservative. Nothing but negative comments, must common comments relate to slow down and crashing. Seems drivers become an issue, be sure you have Windows 10 certified drivers for all of your hardware (motherboard, all PCIe cards, drives, peripherals {even fancy keyboards}, etc) before even considering it.

Wow does that signal get stepped on a few times in that path. Can you say delay? Not sure you need to go to the trouble of locking everything to house synch, if the sources are synched, that synch should not change each time its stepped on with those types of devices. i.e. I doubt they introduce variable delay between their inputs and outputs. Just the same, you can genlock it all if you want, won't hurt when done correctly.

With DataPath (and some others) the newest driver is not necessarily the best choice. With wholesale updates of BIOS, etc you may be moving backwards. Your best bet for assistance is your hardware provider. If your hardware provider is of no assistance, you may want to consider a more qualified hardware provider. Dataton finally got into the business of providing full blown hardware (WATCHMAX), and they will offer options like the DataPath input cards, so there is always an opportunity to find hardware with hardware technical support from Dataton.

Compositions provide the equivalent of a grouping function. Once they are in a composition, they can be rotated as a group.

Simple answer is sort of. The complex answer depends on what your tolerances are. Will you get 16 channels of "synchronized" playback? - Phase accurate synchronization for all 16 channels - NO. - Lip synch accurate for all 16 channels - YES. For 8 channels of phase accurate audio and eight more channels of "wild" audio, works fine. The 8 channel groups will maintain phase accuracy within themselves, they will not maintain phase accuracy between the groups. When we need more than 8 channels of phase accurate audio, we marry a Merging Technologies Ovation server to WATCHOUT and you can get up to 128 phase accurate channels.

Use scaling on the virtual display media objects when you place them on the 2D display to correct for pixel density variations.

Best way to do that may be by triggering the countdown aux timeline from WATCHNET scheduler.

Thanks, appreciate your sharing the information. I guess I am not a youtube person, two levels down seems I need to learn to click "Show More", but It might be clearer if you put that in the post too. Magewell vs Datapath vs Original youtube video posted by Thomas Leong An impromptu video capture cards comparison: Magewell Xi102XE-HD on the left, Datapath RGB E2S in the centre, and original clone on the right. Source is a video played from a laptop (HDMI) feeding a DVI splitter. This DVI splitter in turn feeds the monitor on the right and sends the other outputs to the capture cards processed by Dataton's Watchout 5.5.2 in a X99 i7 5930K PC that sends its outputs to the left and middle monitors via an AMD Firepro W7100 with DP-DVI active adapters to the monitors. Coming from a computer, I guess the input resolution was 1920x1080@60p?

WATCHOUT version used in test? (This very well could change in v6 as changes in the handling of captures streams are implemented in v6).

To be clear, the information is available in the .watch file, but WATCHOUT remote does the work. i.e. WATCHOUT remote scans the entire .watch file for all control cues, makes a list of all of the control cues for quick jumps, and it parses out control cue PAUSE time points so it can generate its countdown timer. Extracting all of its needed info from the .watch file provides its "self programming".

Instead of making a video, it may be easier with a couple of embedded compositions and 12 or 13 still images for the digits and punctiuation. As accurate as you want it to be. BTW This is discussed in the thread: Feature requests? - POST here, post #40, #42, #69