Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by jfk

  1. It is possible that audio files in your v4 show are the cause of the load error in v5.Seems v5's new audio waveform display in the cue can cause this, for whatever reason WO fails rendering the waveform image and the lock-on-load results. Try removing the audio cues in v4 or move the audio files from their correct location so WO 5 fails to find them. This should get the v4 show open in v5. Once it is opened in v5, bring the audio cue(s) back and it will still fault, but not fatally, WO will then bring the audio into the show without the waveform display. If need be, use an audio proxy t
  2. I thought I might post a clarification here,as I spoke with someone today who may not have interpreted this correctly.WATCHOUT 5 only works with one graphics output card.That one graphics card may have up to six outputs provided the graphics card vendor includes driver support for multiple ouptuts under DirectX in 3D mode.The AMD/ATi Radeon with Eyefinity does support more than two outputs with WATCHOUT 5.Not all vendors do that.
  3. Ignoring the economic issue, like the OP's request,for asset security management in some environments, there is value to remotely serving the licenses . There are both upsides and downsides to remote license service. If a license server goes down, all WATCHOUT computers will soon go offline. We have entertainment fixed installation live event customers who simply will not trust the operation of every display to a single computer / network, and in v2-3-4 that decision carried significant expense. From a marketing standpoint, ok, v5 erodes revenue per sale enough, I can see the di
  4. With v4 - use VNC and a host computer to generate the clock image, crop, position and scale in WATCHOUT as needed. A simple Flash app running on v5's WATCHOUT Dynamic image Server would do the trick too.
  5. That is more of a function of the movie decoding codec than WATCHOUT.WATCHOUT itself has no limits, it is bound by the limits of the codec chosen. The movie decoders do have limits, and different encoding (mpg, wmv, avi, etc) have different restrictions. It gets more confusing with QuickTime, as two .mov codecs (h.264 and animation codec at 32+) are decoded by non-Quicktime decoders, so their limits are dictated by their Windows native multi-threaded decoders instead of QuickTime.
  6. Right, that was the distorted major use of the old feature, thanks for correcting me ;-) As I recall, it's original v1 purpose was to display a media object that entered the blend area only if it were in the non-blended areas too. It would not display at all / disappear when the object was only in the blend area. Useful if you have a capture card in less than all of the displays, as you can prevent the error that would occur if the live input touched a display without a capture in just its blend area. Was kind of the pre-cursor of pre-split proxy too as I recall, as the same wo
  7. The edge blend line went away with the introduction of stage tiers in 4.0.Depending on what you are trying to accomplish, there maybe a way to achieve an equivalent using the stage tiers.
  8. Got it, thanks. That method still retains the same restrictions as with earlier versions. i.e. since you are spoofing WATCHOUT by using a single display object to output multiple displays, you lose blending, independent geometry, no compensation for mullions, tier functions are lost, etc. FYI That is different than Display Port 1.2 Display Port 1.2 essentially runs independent streams over one connection. So WATCHOUT will still see individual displays in the stage window. [strong]D[/strong]isplay [strong]P[/strong]ort 1.2 displays will be able to set an address, and will
  9. Yes, that is a good idea.Unlike the main timeline, which has no stop state, Auxiliary timelines have three states - Stop, Pause, and Play. Stop is a dormant state, no media is pre-loaded. Pause is an active state, pre-loading media for immediate response. Play is an active state (obviously) and acts like a timeline play. As JJ notes, going directly from Stop to Play on an Auxiliary timeline takes some time to load up. So yes, pressing stop before pressing play will toggle the Auxiliary timeline to pause, essentially pre-cuing the timeline for more immediate response to Play.
  10. I am not sure I understand the Matrox part of that correctly.WATCHOUT 5 only supports one graphics card per computer, with up to six outputs on that one card. There is no support for multiple graphics cards. (SLI / Crossfire acts as one card, so that could be a little confusing). If that Matrox thingy is working outside the computer on high res outputs and not in the machine, then I assume those can be fed from a single card with three outputs.
  11. Actually, in WATCHOUT 5.0, you can not do that.v5.0 requires all outputs from a single multi-headed computer be the same resolution.
  12. You can try the 23.98p, the display output is still 60p, so WATCHOUT has to do the 60p w/pulldown conversion on the fly, adding to the load. The 24 fps complaints are typically related to motion artifacts. Apple ProRes is a heavy processor load codec, you may find it will work, may not – computer has a big impact there. In general, Apple QuickTime makes poor use of Windows multi-threading, under-performing in comparison to codecs that are native to Windows. As for the conversion and Sorenson Squeeze, I hear both good and bad reports on Sorenson. I will leave it to others to a
  13. No it is not to large in terms of its storage size.The file size does not really matter, as it is streamed during playback. It will play, question is, will it play smoothly? The files output resolution matters very much, the files encoding matters very much, as both determine how much is streamed per frame, how hard the decoding processors must work, and how many frames per second. (Avoid 24 fps whenever possible, convert it to 29.97, 30, 59.94 or 60 fps before using it in WATCHOUT). If you are trying to output one 7680 x 1080 at 60p or 3840 x 2160 file at 60p, your com
  14. Yes.This is documented in the WATCHOUT 5 User Guide There are two methods for controlling WATCHOUT playback. - Control of Production is IP only. reference Appendix D Off by default, must be enabled in Production Preferences. - Control of a Display Cluster is IP or Serial. reference Appendix E, Cluster control via IP is straigtforward, as it is always available. Cluster control via serial is off by default and must be turned on a by a script, etc, also covered in Appendix E. Either method supports SMPTE chase input, DMX output and IP output. Production is only needed w
  15. Inquiring minds want to know? i.e. one of our customers is asking the same question. Can anyone provide direction on the non-WATCHOUT section of the motion tracking solution used at InfoComm? The WATCHOUT side we understand - bitmap media object set to "Optimize For: More Effects and Capabilities", Inputs, Tween formulas, etc But how was the motion tracking accomplished up to the point of the position data provided to the WATCHOUT input objects?
  16. Yes there is a good way to do this. Use the Display dialog scaling feature to program the stage in 1920x1080 chunks while outputting a different resolution that will work with the displays you have. Switch them back to unscaled when you are ready. Reference: [em]WATCHOUT 5 User Guide[/em] - Chaptor 9 - DISPLAY SPECIFICATIONS - page 151 (screenshot of the dialog on pg 150)
  17. Not sure what your question is? So your two blended computers are not synching with each other? BTW We do appreciate all the system detail, but one more detail if you will. Are there any audio connections in the system? Reason I ask is we have heard reports of a synch delay when an audio cable is connected to the motherboard audio outputs, unrelated to actual sound playback on that computer. That may be related to a Windows Control Panel setting ( jack detection ), have not confirmed that yet, but it has been reported as the source of mis-synchronizaiton between displays. T
  18. No. Only one graphics card per computer is supported. Up to six outputs on that one card are possible, assuming the card supports its outputs under DirectX. Also note: all outputs from a single card must be at the same resolution. All other aspects of the outputs are discrete.
  19. Here is the ShowRoom forum post that you are referring to ... [strong]From: Mike Fahl Reply-To: Showroom Date: Mon, 11 May 2009 09:31:58 +0200 To: Showroom Subject: Re: changing the folder for display's media [/strong] There's an (undocumented) command line option that can be passed to the WATCHOUT display software to allow for this. This is what the "Target" field in the application shortcut would look like to use this feature: C:\WATCHOUT\WATCHPOINT.EXE -ShowPath /e:/Shows/ In this case, WATCHOUT is installed on the C drive, and the files are stored in the S
  20. BTW Microsoft says windows XP or Windows 7 32 bit can address 4 Gb of memory. I thought one of the reasons for the 3 x 2Gb for 6 Gb memory was to achieve the enhanced throughput of the triple channel memory as compared to running 4 gb of just dual channel memory?
  21. Well the best example is the WATCHOUT 5 intro show Dataton stages at it trade show booth. Full 3D, two screen blended overlap times two - four projectors with integrated 3d filters.Impressive seems their next exhbit is at PALME ASIA 2011, July 13-15 ( http://www.dataton.com/events )
  22. jfk

    Error #2031

    The error does not come from WATCHOUT, it comes from the Windows OS, and is being displayed by WATCHOUT. It is usually an indication of an OS configuration that is flawed. A simple google search of "Error #2031" indicates many solutions like ...
  23. Simple answer is yes it can be done.Each watchout display is capable of eight channels of output. Audio synch between displays is very good, but not phase accurate perfect. With the way you have split up your audio, that should not be an issue however. As for the motu, you need to test that with your hardware setup. We do have customers who use Firewire motu boxes, but your results may vary as your hardware is not identical to those who report success. There is no provision in WATCHOUT for output of either MTC or SMPTE.(WATCHOUT does read and synch to all forms of SMPTE.) M
  24. I can think of about 30 things with so little information.Could be incompatible hardware. i.e. a hardware configuration that does not meet its specs.There are many settings for the hardware that can cause that too.Contact your hardware vendor and work with them to be sure all components listed in the requried list in the user guide are in fact properly configured for DirectX compliance.
  • Create New...