MatzeLe

This is the question, if LTSC 2019 oder 2021 will work better. But with the IOT question, in terms of the base they are the same. But IOT has some options for branding and also protection of the system image, like UWF.

Some say it will be on Datatons 50ths birthday, in September 2023...

Tell us more please. How much horsepower have your car?

DX9 is not the newest version on Win 7, it is even possible to have dx12 on Win7: https://devblogs.microsoft.com/directx/world-of-warcraft-uses-directx-12-running-on-windows-7/

It is not nessesary to go with the A5000, A4000 should be enough. We have to wait how WO7 behaves, since it supports more GPUs per system. The A4000 is also used in the Watchpax 62.

So, in the Watchpax 62 manual, you can see that they use driver version 473.47 for the rtx a4000. Thanks for telling us. Have you experience with higher version numbers? Since this is the first DCH driver version from Nvidia, it seems that they use a Windows 10 version after or from 2018 (maybe Win10Enterprise (iot) 2019 or newer), so these hints with versions earlier than this leads to nothing.

Ah I see, the RTX A4000 is used in Watchpax 62. So can you provide Informations about the driver version used? Maybe there is the Win10 IOT version used in Watchpax, can you confirm this?

Did you disable all other network adapters on the laptop, also the wifi? Watchout isn't able to handle several adapters.

Dear RBeddig, but shouldn't it be irrelevant which settings are provided in the EDID of the display device, since you can only choose one setting? By the way, TO obviously used no workstation card, so no internal EDID emulation. Also there was nothing mentioned about HDBase-T, he talked about an HDMI over Ethernet converter. HDBase-T has nothing to do with Ethernet.

Dear RBeddig, if it is like you said, then why it is no problem to play HAPs with other programs and AMD cards? What did the AMD technical support told you about this?

Aren't quadro cards also old? What about the new rtx a models?

Since when is "sourcecode is encryped" an argument why log4j should not be vulnerable? Can you explain please?

Watchout can't handle AMD since 2017. It is not quite clear what the problem is, but solution is always: buy nvidia. Got a w6600 running with win10, but really poor results with the recommended win10 ltsb. Maybe it performs better with actual win10?

So, is it likely that other newer radeon pro models, like w6600 or w6800 are also this choppy? This would mean Watchout needs - if you stay with AMD - a 7 years old graphic card (wx7100) with a 4 years old driver? Is this correct?

Or even better, just implement multicast uploads, like every other deployment software do since 20 years.

We use WO in a fixed installation and managed to have it run with 6.2.2 - after some undocumented changes in the remote telnen behaviour, I was very carefully to take further updates, since in my experience, there is always something different than before. But to have a look, I took an update to 6.5 first, the only thing disturbing our way of use is, that the display machines shows the WO logo if we send load command over telnet. This was different in 6.2.2, is there a way to turn the logo of like it was before? But this was some minor annoyance, so I updated to 6.6. We used to play some larger HAP files, and everything worked until 6.5. But not in 6.6 anymore, some files where played, some not - whit no error messages at all. This concerns the production software and also the display software. Didn't have the time to make some tests and have done an downgrade to 6.5, but maybe you can tell anything to this?

I remember a strange behaviour after an update to 6.2.?, we used telnet commands to load shows and goto cues, so there was a list of commands that where sent. After the update it was necessary to wait for the ready message from the display cluster to have the gotoControlCue command worked like before - if you used to have a fire and forget onedirectional approach to use remote commands, it is very funny to implement something bidirectional in some hours to have the show going on next day. These are these little easter eggs you always have to expect after each update...

The same here, after updating from 6.1.6 to 6.2.2 the telnet commands don't work as before. I used to send a stack of commands like "authenticate, load show, gotocue, run" just with line seperators between as a single message, worked fine until the update. Seems there was a mechanism for stacking commands and execute them when ready. Interesting that it works on aux timelines, didn't test this. Another interesting observation was that cues on the beginning of the timeline where found right after load, whereas later cues needed some time after load to be found. My solution was implementing a bidirectional communication for load (waiting for ready answer) and use a standard break of 250ms between each command. 100ms was too short for auth->gotocue->run. So please Watchouters, make it work like before.