Jump to content
Dataton Forum

All Activity

This stream auto-updates     

  1. Today
  2. Quim

    Dante Virtual Soundcard

    Hi all, Anyone tried DANTE VSC for more than 8 channels? Thank you
  3. Last week
  4. jfk

    Windows 10 Tweaking Guide

    Thank you for the clarification
  5. In relation to your second issue with showing frames while MSC is jumping around on the timeline, this has been the case for awhile. Regular playback of a show with MSC won't show any problems.
  6. anuj gupta

    Watchmax Drop signal without any error message

    I was using 3 outputs with 1920 x 1080 resolution
  7. RBeddig

    Watchmax Drop signal without any error message

    How many outputs on which resolutions are you using? Have you tried using an EDID minder in between the outputs and the LED processors. Since WATCHOUT does not resort the displays when it goes black and you see no error message it seems that the graphic card still receives a valid EDID and actually tries to send out data. I've seen some problems with standard EDID data sets and Novastar LED processors lately though.
  8. Miro

    Windows 10 Tweaking Guide

    The -TimeOut command was added in 6.3 so it's pretty new. A simple test to determine if you need to use a extended timeout is when WP.exe starts without issues but WATCHPOINT.exe doesn't. WATCHPOINT.exe has a watchdog functionality and starts WP.exe and if WP.exe crashes or hangs (timeout), WATCHPOINT.exe will restart WP.exe. Therefore problems with infinite restarts are occurring if the window creation time is longer than the timeout. Running WP.exe directly isn't really recommended unless you are using any third part watchdog/safeguard application.
  9. Here's a crazy one. So we are taking in Creative Conners automation data via their Watchout plugin. Once I had it calibrated it was great through the entire set up. Our designer was able to program away using a virtual display attached to the automation data, she didn't have to worry about where the set piece was and could just drop content into a second instance of the virtual display - on the same tier. Yes, I know that gives us a recursive warning but we didn't have any troubles with the system until I reboot it last night. When it restarted, the production machine and displays started acting real weird. 1. Midi and manual cues would play fine on the Production machine, however nothing would happen on the display. 2. Go to force update and the displays would jump to the first frame of the video on that cue but not play (production computer still playing fine). We got a tip it was probably a networking issue because we had to use the second network for a different subnet address scheme for the automation data. 1. Exited WO and disabled the automation NIC. 2. Opened WO, enabled midi and UDP control, put system online - tested cues from lighting. Displays played fine. 3. Re-enabled the automation NIC. Automation and cues all working. Ok, so then I thought it was related to the reboot. We did two shows that way, no issues at all. Then tonight, no reboots or anything, on our second show today, right after the precheck - which everything except automation was working, I wanted to check automation tracking, moved the play head manually, Display computers not tracking...! 1. Repeated process to fix it, automation working, midi cues working. Oh man, this is bad. I have found another bug as well that may be rated. On certain cues coming from midi, if we take them out of order or before the previous cue has played out, the production machine acts like normal but the display computers start jumping to each cue and showing one frame of the video, and then does that all the way to the end of the show. On this bug recalling midi cues in the correct order seems to resolve the issue. Oh, btw - We are using show control MSC over mid, not regular midi. Question: Could this be related to the recursive error I'm getting because of having both virtual displays on the same tier? Question: Why is it being so finicky now, when our designer was here programming, she was jumping around the timeline like a frog and we had absolutely NO issues whatsoever, AND we were using TeamViewer to remote in and do all the programming. Any help or ideas would be super useful...! I'm scared now that cues or automation may decide to stop working during a show. Thank you!
  10. Jason Vaughan

    Help with Conditional Tween Expression

    Hi TimFranklin, thanks for replying. Sorry for not following up sooner, with the urgency of my fix, I jumped on the FaceBook forum to look for help as well. I ended up doing it all with math. I've learned that you can find the value for your slope without it and I developed a repeatable technique for calibration and determining the values needed to calculate 'Y'. If anyone runs into this issue please let me know, Id be happy to share it or post it on this forum somewhere. I did post it on Facebook Watchout forum tho.
  11. jfk

    Windows 10 Tweaking Guide

    Could you clarify please - is the -TimeOut command line parameter new to v6.3.1, or does it exist in earlier versions as well?
  12. I am using watchmax 7100 for running multi layer of Led show, sometime my led screen goes black out without any watchout logo on the screen nore any error message on my production computer. I m using novastar Led processor and Display port to Display port for connectivity between watchmax and processor, at the time when led goes blank procssor also shows that the signal is coming no blinking on input button. I want to know where is the problem in server or in cable it happen with me 2 3 time and after i restart the server its come again but after some time this happen again
  13. Dear MisterK, we have NVIDIA P4000 cards running well with 4x4K outputs on our servers. So it should not be a problem with the GPU - nor the WATCHOUT version. The Windows 10 tweak list will be updated with some minor changes in the near future. The reasons for not make a major update are many, but mainly because making and maintaining a fully up-to-date tweak list is incredibly time consuming: Each windows version needs to be tested and tested with a wide range of drivers for various hardware components, such as graphics cards. And it is not only the single Windows version, it is with all the KB updates in variation with different drivers as well. At point of release, the Windows tweak list is accurate, but with different GPUs, Windows versions, KB versions, etc - it is inevitably going to be less accurate. We have built a wide range of WATCHOUT media servers that is pre-tweaked and setup by our developers. They are locked down to avoid having people updating drivers - to make sure the media server performs as well as intended and so we can provide full support on them. Our reasoning to use the LTSB is also to avoid having to force our users to update Windows with new features and not only security updates. I see from our support log that you have received an answer by our support team. I hope it helps - if it does, please let us know so we can post the same here. Good luck! Best regards, David
  14. RBeddig

    4x4k impossible with NVIDIA ? Win 10 tuning ?

    The limitation Luca is referring to is only valid for AMD graphic cards and Windows 7 due to an AMD driver bug. There are quite a few postings on this forum about this issue. NVIDEA should work. The new WATCHPAX 60 series, the WATCHMAX SDI and the WATCHPAX 4 all use NVIDEA graphic cards. The first two run Windows 10, WATCHPAX 4 WIndows 7 embedded.
  15. I doubt you can output 4xUHD with windows 7 and watchout. Am I missing something?
  16. Hi Dataton crew & everyone else i'm having issues with a 4x4k setup with watchout 6.3.1 : setup is [email protected] x 4. i'm on win 10 x64 LTSB 1607, with recommended update KB4057142 ,tweaked with the official guide. mobo is X99 asus, GPU is Nvidia P4000, last drivers. When i play 3x4k output it works fine but when going to 4x4k watchout display is not running good at all, watchpoint exits and idle on the watchout logo, with no IP adress displayed or name. any ideas ? when i go back to 3x4k everything is back to normal. No such troubles on win 7, 3 or 4 4k outputs work fine ! Is the Official guide for win 10 and watchout is complete ? Is there not some kind of secret tweaking missing ? Is Nvidia not good for watchout, and AMD works better ? Do i need to update win 10 (LTSB 1607) with a more recent update than update KB4057142 or must stay with that one ? i know A lot of question though.... i think dataton should update the tweaking guide and be more precise maybe ? For the moment i stay on win 7. Tak !
  17. Has anyone tested if the system performances changes when enabling S400 sync module? It seems to me that HAP playback (so gpu performances) decreases when S400 is enabled.
  18. Earlier
  19. Luca

    LTSB vs LTSC ?

    i'm focusing on hap playback. I am not able to play an 8k 50fps hap file on windows 10 while on windows 7 it works perfectly. also tried several 5000~6000 x 1000 pixels 50fps hap files and again it works on windows 7 but not on windows 10. bios tweaked like this: and windows 10 ltsc tweaked accordingly to the dataton document (ltsb 1607 was not working)
  20. jfk

    LTSB vs LTSC ?

    Yes, Dataton has. Depends on what you are trying to accomplish. Performance with Windows 10 will be the same as Windows 7 in most cases and better in some cases (mostly capture card performance differences).
  21. Luca

    LTSB vs LTSC ?

    If Dataton was able to properly "tweak" windows 10 on their media servers, I think it could be done on user built servers too. Giving the users the opportunity to build their own servers has always been a great plus for dataton and I hope they will never change this approach. Adding features to their servers (such as SDI IO feature) is a thing, but I hope they will never drop users built hardware support. Now the thing is, a properly tweaked windows 10 server will have same, better or worst performances compared to the same system running on windows 7? Has anyone made a test? And if win 10 can achieve the same/better results, how do u tweaked it? Hardware differencies should not be so important since many many users are using firepro 7100 or radeon pro wx7100 (and dataton servers too) and hap playback depends mostly on GPU
  22. RBeddig

    LTSB vs LTSC ?

    Yes, tweaking Windows 10 can be quite a task and it takes a long time to get the system stable and fast. WATCHMAX and WATCHPAX servers are more expensive than a self-built system but the price includes a warranty for a stable system which took months to set it up and for tests.
  23. RBeddig

    Media files not transferring to Display PC

    Well, usually a warning would pop up in Windows 7 as well but maybe it was sort of half-way registered in the OS. Normally it would also work with an activated firewall but WATCHOUT uses more ports, some of them being dynamically selected by Windows. BTW, we have seen the firewall of Win 10 blocking WATCHOUT although it was turned off. Here, we needed to turn it on, accept the rules for WATCHOUT and then turn it off again.
  24. Sydney

    Media files not transferring to Display PC

    Many thanks for your reply. Yes, I had tried and checked the things that you mention. The WMV file was just for testing purposes, not a final show file. After a long process of trial and error I found a solution with thanks to WO version 5 after I rolled back my software on the Production and Display PC. Going online with version 5, Windows flashes up a warning message about Watchout being blocked by the Firewall on the Production PC. Clicking accept allows the media file transfer to proceed. The transfer was being blocked even though Watchout was already on the list of apps allowed through the Production PC Firewall. It seems that switching off the Windows Firewall completely on the Production PC is the only way to allow media file transfer. WO version 6 doesn't seem to prompt the same warning response from Windows and your left scratching your head. Especially as Watchout reports ''Network Error; Display Computer: No Response'.
  25. Luca

    LTSB vs LTSC ?

    my setup: ASRock X99 Extreme4 S2011v3 Intel i7-5930K 32GB DDR4 2133MHz Samsung 850 PRO 1TB (windows) + Samsung XP941 NGFF 512GB (watchout) Sapphire AMD FirePro W7100 tried windows 10 enterprise ltsb 1607 with amd driver 17q4.1. Did all the tweaking list (excluding the removal of microsoft bloatware which are not present in ltsb) results: black screen. tried windows 10 enterprise ltsc 2019 (tweaked) with amd driver 19q1.1 and 18q4: watchout works properly but poor HAP decoding (video stutters while the same video on windows 7 works well). LTSC 2019 with amd 17q4.1 doesn't work (watchout window opens, then turns black, than opens again and the system is instable) I still haven't found a working solution for windows 10 and I need a system that can support 4xUHD output
  26. RBeddig

    LTSB vs LTSC ?

    LTSB 2016 is the 1607 version of Windows 10. The tweaking document is based on this version!
  27. RBeddig

    Media files not transferring to Display PC

    Are you sure that you only use ONE active NIC (network port) on the production computer, all others DISABLED? Have you tried swapping the switch or using a direct cable between both computers to rule out problems on the switch? Have you tried other media codecs? While it usually works, WMV is not officially supported. See: https://www.dataton.com/watchout-overview-supported-media-images-sound-and-video
  28. piccinaezio

    Windows 10, 10Core, W9100 issues

    No, I installed windows 10 Enterprise Full, not LTSB
  1. Load more activity
×