Skip to content

Multiple controllers in one app #25

Closed

Description

@Skeyelab

Parent

#12

What to build

One app drives several LC6000s, each on its own deck, all sharing Syndicate's one feedback stream.

Acceptance criteria

  • Settings allow more than one controller entry. The one feedback listener fans out to every Bridge.
  • Identical units are told apart by unique id, then channel. Two entries claiming the same device and channel is a mapping error.
  • Feedback for one deck never changes another controller's LEDs. Feedback for a deck no controller is on is dropped but still counts as live.
  • Either controller's browse and load work at any time.
  • Unplugging one controller doesn't affect the others.
  • Written test-first with /tdd, at the agreed seams (the Coordinator with fakes, and OSC packet bytes).

Blocked by

Activity

  1. added this to the v1.0: native Mac app milestone on Nov 16, 2026
  2. Skeyelab commented on Nov 16, 2026

    @Skeyelab
    MemberAuthor

    Unblocked from #24: the same-device-and-channel check belongs in the settings validation (BridgeSettings.problems), not the mapping-file check, because controller entries are stored in settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions