Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

Posts posted by jfk

  1. WATCHOUT installs codecs to playback .mp4. There should be no need to convert them to .mov container. In fact, for WATCHOUT, .mp4 container is preferred over .mov.

    On the other hand, your phone may encode the video for smallest file size which may include bi-directional frames. B-frames are not recommended for WATCHOUT, B-frames have been known to cause instability with prolonged playback. So you may wish to re-encode them as an .mp4 without B-frames and without audio for best results.

  2. 23 hours ago, Balage said:

    wich port used watchpax for upgrade? 

    Dynamically assigned. Ports used will be greater than 1024, but that is all that is predictable.

    23 hours ago, Balage said:

    … I dont know firewall issue, first i used for upgrade tplink router with default config. (i dont see the router defaults.....all devices mobile device) Setip not configured on watchpax, all setting default on devices. I will try tomorrow this repair instructions.

    The firewall of concern would be on your production computer.

    23 hours ago, Balage said:

    … I wanna understanding wibu protection system ( maybe this is a problem) …

    No, this is not the problem. As I said originally, “Licence key not found” during a propagated version change is normal and unrelated to the failure you are experiencing. Nothing has killed your WATCHPAX license. Please move on from the licensing and focus on the real problem.

    23 hours ago, Balage said:

    … I readed this forum and i got this post (maybe this is the problem? how can i find out?😞


    That strictly had to do with an old outdated power up initialization issue and is unrelated to the version change process.

  3. The “License key not found” message is normal when propagating a new version to WATCHPAX. At some point during the process, both the old and new version are loaded. The new version will be denied the key until the old version releases it. In your case, at some point, the new version fails to respond to production. Possible Firewall issue?

    When upgrading from some older versions, an autostart script setIP command causes issues as the new version fails to process the script comand and reverts to DHCP, triggering the unreachable message. Temporarily revert production and WATCHPAX to DHCP to complete the update.


  4. 4 hours ago, MauFir said:

    Hi Everybody,

    any news about the servers using GPU Nvidia Geforce 2 and 3 series?

    I heard that Dataton is releasing a new patch for Nvidia GPU.

    In my win 10 servers (WO 6.6.5) I'm using the RTX 2060 with the old driver (460.89), they work but sometimes I've problems, like a disconnection of 2 of the 4 video outputs.


    Yes, the issue is corrected in the most recent release …


  5. 21 hours ago, Wakanda said:

    im having the same problem here, im using a desktop for production laptop and watchpax 60. Can anyone help please.

    please see log below

    Faulting application name: WATCHMAKER.exe, version:, time stamp: 0x61764850
    Faulting module name: rthdasio.dll, version:, time stamp: 0x5fcdd502
    Exception code: 0xc00000fd
    Fault offset: 0x000193be
    Faulting process id: 0xff0
    Faulting application start time: 0x01d7cf244c98a01d
    Faulting application path: C:\WATCHOUT 6\WATCHMAKER.exe
    Faulting module path: c:\windows\System32\rthdasio.dll
    Report Id: 4cdf5959-d32a-47c6-b1b2-79069a95db8b
    Faulting package full name: 
    Faulting package-relative application ID:

    Again, the WATCHPAX 60 has nothing to do with the error shown. The error shown is a WATCHOUT Production error related to the motherboard audio coprocessor and its software. So the above suggestions all apply.

  6. Sound from a video file is not recommended and is a known possible cause of a crash. The sound should be exported as a .wav file and the video re-encoded without sound.

    You can still play sound from the WATCHPAX 60 and turn off sound playback on your production computer.

  7. The error has nothing to do with WATCHPAX 60, the error is a production computer error. As Rainer points out, the error appears to be an issue with the production computer sound co-processor. Do you even need audio playback from the production computer? Possibly turning it off in production is a simple solution.

  8. 14 minutes ago, Timvideo said:

    Hi all, 

    Ive been trying to understand how to close a 360° projection inside a cilinder ? 
    I can overlap my displays in the stage window, edge blend them, but what should i do with the last (most left and msot right) edge ? 
    How can i blend these ends if i don't want a hard seam ? 

    Thanks ! 

    Create an additional display on each end to force the blends at each end. For these phantom displays,

    uncheck. Enabled:  Use this display

    that will tell watchout not to attempt to connect to the phantom display. WATCHOUT will still apply the blend for the display, whether it is enabled or not.

  9. 10 hours ago, roger said:

    Thank you for your answers, in the installation the watchout works without a controller. I need to update an image stored in a shared fold...

    not sure what is going wrong with this forum system, the above was sent to me as a post moderation notification, but did not appear in the thread. And the notice is truncated so this is just the beginning of the original post submission. Anyway …

    It does not quite work that way. 

    The lowest cost way to replace a still without using WATCHOUT Production or WATCHNET to prepare the image would be to use the URL function and store the images to be replaced at a URL via a web server instead of a shared folder. Then a simple aux timeline could be used to refresh the image that appears in WATCHOUT Display via a run timeline command.

    Alternately WATCHOUT Dynamic Image Server can provide the function using a shared folder, no commands are needed to update the image, it will automatically update as soon as a file is replaced. Only downside would be the requirement for another standard WATCHOUT license to enable the WATCHOUT Dynamic Image Server software.

  10. On 10/13/2021 at 9:13 AM, John G said:

    Hi all

    I'm still looking for these items:

    I'm looking for two trax ektapro adapters 3475-1. 

    This might help ... TN 3475 Ektapro Smartlink home build


    Also a Tascam cable 3483

    Never diagramed that one.

    If you want to use the correct connector for the SMARTPAX side, I believe they are still available. However, all my research was done when that connector was provided  by AMP. AMP has since been sold, so the old AMP part numbers I have will be superseded by the new owner's part numbers. But here are the AMP part numbers to start from.

      Dataton SMARTPAX® female device connector -three parts, — receptacle, — pins for receptacle, and — outer squeeze to release (STR) shell

      AMP STR Female Cord Guard 745002-1, 745002-2 (part numbers for two different cable diameters for the cable strain relief )

      AMP STR Receptacle housing 9 pin 207752-3

      AMP pins for female 66504-9

    There is a bit of a gotcha in the above. The pins require a precise tool for close to perfect crimping or they will never insert correctly into the receptacle. Even when crimping with the proper tool (AMP Pro Crimp PN 58448-2) if you do not get it just right, it will not insert correctly. binned a few for that reason ;)


  11. On 9/27/2021 at 5:13 PM, yashin said:


    Its new watchmax9100 server I recently purchased and using first time. Network, license everything working fine but cant find the input devices/ or the output display channels from the display server in the production laptop

    That is correct, the hardware is in the WATCHMAX so it will not show up in the production computer input hardware settings. The only input devices that will show up in the production computer are input hardware that is physically in the production computer, and this is exactly what you are seeing.

    When programming, you program the display server input behavior by defining a Live Video object from the Media menu and associating it referencing the WATCHOUT input number defined in the WATCHMAX. Be sure to leave preview set to thumbnail. You only set it to live video when there is capture hardware in the production computer and you are feeding the signal to that capture hardware in the production computer.

    On 9/27/2021 at 5:13 PM, yashin said:

    In the display server if press Ctrl+W, we can see all the six outputs display ports as wells all the capture card ports.


    On 9/27/2021 at 5:13 PM, yashin said:

    I can program and play video to one display and the output is fine but if I added 2 or more displays I cant select the specified output on the graphics card. or giving an error invalid channel.

    OK, this seems separate from your input issues and is less clear. Can you provide screen shots of the display configuration that is working and the ones not working?

    On 9/27/2021 at 5:13 PM, yashin said:

    In preferences I cant find any of my capturecard inputs other than my webcam of my production laptop.

    As expected. Your capture card inputs are not in your production computer and therefore will not show up in your production computer.

  12. On 10/1/2021 at 12:59 PM, artboy said:

    DATATON says there is no way until NVIDIA solves it. They just tell us to wait.

    Who at Dataton said that? Dataton is aware of issues with color conversion with new nVidia gpus, they are in the process of making changes to address this, it is in beta test now, and should be available in the near future.

  13. No, anytime you transfer content the show will pause.

    The solution is to bring in content that does not arrive until after a show has started in another way. i.e. you must still prepare for it in advance. Using live tweens and live video input you could bring in content from another source and scale and position it using live tweens …

    Give your client a choice, provide all content by a reasonable deadline and then provide him the extra cost for content arriving after said deadline. 

  14. Sounds normal.

    The timeline is calibrated in clock / stopwatch time, not timecode time. With NTSC 29.97, drop or non-drop, the timecode time will NOT match clock / stopwatch time - that inaccuracy is inherent to NTSC timecode.

    If you want to see timeline position in NTSC timecode format, add a status timeline position display, double click on the time readout, and change the display to the matching timecode type.

  • Create New...