jfk

audio has no impact on synch in WATCHOUT.

Seeing as WATCHOUT does not support audio input in any form, I would not get my hopes up.Seems it may be a major thing to add a feature which currently does no exist.

FYI the issue with audio looping is now a confirmed bug. With the summer break in full swing it may be a little while before it is addressed, hopefully in the next update.

Sounds like a Windows question for a production computer. (You should never see the task bar on Display in full screen mode). Windows version?

Most likely. This might help: https://forum.dataton.com/topic/3633-everything-i-think-i-know-about-dataton-v5-and-v6-license-keys/ Yes, install the correct version, no do not copy the files. (While it may be possible to just copy the files over, success is fully dependent on the organization of the original programmer). Watchout includes a function, "Consolidate To ...", specifically for moving shows. This function automatically adjusts file references to ensure portability. The User Guide gives a good description on use of the consolidate function.

I am a little confused. PC2 is a different scan rate than the other two. How can you scan lock different scan rates - did not think that was possible? Always thought you could only scan lock matching scan rates.

No, should not matter. The fact that it runs correctly sometimes and acts up at others brings another possibility to mind. I have encountered network switches with automatic UDP storm / UDP flood / denial of service (DOS) protections. In those cases the switch interprets watchout's continuous UDP traffic as an attack and kicks in those protections (so it works for a while until the switch takes protective action). But that should not occur on a simple unmanaged local switch, although I did once encounter a D-Link unmanaged "secure" switch that included those types of protection.

Simple way would be to use the Solid media object to create a rectangle larger then the live input and then place the live input object on a higher layer, covering all but the outer portion - voila - border.

Yes, it will work in cluster mode providing the TCP output object is set to port 3039 as it is done in my examples. The cluster master handles the DMX communication. The online comment only relates to Production mode.

Using two DMX channels, one for mute on and one for mute off makes this way more complicated than it needs to be. Additional programming is required to support both cluster mode and production mode, using conditional layers to switch between modes (otherwise if you left both active, there would always be errors). In production mode, you must be online for this to work. ... (damn forum system shrinks this image, original image) for cluster mode ... Use the set condition option on the cluster mode load command , like load Sample_DMX_audio_mute_control True True 2 On the other hand, using a single channel, it is super simple, no special programming for production mode / cluster mode, works either way. No need to set external TCP control of production. No need to use conditions. No need to use Tasks. Works in production mode online or offline. It as simple as this ... (damn forum system shrinks this image, original image) The two shows above (without the audio file, substitute your audio file in the media window) can be downloaded from http://dataton.net/watchout/DMX_mute_stuff/SampleDMXcontrol-audio_mute.zip

Hi Lucas, I had hoped to do this last night, show opens soon and I will not be able to get to it until tonight (US time zone).

It is not a built in function, you build a custom set of functions using the available tools in WATCHOUT. Yes, I can explain it, but before I go through that exercise, need specifics so I do not have to do it multiple times. • WATCHOUT version you are using? • DMX universe and channel for engage mute. Value that will be sent to trigger (easiest way is if 0 value is not active, any non-zero value is trigger, but if you need something else, please describe) • DMX universe and channel for release mute. Value that will be sent to trigger (easiest way is if 0 value is not active, any non-zero value is trigger, but if you need something else, please describe) Keep in mind that you must reset to an inactive value after each trigger / before next trigger. i.e. if 0 is inactive, then after setting a non-zero value to trigger a state change, you must return to 0 before attempting the next trigger. Understood, not needed. WATCHPAX will be sending TCP to localhost to trigger itself, no other TCP needed. I am working at Infocomm 2019 (USA) this week, so it will take some time before I can provide that (have it by tomorrow morning).

Are you saying it is not possible? If it is possible, then the solution is quite simple. Otherwise, the solution using two channels is quite complex - you will need a TCP string output, a generic input, two auxiliary timelines and the two DMX inputs. Either single channel or two channels you need to multiply all audio tweens by the designated input value. And how do you propose to change the mute channel and un-mute channel? There has to be a state change from false (DMX set to a predetermined value or range of values) to true (DMX set to a different predetermined value or range of values) to trigger a mute change event.

Sure sounds like you have a network problem. Is there more than one NIC in your display servers?

I am curious why you would not control master audio mute at the audio system? "What i know you can is with DMX controlling the complete audio volume but that is not ideal. " ??? Why? Do not set audio volume with the DMX input, simply multiply all audio tweens by the input value. "I need one channel to mute the audio and one channel to unmute the audio." That seems unnecessarily complicated. One channel at 0% for off/mute and 100% for on / unmute would make more sense would it not?