jfk

Nice comparison from last August, but before the FirePro 7100 was commonly available, which has since changed. This means it’s (W5100) targeted towards lower power usage scenarios where the high compute performance The higher compute performance is probably not a concern until 3D projectors or virtual displays are among the features used. and 8GB+ VRAM capacities of the W7100 and higher aren’t needed. It is not so much the memory size, as it is the memory bus width and speed that matters most to WATCHOUT. and that is where the 7100 stands out. It is interesting to note the reference to the W600 in that article as well ... " ... the display wall niche W600 ... "

wow, that is a big step from 'can not run one smoothly' to 'now running four smoothly' Had you run tools that monitor performance, you would likely have seen the interference from the hidden background task. The professionals who build computers run such tests to confirm their builds are performing as expected. Anyway, OS: MS Windows 7 Professional 64 bit (tweaked by dataton's tweaking doc) ... ... I've found an active silent vnc service running. ... Let's assume you had tuned correctly, and sometime since, someone else added the offending software. Whenever anamolous behavior is observed, it is always a good idea to go back to the known good state from your tuning. (This assumes you archived that state as outlined in the last step of the tuning guide - IMAGING PROCESS.)

Understood. WATCHMAX now removes that guess work for you. As you have correctly deduced, the W600 is ok for simple video playback only use. And there are some other simple, highly restricted uses for it as well. Did you not notice that was not the only solution offered? Did you not find it suspicious that card is way less expensive than the other recommendations for six outputs? Now you know why.

In theory, it should work. If you want to be a computer builder, invest in the builders tools and let us know what it is doing in reality. Not saying that something is amiss, just saying we do not know. Barring that, create a minimum show that exhibits the issue, bundle it, and send to Dataton by whatever means necessary. Image sequence playback is a new feature and it appears Dataton is anxious to improve any issues identified. Help them out

You will find multiple recommendations against using the AMD FirePro W600 in this forum. We all knew the W600 is way underpowered for WATCHOUT use, I am only a little surprised it has difficulty with such a simple task as a positioning move on three outputs. Once they start stuttering, out of synch is part of that too.

I know nothing about AMD processors and motherboards, but first you must be sure that the processor and motherboard provide enough PCIe lanes to support all of the capture cards and GPU. Assuming this, your best bet: DataPath VisionAV-SDI Capture Card With the correct motherboard and processor, it should be possible to get three of these cards working at the same time (and yes, we have successfully tested three of their two input cards at the same time. ymmv).

Yes, correct, movie decoding is done in the CPU. (WATCHPAX has some exceptions to this, but Dataton controls that hardware so it can be done with repeatable results.) No, it is not DirectX, it is the nature of GPU hardware accelerated decoding. Hardware accelerated decoding may come with restrictions not encountered in CPU software decoding, related to some tweens and compositing functions. This has improved over the years, but that is still an issue, as not all GPU decoding is created equal. Software decoding allows consistent results regardless of the GPUs hardware acceleration implementation variations.

skipping the deinterlacing step does look better.

Be sure to quit your MIDI monitor before opening WATCHOUT or WATCHOUT probably will not see the MIDI data. This is more a function of the MIDI driver, some drivers only allow one connection at a time (including the MIDI driver built into Windows), some drivers allow multiple connections (usually from the MIDI interface manufacturer). On single connection drivers, if another program is connected when WATCHOUT is opened, you will need to quit WATCHOUT, quit the other software connected to MIDI, then re-open WATCHOUT.

All versions of WATCHOUT 5 keys are electronically upgradeable in the field (including the original black keys).

They do not need to match. Yes, the programming computer can be less powerful. Just like version 5, it may be necessary to detune the production preview with less powerful computers. i.e. show video as thumbnails, etc. just the same it will work.

Yes, the pre-split videos should play in synch, provided the videos are encoded properly (Constant Bit Rate, etc.) and also provided the videos are rendered out in synch. The accuracy of that synch can vary. Typically (but not always) when all the outputs come from a single computer they will be in perfect synch. When the pre-split outputs come from multiple computers, synch will be accurate within a frame, but not perfect. WATCHOUT supports a hardware assisted synchronization option, and when this is used, you can achieve perfect synch across the outputs multiple computers. The question becomes- when is software synch (within a frame) and hardware assisted synch (frame accurate) needed? When connecting watchout directly to the displays (projectors, flat panels), and the projectors are overlapped or the flat panels are separated by frames, software synch is typically all that is needed. When feeding to processors or driving mullionless flat panels, hardware assisted synch is probably needed.

The first error states that the Display PC is telling WATCHOUT that the resolution you have typed into the WATCHOUT Display dialog for visualizador 1 is not available. The second and third errors are simply side effects of the first one. Double check to make sure there are no typos in the resolution entered into the WATCHOUT Produciton display definiton. If that is not it, Set your Display PC desktop to the resolution that you entered in WATCHOUT Production, before opening WATCHOUT Display. If you can not set that resolution in Windows desktop and you know the computer can do it, most likely a flaw in the displays communication of EDID to the PC. This can occur from flaws in extenders, flaw in the display, etc. (Been seeing EDID issues arising from Panasonic projectors again recently) Worse case, you may have to add an EDID manager to your Display PC outputs to correct flawed EDID signal.

Have seen that error occur when WATCHOUT installation does not properly complete. Reopen the installer for the version you are running and select "repair", this usually fixes it.

Yes. WDM. Yes, the Windows 7 WDM driver for the Motu 828 will provide multi-channel sound with the new method used in WATCHOUT 6. WATCHOUT still requires a WDM driver. The change is in the WDM calls to utilize a different multi-channel method within WDM.

Definitely not, 64 bit Windows OS is fine. That does not sound like an accurate description of the error message. Is this the error message you are seeing? BTW the information in this message is meaningless, as often is the case with error messages. If so, here is the solution: 5.2 installation issue (MacOS)

FIX Windows error opening WATCHOUT Installer downloaded with a Mac If you download any WATCHOUT installer with Safari in MacOS, it will change the file name by appending an .exe that should not be there. If you then take that file to a PC and attempt to run it, you will get an error message, that is of absolutely no help at all The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. To correct the problem, simply delete the .exe from the file name and the installer file will run as it should. Say yes to this dialog after removing the .exe For example, Downloaded WATCHOUT v6 with Safari in MacOS, and this is the name of the file that resulted WATCHOUT_Installer_6.0.1.msi.exe by removing the .exe in the name, the same file named WATCHOUT_Installer_6.0.1.msi worked as expected. Also note, this issue is unique to MacOS Safari. Downloading with the Chrome or FireFox MacOS browsers do not exhibit this issue.

String output sends the string you enter in the cue to an IP connection. I am also curious to learn more about the new Output - Generic Variable. Could not find a mention in the release notes, could not find it in the online academy stuff either, but I have had trouble finding stuff that was there in the past. Output - Generic Variable does not output to any external connection, and it appears it only stores a numeric value. A cue to an Output - Generic Variable has a fade tween, and it even animates the fades in the Output window Value field. I could not use it as a value in the variable formula of a tween track. But it is accepted as an argument in the Task Trigger field, I could see some uses for that.

v5/v6 WATCHOUT License (USB keys) and WATCHPAX 2 with v5/v6 are available, i.e. all new licenses and WATCHPAX 2 include both v5 and v6 support. Electronic upgrades of older v5 USB keys and older WATCHPAX / WATCHPAX 2 are also available. New v5/v6 keys, new v5/v6 WATCHPAX 2, and upgrades have been available since January 2015.

First off, the WATCHPAX or WATCHPAX 2 license must be ready for v6. If you are electronically upgrading your WATCHPAX license, you will need to use v5.5.1 or v5.5.2 on production to perform the WATCHPAX license update. (WATCHPAX 2 purchased in 2015 should already be v6 ready, you can check this with the License Manager in WATCHOUT Production v5.5.1 or v5.5.2). Once the license is prepared for v6, load the v6 software on your production machine, open a show that addresses the WATCHPAX and go online. You will be asked if it is ok to update the WATCHPAX, confirm this dialog, and WATCHOUT will do the rest.

Temporary keys are not going to happen. Never have, never will. If you can not purchase keys for the purpose, then I suggest you partner with an integrator or dealer who has invested in supporting WATCHOUT properly. You do not indicate your location, if you are in the US or Canada, I can hook you up with a partner who can help you out.

The most reliable way to connect MIDI to a WATCHOUT computer is via a MIDI - USB interface.

No, v5 only keys will not enable v6. However, you can test codecs in production preview without a license.

I think you would have to push the slower system past its performance threshold to see any difference. i.e. if the system with the 1600 memory begins to stutter / drop frames, it is possible the system with 3200 may not. Just because all your show materials are within the slower memory's threshold does not mean there is no potential benefit to the faster memory. But quantifying that is dependent on so many variables, that one person's results may not have any bearing for the next person. i.e. the only way to tell is to test it yourself

No, it will randomly jump to whatever is displayed at time 0 on your main timeline at time of load instead of retaining a common image in the two shows.