jfk

That is the correct method. That needs to be fixed. No. The WATCHPAX is locked. (And that is one of its most significant features). Most likely. Version? Are you getting an OK using the display dialog Test Connection button? Are you using a name or an IP address for the display dialog "Computer: entry?

One way would be to create a device in WATCHOUT for every display computer, use an auxilary timeline in your show that sends the powerDown sequence to each display, shutting down the cluster master last. With that prepared auxiliary timeline I would name powerDown, just send one command to the auxiliary timeline, run powerDown Shutting everything down with one command always makes me wonder, how you will power them back on?

OK, now I am confused ... I don't have access to a test setup to try this on my own at the moment ... I am not even sure what that means. Not sure it matters. Is it possible to see MIDI notes while MSC is active in preferences? 1 Windows MIDI service, ok. But multiple devices can be daisy chained within the MIDI domain. So providing the user gets his MIDI buss setup correctly, it should be possible to configure multiple MIDI devices to arrive at Windows as a single Windows MIDI connection. in other words, forget about how the MIDI gets there, regarding WATCHOUT's function, Is it possible to use MSC on main timeline or subset of auxiliary timelines while simultaneously triggering other auxiliary timelines with MIDI notes?

Yes As indicated on your first question, the display computer retains the name on its own. Of course, each time you start a new show in watchmaker, the stage is blank, so each time you make a new display on the stage its computer field in the display dialog will be empty, you need to fill in the name. Why would you want to do that? You change the name the same way you assign a name, through watchmaker's Network Window. Yes, they are different things. For additional information, reference: v5.5+ computer name - fundamental change in display dialog address assignment

As you note, that behavuor is user definable, to provide detail on that ... File - Preferences : Control - MIDI Show Control / MSC Cue Lists WATCHOUT 5.5.1 The default setting (Ignore all MSC commands with a cue list parameter) will result in nothing working on most consoles, as the console will always send a cue list parameter. Seems with most consoles, effectively, you must choose between main timeline only or auxiliary timelines only. Control systems can do both of course. reference: WATCHOUT 5 User's Guide version 5.2 Appendix F MIDI Show Control page 275 Some MSC commands allow a cue/list/path to be specified. WATCHOUT doesn’t use the “path” number. The “list” number can be handled in either of three ways, as specified in the WATCHOUT Preferences: • Ignore Command. In this setting, the entire command will be discarded (not acted upon) if a list number is specified. • Map all to Main Timeline. This setting ignores the cue list number, sending all such commands to the main timeline. • Map to Auxiliary Timelines. If a cue list number is specified, the command will be applied to an Auxiliary Timeline with the same name (where the name must be numeric, to match the list number).

In what context are you encountering this error? We would see errors like that with MIDI in older versions, what version are you using?

OK, no issues with that version. Did you follow up on Jonas suggestion? i.e. Before you can access VNC, you must have the Stage Window as the current active window and you must select one of the display rectangles associated with the computer you wish to access. Until you have done that, VNC will be grayed out.

ugh, 5.3.1. Assuming you have performed the proper prep Jonas suggests. Something else to try. Open the WATCHOUT installer. Select Repair and Run Repair. When the repair completes, let it sit on the finish screen a couple of minutes. Then click finish and try watchpoint again. We did not typically see Win 7 OS errors when the original 5.3.1 installation did not complete, but we did see similar errors in both watchmaker and watchpoint, refusing to recognize movie formats that it normally would. Repair with extra completion time would correct that, possibly this is something similar with a Win 8 twist?

While it is technically possible to do both, rarely does a lighting board support that. It is usually either main timeline only / or auxiliary timelines only with lighting consoles, based on the WO preference setting for handling cuelist values. On the other hand, with Q-lab you might be able to pull it off. To control the main timeline with cuelists mapped to auxiliary timelines, you need to send a MSC Go cue # with no cuelist value. With the cuelist value missing, it is still a valid command, as the cuelist value is optional in the MSC spec. But that is probably not worth the bother, you are going to have to use at least one cuelist to achieve two separate asynchronous cued timelines, you might as well simplify, and do it all in aux timelines and leave the main timeline out of it. Using MIDI note as a relative 'next cue' trigger is not as reliable as using MSC as an absolute 'go cue #' trigger. I guess you could use a different MIDI note for every cue, but that would be a major pain to program in WATCHOUT compared to MSC. If you can get MSC working with cuelists, and I suspect with Q-Lab that is easy enough, then MSC would be better.

Depends on how you are going to tell the system when to complete its loop and move on. Personally I only thing in cluster mode playback, so ... Say you loop and free run a composition from a paused timeline. If I interpret correctly, on command, the loop should continue to its end one last time and then roll into the next cue. One way I can think of is to control an input device from an external source that can maintain the on state - tcp/ip, midi note (maybe), midi controller, ArtNet/DMX. A second input device is to be controlled by the looping composition itself. (and yes, there is an advanced trick to this using localhost and sending the setInput cluster command to itself.) The composisiton should set its input to 100% for about 1/4 of a second at its roll out point and then return to 0%. A task with a triggering condition of both inputs True then releases the looping composition via a control play cue pointed at the paused timeline with the loop. There may be a better way, need to let the idea "breathe" a little longer

