jfk

Have you tried a standard VNC viewer on the Windows machine to connect to the host Mac VNC server? I would not worry about WATCHOUT until it is confirmed that the Mac computer host is working normally with standard tools. If it is not, use Mac support to determine what needs to be corrected on the Mac.

That is nice, but what does that have to do with Bootcamp? You certainly can not run the Mac platform and bootcamp at the same time

Yes, I was wondering about the receiver. The picutre of the transmitter appears to have a second device that might be a receiver, but it is just a front and rear view of the transmitter. $350 for the receiver + the $80 transmitter kinda of invalidates that TomT

There is a three button option too: Cue Lights > Transmitters — How many do you need?

Ideally DataPath Vision RGB E1S with a simple passive DVI-HDMI adaptor. Alternately BlackMagicDesign Intensity Pro 4K. Both are PCIe x4 cards. The DataPath is a full RGB solution that should work at any computer resolution, most computers output in RGB native. The BlackMagicDesign is a YUV solution and works at video resolutions only, most computers can step down to that level of output. WATCHOUT offers NO audio input functions, so yes, you will need to use separate audio from the notebook. And you will need to add an audio delay to the system to accommodate for the delay in the video capture process. Yes.

Are you saying that your application changes the .png source file on the display computer without using watchmaker to place them there? That will not work. All .png files are preprocessed during the transfer from watchmaker. Changing the source file on the watchpoint PC after watchmaker has placed them will not change the preprocessed information, so you will not see the change. Would be better to use the URL proxy function to reference the new .png files. Have done this with as many as 45 URL referenced 1920x1080 .png files changing every ten seconds and it worked fine.

Bootcamp is no different than any other Windows computer, for best results, you still want to follow the Windows_7_Tweaking_list_2.1.pdf Other than that, Bootcamp drivers appear up to the task.

Just leave 0.001 seconds of black at the head of each timeline. When you pause them from the stopped state they load up at time 0.000, so won't matter which one is on top if you only roll one. Of course, you will need to perform housekeeping to kill each one after it is used.

Scrolling horizontally while the timeline is running, the layer names stay locked in the left side of the timeline window while the cues / time position scroll. Scrolling vertically the layer names stay locked to their layers. Same in v4, v5, or v6. I do not understand what you are asking?

No, there is no inputs to WATCHNET other than the panels.

Your effort to communicate in English are appreciated, but it is difficult to ascertain the meaning. Will give it a shot ... If two video cards are installed in the computer, you can only use the outputs from one video card. Of course it depends completely on the video card, but in most cases, yes, you can output 2560х1600@60p on each output. It is possible to use DisplayPort 1.2 Multi-Stream Transport (MST) to provide multiple outputs (up to three 1080p usually) on a single DisplayPort 1.2 connection. Success is highly dependent on the MST hub chosen. Setup of the graphics card via the graphics card's manufacturer's driver is crucial to success. When setup correctly, the outputs from the MST hub appear as standard outputs in Windows. WATCHOUT itself is not involved in MST setup, all WATCHOUT needs to see is compliant outputs from the OS. Any questions on MST hubs should be directed to your hardware vendor.

WATCHOUT has never natively supported .mp3 audio files. Granted, they would sometimes work due to non-WATCHOUT components on the computer that enabled .mp3 for DirectX, and WATCHOUT would inherit support for mp3 via DirectX. So you need to troubleshoot your third party DirectShow support for .mp3 or convert your audio files to .wav.

You can not send commands to other devices directly from WATCHNET. BUT, you can send commands to your projectors with WATCHOUT. AND, you can trigger that WATCHOUT command from WATCHNET. So put each shutter command in its own auxiliary timeline, then trigger that command from WATCHNET by running that auxiliary timeline. BTW The Panasonic projectors are notorious for being inconsistent in responding to PJLink commands. Instructions on sending the shutter command can be found here: PJLink protocol

An iPhone, iPod Touch or similar device running a WATCHNET panel with just the one button would be easy enough. Your incremental cost is 0, as you can not use WATCHOUT Production and WATCHNET on the same cluster at the same time (either/or). WATCHNET uses a standard WATCHOUT License (the web site may lead you to believe it is a different license - it is NOT.) So quit WATCHOUT Production when you are done with changes - releasing the license key, open WATCHNET, using the same license, to serve your simple remote. Could not be much easier.

When troubleshooting a signal like this, start out by using the Blackmagic decklink card's Media Express Utility. i.e. eliminate WATCHOUT. If there is a DHCP issue, it will have the same effect in their utility. From that point, use other resources for assistance in determining how to turn it off on your iMac. Talk about misleading information on HDCP, I enjoyed this quote from a user on BlackMagicDesign forum ...

Will you be using timecode in cluster mode? (i.e. no Production computer - recommended) or with a WATCHOUT Production computer online? The procedures are very different.

search is your friend: http://forum.dataton.com/topic/1393-multiple-live-video-camera-capture-cards/?p=7365

Yes, DVI should work fine (providing your iMac is set up properly to NOT require HDCP handshake). No, audio capture is not possible. Feed audio to your sound system via an audio delay capable of adding up to 4 frames delay or so, should be a little less than half that.

Curious, have you contacted Martin for their thoughts on static Qs or static channels? Not familiar with that concept in DMX, don't Martin use a proprietary communication between Martin Boards and Martin Instruments, i.e. could those functions be a Martin proprietary thing? Bump — looking for Martin savvy help from others

Another proven technique to keep the capture cards open at all times is to place cues for the live inputs the full duration of the show on standby layers. reference: Datapath Input Freeze

Yes, WATCHOUT fully supports alpha channel in movies (animation codec) or stills. Any still or video can be keyed as well. The only potential limitation is computer resources, Some alpha channel videos can be resource hogs and add the second video and you may find the limits of your computer, may not. Depends a lot on the hardware, resolution, frame rate and chosen codecs of the videos. I know you said v5, but v6 adds support fot HAP alpha codec, which is more efficient than animation codec.

WATCHOUT 6 is still 32 bit. If it were changed to 64 bit, then it would have to drop support for Apple Quicktime, which remains 32 bit. Still no harm installing the 64 bit OS, does help with some capture cards, does not matter much to WATCHOUT. But WATCHOUT 6 for now remains within the 32 bit memory space. I have lobbied dropping QT support and moving to 64 bit. In v6 - ProRes, h.264, and animation codec .mov files are already supported without Apple's quicktime support.

Did you obtain the iOS app from the App store (out of date, will not work iOS 7+) or using the instructions on the Dataton web site: WATCHOUT REMOTE APP ?

merged some common threads, bump to the top for the new post above ...

Hi JJ, I have the utmost respect for your knowledge, but I am not seeing issues with looping a composition in v6. I suppose you know this, but to get it to work correctly, you must place the video at time 0 and then trim the composition duration to exactly match the video's duration (and I lock the composition's duration after doing that). Do not designate looping or free running in the movie cue inside the composition, only do this in the composition cue. so for video cue placed at 0.0 with a duration of 11.4 set composition timeline settings duration to the same value in the composition's video cue do not check loop or free run in advanced and when calling the composition, in that cue, DO set loop and free run