Jump to content

jfk

Moderator
  • Posts

    1,802
  • Joined

  • Last visited

Everything posted by jfk

  1. jfk

    DMX USB Pro

    WATCHOUT supports ArtNet. For DMX, you will need to convert ArtNet to DMX. WATCHOUT does not support direct DMX interfaces.
  2. The protection circuit in a WATCHPAX contains a restricted non-transferable license. The price of the WATCHPAX reflects the restriction. ie literally no value is placed on the license in order to keep the hardware cost as low as is feasible. If the license is in fact corrupt, arrange to send it in for repair. That is an extreme rare failure, it should be repairable.
  3. You have not specified the WATCHPAX model or the WATCHOUT version you are using. This thread would have been a lot shorter if you had included that basic information. 3360 WATCHPAX and 3362 WATCHPAX 2 are the only WATCHPAX units capable of running v5. Neither of these units as delivered is compatible with v6.6.7+. If you install those most recent versions you will encounter “License key not found”. This is noted in the WATCHOUT release notes. Dataton will update the firmware on a WATCHPAX or WATCHPAX 2 to be compatible with v6.6.7+ at no charge. But you must return the unit to Dataton or a premium partner for the update. If you want an official statement from Dataton, please use the support channel. The public user forum is just that.
  4. SDI is an option when configuring 2D display. reference: https://www.dataton.com/watchout-users-guide/displays-and-projectors/2d-display-projector As for input, you configure WATCHPAC 60C inputs the same as any other input, in watchpoint’s video in menu. Note, if you define a WATCHPAX 60C SDI channel as both an input and an output, output takes precedence.
  5. jfk

    Mr

    Windows includes technology currently used by WATCHOUT, most notably Microsoft DirectX, including graphics card hardware acceleration of DirectX 3D. Even Windows in a virtual machine significantly suffers from the emulation layer in virtual environments.
  6. The manufacturer warranty period for 3150 Dataton WATCHOUT License (USB key) is for 2 years. Warranty does not cover physical or electrical damage.
  7. Partially true. You are correct, as long as you return the defective key, you do not have to pay the fee for the WATCHOUT software. However, all licensed components included in WATCHOUT (mpeg decoder, AC3 decoder, etc) are charged by the physical key, those licensing fees are not transferable from one key to another. Dataton must pay those fees. Even Wibu, the hardware vendor for the key, adds licensing fees for their software protection system. So the cost is more than the simple hardware cost - there are licensing fees that must be paid by Dataton on every key Dataton enables for WATCHOUT. To the best of my knowledge, the current fee charged by Dataton for a damaged key swap is below cost. i.e. Dataton underwrites damaged key replacement.
  8. I would not be so sure. Over the years have observed some pretty strange behavior related to a second VNC install. Such as disc full errors when there are terabytes of free space. ie behavior you would not relate to VNC. And simply uninstalling VNC did not fix it, had to restore the original tuned image from before the VNC install. You may be right, it may be unrelated. But it is an issue that has caused unexpected anomalous behavior in the past. Also, I would try 16 chunks for the 8k 60p clips (if that is possible).
  9. Interesting issue. WATCHOUT version? How many chunks in the HAP movies? Have you tried cluster mode? Installing another copy of VNC on any WATCHOUT machine invalidates any results. Why not just invoke the VNC already installed by WATCHOUT?
  10. Fyi for conditional layer control novices You can also set default conditions that automatically enable when no conditions are specified. This is useful for defining a default language for example, so the show is less likely to run without audio. Those default conditions will re-enable for the 0 condition arguement. i.e. layer condition 0 is NOT all off, it is return to default. Default is defined in File - Preferences - Conditions. Anything enabled in this tab when the show is saved becomes the default when the show is opened. However, if you define non-zero conditions at load, or send a non-zero enableLayerCond command after load, either will override the defaults.
  11. Layer condition is an optional argument to the load command. Integer value following the show name to load. For exactly the purpose you request. https://www.dataton.com/watchout-users-guide/appendix/c-control-protocol/list-of-commands
  12. yes, it is best to leave the movie in the comp as normal, trim and LOCK the comp duration to the end of the movie cue, and then free run and loop the composition.
  13. Sounds like you are also using Live Update. The error message typically means WATCHOUT Display has crashed. Since the only thing that has changed is the new .mp4 file, that is what i would suspect is the cause. For the purpose of diagnosis, first, simplify things. Turn off Live Update and stay offline. Drag the suspect .mp4 into the media window. If that works, put the movie as a cue in an empty aux timeline. play the movie in production preview. If that still works, try to go online with Live Update disabled. Then play the movie on display. If all that works, then we will look at things other than the media.
  14. https://www.dataton.com/watchout-overview-tracking-and-rttrpm
  15. When operating without a production server (aka from a control perspective - cluster mode), load “show name” defines the control cluster members and defines the control cluster master. The control cluster definition consists of the loaded show file’s stage window. i.e. Any valid display server definition (Display - Specification) in the stage window is a member of the control cluster. The WATCHOUT computer address parameters (name - cluster name) are something different from a control cluster. watchpoint will accept new load commands from a valid IP connection or script at any time from any connection, the most recent takes precedence. The load command should only be sent to one member of the control cluster. Since every member of a group contains a copy of the show file, any member can be the master. If you want to change the master and/or change the group, simply execute a load of a show containing the desired new parameters.
  16. That is not a requirement. Cluster is an optional patameter. If you do change this parameter in the WATCHOUT Network window, you must then update the show from production without errors before the load command will function correctly. Of course, you must add the new cluster name in File - Preferences - General - Cluster to successfully update the show. No. The WATCHOUT Display computer that successfully executes a ‘load’ command is the cluster master. Single computer clusters are the most common type and of course they work under IP control. The cluster master still functions as a normal display computer. Not really, have not observed load commands abort.
  17. Yes. As long as all are same refresh rate, no problem. No No it is possible. This was an improvement during the WATCHOUT 6 run. Can not recall which 6 version added this, but it has been a while now.
  18. To play an auxiliary timeline, you must add the timeline name to the run command. Note, the timeline name must be an exact match, case sensitive. i.e. run “Timeline 1”
  19. Trigger via IP. Trigger via MIDI. Trigger via ArtNet. Timecode chase. But no keyboard triggering.
  20. You did not indicate your WATCHOUT version. From WATCHOUT 6.6.7 Release Notes: An issue with newer NVIDIA drivers (version 461.x and later) affecting conversion to NV12 color space has been fixed.
  21. Sort of, yes. It is not as straight forward as a command to backload the show. But there is a way to access the files you need. While the media files will all be intact, the .watch file must be recovered. To access the files: At the end of the instructions above is a link describing the process of recovering the .watch file.
  22. And to answer your question, autostart.txt is valid for watchpoint / WATCHOUT Display only.
  23. As many of you know, I would go to great lengths to avoid using watchmaker / WATCHOUT Production in daily operation. Running in an editing mode when it is not needed is unnecessary risk IMO. I would consider running in cluster mode. Instead of running production software, use that pc and license to run watchpoint / WATCHOUT Display. Logical choice for cluster master is this former production, now audio server. Only challenge then is performing the production -> display transfer on the same PC. A second license for that PC would be needed temporarily to pull that off.
  24. Options are same as always. You may freeze on currently displayed content instead of logo screen / progress bar using the -NoLogo command line switch. Or you may transition to static user defined content by using the standby function.
  25. that should return an error. There is a specific command to unload the current show. unload with no arguments. This command requires authenticate 2 and only affects the one computer it is sent too.
×
×
  • Create New...