Skip to content

LEDs dark on hardware with output open and no send errors #146

Closed

Description

@Skeyelab

After #144 (main 3551ccc), the LC6000's LEDs stay dark while Syndicate plays. A MIDI Monitor spy on both destinations (WD and Controller) shows nothing from the bridge.

The log shows "Connected … Controller" four times (once per layer), no "Couldn't open MIDI output", and no later disconnect, so no send has failed. Saved settings are automatic, with ledsEnabled true. Endpoint unique IDs are distinct, and MIDIObjectFindByUniqueID returns the right objects.

In the Kit, the same path (bundled profiles, the real names WD-first, start(controllers:), deck colors, Playing 1) sends Play 127 to the Controller. Still to rule out: an LED gate in the app's live state, and whether CoreMIDI delivers MIDISendEventList (UMP) to this USB device.

First step: a log line naming the LED output, or saying none was found.

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

    Not a bridge bug. Syndicate's OSC feedback subscriptions were off, so only ColorPalette arrived (Syndicate always sends it). The bridge's state for each deck stayed "stopped, empty". The LED sweep confirmed the output path works. Follow-up: the app should warn when Syndicate's deck feedback is missing (see the newest v1.0 issue). The logging from PR #149 stays useful.

  3. added a commit that references this issue on Nov 16, 2026
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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions