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

Hi, in several cases I solved by putting the NDI flow into an auxiliary task and then putting a jump back on its timeline. In this way, once set to play, the jump will keep the flow always active, otherwise the NDI driver, if it does not hear a regular flow, pauses the streaming to save on the network data flow. This function cannot be changed since it is intrinsic to the NDI driver. Best regards. Diego

I found that the problem exists only on Display computers in versions v6.3.1, v6.4, v6.4.1 (the v6.5 I have not tested to the end) with Win10, and the solutions I found are only paliatives to bugs that are dragging on for some time . Problems encountered: 48KHz 16bit WAV LPCM file during a free-running if you put it pause on the computer Producer continues to play while on the computer Display stops problem sometimes found only in the main timeline and not on the auxiliary timeline (v6.3.1) problem encountered even with TimeCode tracks generated at 48KHz 16bit WAV and put in the Main Timeline WAV 44.1KHz 16 bit audio files made with Logic Pro for Mac, they crashed the Production (v6.4) with Logic Pro for Mac have another problem happened that after some time the WAV it went out of sync with the loops and the Logos on the Display computers came out without giving errors on the Producer (v6.3.1) problem sometimes encountered even with conversions made by MediaEncoder Solutions currently adopted: conversion of files via FFMPEG to WAV 16bit 44.1KHz creation of 44.1KHz audio files with programs other than Logic Pro I hope this can be of help waiting for the continuous bugs repeated in multiple versions and that have been generated by v6.3 onwards are definitively solved. Best regards. Diego

Good morning, there are often needs that I have not yet seen integrate and that I would often need. The list for practicality: OSC In / Out protocol Dante In / Out Protocol MIDI Out Protocol NDI Out Video and Audio Protocol A coutdown for videos that can be added to the STATE window or separately and can be sized as desired You can decide in the Tasks the size of the STOP and PLAY keys Possibility to color BACKGROUND TASK TITLE in a separate and independent way Possibility to color CONTROL CUE in a separate and independent way Possibility to color BACKGROUND LAYERS in a separate and independent way Integrate a real hot backup system (with a Master and Slave system) for the Producer A multipoint Warping system similar to that of Panasonic or Epson but maintaining the curvature management that already exists Create a multi-layer Warping system similar to the D3 Desguise Have a window that allows you to see and possibly force the Display Computer EDID without having to log in Remote and do it on the Driver You can import SketchUp * .skp files into the media without having to convert them To enable a grid or a measurement tool in the STAGE that allows you to accurately calculate the mapping of the pixels used or displayed To convert, if you wish, the VIDEO in HAP directly from the MEDIA window (Desguise has released the HAP Encoder for free) Thank you for your attention. Best regards

Hi everyone, regarding the MPCDI protocol I wanted to know if someone has already used this format and with which types of cameras it is possible to use it in the future with Watchout 6.3. Thank you.