RBeddig

That's were the Hucht Copy Encoder/Decoder came in place a few years later which enabled to encode a CD to carry the control code in the LSB of the audio data. Not sold that often but very handy indeed. I also read the request for PAX gear and can check what I have in my huge "PAX and friends" storage but since I'm a few continents further west it might be easier if you track something down-under.

I just tried to install v 6.6.4 over a previously installed v 6.6.3 on my Parallels Desktop and Windows 7 and this worked as expected. My folder is the default C:/watchout 6 folder. I don't have a second drive on my MacBook and therefore can't test whether the drive makes a difference. Can you de-install WATCHOUT, clear everything from the old installation folder (a few folders usually remain), install WO 6.6.3 or 6.6.2 again and try the update process once more? Just to rule out that something in the registry was weird (due to a previous update) which might have caused this error. Best regards

สวัสดีครับ Kai, Contact me through a personal message and I'll send you a link to our server. Regards, Rainer

You will need something to capture your graphic card output from WATCHOUT and convert this into a stream. The Blackmagic Design ATEM series could be one way to do it but you can also use a capture card on a second computer and some software like OBS, vMix etc. to mix and convert the signal for your stream. WATCHOUT is designed as a professional tool for multi-screen presentations with one or many synchronized outputs and renders the content live when it sends it to the GPU. It does not have any function to convert an output into an internet stream.

The Windows 7 compatibility issue with mainboards is usually related to USB 3.0 drivers and there are a few workarounds to add a driver to the installer DVD. Regarding WATCHOUT 5 you should check "Dataton software - earlier version archive" which is pinned as one of the top threads in this forum. WATCHOUT 5 does not work on Windows 10. The latest version is Windows 8.1. You'll also need to install Quicktime.

Switch settings can be confusing and even have different names on different brands. If you want a solid system, look for a robust dumb switch without management options. Those switches will always work. And make sure that you only have one network port open on your production computer!

Which IP are you using in your production computer and which IP is shown on your display computer logo screen when you start the system? What sort of display computer are you using? WATCHPAX/WATCHMAX or custom built?

Are you sure that there is no black frame in your content at the beginning or end of those clips. What is the filesize in regards to pixels (w x h)? Have you tried extending the pre-roll manually in the second video clip? This used to help in the past when the perfomance of a computer system was not good enough.

We have scanned it 13 years ago and still have it on our server. Since it is appr. 20MB you should contact me off-forum ans send me an email address.

Under Preferences/Control you can define the standard universe for incoming and outgoing cues over DMX (Art-Net). Create an output in the output window, select the correct channel and universe and then drag the cue from the output window into your timeline. Use the tween track to fade the signal up and down. Two traps, you might fall into: 1) WATCHOUT only sends DMX values if the computer is ONLINE (dongle needed!). 2) There might be an offset of one channel or even universe since some devices count from 1-512 and others from 0-511. A good tool to check what happens in your network is the free tool Artnetominator.

If the signal comes through a capture card, you a) have to make sure that the capture card is properly installed and Windows can see it as a capture device. Then you need to define an ID for the capture channel on your display computer(s). You can remote into the display computer from the production software. Then you set up a "Live" media which you set to the same ID and drag it into your timeline. It's pretty well documented in the manual.

WATCHOUT will not "find" an Art-Net device in the network. WATCHOUT sends out ArtNet data on one or more universes to any ArtNet receiver in the same network. So the first thing is to check whether the Art-Net receiver is really listening on the same network. Some lighting devices use very specific network settings and can only send Art-Net in these networks while WATCHOUT can actually send in an network, as long as the whole WATCHOUT cluster is also living in the same network.

You can move your logo with a position tween or animate a (transparent) video for the logo. Remember that the correct way to do this is to use a virtual screen as a canvas for your 3D object.

I've used UNIVERSE show control to retrieve timecode from more than 3 or 4 aux timelines at the same time. I can't recall how many I used but more like 10 or so. Still one should keep in mind that the network is also used to synchronize the system etc. and that polling to many timecodes at a time does put some load on the system. You should have no issue sending the authentication command though. The only times when I saw something like this was when a nother higher level of control had a grip on the display cluster, e.g. WATCHMAKER or WATCHNET. You should not send "autheticate 1" to a cluster while being ONLINE on WATCHMAKER at the same time.

What hits my eye here straight away is: $D0 instead of $0D I'm not sure whether you actually need to send the CR at the end (it's been a while since I played with those devices) but it should definitely work. You should also use some wait commands to slightly slow down the data sent to WATCHOUT since WATCHOUT usually creates an acknowledge string after receiving a command. If you don't find a wait command in the IOCORE software you might first try to send "authenticate 1" from one input and then a command like "setInput Test 1" from a second input. You only need to send the authenticate command when you establish a network connection to the WATCHOUT cluster, not with every command as long as the connection stays open. If I understand it corractly, you also look for a way to reset the generic value internally in WATCHOUT. Unfortunately this can't be done without actually sending the command again - from somewhere! You could try to send strings from within WATCHOUT to the same generic input after starting the timeline and using a cue sending "setInput Test 0". You would need to use an output set to the IP of the cluster master or 127.0.0.1 and send "authenticate 1" at some point before sending the command. It is possible to connect more than one client through authenticate 1 at a time.

Is everybody sure that Mahesh Verma wanted to use an iPad to control WATCHOUT? He didn't answer my question of what he actually tried to achieve. If it is just controlling WATCHOUT remotely, I guess there are a few cheap apps on the market running directly on iOS. All other solutions which come to my mind here run on a proper PC or MAC and offer a gui webserver to which a browser on the iPad could connect to. While Blocks is an excellent tool and has many cool features it will most probably be a bit overdone and most probably way over the budget. A bit cheaper could be UNIVERSE which also now comes with a cheaper LITE version. If the original idea was to use the iPad as a display (?), it won't work. If he want's to use the iPad as a source (streaming the content into WATCHOUT) one could buy a little NDI app and use NDI in this case.

What do you plan to do with yout iPad and WATCHOUT?

If you have a second computer and a capture card, you could capture the output of the display computer and generate the screen shot. If not, you'll need to do it on the production computer. I would use the feature to record and export a video. For this you need to have Quicktime installed and you've got to scale the stage window up. Then you make sure that only the screen you want to capture is fully visible in the stage window. Check the manual for information regarding the video export function.

Just in case that you're not aware of it. Most tweens can be controlled dynamically through MIDI or Artnet. E.g. scaling, position, rotation, etc. Maybe this helps to adjust some settings while you're live.

Well, as I said before, you could place your masks (taken as screen shots and imported as transparent images) in a layer above everything else and turn the layer on and off by sensing control cues to yourself. This would allow you to enable the masks at one part of the show and to disable them when you reach a certain timecode. On the other side, if your servers and your production computer are good, you could of course also play sound from WATCHOUT. The sound can come from either the production computer or from a display server! Both works.

If I understand it correctly, you want to use your two computers with softedge in a part of your show without being slaved to an incoming timecode and later in the show, you want to use the same projectors as a slave to timecode without applied masking? As Morgan wrote already, there is no way to switch off the mask while a show is running. I would follow Morgan's advice and capture the applied masks in some way and add those to the show as a "mask media". The first part of your show could probably live in an auxiliary timeline since you don't control this by timecode. You can of course use a timeline set to "above edge blend" and start this with a control cue from your other timeline but you could also consider to use the top most layers for your mask. Take a look at the conditional layers which could maybe help here. You can control the conditional layers from within your show by sending control commands internally. The command is described in the manual.

You're welcome Jim. That's another way to do it. I ususally just place a locate to time or cue point somewhere in the middle of the cue, jumpnig back and pausing at either a time within the cue or the cue to jump to. Have been hitting the space bar too often when I wanted to run an aux timeline and instead ran the main timeline 😉.

No, Medialon Manager was always able to control auxiliary timelines. What might have changed here is auxiliary timelines in folders which in fact might not work since Dataton changed the API. I would also place the remapping (virtual screens) in the main timeline and make sure that I have a loop back command somewhere inside the cue to make sure that the timeline can't be moved out of the relevant part by accident. The main timeline can't be killed. It is always on.

If you haven't changed anything in your system and WATCHOUT used to play the two signals ok before, I would rather guess that something in your server or in the incoming signal flow incl. the cables has changed or got broken.

Which driver are you using for the Radeon Pro cards??? Did you run your show in WATCHOUT 5 on your new system or was it on a different system? Did you try to update the old system to WATCHOUT 6.6.1 or 6.6.2? When HAP shows green videos, it is usually an indication that you have more codec packs on your computer than just those installed with WATCHOUT. Could that be the case? Is VLC running on the new computer? Did you install any HAP codec on your new computer?