jfk

Not easily, not impossible. The information exists in the .watch file, in text form, but it is not in an immediately useable format. Dataton does not document internal file structures, but by the same token they do not hide the data. All of the information that defines every object (cue., layer, display, media, aux timeline, etc, etc) in the .watch file is there in text form. You would need to filter it and turn it into a form useable for your purpose. An example of a third party application that does something along those lines: WATCHOUT Forum - topic: Import Layers from Photoshop The app shown externally generates new media items, a new composition, populates the compositions with advanced media cues on multiple layers and then imports all that into a current watchmaker session. If you would like to see what a text representation of a media cue looks like, open watchmaker, select a media cue, copy it, open Notepad, and paste. The now discontinued WATCHOUT System Manager toolkit included a developers api. But it did not include a media cue list or a media list export function. The api existed to support third party control applications. One of its functions extracts (and optionally filters) a list of watchout control cues by timeline, as that had purpose from an external control perspective.

Other ArtNet - DMX convertors that have been successfully configured to work with WATCHOUT Kissbox DMX1TR - DMX-512 Transceiver Sand Systems SandBox

I can confirm Mike's belief, tested it, and either upper or lower case letters will work the same when defining hex values in the WATCHOUT String Cue.

While it is certainly not impossible for watchout to have a memory leak, it is just as likely the leak is in a driver that is indirectly called by WATCHOUT (via standard Windows API calls). Take a close look at all your drivers for compatibility with Windows 8.1 would not be the first time motherboard drivers (USB, disc controller, disc drive, etc) showed issues like this. So when checking be sure all motherboard related drivers show Apple as their source. I have used Apple bootcamp windows drivers with Windows 7 Professional with no issues, but no experience with Windows 8.1 and bootcamp. (Yes, I know current Macs will not allow win 7 with bootcamp, my Mac is a bit older ;-)

Yes, that is correct providing "Display 1" and "Display 2" are the correct names for your displays (case sensitive).

There are two methods for implementing pre-split proxies. The "new" pre-split proxy method (extension on movies, no extension on folder), and the "old" pre-split proxy method (extension on folder, no extensions on movies). Seems 6.0.1 works with the new method, but errors as you describe with the old method.

That is an incorrect assumption.

Seems every time there is a new release, we see this issue come up in support communications, so as a reminder ....

Yes, the problem comes from file name change that occurs when downloading in MacOS 10 Safari. Please see here for the simple solution: 5.2 installation issue (MacOS) BTW I recently tested under MacOS using Google Chrome and FireFox instead of Safari, and both work correctly, this is a Safari specific issue. but no matter, its easy enough to correct once you know what it is

so to generate the equivalent to \n (new line / carriage return), in WATCHOUT's string cue you would type $0A$0D

I am not sure I understand what you are saying. The string cue in WATCHOUT does not require quotes around ASCII text. If you can type them in telnet without the quotes, they should work the same way from a watchout string cue. Granted, the non printing carriage return character is different (typing $0D where you hit the return key in telnet). OP At the end of the day, it still sounds like the connection is failing. Without a connection, the strings are never sent. And that is why watchout displays a message to that effect. If the connection is valid and the string is sent, good string or bad string for the receiving device does not matter. WATCHOUT will not give any error message for a string that the receiving device does not like. WATCHOUT does not monitor any return traffic from the device, it blindly sends the string to the connected device and nothing more. So while it is possible the string is wrong, if the connection is good, you will receive no notice from WATCHOUT about a bad command, etc. So if your problem was syntax, you would not be receiving a failed connection message. You must get rid of that message before you can worry about the string syntax. Opening a single numbered port in the firewall is probably not good enough, you must open all ports used by the watchout application. For the purpose of testing, please disconnect from any internet or other non-essential connection and turn off the firewall.

From what you describe, I do not think the issue is with your string cue. I would be looking at any potential network issues or possibly the String Output definition Was Telnet run on same computer as watchmaker testing? Is there a firewall or any other potential network obstruction? (Applications like telnet and watchmaker on the same computer can still be individually blocked by a firewall, for example)

Could you be more specific? As a display output card for watchout - no. As a media drive interface - probably (DirectX compliant DMA support required). As a WDM capture source (WATCHOUT Live Video), the term WDM does not appear on their overview or specifications pages, so I can only guess - Not.

since setIP works differently in v5 and v6, the version you are running is critical to answering your question. in v6 IP addressing is a no-brainer, look specifically at the thing that changed, your production computer. In v5, I am pretty sure I did what you describe, and I did not use setIP on any watchpax. this made for a solid reliable system. reference: v5.5+ computer name - fundamental change in display dialog address assignment As for you replacement produciton machine, check for firewall, etc. Bootcamp simply identifies it is a true Windows native install, so all Windows considerations apply, including the Apple sourced hardware drivers supplied in the bootcamp materials. (specifically the NIC driver, if it says Microsoft source, that is a likely issue.)

Dataton support is not going to provide any unequivocal statement on a system config. From a simple specification standpoint, yes, that setup will allow WATCHOUT 6 to open and run. From a performance standpoint, I agree with jcvargas, the w600 is a minimal performer. Bumping in to its limits all depends on content demands. For example, I would not try pixel mapping WO6 3D projectors with that graphics card.

Owen should have mentioned he is using 5.5.2 We have communicated offline ....

1. Essentially correct. The media production tools in WATCHOUT Production software (aka watchmaker) are fully functional without a license. You may open existing shows, create new shows, save shows, etc. All media animation functions are fully functional. The license key activates three functions in watchmaker. Network communication to WATCHOUT Display (aka watchpoint) for transfer of the show to the display computers, as you note. Export of a synopsis movie of your work (File - Export Movie) is disabled without a license Output objects for ancillary device communication (DMX/Artnet, String, Generic / Window - Output) are disabled Input objects will work without a license (Generic, MIDI controller, MIDI Note, DMX/ArtNet / Window - Input) 2. WATCHOUT Production software includes a full rendered Preview of all outputs as one of its standard functions. In summary, yes, the WATCHOUT Production software is very functional standalone for all media functions and it is well worthwhile to learn it without a license.

This may be counter-intuitive, but you may try encoding the videos at higher bit rates. When video is heavily compressed, you will hit the threshold of the CPU. Compressing them less (higher bit rate) eases the load on the CPU, while increasing the demands on throughput. But I do not think you have come anywhere near the throughput threshold.

Remote restart already exists via the cluster command powerDown and Wake OIn LAN functions. HOWEVER, when the error condition prevents watchpoint from functioning, that does not help much.

Well that is encouraging, but those cards are not available yet to the best of my knowledge. As always, the drivers are critical to success, so until we can get our hands on them, we will have to wait and see.

Don't know of any other solution with four HD-SDI inputs per card. With a proper motherboard, two BMD DeckLink Quad 2 will provide eight simultaneous inputs. The motherboard needs to support one x16 (graphics card) and two x4 slots at the same time, not all CPU/motherboard combinations can provide that.

Once WATCHPAX (original or 2) is powered on with no valid outputs connected, it is in an error condition and will not accept IP commands for any further action. So yes, once the unit is in error, the only solution is to pull power from the unit to restart it. Two potential solutions. 1. Add EDID managers to all outputs and then the WATCHPAX will always see a correct display load regardless of display state. - or - 2. Add a remote control power switch controlled independent of the WATCHOUT stuff and cycle power when needed via the remote power switch cycling.

Yes, with thumbnails only in production, movie files are not played back in production, and of course that includes the audio that is embedded in a movie file that is not played. There is no way to play embedded audio without playing the entire movie file in production, and playing the entire movie file in production is what is disabled in thumbnails only. With thumbnails only set in production, audio is still played normally in the display computers.

Does the capture card appear in the Windows Control Panel - Hardware Manager List? i.e. does the computer see the card in its expansion slot? If it does not show up in hardware manager, installing a driver or restoring an archive is not going to fix it and it probably has experienced shipping damage and needs to be returned for warranty service. If it does show up in Windows Hardware Manager, and the watchpoint window mode menu for Video In is grayed out, I would recommend restoring the entire computer from the Acronis archive included on the WATCHMAX. Dataton assures me that WATCHMAX capture cards are tested with watchpoint and a live signal prior to shipment, so it was working when it left the factory. As such, the properly configured driver is part of the archive, so an Acronis restore should guarantee proper configuration of the capture card driver.

Use the same guidelines as for 1080p and multiply the bit rate by 4. Codecs for stable WATCHOUT playback In the first post, scroll down to WATCHOUT - Codecs for stable WATCHOUT playback - 2012.pdf