Jump to content

RBeddig

Dataton Partner
  • Posts

    610
  • Joined

  • Last visited

Everything posted by RBeddig

  1. In your other post you talk about a new Mac to encode and program WATCHOUT!? Are you using Bootcamp or a virtual machine? AFAIK, Bootcamp is not supported on M1/M2 Macs anymore and virtual machines can introduce a lot of issues, depending on the driver implementation of the virtual environment. Or are you having the issues on a true Windows computer? In this case, which Windows version? I've used Windows 10 and 11 on PC notebooks but also on a 2019 Intel Macbook. No issues with HAP files. As you're already using Jokoy encoder software, have you checked what the Jokyo HAP player says about your different HAP files? It's a good and free toll to get some information on the encoding settings.
  2. Sounds a bit like an user rights (UAC) issue or something similar.
  3. In respect to the upcoming WATCHOUT update, I would rather switch to NVidea RTX A5000 or faster cards. WATCHOUT 7 will make way more use of a fast graphic card.
  4. I doubt that the 2017Q4 driver supports the W6800 card. We used it on two occasions where frame-lock was not important and with a newer driver. I don't remember which one🤔 The main difference is that the W6800 doesn't support the S400 sync board and I'm not sure whether the 6 outputs on this model are frame-locked to each other. This was not the case on the WXxxxx cards. Genlock and cross-server sync doesn't work with the W6800.
  5. A dongle which is not readable could be an issue but normally throws error messages. Check the log files on both display and production computer as well as the Windows event messages. I always try to avoid non-SMPTE resolutions. This can lead to all sorts of issues and maybe this was the problem here as well. Always use the next larger SMPTE resolution, here probably UHD and make the LED controller just pick the right pixels.
  6. OK, most versions after 17Q4 will show bad HAP playback. Send me a private message and I send you a link to 17Q4.
  7. I'm not a big fan of using 6 channel graphic cards and you have to keep an eye on the bottle necks in the system. W6800 works but has no framelock on the outputs and can not be locked to genlock or be synced to other servers. For softedge projection it is fine, for large LED walls it's bad. I've not looked at all of the components but noticed that the SSD e.g. is PCIe 3.0. Standard today is PCIe 4.0 and it's faster. For semi-professional use the components might work. For a real workhorse for large shows, I would only use workstation grade mainboards and components and rather a NVidea RTX A5000 or better than a W6800. Also I would never buy a blackmagic capture card. They are rather cheap but will also make sure that you'll have lot of fun and wasted time when you try to make them work. The drivers are awful and you won't get support from the manufacturer.
  8. Difficult to say since we don't know your setup. How many outputs in which resolution are you using from one server? How are your servers configured? EDID set up correctly? What codec is used? What happens if you disable all but one screen and try to use this one? I have seen some black outputs when the operator used too much content on a server at some positions in the timeline. Too much means that the amount of data was more than the SSD could load at a time. Be aware that looping videos count twice! After reducing the amount of videos a bit all went fine.
  9. Which graphic card driver? Which codec? SSD getting enough cool air?
  10. My servers play appr. 20-24 instances of HAP fullHD@60fps on 4 outputs without stuttering. WX7100.
  11. Hi Alex, Thanks for the efforts. Unfortunately I'm at the gate waiting for a flight and won't be able to test before the end of the month. An alternative would maybe be a broadcast address but I've not used this myself yet. The broadcast address would be 192.168.0.255 in a 192.168.0.xxx network. This would surely stay inside the local network which adds security. Kind regards, Rainer
  12. Muito obrigado! Looks nice. Couldn't the app work with UDP broadcast as well? Then the team colleagues could install the app and just listen to the broadcast instead of having multiple cues to the different team members in the timeline.
  13. Some HDMI converters know two versions of SDI. I recently had to play with the settings of my Decimator interfaces until I found the right combination.
  14. Hello Ryan, Two things to consider here. a) Blackmagic graphic cards are unfortunately not the best choice since the cards drivers usually don't analyse the input signal format and one usually needs to play with the driver settings of the Blackmagic software and the settings in the input in WATCHOUT for a while to get those cards working. More professional cards like those from Datapath identify incoming signals correctly and it usually doesn't make much difference if the settings in WATCHOUT are wrong. They will still show an image. We have seen cases where we needed to set the input in WATCHOUT to e.g. 720p25 when the source sent signals at 720i50 etc. b) Testing the signal from a DVD on a Blueray player might not be the best idea. Blueray players usually use DRM coded outputs which will usually work on monitor inputs but never on capture cards, no matter what product. The manufacturers of capture cards are usually not allowed to capture content from DRM protected outputs. The better source would be a camera with SDI output or a normal HDMI signal from a computer desktop converted using a HDMI > SDI converter. Hope it helps.
  15. Thank you for sharing. I recently stumbled over an AE/ME/Premiere plug-in encoder for HAP which was until now unknown at least to me. We did some test encoding regarding banding and the slow encoding of this package looked better than the result of AfterCodecs. Check: https://jokyohapencoder.com/
  16. From my experience, HDBase-T sometimes shows incompatibility issues between transmitters and receivers. Especially when it comes to older variants. The second point is that I never copy an EDID signal from a display since this includes all possible frequencies the display is capable of working with. I either use external EDID minders with only one frequency burnt in or the EDID settings of the graphic cards driver.
  17. Do you have any other production computer for testing? It looks as if the problem is on that side.
  18. WATCHPAX units are set to DHCP as default. What IP address do you see at the splash screen when the server starts? You can set an IP address when using a mouse and keyboard and the keys Ctrl + W. Look for the startup script in the File menu which explains where and how to do it. More important than the network list is actually whether you can connect to the server. In the screen settings dialogue box on the production computer there is a connect button which should turn green if the software "sees" the server and all necessary ports are open.
  19. WATCHOUT manual page 172... Don't forget to define the MIDI device under preferences control.
  20. I the show works fine using production computer A and shows errors using production computer B, the gear to investigate is the production computer. Are you using the same network cable and the same port of your switch when you swap the production computers? If not, do so to rule out faulty cables or broken ports on the switch. To analyze what's going on on the network, it could help to use Wireshark on the production computer. It will write millions of events in it's log list but you can easily filter out parts once you compare the time of the network loss.
  21. Well, since I have not seen such a behavior and we have not heard of other cases so far, looking at the log files seems to be the only way to solve the problem. While in most cases, problems like this can be related to broken cache files or broken content files, it could of course be hardware related too. E.g., have you ever tested your RAM with something like https://www.memtest86.com/ I remember a case probably 14 years ago, when a client programmed a show with appr. 10 display computers and all of those did an unintended reboot after some 4-8 hours. Some earlier, some later. After long investigations, we found out that the RAM modules used in the server didn't work properly when more than one module was used. As the mainboard used quad-channel RAM architecture, there were of course 4 modules in the chassis. Taking three out made the system stable. The RAM was specified in the QVL list of the mainboard! We then changed the RAM to another product which we used at that time in our servers and that cured the issues.
  22. If I understand it correctly, the show crashes on the production computer when the timeline reaches 25+ minutes? Have you checked the log files on the production computer? Have you checked the event log files (application) in Windows? Have you deleted the WATCHOUT cache file on the production computer so that it gets rebuilt? Can you rule out that some media at that point in the timeline is corrupt?
  23. Could be difficult since you're just using a web browser to access WATCHNET. As in every other web project, there is no real mechanism built into WATCHNET to make another browser change the page. But this is standard web browser behavior.
  24. If you can make it work under Windows and turn off all other NICs, it should work with WATCHOUT too. WATCHOUT does not have any adaptors!?
×
×
  • Create New...