Jump to content
Dataton Forum

Eddy Lui

Member
  • Content Count

    6
  • Joined

  • Last visited

About Eddy Lui

  • Rank

Contact Methods

  • Website URL
    http://omnigram.net

Profile Information

  • Gender
    Male
  • Location
    Singapore
  • Interests
    immersive visual | interactive programming | show control | bespoke integration

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Currently working on a physical design with rotary encoder as an input interface to an interactive app. Incremental encoder is quite common in our daily life — we can find it in the knob of a sound system or a fan speed control. Some other use cases include: Timeline control with linear duration that can either go backward and forward. Range value control eg: volume or menu selection. Angular position/degree trigger mechanism. In this experiment, I am using a rotary encoder with a 3D printed wheel interface as a control for WATCHOUT linear timeline. Turning the wheel
  2. Hi Dave, Cheers from Singapore! I'll focus on WatchOut only and here are some of my thoughts on it: Workflow : the steps from setting up to running a show is simple which mean you can focus on the most important thing, that is your show itself. Reliability — I've been using WatchOut for over decade now, mostly in fixed installation. Throughout the year, many features got added in slow but deliberate manner. Eg: the major version upgrade from v4 to v5 which raise the per machine output from 1 to 6. For me personally, looking at the clean and compact files in WatchOut insta
  3. I've had a few installations in the past few months using WatchPax40 and custom-built machines that required master volume control. In WatchOut control protocol, there doesn't exist yet any command that allow you to adjust the system master volume level. The closest you get to achieve volume adjustment is to define an input variable and attach that input to the video's or audio's volume tweening function (or through DMX). And then, you'll get to adjust the level using "setInput" command. In a show that contain dozens of video or audio files, tweening the same variable to the input can be
  4. Hi jme, Yes, that's how I understood it and I am well aware of that. Thanks for the additional explanation to the thread. Best regards, Eddy Omnigram
  5. May I know if you've selected the same stream for both the default and alternative stream name when you add the NDI Video media? The alternative stream is actually optional. I've seen those source switching warnings many times in my setup and I'd say those warnings are pretty harmless. From observation, it didn't seem to affect the stream quality — no visible frame drop or stream lag at all.
  6. The thing about command tagging I observed is that, the tag only get returned on the first reply. For example: [16]ping<CR> [16]Ready "6.6.5" "WATCHPOINT" "Windows" false If you use a subscription based commands such as getStatus, subsequent replies will not have the tag returned: [18]getStatus 1 "TaskList:mItemList:mItems:TimelineTask \"Intro\""<CR> [18] Status "TaskList:mItemList:mItems:TimelineTask \"Intro\"" 2 6427 1858406 Status "TaskList:mItemList:mItems:TimelineTask \"Intro\"" 2 11460 1863418 Status "TaskList:mItemList:mItems:TimelineTask \"Intro\"" 2 16459 186843
×
×
  • Create New...