keitht

I am just guessing here... but do you have any layers in either of those timelines that have a blend mode (screen, multiply, etc...) other than normal? That would cause what you describe. -kt

I'm just wondering if we are only talking about the Display software here? I run production on Windows 10 just fine. Anyone else?

I concur. I was the source of that link posted above by Jim. With Hap v8, Watchout played consistently. Individual files were good, but there was consistently a problem with playing them in PreSplits. The problem with 8 was the ENCODER was crashing on Windows. He fixed this with v9 - but now the movies have issues in Watchout. It was a bit inconsistent and hard to nail down - but I concur, there WERE issues. Unfortunately I am not in front of any v6 keys to test more at the moment, but figured this info might help other identify (reproduce) the issue. Here is some notes I had... wondering if Pertti has the same symptoms. there was inconsistency I never worked out (I was not getting the same result every time it seemed). In addition to the color issues on presplits.. some hap movies (both individuals and presplits) did not play at all. No error… but when I would jump to that area of the timeline the movie would not play - kind of strange situation. There is no error message. If there is something already displayed (either from previous location on timeline or even the WO logo), the previous item REMAINS displayed, as though I never jumped the timeline to this area. Very strange.

Yeah - I thought so. If that were the case, I could set them in Production and save them there. What I want is to adjust on the fly with sliders in WatchNet - then have them save. Back to ye 'ol drawing board. Just saying... if WatchNet could at least give me feedback of exact values, then it would be easy to go hard code them back into Production and upload. Thanks Mike - hope your doing well. kt

I am using WatchNet to control a few clusters. I have some buttons and sliders that control Generic Inputs that do things like volume, mute, brightness, contrast etc... These are settings that we want to be able to adjust during setup and save for the run of the event. There are 10 identical events over the next year. Is there a way to adjust sliders (inputs) in WatchNet and have the cluster SAVE the show so that the inputs are saved? So, when we power down for the night and boot up in the morning (all done with WatchNet panel), the inputs are not reset to defaults originally saved in the .Watch file? P.S. I am talking in 5.5.2. If v6 has something that will solve this, I can take this show up to v6. Thanks, keith

I don't agree. I always have edid managers in line. I also alway have full running backup systems. Therein is my problem, not just getting the system to remain consistent (which typically works as long as you keep the same connections there on reboot), but matching output numbers and ports from the primary to backup system so they are identical. Currently I employ this solution. Reboot clean with only 1 connection. Go into windows display properties. One by one plugin the next port and extendl the desktop. Most of the time, windows adds them in reverse order (the newly attached port =monitor 1), and (most of the time) watch out IDs the displays as 1-x in the order attached. I stress the MOST OF THE TIMES because sometime it inexplicably does different things, puts the new display in a different order or watchout's I'd #'s align differently to windows id's. I recognize this is mostly a windows issue, and would love to find the utility that can help manage this(please post that link to the fireproof utility if you can find it)... BUT I would also like to understand and be able to predict what is going to be the order in watchout based on what I see in windows display properties. Can anyone shed any light on that? Thanks for listening!

Mike, can you post a link to that utility?

I am experiencing a color shift (washed out saturation) when exporting movie. Even when saving to Uncompressed. Has anyone come across that? A solution perhaps? Thanks, kt

Not that it ever bothered me much, but I have seen this behavior many times. So, now you know it is not just you.

If others are interested. I have success with Echo AudioFire12. All 12 channels work under XP. 8 channels work under Win7 (Echo is working on getting it to 12, but does not sound like it will happen soon). I hope this helps.

I second that!