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

EPIC: Live Data Input (triggers, actions, recording, etc.)


    • Type: Epic
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core Framework
    • Labels:
    • Epic Name:
      Input Data
    • Epic Colour:
    • Epic Status:
      To Do


      Copied from a mailing list post.

      The idea – no idea how feasible it is – is to have some sort of abstraction that mirrors what we have with controllers and outputs. That is, we might have a bunch of different 'input' modules, and each module would provide one or more 'input' channels to the system.

      Within whatever setup interface we have, we would be able to configure each input and/or channel to do something different – maybe within the sequencer you could select a bunch and 'map' them to certain elements and effects (as per Giz's example), and the sequencer could read that data and decide to record it. Or the scheduler might listen on some particular input channels to trigger scheduler events – start a show, stop a show, pause, play a certain sequence, mute it, etc.. Or, maybe we could configure it in another module ('live playback' or something) so that the user could play a MIDI instrument and have elements light up directly!

      There's obviously lots of issues and things to consider – I have no idea what formats the inputs could be in (some would be binary on/off, I think MIDI is 8-bit, etc.), and how we could make a common data format/stream out of them. Plus many more......


          Issue Links



              • Assignee:
                michael Michael Sallaway
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created: