Search the Community
Showing results for tags 'stills'.
This is a multi-part question: I occasionally get tearing on stills in Watchout. It doesn't seem to be consistent, and I can't quite nail down why. It's almost always big stills...8k, 9k wide. I've tried different file formats and nothing seems to be the silver bullet. So the first part of the question is, what part of the computer does the heavy lifting of fading a still? Is that the GPU or CPU? And would additional system RAM or video ram help that? The second and related question is using sync cards between machines. We have traditionally used AMD cards with the s400 sync modules and had good success. However, we have been moving to nVidia Quadro cards (M4000 and P4000) as they benchmark at better performance and have much more flexibility in the software. We have the appropriate Sync I and Sync II modules. In my current scenario with two display machines using these nVidia cards and sync modules, I have set them in various configurations: to be external sync on both cards, external sync on one card feeding sync the second, and internal sync on one feeding the second. In all cases, I still intermittently get tearing between machines. It doesn't seem to happen on the videos, but does on stills. Curious what's happening on the back end which could cause this. And finally, can someone elaborate on what the "sync chain master" checkbox does under the hood? Does Watchout actually talk to both the s400 and Sync I / II modules? If you are using external sync to each module, does this checkbox still matter, as there's not really a "master"? I have also found when I make an adjustment on one display machine (say re-launch Watchout), sync struggles until I re-launch on the second machine. Is this expected behavior? Just trying to understand the technology better so I can fix things quicker in the middle of the night on a show! Thanks!
Hi, We recently had a show that we updated from watchout 4.3 to 5.1 to use the multiple outputs per display computer and we ran into a couple issues. We had 1 production and 2 display each driving 3 outputs. Watchout machine specs CPU-Core i5 750 @2.66 Ram-4GB GFX-AMD Radeon HD 6970 2GB GDDR5 Mem Win 7 32bit HDD-Solid State drives Rack Mount cases First and main issue was: every time we would change the output # on a display computer it would re-send all of file into the computer even though there files were already there. This certainly caused some slow down in the production. We had to change output # for troubleshooting purposes. But this would also be done if we would need to switch to a back up display computer in which case it would be a problem. 2nd: The auto-detect of the alpha type for stills wasn't detecting properly. This use to work just fine in watchout 4 but in 5.1 I had to go specify the type of alpha for each media. That only seemed to happen on stills. 2nd and 1/2: Hard to say exactly what happened here but 1 night we made some very specific masks and put them into the show. All was well then but the next day when we turned on everything the masks were not the same anymore. (I do not have all the details because we had left by then) I asked the watchout technician onsite to try to play with the alpha modes, I also re-sent him the files because maybe they had been corrupted but in the end he had to re make the masks from scratch. Very strange. Any thoughts on that? 3rd: The production computer is getting TCP command from a medialon machine in this installation and at one point i turned off the triggering so I can work without being triggered but I was still receiving the commands. What do you think? Thank you.