Diego Marchente

What does the Runner's choice of Channel depend on? Is it possible to understand in what ways the channels have been routed relative to the outputs of the Graphics card? Thank you Diego - PlayIT

They may seem like trivial questions, but are you sure you have installed all components from Watchpoint, DVS and other components in 'Administrator' mode? Are you sure UAC is totally disabled? Have you tried uninstalling Watchout, rebooting, and then reinstalling Watchout? Diego - PlayIT

Have you tried delaying Watchpoint startup via the Autostart.txt batch? You can add 10-15 seconds so that once the DVS is started correctly and with the network active, it is already available for the Watchpoint and therefore does not put the first generic driver it finds. If I were you I would also remove the Nvidia Audio drivers. Best regards Diego

Hi Claudio, Thank you for the answer, but it's not clear to me why if I take a project that I just need to check, it's not possible to view it even if there are no files to convert. This is not described in the manual. See you soon. Diego

A friend passes me a v7.1.1 project without contributions (I just need to see the preview) to verify the correct execution of some tasks. I'm not using a license and to my surprise I don't see anything and it won't let me upload any media... Also if I do a project without a license, I can only upload PNG and HAP, all other file types including WAV are disabled, why?... But wasn't it supposed to be the same workflow as v6? Thanks

You can control remotely via VNC with any device you find convenient, even over WiFi.

Thanks Mayunta...🖖 Would it be possible to add more Custom displays to the calculator later? I find it very useful.

If I activate a variable from a cue in the timeline, if it does not have a key in its properties, it also activates the masterVolume. To avoid this I have to forcefully insert a key.

Il tuo problema risiede nel fatto che hai una risoluzione custom verticale che non è multipla di 8... se inserisci 4224x1312@50 non dovresti avere problemi a meno che il tuo convertitore da DP ad HDMI non abbia il limite del 4096 pixel orizzontali e se usi anche un'extender verifica che permetta delle Custom Edid oltre i 4096 pixel. Come datarate per il segnale sei dentro alla pixel clock massima e quindi non è un problema di larghezza di banda ma solo di una errata configurazione o di limite della timings list. Your problem is that you have a custom vertical resolution which is not a multiple of 8... if you enter 4224x1312@50 you should have no problem unless your DP to HDMI converter is limited to 4096 horizontal pixels and if also use a verify extender that allows Custom Edids beyond 4096 pixels. As datarate for the signal you are within the maximum pixel clock and therefore it is not a bandwidth problem but only a wrong configuration or limit of the timings list.

Was the fai you are using generated by you? Did you do it in WAV format? Are you sure your connecting cables and connectors are healthy? Best regards

If you have an i9 processor, that is most likely the problem. Use i7 processors only.

After several months of testing, solutions and analysis of both versions and operating systems, we came to the unpleasant conclusion that Watchout with LTSB or with LTSC, with or without DCH driver, with an i9 processor and WX9100 graphics cards (but in some cases also WX7100) do not work. They generate calculation errors and there are continuous tripping even in offline, terrible management with resolutions beyond 1080p and the impossibility of using custom resolutions or with different resolutions on multiple screens. I would say it would be interesting to understand why they can't work together. With a clone system but with an i7 processor all this does not happen.

Hi, Have you tried to run it through FFMPEG and see if it fixes some Header or structure that QT doesn't like ??? I often solve many problems by doing so. Diego

Hi, Do you also have Brightsign installed on the same network ??? Diego

I am testing version 6.5 and it should be fixed. I've seen a noticeable change in file transfer speed compared to v6.4.1. In the meantime I verify its stability since in the last versions it has unfortunately disappeared. Best regards Diego