jfk

Additional delay compared to progressive, yes. 'Too much' is a personal judgement. ymmv

I do not believe replacing the camera will change anything. I see you are using interlaced signal inputs. Those have to be de-interlaced on the fly and I am pretty sure that task is performed by the cpu. Likely your cpu / motherboard / memory subsystem is hitting its threshold deinterlacing three streams. You will likely need to upgrade your computing power to achieve four without stuttering.

NO. It will go to a control cue in the main timeline named "TOD" and sit there. If that control cue does not exist on the main timeline, it will do nothing. If you want to play an auxiliary timeline named "TOD", you would send run "TOD"$0D If you want to jump to a control cue in an auxiliary timeline, you need to include the optional parameter 'timeline name'. So to jump to a control cue named "example 1" in an auxiliary timeline named "TOD", you would send gotoControlCue "Example 1" "TOD"$0D an then if you wanted it to run from there, you would send a second command, run "TOD"$0D

Almost got it right. Needs to be gotoControlCue "TOD"$0D How is your output device setup for the second production computer?

And specifically, my post #7 under the topic - Remote Controlling with Watchout Problems is a "how to" for setting up and controlling the dowser of Panasonic projectors using the PJlink protocol.

That is not necessarily correct. Depends a lot on content and programming. The GPU does a lot of the work. reference: Mechanics of WATCHOUT Yes there is. No synch issues with two MST hubs driving six outputs that we have observed in our testing. We have been testing with a FirePro W7000, Windows 7 SP1 64 bit, WATCHOUT 5.5.1 and another system with a FirePro W8100, Windows 8.1 64 bit and WATCHOUT 5.5.2b The W7000 is a bit underpowered for six outputs and there is a noticeable degradation in image quality driving six. The W8100 system does not show this degradation, although under prolonged testing, it appears to be overheating. BTW We recently received a new model of MST Hubs (StarTech), and this version is passing durability testing so far (Club 3D failed durability testing). Will update again when the testing is completed.

We have been using the ATi FirePro 9100 for six outputs on over a dozen systems now and it works well. As for those tempted to use the FirePro W600, beware, the GPU is a bit weak for WATCHOUT. The W600 is targeted at home video applications, not so much for DirectX 3D accelerated apps. If all you are doing is video playback and very little with tween tracks, no masking, no keying, etc. you might get away with the W600. That implies you have control of the content and its programming.

Quick way to the head of a timeline is three keystrokes - , 0,

FYI directions on how to use WATCHOUT Remote can be found in chapter 2 of WATCHMan User's Guide.pdf, archived in the WATCHOUT Systems Manager download. The screen layouts on iOS may be slightly different, but the function is pretty much the same.

From a GrandMA? Why and the world would you not use MIDI Show Control for that? MSC is a cue based protocol, and triggering auxiliary timelines is cue based. DMX is a level based protocol, makes little sense as it relates to cues. I guarantee you MSC would be far more reliable. DMX input was meant for live tweens, not triggering timelines. Obviously you can make it work, but I would not be surprised by strange behavuor with such a hack. Nor would I spend time trying to track down anomalies with that method. Using DMX to trigger timelines reminds me of an old adage, 'when all you have is a hammer, everything tends to look like a nail' But with a GrandMA, you have more than just a hammer, there are other useful tools in that toolbox, aka MSC.

How are you determining that? What tween formula are you using it in?

Yes. If you had searched this forum you would have found examples of that. reference: 4K Video Playback , Supported 4k / High resolution video cards - Single Output You would be best served with 2 powerful computers for that task. Show Sage can provide computers tested and certified to run 4k movies to 4k outputs. If you plan to build your own, start with a i7 six-core on a motherboard that supports quad channel memory and a graphics card that is specified to provide 4k output (AMD FirePro cards with four digit model designations, aka FirePro 7100, etc.) are a good choice. You will need to do your homework and test to confirm a system that can handle the task.

That is not permitted and is not going to work unless you use dynamic image server to accomplish it. It is not that simple. No. Sounds like you have two copies of watchpoint installed in different locaitons. Also not a good idea. Either that or you did not follow the first recommendation when preparing a display and UAC is not disabled. not weird - expected. That is because still image files do not play back from the original file. They play back from the cache that is created when WATCHOUT Production (or WATCHNET) transfers the file to display. Dynamic Image Server would provide the function you seek. Comes from the cache folder, and you do not get to mess with that data. Nope. WATCHNET can provide the function as well.

Yes, all four outputs can be displayed simultaneously on any and / or all displays connected to the computer containing the card.

For all practical purposes WATCHOUT is ready to handle any user installed DirectShow codec. Third parties seem to offer HAP DirectShow codecs. If this is true, then installing them on your production and display PC would provide HAP support in WATCHOUT. Of course, you are then at the mercy of the third party supplier for support with that codec. ' For example, seems a group called RenderHeads Limited offers what they describe as FAST GPU FRIENDLY VIDEO CODEC FOR WINDOWS HAP FOR DIRECTSHOW Not that I know of - you can be the first

Also, the DataPath driver is far less finicky than the BMD drivers. i.e. DataPath is far more forgiving regarding signal settings than BMD, resulting in higher success rates when setting it up. We have not tried the DeckLink 4k card, but we have successfully used the DataPath DL-DVI card to capture 3940x2160@30p. May also be related to WATCHOUT itself. That issue is the same for BMD and DataPath. The workaround is to open the input once and keep it open. reference: DataPath input freeze Dataton preferred would indicate Dataton takes some responsibility for something completely out of its control. Don't see them doing that. Motherboard, driver configs, other options all interact to determine that success. That responsibility lies with the hardware vendor. That said, as a hardware vendor who does support these things, hands down, I would choose DataPath over BlackMagic Design every time, if budget is not a consideration.

Yes. But if you have a control system to ask that question, why not use that system to load the show? The load command establishes the cluster, and at that time, the response will indicate any issues. for example, here is the response when one output was missing at load ... load "myshow" Busy "Establishing Cluster" "" 0 Error 4 -2146950355 "Address not found: WO2; Display \"Indoor06\" of Stage Tier \"Indoor\" of Stage" Busy "Cluster Established" "" 0 Otherwise, getStatus should provide what you seek.

Certainly. If you search this forum, you will find more than one thread on that. Depends on the signal type. For HD-SDI 720p / 1080i or lower resolutions, the most cost effective way is with a single BMD Decklink Quad. For higher SDI resolutions, two DataPath VisionSDI2 would do the trick as well.

Do you have access to any method of monitoring the MIDI data? Midi-Ox or some such. Edirol is not my favorite vendor, weirdness from their products would not surprise me in the least. Toss in customized software and .... Monitoring the MIDI channel may reveal something. I have assisted with a few switch closure / MIDI Note systems that do not act like that. Pushbuttons (simple switch closures) trigger shows (aux timelines). Used MIDI Solutions F8 in multiple systems. (once you get it setup correctly, bulletproof) some with a MOTU Fastlane USB and an some with an off brand simple MIDI-USB adaptor. No anomalies.

Since he is using a FirePro, I assume he means the new EDID management in the Catalyst Control Center. OP want to clear that up? Sierra Video Group Multi-viewer Like most guys who own them, it allows you to view multiple outputs on a single display. Often used for in-house testing / production before connecting to the real displays on site. It was other producers with the same idea who discovered they are often not valid for synch evaluation. (using FirePro with s400 scanlock) Just the same, that means the graphics card is connected to another processor, not directly to a display. So for tech check-out, when display signal anomalies occur with such a setup, it aways makes sense to keep it simple by isolating the problem. First step in doing so is ...

As has been said above, this is a computer preparation issue. Integrated graphic processor and discrete graphic processor on laptops is not all that new, just becoming more mainstream. Been running a production laptop with such a setup (Intel / nVidia) for three years with Win 7 and no issues at all. Work with your hardware vendor to determine where your comptuer preparation is awry.

It most likely disappeared because it crashed. If the display logo screen appears, the watchdog has cleared the crash and reloaded watchout display. Subsequent behavuor depends on mode (production or cluster) Delete it and make a new one. That sounds really optimistic for that hardware. Movies are progressive or interlaced? Frame rate matters too. Encoding will play a role on success. If you are not seeing a logo screen the EDID signal may be causing issues. You would not be the first to experience anomalies with multi-viewers. Don't trust the synch you see on those things either, they have been known to insert different delays on different inputs. OK, what happens on the display after this message is seen? Jim The switch I am using is a HP 2530G 24 Port Switch (I have an unmanaged switch arriving today to test too). Any ideas what is causing this show stopping problem? Is it Network? Media? EDID? Something in Windows? Any help would be greatly appreciated! Many thanks, Rob

Either take the opacity down to only 3%, or, if you are not using standby, place a live video input cue the length of the timeline on a standby layer. Reference: Datapath Input Freeze

all that is correct ... Yes, that would be preferred. Yes, using two outputs would provide you the ability to independently converge each projector using WATCHOUT's geometry control. You therefore create a display object (rectangle on the stage) for each projector. Use Stage Tiers to create a new tier, and then place one projector on each of your two tiers at the exact same stage co-ordinates. (maybe name the displays top and bottom for clarity) Overlapped stage displays (projectors) only blend when they are on the same tier. So for double stacked single converged projectors you want to place each on its own tier. (If both were one the same tier, each would run at 50% opacity to create an un-needed blend. ) If the projector setup provides that function, that is an alternate option. Should you choose to use a projector's geometry functions instead of WATCHOUT's, then I would recommend using a single WATCHPAX output / single stage display object and a 1x2 DVI splitter / distribution amp to feed the two converged projectors.

First off, WATCHOUT does not care about the format of the input signal. There is nothing inherent in WATCHOUT that would prevent this. But that is not the issue, the issue is the signal type and capture hardware / driver, not WATCHOUT. Yes, WATCHOUT does support RGB 4:4:4 input. The DataPath VisionRGB E1 and E2 (SL DVI) both provide that type of signal to WATCHOUT without any issues. Somebody correct me here, but by definition, is not SDI limited to YUV? I have never heard of RGB signals over SDI. So the conversion from your computer to SDI is the cause of your confusion, what you observe is normal for SDI signals.