Jump to content
Dataton Forum


Dataton Partner
  • Content Count

  • Joined

  • Last visited


About RBeddig

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location
    Berlin - Germany

Recent Profile Visitors

977 profile views
  1. Cooling of the media drive could be an issue. When M.2 SSD get hot they throttle down. Also check whether you have turned off everything that is related to throttling down the cpu when the load is low. SpeedStep etc. HAP does not give much load and the computer might feel that it is in idle mode. You can test this by adding a H.264 in the background. This will keep the cpu more busy and the computer will not step down.
  2. I'm not a friend of consumer cards since they are usually outdated within weeks again and if something breaks you'll never be able to get the same graphic card again, but... The speed of the graphic cards is not the main factor for WATCHOUT anyway. Except for HAP codecs, the rendering is done on the CPU and the GPU is not used that much. On the other hand Tweens are handled by the GPU rather than the CPU. So if you mainly plan to play videos as they are you won't need the fastest GPU.
  3. The MP4 (H.264) format does not hold any information on transparency. Transcoding this to another format will not generate the extra byte needed for the transparency.
  4. MP4 (H.264) uses temporal and spatial compression and depending on the settings in the encoder can be compressed quite a lot. The back draw of this is that the CPU needs to buffer a lot of frames - even more if you compress B-frames as well - to recalculate the individual frames in real time. I've seen a 4K video compressed to less than 1 Mbit/s which then played back with 1-2 fps on a quite powerful server as a result. HAP is far less compressed and does not use any temporal compression to my knowledge.This makes it far easier for the server to render those files while the CPU is almost asleep. I'm not aware of any settings in ffmpeg to increase compression.
  5. I don't know whether it works on your OS-X version but I've installed AVF Batch Converter on my OS-X 10.10 and it exports all the formats I usually need including chunks for HAP files.
  6. Am I right assuming that there is no cut between media files at the connection between LED 1, 2 and 3, i.e. the media is not split at this spot? What I would try is to use two outputs from one server and two outputs from the second server on ONE led first. Then you can see whether the outputs are framelocked between two servers. The difference is that all outputs would have the same orientation and resolution in this case. What hits my eye is that the centre led seems to have a different orientation, i.e. the screens here are rotated. Is this the case? This could be one reason for your problems since displays (led screens too) usually have some sort of scan direction.We've seen this often when rotating LCD or plasma displays by 90° where we had the same problem of small offsets. Led screens usually have much higher scan rates but it could still show a problem in fast movements. You could then check whether there is a difference if you use your outputs all in landscape orientation. Since the centre part is higher than 1080 or 1200, you'd need to tile your outputs with two rows of display. Secondly I would not use non-standard resolutions either. We have seen issues with NOVA controllers with source resolutions different from 1080p. Lastly we have been involved i a show recently where we used three outputs on three processors driving one big led wall. The outputs were synced with a S400 card and the AnalogWay Ascender in between us and the led display was also in sync. The led processors had a framelock function which was not set correctly and this led to very visible sync issues between the three processors. Once it was set correctly, the wall looked fine.
  7. Another hint maybe: try with 6.2.2 or 6.3.1 first.
  8. I've seen H.264 files failing before and the reason was an unsupported encoding level. This could be your problem as well. Dataton has only limited options to cure this since it is a problem of the third party decoder used in the program. You can check this with software like MediaInfo or VideoSpec (both OS-X) or similar programs you might find for Windows OS.
  9. The production computer can be any computer capable of running Windows 7 or newer. I personally like using powerful notebooks since they are portable and flexible, can be taken back to the hotel room and have a UPS built in by design. The network can be any 1Gbit network, preferably using unmanaged switches. Managed switches are ok as well if you know how to set them up. If you have a lot of content in HAP or image sequences you'd rather select a desktop or 19" rack mount pc with 10Gbit network cards and a 10Gbit network infrastructure. The display units are the display computers, e.g. WATCHPAX, WATCHMAX or similar builds.
  10. Hmmmm.... start reading the manual from A-Z and all in this forum. Alternatively enroll into a WATCHOUT Certified Training session.
  11. I haven't done it with Nvidea for quite a while but maybe you can check the two pages under "video". If you come across something like 16-255 or the like, this is the place to change it.
  12. Have you checked the settings for the colour range. I remember NVidea cards used to go from 16-255 instead of 0-255. You can change this in the graphic card settings.
  13. This is the behavior if you change it in the preferences. Preference changes are something which works like a preparative preset for your show, not something you change during a presentation. You can though change the conditional layer status from outside through telnet at any time while the show is running, e.g. through a control system (WATCHNET, BLOCKS, Medialon, Universe,...). You could also send strings from a timeline to change the selection while the show is running.
  14. Simple answer, this feature was introduced in WATCHOUT 6. You can't export WATCHNET bundles in WATCHOUT 5.
  15. It very much looks like a network issue and probably it is not WATCHPOINT generating the issue but the underlying Windows OS. I found some hints on SSL on the web which does not make sense here, but you should check whether you only use one NIC on both the production side and the display computer. Are both computers running Windows 10? Have you been able to use the computer(s) with WATCHOUT before? Is the firewall turned off on both ends? We have seen cases with Windows 10 where you'd need to turn the firewall on at first, then connect WATCHOUT (online) and tell the firewall that you want those ports to be open and then turn the firewall off again. It wouldn't work when the firewall was off right from the beginning.
  • Create New...