jfk
-
Posts
1,808 -
Joined
-
Last visited
Posts posted by jfk
-
-
watchpoint's NIC selection is not related to Windows NIC priority. Apparently something in the registry determines the NIC selection when more than one active NIC is available when watchpoint starts. It would appear your only choice is to both use the NIC watchpoint automatically selects AND set that NIC as first in Windows priority when more than one active NIC is available.
0 -
4 hours ago, kraves said:
Now it has been out for while and gaining traction, is there any progress on adding NotchLC codec support?
It has been on the radar for a very long time. There are technical reasons Notch LC can not be added to the current WATCHOUT versions. Notch LC is up and running in the internal next major version of WATCHOUT. Don't ask me when it will be released. Last i heard, there are delays
0 -
On 8/29/2022 at 5:37 AM, jaygrovr said:
So I set the priority of my desired NIC to be used for watchout control to 1, and I set the other nic to 2, and when I rebooted it took the IP address of the priority 2 nic. Any reason why that would have happened? I had to keep the second nic unplugged and bootup the machine to make it take to the NIC I wanted it to.
Any thoughts?
The comments about NIC order refer to watchmaker.
Good question about the impact of NIC order on watchpoint. Will look into that.
0 -
The h.264 / mpeg2 / mpeg4 decoders in WATCHOUT do not support 8k. You would need to use a HAP variant .
reference: H264 level limitation in WATCHOUT 6.2
0 -
Playback 8k width video — WATCHPAX 40, WATCHPAX 42, WATCHPAX 60 and WATCHPAX 62. Note, the WATCHPAX 62 can output 8k on a single output as well. We have very limited testing with 8k content.
0 -
On 8/20/2022 at 2:18 PM, trnhnnh said:
… I am able to see the screen capture on the Display computer in the application that is required by the software. As a test, I can also see it as a source in OBS. …
In most cases, the application supplied by the hardware vendor uses a proprietary driver. WATCHOUT requires a generic driver as defined by Microsoft Windows Driver Model (WDM). ie two different drivers may be at play. So the manufacturer’s utility confirms physical connection, it does not confirm the WDM function required by WATCHOUT.
When you go to the “Video In” menu in watchpoint, what choices do you see?
0 -
8 hours ago, artboy said:
The confirmation is late.
Thank you for your detailed reply.
Is the meaning of 'automatic recovery of a watchpoint' correct to follow the show again when watchpoint is forced to shut down due to an error and watchpoint is re-run by watchdog?
Correct. A cluster member will load and re-synch automatically on its own after a watchdog restart. Only in cluster mode. Only a cluster member. If the cluster master goes down it will not recover and all members become freewheeling.
0 -
WATCHOUT Version?
WATCHPAX 40 system revision?
someone could probably mark this up better than me ... anyway, fyi system revision on end of last line ...
0 -
7 hours ago, artboy said:
I'm writing because I'm curious.
Why is Production Mode not recommended when controlling with external control protocols via public network?In Production mode, the watchpoint stations are in read/write condition. Gaining access to production allows show changes to be made. Furthermore, repeatedly going online risks unintended changes.
In cluster mode, the watchpoint stations are in read only condition. They will not change - more reliable.
During playback, as it relates to playback control in watchmaker, anything that can be done in production is supported in cluster mode. IP output, ArtNet (DMX) input / output, timecode input, MIDI input are all handled by the cluster master in cluster mode.
Also, automatic recovery of a watchpoint cluster member is only available in cluster mode. In production mode, you must send an Update to resynch a recovering watchpoint station (update is faster than offline / online). With multiple watchpoint stations, cluster members recover without intervention.0 -
On 8/12/2022 at 2:06 PM, wiesemann said:
I had exactly as a feature request at the beginning of the pandemic. ...
And it has been heard. I wish things were moving faster. Suffice is to say, NDI output is included in the next major release ( and has passed alpha testing). One of numerous additions. I hope i live long enough to see it reach the market
. In all fairness, we do not want a product that is not ready.
0 -
Dataton AB use a BirdDog in the WATCHOUT Academy. We also hear good things about the Magewell NDI products.
0 -
-
6 hours ago, jaygrovr said:
… Is there a way to force it to use a different NIC in the autostart.txt? …
No.
WATCHOUT will use the first NIC in Windows NIC priority. To change the NIC used by WATCHOUT, change the NIC priority in Windows.
0 -
Bad NIC hardware is pretty rare when some network functions work. i.e. it would be unusual for bad hardware to act like this. Incorrect NIC software configuration / settings maybe.
the support team suggested multiple production computers on the network as a potential issue. Also version mismatch between production and display may cause an issue that looks like yours.
0 -
reinstalling watchout software is a waste of time.
If you re-encode the movies, i strongly recommend you encode with the HAP cosec.
0 -
Nine times out of ten this means that the display server has crashed. Most times, the display computer watchdog software component has cleared the malfunction and returned to the logo screen, ready to try again. If you are online, an update from production will bring it back.
The place to look for more information is the display computer logs (in a folder called logs in the installed WATCHOUT location). Most often the watchdog log provides clues as to the cause. Occasionally the watchpoint log helps.
The decoder for mpeg2 / mpeg4 / h.264 is often the culprit. If the multitude of encoding parameters are not tweaked correctly for these codecs, instability will result.
0 -
On 7/26/2022 at 11:03 AM, JamesC said:
… Client has power cycled the unit, extenders, and projectors a few times …
More of a general note - with WATCHPAX, any time *any change / disruption in the display connection* occurs - you MUST then power cycle the watchpax LAST. Plugging / unplugging a display connection, powering up or power cycling a display or extender, all will freeze a powered up WATCHPAX.
0 -
Check the network port is operational. i.e. Confirm an LED immediately above the RJ45 connector is lit. Also, take a closer look at the startup logo screen text information - is the assigned static IP address correctly displayed?
0 -
Have encountered what you describe with others. While weisman provides solid advice, i suspect something else is at play here. i do not know what. (BTW multiple NICs with NIC priority issues do not affect online/update file transfer, just transport and timing / synchronization communication.)
My suspicion is file access permissions. Typically occurs after a version update. The uninstall / install process when updating may result in permission changes? I do not know. Also suspected partial obstruction of network communication- firewall settings are possibly lost during the update?
Others have reported the same symptoms, but as of yet, no one i have worked with have identified the cause. Some replaced the suspect computers and moved on due to time constraints. Others corrected by wiping clean and restoring the initial tuned configuration, stepping back to the archived version.
0 -
Before a show is loaded, the logo screen is displayed using Windows basic general purpose rendering mode. Once a show is loaded, the graphics mode switches to DirectX 3D hardware accelerated mode. Apparently your capture utility does not support DirectX 3D hardware accelerated mode and PrintScreen does.
0 -
50 minutes ago, John G said:
Hi
Can you reload the Smartpax pdf to Dropbox please?
regards
John
SMARTPAX Product Sheet expires 24–July–2022
0 -
25 minutes ago, TonyShamel said:
Side note did you have quicktime installed?
I had an issue with hap playing back on my win 10 production and the issue was quicktime was not installed
WATCHOUT installs its own decoder for HAP. QuickTime is not needed by WATCHOUT and is not recommended. (Note: All Dataton WATCHPAX do not include QuickTime.)
QuickTime does not decode HAP with its default install, HAP is an extension that can be added to QuickTime.
More often than not, HAP issues are caused by third party HAP decoders interfering with WATCHOUT’s decoder.
0 -
9 minutes ago, Gates kweon said:
hi dear
I want to write a protocol to control the watchout externally.
I'm trying to find a way to take control from anywhere with the internet.
Thank you always for your replies.
It is quite straightforward to control WATCHOUT in cluster mode via IP. (I would not recommend production mode for connections to public networks.)
Please reference the WATCHOUT Users Guide for IP control information. Appendix C - Control Protocol
https://www.dataton.com/watchout-users-guide/appendix/c-control-protocol
0 -
No, WATCHOUT does not offer time of day triggers. Typically that type of trigger is left to control systems. (Dataton WATCHNET offers time of day triggering of WATCHOUT).
0
Feature Request ? Post here
in WATCHOUT FORUM
Posted
I wish I could provide a specific response. I am not at liberty to do so.