Jump to content
Dataton Forum

jfk

Moderator
  • Content Count

    1,496
  • Joined

  • Last visited

Everything posted by jfk

  1. I am not going to try and answer all of those, but one I could clarify is ... That note refers to synchronization between display computers only.Production computer could be anything really, even a different vendors graphics card. The note typically means that all the cards within a group of displays should be from the same manufacturer. Have not tried mixing the FirePro and Radeon families among displays, but have mixed various generations and processors within the Radeon family and no synch issues arose.
  2. The iPad was using an app custom written for the presentation.Dataton offers a generic iOS WATCHOUT Remote app. That was used as a starting point for the custom app written specifically for the presentation. The custom app was written to copy the images to the Dynamic Image Server via WiFi.From there, the WATCHOUT program was written to display the image from the Dynamic Image Server .Dynamic Image Server accepts new images while the show is running and updates them to the displays as soon as the transfer is complete. Posted in this forum.WATCHOUT version 5 - Specifications on InfoComm 2011 S
  3. Dataton has addressed that with WATCHOUT Systems Manager,a set of software applications and components, allowing you to manage one or several WATCHOUT systems. It provides capabilities to control and monitor their operations in a predetermined, or interactive, manner. The utilities include WATCHOUT Remote, WATCHOUT Scheduler and The WATCHOUT Management API. All the applications included come with source code, allowing you to use them as starting points should you choose to customize for your own applications. Documentation is included in the WATCHOUT Systems Manager download packag
  4. I hesitate to use the word "perfect" as that leaves no wiggle room ;-) With the visuals yes, three independent stereo audio files will play with very good visual lip-synch. "Perfect" synch to each other - no. i.e. While WATCHOUT is frame accurate, when playing multiple audio files, it is not phase accurate when spread across multiple displays. In very critical applications, you may observe small amounts of sub-frame drift over a long time. When this occurs, the display will vari-speed back to synch. The drift is not enough to affect lip-synch, but it will disrupt audio multi-channel
  5. Version of WATCHOUT?There is a malfunction in 5.0 with audio from production that [em]may[/em] explain your issue. It will cause production to cease audio output if the audio file's speaker icon is not visible on the stage. Fixed in 5.1. Since its a laptop, as a troubleshooting step, have you tried moving it to the connection point and using a short simple connection cable? Anytime I hear mini RTS to XLR cable I am always concerned about level mis-match too (-10 dB vs + 4 dB, etc.)
  6. Yes, you can.Not sure what manual you are looking at, but it is documented in the v5 user guide. It is not in the v4.0 user guide because those commands were added in 4.0.1 afte the user guide was published, so it appears in the Help > What's New section of the production Software for v4. Commands are the same for both versions. run [] Start running, optionally specifying an auxiliary timeline name. halt [] Stop running, optionally specifying an auxiliary timeline name.
  7. An uninstall and reinstall should clean the registry. If the OP is Sid, then I can add that it is possible to Telnet into his display clsuter and properly extract a list of the shows. (Sid had his single cpu display cluster on a public IP and I was able to do this remotely). Again, if this is the person I spoke with last night, the remote referred to is the yodesign iOS WATCHOUT remote. OP did you modify any of the iOS code? At the same time I was able to Telnet in and retrieve a show List, Sid was still unable to get iOS WATCHOUT Remote to do the same. BTW For anyone int
  8. Just about any switch meets that requirement. The real question should be ... This is NOT a WATCHOUT issue, it is a Windows 7 / hardware interaction issue. Just because a switch works fine for someone else with their hardware and Windows configuration, does not guarantee the same will be true for you. I must be lucky, my seven year old dLink DGS-1005D Gigabit switch has worked fine with Win7 without any adjustments on my part.
  9. WATCHOUT only supports one serial port per display computer, hard coded to COM1.Provided COM1 is fully Windows compliant, it should work, ymmv.
  10. No, there is no external control method to power down the production computer.But, there will likely be an alternative solution to your requirement in WATCHOUT 5.1 when it finally arrives, so if you can hang in there for a few more weeks ....
  11. I think you are "barking up the wrong tree" there.That is related to Microsoft networking and sharing. WATCHOUT does not use Microsoft networking and sharing. Best to turn those things off. All WATCHOUT communications are TCP/IP, which is independent of Microsoft networking and sharing. In the NIC properties, the only setting that matters is TCP/IP v4. You can uncheck everything else in the NIC settings and it should work. I did see one very good suggestion in one of your links - disable any network device that is not being used. Windows likes to default setup Firewire, WiFi and Blu
  12. Reminds of the system installed in Cisco Systems San Jose, CA world headquarters Executive Briefing Center.It was initially setup with a managed Cisco switch and it would not work properly. I was hoping they would bring in one of their experts to address it and we could then learn what to do, but there solution was to go to a local computer supply house and buy an unmanaged Linksys switch to deal with it. (Yes, Cisco owns Linksys too). Configuring managed switches is beyond the scope of WATCHOUT support of course. That said, we do have a dealer in Virginia who has a large site lic
  13. Yes, when the update is very long, this has been known to occur. It has been identified and corrected in the next release. Note: a network issue that causes slow transfers can exacerbate this issue. There is also a workaround that can be used with 5.0, but I suspect I should not post that here, so call your WATCHOUT vendor driectly or email support for enlightenment on that. As for the mouse cursor issue, that is something a bit different. Once that occurs, watchpoint is not going to be very stable. Quit and restart WATCHOUT Display to eliminate that.
  14. continued .... and there seems to be some issues unique to nVidia GPUs ... and this can go on and on, you really need to research your specific system, or find a hardware vendor who will certify your system with your switch, etc.
  15. seems there is a maximum post length and my response is to long, so it is broken up among the next few posts here … Its not WATCHOUT, its the Windows settings and the network infrastructure.And it sure looks like there is more than one issue at stake. Point is, if your network is running slow, there is no single "do this and you are fixed" answer. You need to identify what is amiss in your system. ------- Periodically we hear reports of very slow online / update times with WATCHOUT under Windows 7. XP machines in the same cluster do not exhibit speed issues. Research has sh
  16. The short answer is - no. TCP/IP Generic input is not the way to approach that, you have to connect and obtain permission, most simple sensors are not that smart and would require an intermediate device (Medialon, Mediamation, Crestron, AMX etc.) to interpret the input to the IP format and manage the IP connection. I would think sensors that transmit MIDI notes or MIDI continuous controllers would be the easiest way, that should be straight plug and play. Once you know what you want the "sensor" to do, post on the The Show Control Mailing List, you should find some good
  17. Pretty generic question.How to set one up in the WATCHOUT input window? How to use one that is already setup? The format for the command sent from a controller? Generic input is only available when commanding a Production Computer via Production Computer Protocol (ref: WATCHOUT 5 User Guide - Appendix D - pg 241) No Display Cluster Protocol equivalent. The generic input accepts an unsigned floating point value to WATCHOUT Production via IP command from a controller supplied by others. So it only accepts a value. I like the ability to override a DMX or MIDI controller
  18. That is one way to do it, yes.But if you do it that way, then no, you can not use command files with that method. You enable timecode chase in the production computer preferences, save the file, and it will remember that preference when the file is reopened. You can automate show load on Production from a third party control system via IP, but not a command file. I think we are mixing our metaphors here. There are two chapters in the User Guide related to control - Appendix D Production Computer Protocol and Appendix E Display Cluster Protocol. [strong]The two are mutually exc
  19. There is nothing in the IP [strong]control[/strong] commands to do this. You may be able to accomplish your goals with output devices and output commands on the aux timelines to communicate this to your iPad apps.
  20. But it seems its not ok, a message of : "invalid file data format. Shows made on older versions of WATCHOUT must first be saved using version 2.3" is shown Also i tried the timecode reader and it seems to work ok so the machine is recieving the timecode... Can anyone help me with that? It appears as if your script's load command is failing.Once a script command fails, it stops executing, so if the fail is occurring on the load command, the script timecode command never executes. BTW kudos for explicitly stating the timecode format (EBU 25 fps) in your timecodeMode command
  21. I am not going to recommend a switch, but beware, the OS you are running may make a difference. Win 7 changed the default NIC settings and some switches will not play well together with Win 7 until you adjust the NIC settings. Symptom is super slow network transfer and what appears to be network loss, reported by watchmaker. This is a common issue independent of WATCHOUT, google "windows 7" "slow network" and you will find lots of info on addressing that issue. Point is, what someone finds works well for them may not work well for you with Win 7 without the proper tuning. It i
  22. There is no cluster control of power. The production computer (watchmaker) talks to each individual WATCHOUT Display (watchpoint) computer to power them down. No big deal with IP like watchmaker does it. So if you wanted to do it through RS-232, at the least, you would need to connect and enable RS-232 to every individual computer. to powerDown an indivual watchpoint computer, connect to that computer, authenticate at Level 2 and send the (case sensitive) command powerDown Another useful individual / level 2 watchpoint command is getMACAddr Retrieves the MAC ad
  23. Hello Rogier, The Move command comes to mind, but I don't think you can simultaneously move displays on different tiers. Display settings are usually set and forget, aren't they? That math is often worked out before media is created. In the rare instances where the stage is re-arranged, it is not that big a deal to duplicate the new settings. I think you are doing it the right way now. For backup or double stacked projectors, the advantage is you have discrete / separate geometry and colorimetry adjustments with unique display objects.
  24. Seems your license key driver may be failing. What version license key (wibu) driver are you using? (the one in the WO 5 installer has shown this issue on some systems, a newer one on wibu's web site cures it.) Next release of WO 5 will have the newer driver in its installer. WATCHOUT will check for the license on a continuous basis. While the response to license removal is not immediate, you only have a minute or two to replace it. v1.0 was the only version that only checked at startup / online. When 1.0 user's reported they could start their backup system, move the
  25. Well kept secret until now I guess. Couple of details. As JJ describes, the -NoLogo command line switch is placed on the display computer shortcut(s). You must do this to every display computer in the group to eliminate all logo screens during update. It is a good idea to rename the shortcut with the -NoLogo switch to indicate the modification. I name mine "watchpoint no logo", but you may use any name you choose. > You will still see the logo screen until a show is loaded. Once a show is loaded, you should not see the logo screen again with that switch in place. Nov 20
×
×
  • Create New...