Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited


About jfk

  • Rank

Contact Methods

  • AIM
  • Skype

Profile Information

  • Gender
  • Location
    - Boca Raton, FL USA

Recent Profile Visitors

1,410 profile views
  1. jfk

    Videos not playing properly

    This is an error in configuring your production computer. ]The display computer is NOT playing at all, video or otherwise. Multiple network ports are active and the UDP traffic is going out the wrong port (transport commands are UDP, file transfer etc are TCP, so the TCP activities get through regardless. Either turn off all network ports except the WATCHOUT port or re-order the network ports properly. This has been covered in the forum multiple times before, next time search first.
  2. Good question. Ultimately the limitation is the display machine, but no, the production machine is not checking with the displays when it accepts the movie. In fact, the production machine may have lower limits than the display machine, and it might choke on the a HAP file the display machines could play. If this occurs, you would have to use a movie proxy to get around that. One option with a proxy is to tell the production machine not to try and play the movie and not to open it in any way, instead, you have to tell production the resolution and duration and production will present a generic icon for the movie in the stage and then pass the movie file to display for it to deal with.
  3. If a customer is encountering a maximum HAP resolution, it is most likely a GPU limitation. i.e. the GPU has buffers that probably max out at 8K. 8K is not a limitation imposed by WATCHOUT, and there are customers who have successfully encoded HAP videos where the width has significantly exceeded 8K, but I can not recall the GPU they were using. With HAP encoding and assuming the GPU buffer can handle the final size, it is best to split them up into Display server sized movies. If all of your movies will play out from multiple outputs on a single server, then I see no need to pre-split HAP movies. Although keep in mind the HAP 'chunks' encoding setting is important to success with movies larger than HD60p.
  4. Hi David. Did you update the AMD driver? The symptom you describe is known with the latest AMD drivers. i.e. There are issues with 2018 drivers from AMD where the driver would cause a blue screen when starting windows. The driver from 2017 Q4.1 should correct this
  5. jfk

    WATCHPOINT exit code meanings

    That is not a watchpoint exit code, it is a Windows error code. see: Error messages
  6. You build a display computer, it is solely your responsibility. Seriously, all you are going to receive in response is an educated guess with nothing to back it up. i.e. if someone says yes it will work and it doesn't, it is still your issue. The only wise method is to build it, test it, and confirm it will work with your content. Otherwise, work with a Premium Partner to arrange a demonstration of one of the Dataton built and warranted servers.
  7. jfk

    I have some errors.

    Ok, but all of your errors are from the Display Computer, not your Production computer. So your MacBook production computer running windows under Parallels is not the concern. Since the errors are indication the Display Computer may have crashed, have you checked the error logs on your Display Computer?
  8. jfk

    Akai LPD8 Midi Controller Issue

    Please be specific, which commands are you seeing in MIDI-OX? WATCHOUT Version?
  9. jfk

    Akai LPD8 Midi Controller Issue

    First off, if MIDI-OX is open, it owns the port and depending on WATCHOUT version, WATCHOUT can not access it.
  10. jfk

    I have some errors.

    the only error of interest is the first one. The others may be a result of the first. All of those errors are from the display computer. Is your "Watchout in Parallels Desktop of MacBook Pro" the display computer or the production computer? also - WATCHOUT Version? Windows Version?
  11. With progressive input signals - neither. Progressive signal capture latency is primarily a function of the capture card and its driver. CPU does come into play when de-interlacing captured interlaced signals. But I am pretty sure that is a go/no go situation rather than a latency concern. WATCHOUT does add latency in the process of rendering the complete image, but again CPU and GPU are pretty much in a go/no go situation as it relates to processing power. Rendering latency time will not vary with CPU/GPU power/speed. Instead, they will fail to keep up and start dropping frames once the processing power thresholds are exceeded.
  12. Doubt there is any single LED wall processor that can accept that resolution ;). So you will obviously break it up for the number of processors it will require. Once that is determined, motion content should be pre-split into Display server sized chunks. Stills can be left as big as you want/ need.
  13. jfk

    Windows 10 pro in both

    No. You may even mix Windows 7 and Windows 10 computers in a WATCHOUT system. No. Windows 10 Enterprise with specific tuning is recommended for WATCHOUT Display, tuned Windows 10 Enterprise LTSB is even better. Other variants of Windows 10 are not supported and may exhibit instability that you are on your own to deal with.
  14. Seems the attached files are damaged in the upload. So it is not possible to determine the codec you are using in the 09_360-MAIN.mov file. Keep in mind your production computer has Quicktime and WATCHPAX do not offer Quicktime, that may explain the issues with 09_360-MAIN.mov. WATCHOUT does support h.264 with no audio and ProRes (WATCHOUT 6 only) without Quicktime, but many Quicktime codecs are not supported on WATCHPAX. WATCHOUT supports HAP, HAP Q and HAP Alpha, but does not support HAP Q Alpha, so that may explain the issue with 17_410-MAIN_HAPQA_AE.mov
  15. jfk

    Control Watchpax over IP from E2

    WATCHPAX is no different than any other WATCHOUT Display server as it relates to IP control. Prior to triggering auxiliary timelines you must perform some basic preparation as outlined in the user guide. So before you can trigger the aux timelines you must connect to port 3039, send authenticate 1, and load the show. Loading the show from production and then switching to direct control will result in unexpected behavuor, you must load the show from either IP or a startup script. If the show is already loaded from Production, you must still send the load command from IP to reconfigure the WATCHPAX for direct IP control. Once that is done, as long as the connection is maintained, all you need to send is: run "Timeline Name"