Uploaded image for project: 'Vixen 3'
  1. Vixen 3
  2. VIX-378

EPIC: Controller Improvements

    Details

    • Type: Epic
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Controllers, Core Framework
    • Labels:
      None
    • Epic Name:
      Controllers
    • Epic Colour:
      #6ECFF6
    • Epic Status:
      To Do

      Description

      There's a bunch of work that we need to do related to controllers. There's two 'big-ticket' items, and then other miscellaneous bugs/improvements (listed in issues below).

      1) 'controller linking' (VIX-190): essentially, we want to split up our current controller modules into the concepts of a controller 'bus' and controller 'device'. This makes it easier for users to set up what they have, and it's clear for them to follow it (instead of, say, a single E131 bus with 8000 channels...)

      2) Smart controllers (VIX-202): current controllers are all quite 'dumb' – they just take raw values (usually 8-bit) at a fixed frequency and do what they need to to update. We could add another type of controller – 'smart' controller – that can take 'intent' data types, and know how to deal with them. This has been requested for some things that want to do processing off-box (some embedded devices), and I could see it being handy to put audio tracks into a separate controller and element, which could give us better control over audio playback, positioning, mixing, etc. (with work in VIX-375, it has been discussed that the previews might become smart controller modules.)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              michael Michael Sallaway
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: