Jump to content
Dataton Forum

jfk

Moderator
  • Content Count

    1,353
  • Joined

  • Last visited

Everything posted by jfk

  1. While those are very valid arguments, the main reason is the DirectX 3D multiple output native Windows function that provides multiple outputs on all gpu types is restricted to a single graphics card / six outputs by Windows.To get multiple output cards / more than six outputs under DirectX 3D, a different multiple output model that is not native to widows is required (eyefinity, mosaic, etc.).
  2. No, if you want version 5 added onto a version 6 only key you will need to send the key to Dataton for a physical swap i.e. version 5 cannot be added electronically. And there will be a minor fee for the administration of this.
  3. Sort of. For dongles purchased prior to June 2019 you can use one dongle for either. But not both at the same time. The WATCHNET dongle must be a WATCHOUT dongle capable of supporting WATCHOUT 5 (use WATCHOUT Production License Manger to check supported versions). There are WATCHOUT dongles that only support v6 and those can not be used for WATCHNET.
  4. x2. Sorry i did not mention that earlier. WATCHOUT Productionoutput of any type is disabled when offline, so as Rainer correctly points out, no DMX output will be sent when offline.
  5. The error simply indicates that a correctly configured audio input is not found. WATCHOUT version effects the answer to this question. Keep in mind that WATCHOUT 6.4+ requires either an ASIO or WASAPI driver for the audio input used for timecode.
  6. There are two ways to do this now. The output you created and how it is used is the key. If you choose to use the setInput command, you must define the output differently for cluster mode or production mode (different port numbers, 3039 for cluster, 3040 for production). Either way, the IP address is 127.0.0.1 (localhost). Then it is simply a matter of wtiting the output string cue as a setInput command. Be sure to end that command with $0D or it will not work. This method has always worked correctly every time i tried it. Another simpler way to do this would be to use DMX for both output and input, set to the same universe and channel number. Last i tried this the DMX input value would change when i changed the corresponding DMX output value, but for some reason the input in the tween did not repond. I believe that has since been corrected however.
  7. Might make more sense to open the WATCHOUT 6.5 installer. Since that version already installed, the installer will now show a repair option. Repair is a less risky method of confirming the installation. And if that does not work, every ShowSage computer has an Acronis archive of its original tuned state on its hidden partition. Restoring that archive removes so many unknowns it is faster than trying to determine what might have been added / adjusted to trigger an issue. Once that is done, uninstall the old version (both WATCHOUT and Codemeter) and then install 6.5 on the media drive. (and if you wanted to be thorough, before doing anything else, create an incremental archive on the hidden partition to restore directly to clean installed 6.5 in the future.)
  8. No No, it will not do that. Simplest way is to completely delete the show on the display computer and then retransfer the show.
  9. Keep in mind that when in standby the non-standby content is still rendered on display, even though you do not see it. So it could well be related to the movie encoding of the movies you are scrubbing. mpeg with B frames is particularly known to cause this issue. Try scrubbing the same movies when not in standby, same issue should occur.
  10. Shot in the dark, but I have seen this happen when user installed VNC is added to the WATCHOUT computer. Uninstalling did not help. The only way to get rid of the issue was to completely restore the original pristine tuned state.
  11. Increasing the start delay to such a large number likely just results in an error and no delay (check the error log on the display computer). Yes, scheduling defray at startup could definitely be the cause. Simple enough to disable it and try again.
  12. When you see the task bar on WATCHOUT Display full screen mode after power up and autostart of Watchpoint 6.5, it likely means that WATCHOUT has loaded before Windows has completed starting up. Increase your start delay to avoid this.
  13. Your manufacturer's utility uses their own proprietary driver. WATCHOUT uses a generic Microsoft Windows Driver Model (WDM) driver the should be supplied by the same manufactuer. So the manufacturer's utility verifies the signal is connected properly, it does not verify the WDM driver is functioning properly. You might want to contact your vendor or check message boards related to that product to determine if there is a known WDM issue.
  14. Then I suspect your EDID management has changed / malfunctioned, as you are now seeing what would be expected if there were no EDID management.
  15. ... and Nigel provided instructions on how to do it from the production computer. The existing method is very flexible. At that point, it is a matter of opinion I guess, as Nigel states "It's really easy to do ..."
  16. The big issue is you indicate it has worked for two years. Clearly something has changed in the hardware or OS configuration. Quite honestly, I am surprised it ever worked as described — running computers 24/7 while turning on and off displays every day. Unless you are running EDID management, just a really bad idea. I would expect loops to stop and other issues when you force a graphics card reset by disrupting the display connection while the show is running. Sounds normal to me. Best practice is to power down display computers first / before powering down displays last. And then power up displays first and power up computers last. Running computers when nothing is being displayed is wasteful of energy and destabilizes the computer. But as you indicated, it worked for two years for you. As such, pretty much leaves you on your own when you have had success with less than best practice. And now you are seeing what we would expect all along, so how does anyone address that? "i ran computer check for the graphic card, cpu, memory, disc"
  17. To remove the default edge blending, best way is to disable blending in each output definition. Display Settings - Advanced - Uncheck Use Default Soft Edges If you have defined custom masks, that would be different.
  18. jfk

    win 10 home

    If you are only using it for editing and don’t mind an occasional crash from Windows background activity, then home is acceptable. That works ok for integrators, etc who run their actual playback in cluster mode (without production). If you choose to run the actual playback live from production, home is not such a good idea.
  19. Bad idea. The removed USB License will take approximately two to five minutes before its absence will force production offline. At that point, the system loses its timing master. (i.e. Dataton provides a grace period if a key is momentarily removed). As Callum correctly suggests, moving the timing master to a display computer by invoking cluster mode will allow playback without production. Just remember, if the show is already loaded by production, you must still send a valid load command from IP. load is the only command that moves the timing master. It establishes the display computer executing the load as the new cluster master. If you do not do this after an online production session, IP cluster commands will not be relayed to the other display computers in the system among other potential anomalies.
  20. In addition to production error window messages, look in the Watchout folder for a logs folder in the computer that actually crashes. In there will be plain text files with event records that may more accurately identify the issue.
  21. If the fan does not rev up to full speed on power up (and then step down), arrange repair with your Premium Partner or go to https://www.dataton.com/rma-application-form
  22. There are two types of NDI streams - NDI (which is essentially uncompressed, for example 1920×1080@30 fps NDI stream ≈ 125 Mbps) and NDI | HX (aka high efficiency - which is h.264 compressed, 1920×1080@30 fps NDI | HX stream is from 8 to 20 Mbps). Sounds like you may be using NDI | HX. Long delays in acquiring an NDI | HX stream are normal due to the compression used in that stream type.
  23. Simple answer is no. There is an undocumented experimental cluster control command that allows interactive adjustment of playback speed. It would require a control system to achieve any useful function. This adjustment effects all playback (i.e. the timeline speed is adjusted, not just an individual piece of media's playback speed). The experimental function is limited to ±20%, which may not be able to achieve what you describe. And keep in mind, this function is cluster mode only, it is not available when watchmaker is online.
  24. This appears to be some kind of hardware issue. We have not seen any other reports of this nature. If you would like to have Dataton evaluate this, please send a simplified sample show file, media and description of how to reproduce the issue to support@dataton.com. We would test it on our hardware to see if it is reproducible. The loop setting solving the issue is very strange. It is exactly the opposite of what we would normally observe. Looping loads a second copy of the media which increases the work load - often movies that play ok standalone begin to stumble when looping is enabled. Again this points to some sort of very unusual hardware anomaly.
×
×
  • Create New...