Jump to content
Dataton Forum

Search the Community

Showing results for tags 'aux timeline'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type



Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Pixel Native

    Aux Timeline Fade up problem

    Hi there, First of all... Very happy with 6.2.1, Im enjoying all the new features and updates to WatchOut. The only problem Ive seen so far is that when I you a Aux Timeline, the fade in on clip do not work.... the clip just seems to snap in. Ive tried running the fade later in the clip as well as applying a pre roll on the clip... non of this makes a difference. Am I the only one with the bug or gas anyone else had the same experience.
  2. Working in primarily corporate presentation environments, I am interested in exploring the possibility of using WATCHOUT v6 as a substitute for some applications that would otherwise be suited for a Spyder X20 or Barco e2. Unlike WATCHOUT, the core operating concepts of those screen management systems is the use of presets and the ability to recall a given preset at any time and in any order. From the research on this forum and other sources, it is my understanding that auxiliary timelines are the best approach to replicating this behavior. However, I am having issues in fully doing so. Most of the trouble I am experiencing (I'm also new to WATCHOUT) is in in the management of PiPs and their entrance/exit on screen. To explore this, I have created a project with the following stage items: (1x) 2-projector blend (1x) downstage monitor (1x) virtual display. The virtual display is present on the stage to act as a single location to present the live sources. The virtual display, being considered by WATCHOUT as a media item, is reused on the DSM as well as a PiP on the main screen. In practice, the media will consist primarily of external live inputs such as PlayBack Pro and PowerPoint. For the most part, the only media in WATCHOUT will be background content (looping videos etc...). For this example project I am using two photos as placeholders for live inputs to represent PowerPoint and PlaybackPro. I have also created three auxiliary timelines (ATL): PiPsManages the virtual display on the stage canvas. Specifically, on the DSM and Wide Screen. CUES:@0sec 1sec opacity ramp @ 1.2sec PAUSE @ 1.4sec JUMP TO 1sec GFX Places GFX source on the virtual display and calls triggers the PiP ATL. Always on top CUES:@0.2 places content on Virtual Display @0.3 runs PiP ATL @1.5 PAUSE @1.6 JUMP TO 0.2 PlaybackPlaces GFX source on the virtual display and calls triggers the PiP ATL. Always on top CUES:@0.2 places content on Virtual Display @0.3 runs PiP ATL @1.5 PAUSE @1.6 JUMP TO 0.2 Behavior Running the GFX or Playback ATL the first time is no problem. If the operator runs an ATL that is already "on-air" there is no change on screen (desired behavior). However, when a different ATL is run it cuts sources rather than dissolves the new source in (because the PiP is already past it's dissolve). Desired Behavior Running GFX or Playback ATL dissolves the source on screen either from empty canvas or dissolves through the other source if the PiP is already live - like a standard screen management system (X20/e2). I'm sure I could eventually create some spider web of impossible to understand nonsense that would accomplish this somehow, but I would like to know if any other users have a clean workflow to handle this scenario. Screen shot https://drive.google.com/uc?export=download&id=0ByvQLu5LpvPrS3BhNmNJMlBDSjQ
  3. In the past, we've always had great luck triggering the main timeline using MSC from our ETC Ion (and before it our Obsession). On this show, I had an element that needed to be triggered on cue, while the rest of the timeline was still running. My solution to this withing Watchout was simply to put this extra element in an Aux Timeline. That's when I started to run into problems with the midi. If I set my "Midi Playlist" setting to "ignore", nothing happens. If I set it to "Map to Main Timeline" I can't trigger the aux timeline. If I set it to "Map to Aux Timelines" I can't trigger the main. My first try was to make a timeline called "1" that had all the midi triggers and it, in turn, trigged the main or aux timeline as appropriate. This was intermittently dropping cues, though. I tried putting all the content in timeline "1" and the extra element in timeline "2" but that was still inconsistent. Has anyone run in to this in the past? Ultimately, this became a convenient way to convince the director that this particular cue was a poor choice, but it is something I would like to be able to do in the future. We're running 5.5.1 on Windows 7sp1 Jim
×