zackboyd

I think I understand what you're doing? You have a play cue then a pause cue at the top of your aux timeline to pre-load content? I tend to put my pauses for preload 0.5 seconds into the timeline without any issues. It allows a little bit of breathing room for the control cues to fire.

Make sure your resolution and framerate in Watchout Production match your hardware settings. Also try using EDID emulation in the Firepro control panel.

Often times with BMD capture cards, this comes down to a framerate thing. Try halfing the framrate(if you're at 5994, try 2997).

What lighting console are you using?

I thought the framerate preferences in the showfile directly affected this. Am I wrong?

Double check that your project framerate is the same as the displays. Also make sure your resolution in watchout matches that of what your display servers are set to.

This is one(of the many) reasons I don't install quicktime on my machines.

I use AMX, but have seen others deploy this using a custom app written in C#.

I've done this many times successfully, but you need some sort of intermediary interface to translate the tracking system api into watchout api using setInput. From there, the sky is the limit.

I usually put a half second at the top of my aux timelines to allow load times, and extend the preroll time to allow loading if a cue has a lot of processing in it. Always better to play into something than to start right at it. Try that and see how it goes.

Try RTE 1$0D$0A

I thought watchout wasn't supported on Windows 8? Could that not be the culprit?

Haven't done it on a 3D object, but synced 2d content to position and rotation tweens based on automation data many times. I'm not sure why your initial idea wouldn't work.

I've definitely had some weirdness with comps. That'd be my first guess. Also, are you sending sync to your capture card? The sync module is only for the outputs.

I've experienced similar issues across 5 and 6 with a hang on boot, but fine after watchpoint restart. Every time it was related to quicktime. I'm pretty religious about not having quicktime installed on my display machines. Try uninstalling and see if it persists.

The tiers still work if you use masking instead of the blend functionality.

Have you tried using a null modem?(swapping pins 2 and 3)

2 Things: I typically give my aux timelines(which is how I typically organize all my video cues) a .5 second buffer at the start, ie the whole timeline starts at .5 instead of 0. Just to allow the automatic preroll to take effect. Also, in some situations with live inputs, I've found it necessary to add a black solid above it, and adjust opacity on that to do live fades. If you allow that to roll for roughly half a second, the live input will have been activated beneath it, then the fade occurs. I know this is a 'hack', but I don't believe this is a watchout problem, I believe this is related to the capture card driver activating the capture card's input stream, but I'm sure one of the guys who knows the inner workings of the software better can elaborate or correct me.

I've used the extron extenders many times, and they do indeed pass EDID without flaws right out of the box.

You could position the camera in the stage to view the 3d model as you like, then export the show as a movie.

For 3D mapping alignment, I've found I was forced to turn live update on, is that not the case? Am I doing something wrong?

Would ya look at that! My mistake. Sorry! I've had such a bad taste in my mouth from display servers with Radeons, I immediately shuddered at the thought... still a little offended by the name of the card, hah!

I stay away from the radeons - have had a few issues. I love the firepros. And getting a firepro is the only way to have EDID emulation on the AMD line.

This doesn't account for the fact that the problem is fixed when he has the exact same cue setup(one video multiple times) and then changes the video file on five of them and the problem goes away. I'm travelling and don't have a rig with me to test right now but now I'm very curious. Z

I've used the Duo many times over. A little quirky and requires correct configuration in the driver and watchout, but solid and the price is right.