Jump to content
Dataton Forum


  • Content count

  • Joined

  • Last visited

About matkeane

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

350 profile views
  1. matkeane

    Changing layer conditions with String Cues

    I'll take Mike's word for it that it's OK to force all conditions to zero - although I've also added a switch for it, just in case the default behaviour is useful in some circumstances. And, after a busier couple of weeks than planned, I found time to Mac/Windows builds of my helper app, which can be downloaded from my website: https://matkeane.com/project/watchout-conditional-layers-utility. The readme file in the zip has some instructions but, basically, conditional layers can be switched through the UI, or via UDP/OSC commands. The UI controls can be disabled if only network control is required. In addition to switching individual conditions, they can be assigned (in the UI) to groups and presets for more flexible recall and switching.
  2. matkeane

    Toggle layer conditions from within watchout

    I'm quite happy to share once it's ready - I already have a couple of other utilities for Watchout on my website for download. I'm working on loading/saving settings for the app, since setting things up manually each time gets a bit boring and after that it should be usable, even if it's not going to win any awards for UI design! The apps are all developed in Java, since I generally work on Mac but want something which will work on Windows too. I have thought about switching to another language, but I've yet to find something really suited to cross-platform desktop development with a decent UI library (If anybody has any suggestions, I'm all ears). I have a project coming up in a couple of weeks where the app might be useful, so I should have something to share quite soon...
  3. matkeane

    Toggle layer conditions from within watchout

    I'm pretty sure I added a feature request a while ago for the ability to change a single layer condition from within Watchout. Like you, I'd like to be able to change one condition without affecting others - effectively impossible without storing and recalling all the other layer condition values. This would make it easier to use conditions to manage the visibility of content. I also use conditional layers to manage the 'visibility' of layers containing control cues, which allows some simple switching logic within Watchout. I agree that 'setLayerCond x 0/1', 'enableLayerCond x' or 'toggleLayerCond x' would be useful additions. With this in mind, I've been working on a little external control app for managing layer conditions. Still a bit rough around the edges, but it allows for: toggling or setting a single layer condition, creation and recall of presets, groups of conditions with different behaviours (radio buttons, synched, etc). Layers can be switched through the UI, by UDP commands (from Watchout or elsewhere), or by OSC commands (not from Watchout!).
  4. matkeane

    Changing layer conditions with String Cues

    That's interesting and potentially very useful, but I wonder if it's intended behaviour, or whether overflowing the expected maximum value just happens to result in all conditions being set to disabled. I wonder, because I'm working on a little utility to make managing layer conditions easier for me and, shortly after trying 1073741824 instead of 0 to turn all conditions off, my Watchout production machine became unresponsive to further enableLayerCond commands and eventually crashed WatchMaker altogether. It could just be a coincidence or another bug in my app of course...
  5. matkeane

    Jump cue causes still image flash

    I've seen this behaviour before too when trying to jump between control cues in a timeline, in earlier versions than 6.2.2 and I think as far back as v5. The workaround I found was to split the background (unchanging part of the loop) from the foreground in two separate tasks so that I could fade the background image in and out in one task, and then jump between cues in another task. It works most of the time (still not entirely reliably) and complicates the programming a bit since you now have twice as many tasks to manage.
  6. Just guessing, but is your 3D object a very complex model? I've experienced Watchout production becoming unresponsive in the past when I imported a 3D object with a very high vertex count. It's just possible that in your case, the production machine managed to import the model, but the display machines are struggling and appear unresponsive. The Watchdog process running on the display machines may have launched a second instance of Watchpoint, if it appeared that the first instance has crashed.
  7. matkeane

    NewTek NDI with Alpha

    When I was looking at different playback software to try and find a solution to the seamless loop issue (http://forum.dataton.com/topic/2838-getting-out-of-a-loop-at-the-end-of-loop/) I discovered Mitti (https://imimot.com/mitti/) which not only makes the looping question very easy to manage, but can also output NDI with an alpha channel and can be controlled with network/midi/dmx commands (although sending OSC commands from Watchout is still a sore point). I managed to get a 6400x1200px HAP alpha file playing smoothly over my Watchout background using an NDI input. More expensive than VLC - obviously - and some of the alternatives, but I'm still tempted to buy it because it seems both versatile and very simple to use.
  8. matkeane

    Audio bug in 6.2.2

    Did you by any chance open an older project in which the audio files were already imported? I had a similar problem recently with audio not playing in a old (probably 6.0.x) project from last year when opened in 6.2.2. When I looked at the audio channel configuration for the cue, no audio channels were recognised. I had to re-import the media (double click the cue in the media window to reselect the source file) to force Watchout to update the media completely - a simple refresh didn't seem to do the trick.
  9. matkeane

    standby from timeline

    I've never actually tried this from a timeline, but 'standby' is listed in the manual (p164 in the 6.1 docs) as one of the available network commands, so it should be possible to send a TCP/UDP output string from a timeline with something like 'standBy true 1000' to enter Standby.
  10. matkeane

    Project challenge

    Assuming the forum moderators have no objection to blatant self-promotion, I built an app to help with display layouts like this. Enter the screen resolution and dimensions, the offset between screens (use a negative value for the overlap), and the app works out the stage size calculations for you, ready to paste into Watchout. You can download it from my website: https://matkeane.com/project/watchout-display-builder-softedge-calculator The version currently online only supports display rotations in 90 degree increments, so there's one display in your layout you'd have to tweak by hand. Also working on supporting virtual displays as well as 2D displays.
  11. matkeane

    HAP Encode / QT / Etc

    It's not listed on the VLC features page but, according to recent posts on other forums, version 3 of VLC player does now natively support HAP playback. It seems to work, but with a HAP-alpha file, the edge of the alpha channel looks a bit nasty (flashing pixels) on my machine. Standard HAP files seem to play fine though.
  12. Hi, In the past, my solution to the port closing issue was to create a looped task in Watchout which fired a blank - literally "$0D" - command to the projector every 10 seconds to avoid the connection timing out. My real commands for the shutter could then be sent once when needed and worked reliably and on-cue.
  13. matkeane

    Watchout 6.2 Mask/Edge Blend Issues

    Watchout applies edge blending when Displays overlap on the same Stage Tier. If you move the stacked/overlapping Displays to another Tier things should probably behave as you expect.
  14. matkeane

    Feature requests? - POST here

    I think the comment by Dimi (http://forum.dataton.com/topic/794-feature-requests-post-here/?p=11737) about finding another way to manage feature requests makes sense. There are also some handy tips hidden away in this thread, but without paging through all the comments people are unlikely to find them. Maybe another sub-forum could be opened so that each request could be in its own thread without making this main 'Watchout' forum too noisy. A thread-per-request might make it easier to gauge user interest, and it would also be nice to get an idea of Dataton's feeling about a request - whether it's "yeah, we're thinking about that" or "won't-fix, deal with it". Funnily enough, the idea of a layout tool for Displays was mooted on page 1, didn't get much support, and has now been implemented in v6.2. Meanwhile, the request for a way to organise the Task window has received several positive comments, starting on page 2 of this thread back in 2012...
  15. matkeane

    Getting out of a loop at the end of loop

    OK, I'm trying to be positive here, but I apologise in advance if this turns into a rant as I've just spent the day dealing with this and related issues. Can somebody from Dataton please show this thread to the Watchout developers and see if they can come up with a solution to what is a conceptually quite simple problem. The client just wants to transition into a looping animation, then transition seamlessly out again, and they don't want a long explanation of why that's complicated and how we should just avoid it or simplify the animation instead. Like others on this thread, I've tried the various, increasingly convoluted workarounds (DMX commands which trigger MIDI commands which trigger Aux timelines... really?!), but none are particularly satisfactory. A quick opacity tween out of a looping video works as long as the animation is simple enough for it not to show (try using a quick cross-fade from a looping globe animation currently showing the American continent to the exit-animation which starts in Europe and see if anybody thinks that is seamless). Or we can add a cue to a task to jump back to the loop point... and hope that it doesn't flicker - sometimes it works fine, mostly it doesn't and I haven't managed to pin down exactly what the reason is. Conditional Layers actually seem to work the best, but better hope you don't need to manage several conditions simultaneously as there isn't a way to toggle just one condition, you need to set the binary value taking all of the other conditions into account. So a Task which wants to unset a condition needs to know the current state of all the other conditions, and there doesn't seem to be a way to do that within Watchout (OK, there probably is, using an enormous number of tasks evaluating all the possible combinations of layer conditions, but I mean something simple). Maybe I'm abusing layer conditions by using them as boolean variables to track the state of various things in the show. Generic inputs are great, but then they can't be used to enable/disable control cues, so we're stuck messing with layer conditions. So what would be really helpful, would be a new 'set_layer_condition x true/false' command, so that we can just toggle the current value of an individual condition without changing any others. That would already simplify a bunch of stuff, and I could stop writing my helper app just to deal with it. I assume that, somewhere deep in the Watchout code, it's keeping track of each looping media cue and knows when it hits the loop point - it's just not currently exposed to the user at all. Maybe we need a way to get the current state of looping media (0-100%) and, even better, be able to evaluate that in an expression in a control cue. Each time the media reaches the loop point, the pause cue holding the timeline at that media cue would evaluate a condition ('my_generic_input == 1', or 'layer_condition_8 == true') and either stay put and keep looping, or no longer be considered an active 'pause' cue and would allow the timeline to run seamlessly into the exit animation. I dunno, something - anything - other than the current situation would be good! Don't get me wrong - I'm impressed with the major functions being added to Watchout (Virtual Displays, HAP codec, 3D mapping, NDI support) but it more mundane tasks can still be surprisingly frustrating (which reminds me, I have a bunch more comments to add to the never-ending feature request thread!).