Jump to content

jfk

Moderator
 View Profile  See their activity

  • Posts

    1,810

  • Joined

  • Last visited

 Content Type 

Everything posted by jfk

  1. jfk
    When you define the Live Video media object, there is a choice for the input device number set on your display computer in the Basic tab AND and under the Advanced tab a choice for Signal Input. It defaults to 1. Signal input should allow you to select the other input. https://www.dataton.com/watchout-users-guide/commands/media-menu#add-live-video
  2. jfk
    Are not these windows resizable? Or are you requesting variable magnification?
  3. jfk
    To be clear, I do not suspect any network issues. Identify the watchpoint station that is crashing in your current scenario and substitute the WATCHPAX in that position. Change nothing else. The idea is to attempt to duplicate the crashing on the substituted WATCHPAX in the same manner as you are currently observing.
  4. jfk
    Agreed. You can try. My experience has been that uninstalling does not always clear all remnants. Hopefully you archived your tuned Windows install prior to adding VNC. If not, you may consider starting the tuning process from scratch and archiving accordingly Yes. That is the only place you may find clues to why watchpoint is failing. highly unlikely Something is taking watchpoint down. So many potential reasons. Things as basic as the OS indexing a drive in the background, checking for updates in the background, etc. A good way to determine if it is OS tuning or media would be to attempt to duplicate on a WATCHPAX.
  5. jfk
    First, i dispute your dismissal of VNC. I will bet no other product you have run uses the archaic DirectX 3D multi-output rendering method used by WATCHOUT. Vnc and rendering are interrelated. Furthermore, WATCHOUT uses DirectX 9, which almost no one else still uses. Any observations with other product likely mean nothing as it relates to WATCHOUT. Just the same, it is probably something else. My best guess is you are seeing watchpoint crashes with watchdog reset. The most common cause of watchpoint crash is incorrectly encoded mpeg (AVC / mpeg 4 / h.264). unless you are expert at codec settings minutiae, avoid mpeg (AVC / mpeg 4 / h.264). If settings are wrong, mpeg movies will play, but become time bombs, eventually crashing the system. Default encoder settings for mpeg will be the wrong settings. 'Best' encoder settings for mpeg will be wrong (and best is a misnomer, multiple choices can provide the same quality depending on other settings).
  6. jfk
    Not sure where to start. Best accomplished in cluster mode (ie turn off production and control display). In its simplest form, the IP command to play is run and the rewind is gotoTime 0 or possibly reset details … https://www.dataton.com/watchout-users-guide/appendix/c-control-protocol/controlling-the-display-software
  7. jfk
    Yes, that is true. i went there first too. Then i discovered the timecodeMode command is not available in watchmaker.
  8. jfk
    From watchmaker - no. Yes, in cluster mode. As watchmaker was never intended as a show controller, it lacks many show control features that are available in cluster mode. watchmaker is a composition assembly / editing tool.
  9. jfk
    Please visit the link provided above. Instructions on how to enable NoLogo are there. If you need information on how to prepare command line option, it is in the WATCHOUT User Guide on the previous page (accessed from the link at the bottom … ← D. Command Line Options) That is simply incorrect. Possibly you have an old shortcut with the modification already in place or whatever. Please consult your Dataton partner for further assistance.
  10. jfk
    It is normal for the logo screen to appear during update. If it was not appearing in an older version, then someone enabled the optional command line instruction -NoLogo. When you updated versions, you lost the optional switch. reference: https://www.dataton.com/watchout-users-guide/appendix/d-command-line-options/display-software
  11. jfk
    Seems an example of “your milage may vary”. I am not sure what you have experienced but that is not always the case. I have a fair amount of experience migrating shows from old versions, including moving shows from v4 to v6 and shows from v5 to v6. While i have observed issues with audio cues - video, stills and tween animation have been trouble free. In almost every case the migration included display upgrades that increased display resolution at the same time. To accomodate increased resolution i would move the original content to a different stage area where virtual displays at the original resolution were added. Then the virtual displays were scaled to the higher resolution new displays. That technique maintains original programming while providing access to the new resolution for new content.
  12. jfk
    Nine times out of ten, the network error message you observe is NOT a network issue. The significant part of that message is “… Connection lost…”. While a network error is one possible explanation for a lost connection, far more common is the WATCHOUT Display software (watchpoint) has crashed and stopped communicating, resulting in connection lost. So, when you see this message, observe what is occurring in WATCHOUT Display (watchpoint) to determine the more likely cause. If watchpoint is displaying its logo screen, that most likely means it has crashed and the monitoring part of watchpoint (aka watchdog) has restarted the watchpoint software. If you determine watchpoint has crashed / restarted, forget production and its meaningless message and focus on watchpoint and the possible causes for its crash.
  13. jfk
    You asked for info on WATCHPAX. WATCHMAX are not available in the North American market so i do not track them.
  14. jfk
    This is not an official Dataton web page, it is one i maintain personally for that purpose. http://www.dataton.net/watchpax/watchpax-image-wo_ver.pdf
  15. jfk
    WATCHOUT 6.7.2 is in public release: Dataton WATCHOUT current version
  16. jfk
    Check the watchpoint audio output menu to confirm the audio is correctly assigned to the 2i2. Switching from v5 to v6 may break audio cues, they may lose their assignment to a server. It is best to update all audio cues from the old ‘assign by an icon on the stage’ to the newer ‘assign by server name’. I also encountered a v5 system that when updated would not play some of its wav files (that worked in 5). Opening them in an audio editor and resaving them cleaned that up.
  17. jfk
    Very possibly yes. Won’t hurt to try . Given a choice, i would pick ASIO.
  18. jfk
    The audio driver should come from the entity providing the audio hardware. In the case of motherboard audio, then the motherboard vendor. If this is not possible, i believe there maybe generic WASAPI drivers that may do the trick. Hopefully someone can assist with a source for that.
  19. jfk
    WATCHOUT prior to v6.2 uses DirectX WDM for audio. WATCHOUT 6.2+ changes to ASIO or WASAPI for audio. Most likely you will need to find a different / appropriate ASIO or WASAPI driver for audio to function properly.
  20. jfk
    fyi This is now a known issue with some variants of Window 7. WATCHOUT 6.7.2 will correct this issue.
  21. jfk
    It is pretty tough to beat the Notebook offered by Show*Sage. They have optimized so many details, for example, the keyboard has a separate number pad to take full advantage of WATCHOUT shortcuts. And more. https://www.showsage.com/beta/docs/workstation_guide.pdf More important, they have performed the tuning and critical confirmation testing. And should anything go awry, they support the notebook / WATCHOUT combination. Put a price on that I am sure the AMD processors will work fine. The few users who have gone that route have not reported any issues. On the other hand, that is a small sample size. The overwhelming majority of WATCHOUT server cpu s in the field are Intel based.
  22. jfk
    Society of Motion Picture and Televison Engineers — SMPTE
  23. jfk
    The servers rely on UDP timing data from the master to maintain synchronisation with each other. Possibly something is disrupting those transmissions?
  24. jfk
    OK, that indicates a valid network cable / hardware / electrical connection Powered off, may indicate ready for Wake-On-LAN. It does not tell you if or when the OS driver is loaded and initialized.
  25. jfk
    Correct. And this is a situation where the duration may exceed the clip length as it will keep lopping for any duration. I was answering that one when this post appeared .
×
×
  • Create New...