Jump to content
Dataton Forum


  • Content Count

  • Joined

  • Last visited

About Claude.Rivet

  • Rank

  • Birthday 07/07/1975

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello JFK, In this case it would be 6.3.1 and 6.2, the problem happens with still images or videos. However, we think we found the culprit and will be testing further tomorow to confirm but it looks like it's a license key issue, the hardware dongle itself. Changing it seems to have solve the problems but we barely tested at the end of our troubleshooting day. I will post the confirmation after the tests. Thanks for helping!
  2. Hello guys, We are currently installing a new display computer and are stumbling upon issues and while we are still testing and hunting for solutions I would like to dive in the collective minds for solutions. x299 (MSI raider) i7 8 cores w9100 32GB ram (4channel of 8GB) on board network adapter (1Gbps) Win10 pro (we are trying win10 entreprise LTSB atm) win10 tweak list applied Problems: -1- some medias just do not show up on the display computer, we tried solid and a jpeg. The same media that was not showing can start showing a
  3. Hello, A few things to consider: -Update win7 to the latest service pack (sp3 I think) -If given the choice pick faster clock over number of cores, Watchout uses 2 cores mainly, it is a 32bit app also. Capture cards and external control can lead to more than 2 cores being used but at a fraction of the first 2. Since you work with HAP speed, not concurrent processing, is important, the GPU works, not the CPU. -Update your BIOS, M.2 drives are constantly getting performance boost and stability improvement trough those, they are recent and still being tweaked by BIOS vendors. -If you have
  4. Use virtual displays, you lose the warping, which is a shame, I'd really like to warp the show as a whole rather than by screen but otherwise it would do the trick. Other than that you basically seem to be referring to what Watchout calls task, which are timelines you can start and stop independently of one another, each task can be layered according to the rule it is set to (always above, according to list order...).
  5. Until Watchout supports generative and procedural content and input processing these tracking things will remain tricky to play with, high interactivity does require much work when working with playbacks. Other than that Watchout has no input processing whatsoever, so damping and prediction must be done before the input is sent to whatchout and Watchout doesn't give feedback; positions, orientation, rotation, all manipulated parameters or coordinate must be tracked in the external software as you cannot query Watchout for the infos (as far as I know, would be happy to be wrong). That being
  6. First things first: Select wireframe preview, try Still crashing? First possible culprit is the medias, Watchout can deal with a great variety of format, just not all at the same time, general rules of thumb: -HD = HAP or .m2v (mpeg2 video stream, no audio) or .m4v (mpeg4 video stream, no audio) -Non-Standard resolution under HD = HAP or .m4v -Non-Standard resolution above HD = HAP -Transparency = Hap_Alpha -Images = png -images transparency = png 32bit -audio should be .wav -HAP, each side must be divisible by 4 -.m2v, each side must be divisible by 16 -.m4v, each side must
  7. M.2 drives are actually the way to go in display computers but there are a few things to keep in mind 1- Number of lanes: PCIe bus have 1GB per lane of bandwidth (roughly), it is important that you do your bandwidth calculation before building your computer and it is important you manage those lanes appropriately else you will have less performance from M.2 drives than from a normal SSD. Some slot share their bandwidth with the M.2 slot, if you install your graphic card in slot 1 for example and your M.2 drive in M.2 slot 1 they will compete for bandwidth and dramatically reduce your perfo
  8. Hello guys, I posted the issue on Github and they answered saying it was a Watchout issue and to contact Dataton. So it IS a known issue, and it IS in the hands of Dataton, this is almost good news as it means we will soon see a dramatic increase in playback performance as soon as this is fixed. Thanks for the help looking forward to the fix regards
  9. Still haven't got any reply from Dataton so I guess I won't get to test that. So basically Hap seems to be decoded in the CPU embeded GPU rather than on the AMD W9100 which only reserves the amount of memory needed for the frame buffers (or whatever it is named). If I used two output it goes from 302-304MB to 600ish and at 6 outputs the amount of reserved memory is around 1.8GB, so GPU-Z does report some stuff correctly now maybe some usage is not monitored and my assumptions are wrong but it does look like WO only takes ram on the GPU for it's output and decodes HAP elsewhere. My gues
  10. 50+files simultaneously, introduced one by one with 1second gap between. I will ask support, thank for the tip!
  11. Yes, this is a recipe for disaster, from experience. However, why not use a dual boot system, one for watchout, clean, and one for other stuff. A local clonezilla with two images accessible at boot via an F key is also a solution if the switch from Watchout to other stuff is rare.
  12. Here is the screenshot, long story short HD007 and HD008 are the 55th and 56th files added, usually is starts at around 51st and 52nd. http://imgur.com/a/FZUY4
  13. Is it possible HAP files are decoded with the intel GPU rather than the amd pcie card? It would explain getting identical results from an 8GB and 16GB machine and the GPU-Z reading.
  14. It keeps teasing me with it's cheap 6x outputs, I wouldn't run shows on them but I could see a small system for museum driving 6 output from one cheap computer playing back one HD stream per output (2x HD per output max when crossfading between content), facilitating management and saving space. Would be nice to know what results you guys got with it. Thanks, regards
  15. Good day, I am in the process of building new stations, I will post results and testing procedures when I am done as requested in another thread when I am done. However while testing HAP playback I stumbled upon an issue where my production computer was running out of video memory (as stated in the message panel). At 8GB I was not so surprised as I was playing 50x HD files however when playing those same files on my display computers I got the same message even though I have 16GB of video memory available. My production preview was set to video as thumbnail. Surprised I ran GPU-Z o
  • Create New...