Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

632 profile views

DavidPatrick's Achievements


  1. I've confirmed this also happens with still image files, so it's not only videos. That makes me think it's not framerate related. And they are pretty small images at that. I'm going to send a test file over to dataton support and see what they say.
  2. I have several video files in a show which have match frames - i.e. the ending frame of video one is the same as the starting frame of video two. When I butt the two videos together (either on the same layer or on different layers) I get drop outs. Meaning Watchout shows a quick flash to whatever is below when it rolls past the break in the clips. To solve this, I have to overlap them between .1 and .2 seconds. Sometimes this is an acceptable workaround, but sometimes it doesn't due to the animations. Is this expected behavior? Is there anything I can do to eliminate these flashes consistently without overlapping? Is there anything which would impact this which I can avoid or change (framerate, codec, etc)? All content is currently at 24fps, running the system at 30Hz. All files are chunked HAP. Fast HDDs and solid video cards. I can't say for sure, but I recollect I have done this before in previous version of Watchout and not had these issues. Currently using 6.2.2.
  3. @matkeane Thanks. I'll give it a look - that might be a good option. @Benoit I'm currently running WO 6.2.2, but can't see a way to load a video into DIS. Inside the program you are limited to JPG, TIFF, PNG, SWF, or HTML. And inside WO, you can choose image, flash, HTML, or Desktop. I'd love if DIS supported video files - doesn't seem like a stretch to incorporate them.
  4. I confirmed via testing today that the Scan Converter app is not compatible with Watchout Display. Once Watchpoint goes full screen, I only get a black output.
  5. A further update: The NDI plugin for VLC only works with VLC 2.x. (An update to NDI is supposedly coming...) However, alpha channels are only supported in VLC 3.x. I have some other options for an NDI source, such as Millumin and ProPresenter, but have not dug into those. I think the death nail on this may be sync. Even if I can have a simultaneous fire of both Watchout and my second video source, I don't believe the NDI feed will ever sync with the video pieces local to the display machine. I also attempted to use the NDI Scan Converter app on a display machine to have Watchout act as the NDI output, but apparently when Watchout goes full screen it prevents NDI from sending the content. I was only able to see black.
  6. @Benoit That's fair. In this case it's for speaker titles during a show. The client wants nice, animated titles, but may not know the order or even the name of all the presenters before the show starts. Since Watchout will be live to screen, I won't be able to ingest new media later in my timeline without interrupting what's already live to screen. This means someone from the content team would render titles during the show, then we would live composite those with existing backgrounds. We can do this with a downstream key in a high res switcher (E2, Spyder, etc), but I was researching options to keep it all inside of Watchout, reducing the complexities to a single operator. NDI seems perfect if I can fit all the pieces together.
  7. Sorry about that. Yes, video. Ideally HAP Alpha, though any QuickTime flavor is probably fine. Animation with alpha, etc.
  8. I'm considering using the NDI VLC plugin to play clips. The biggest thing is I need to be able to trigger my main timeline and my alpha clip at the same time, so my third party playback software needs to accept TCP commands I can place in my WO timeline. @Mike Fahl Thanks. I read the article, but as I understand it Dynamic Image Server won't play back video files, only stills, flash and HTML5. In my case they'd need to be actual videos I think. I wish DIS would support video, especially since it's based on NDI now.
  9. I've notice when adding an NDI media element there's an option to choose one with an Alpha channel. Can someone give me more information about this? How do you output the NDI stream so it supports the alpha channel? In my quick looking in the NDI Scan Converter tool there doesn't seem to be any options for this. Is there specific hardware / software which supports this?
  10. We have also had good success with Magewell products. They sell dual and quad input HDMI cards. http://www.magewell.com/pro-capture-family
  11. Has anyone tried using the NDI Scan Converter software running on a display machine to act as the NDI output, then feed that back into Watchout to be used elsewhere? In my case I need to add media to a timeline during show, so I need a separate system to do this. But that content needs to be live composited on top of existing content in my main timeline. And it all needs to be triggered simultaneously. Seems like using NDI out on one display machine and NDI in on the main system would work nicely, then IP commands to make everything fire simultaneously.
  12. Thanks Mike. Sorry for my lack of detail. Good info to know. We have had lots of other issues on this show, so I can't entirely isolate the cause. However, after some reworking of the sync signal and EDIDs on the graphics card, this seems to be resolved. I'm going to chalk this one up to weird refresh rates in the chain.
  13. 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!
  14. We have both the FCA610 and 1616 boxes, and they work very well for us. 6.2 will add ASIO support, which opens up a lot of options.
  15. I've also found it can be due to the placement of your cues. This may not be the actual "cause", but separating the pause cue back from the media cue (back the pause cue up .5s for instance) seems to help. This extra time may give Watchout a chance to push / receive the command over the network despite the traffic, and results in the display machines not moving on to the next piece of media. Give it a try. That's usually our workaround when we don't have time to suss a network issue.
  • Create New...