Technically, stopping early is much easier than starting after the beginning. I suspect in-point is less intuitive because it is not the best way to do that. There is no reliable way you can set your in-point to target a key frame. As a result, a lot of calculation may need to be done to successfully do this. That is why i recommend a manual pre-roll, to allow as much time as needed to get the new start point ready. Rolling through a file and ending early is much easier than in-point. When you edit the file, the first frame is always a key frame, making the start easier / more reliable.

Did you try manually entering the In-Time: in the Video Cue specifications? Depending on encoding, this can be a challenge, you may also consider a long manual pre-roll when using this feature. It is better to edit the video for the correct in-point.

BTW There is no one and only right way to do this, there are a couple of ways, each with their own set of implications. Yes you can. That will work. Or you can put the housekeeping in each auxiliary timeline. i.e. after one timeline starts, add control cues in that timeline to tell all other timelines to jump to 0 and pause. Then you can use simple input triggers (MIDI, tcp/ip, etc) to trigger one aux timleine and let each aux timeline clean up the others.

Simple answer is no. The function you desire may be achieved in another way by using auxiliary timelines. Depending on the number of called cues needed, you may be able to keep them all loaded (paused) for immediate access without the black interval. An inactive auxiliary timeline (stopped) will still need time to load when asked to play from the stopped state, the same as jumping within a timeline.

We have successfully used some of the Focusrite Saffire Firewire interfaces. Nothing to do with WATCHOUT, but the Focusrite Saffire Firewire interfaces are sensitive to the Firewire controller used. Best source for info on that sensitivity is Focusrite themselves. Focusrite Reference: How can I tell if my Firewire chipset is compatible with my interface? Note: the WDM drivers for these devices will only provide eight channels of output. Furthermore, the WDM driver output mapping under Windows 7 seems to have changed a bit. We have encountered situations where channel 9 and 10 in the audio file map to outputs 7 and 8 on the audio interface and channels 7 and 8 in the audio file do not map to any output.

You would need an active dual link DVI adaptor for that resolution. something like: StarTech DP2DVID DisplayPort to DVI Dual Link Active Converter – USB Powered

WATCHOUT version?

I have seen that happen from an installation of VNC - I know, it does not make sense, but it turned out to be the cause. Some VNC variants can be quite disruptive to WATCHOUT Accidentally copying the display software to startup items (instead of a shortcut), but that does not sound like the case here. Also confirm you do not have two instances of watchmaker running.

That statement kind of confuses me. The BlackMagicDesign DeckLink Quad has been around for a few years now. I do not understand that statement. It is best to use Windows 7 64 bit when using BMD capture cards. Never had any memory issues with the Quad. We have been building them in our computer offerings for over two years now. It works as well as any other BlackMagicDesign capture card. The HD-SDI connectors on the quad are not the mainstream BNC connectors. The DeckLink Quad uses DIN 1.0/2.3 connections rather than larger BNC type connectors. i.e. Molex, Winchester, Canon, Switchcraft, Canare, etc.

No, there is not. The normal procedure is to take the audio from your tuner through an audio delay and then to your sound system. (An item such as the Rane AD22S Audio Delay).

I have seen this occur when Windows is set to hide known extensions, which can be deceiving. A quick test to check to see if this is the issue is to change your shortcut to the command file name Cmd.txt.txt

You can assign a layer to function in standby in the Layer Settings dialog. Select the layer and choose "Layer Settings" in the Timline menu or double click on a layer name to open the Layer Settings dialog. Under the setting Perform: choose In Standby All cues in that layer will now be visible in standby only. You may have as many standby layers as you wish. If you define no standby layers, or no standby layer cues at the time position when standby is entered, standby will fade to black. If you remain online and move the timeline cursor, the standby cues for the new time position will be displayed. A single standby layer cue lasting from 0 to the end of your show will make that undectable. Also note: Preview may perform differently than display when entering Standby. This allows you to work offline in production and see the show content while the system is in standby. You can change the preview standby behavior in the Preview menu, reference: WATCHOUT 5 User Guide, page 103

Right there defines either six digital output or five analog output maximum. Stop that! Once you do that all bets are off. Do not plug a vga (analog) adaptor into a digital only DVI-D connection. Yes, I know some of cards provide a DVI-I connector for a DVI-D restricted port, that is so a DVI-I cable can be used for the digital signal, not to provide VGA output. that output configuration is not capable of six vga, only five. You might be able to use a digital to analog converter, but that is not what an active adaptor does.

I need to check, I thought Catalyst Control Center setup the DisplayPort 1.2 output. Should not need a driver specific to the hub, but let me confirm that, kind of busy around here today so may take a while ...

Show Sage has been testing the Club 3D MST hub. While we are successful in obtaining three outputs, we have not tested enough to certify its reliability. Initial testing did indicate some stability issues that may be related to heat, as they appeared later in the testing process and we ran out of time to track them down. Will report back after out next bench session.