Light up any key, from anywhere.

# Mode → 8 ms → clear → 120 ms → query → paced target
F0 7F 30 7F 7F 20 00 0F 05 F7
F0 05 30 7F 7F 20 00 71 00 F7
F0 05 30 7F 7F 20 00 01 F7

# Optional C4 E4 G4 C5 diagnostic; two packets, at least 8 ms apart
F0 05 30 7F 7F 20 00 71 03 3C 08 40 08 43 08 F7
F0 05 30 7F 7F 20 00 71 01 48 08 F7

Use $partykeys-protocol to connect this project's key lighting
using the user-confirmed PartyKeys ChordCut profile.
Preserve existing MIDI input, audio and host-owned connections.

import {
  createPartyKeysLighting, lightingSysexAvailable
} from './skills/partykeys-protocol/assets/web-midi/connect-lighting.mjs';

// access: your existing MIDIAccess / injected Web MIDI connection.
// sysexRequestSucceeded: true only if {sysex:true} actually succeeded.
const lights = createPartyKeysLighting({
  inputs: access.inputs,
  outputs: access.outputs,
  outputId: selectedOutputId, // omit only when there is one supported output
  sysexEnabled: lightingSysexAvailable(access, sysexRequestSucceeded),
  onStatus: (state, detail) => console.info(state, detail)
});

// Keep the original parser/scoring/audio path; forward bytes alongside it:
// lights.receive(rawBytes, pairedInputId);
lights.set(currentTargetMidiNotes); // same notes as the screen
// Pause / stop: lights.off();
// Exit / output change: lights.dispose();
// Reconnect: recreate, then restore current target only if active.
// "sent" means written to the MIDI API, not a physical LED acknowledgment.

const midi = await navigator.requestMIDIAccess({ sysex: true });
const out = [...midi.outputs.values()].find(p => /partykey/i.test(p.name));

// Enter LED mode (required once)
out.send([0xF0, 0x05, 0x30, 0x7F, 0x7F, 0x20, 0x00, 0x0F, 0x01, 0xF7]);

// Light keys 17, 18, 19 red/green/blue
const enc = v => [Math.floor(v/128), v % 128];
out.send([
  0xF0, 0x05, 0x30, 0x7F, 0x7F, 0x20, 0x00, 0x15, 0x03,
  ...enc(255), ...enc(0),   ...enc(0),   1, 17,
  ...enc(0),   ...enc(255), ...enc(0),   1, 18,
  ...enc(0),   ...enc(0),   ...enc(255), 1, 19,
  0xF7
]);

const access = await navigator.requestMIDIAccess({ sysex: true });
const out = [...access.outputs.values()].find(p => /partykey/i.test(p.name));

F0 05 30 7F 7F 20 00 0F 01 F7

F0 05 30 7F 7F 20 00 15 <numGroups>
  <group_0> <group_1> ...
F7

# Each group:
#   R_hi R_lo  G_hi G_lo  B_hi B_lo  keyCount  key0 key1 ...

// v ∈ [0, 255]   →   [high, low]
const enc = v => [Math.floor(v / 128), v % 128];
// firmware reconstructs: value = high × 128 + low

# Highlight one C3 octave — palette slots 1–12 (full brightness × 1.0)
F0 05 30 7F 3F 20 00 71 0C
  30 01  31 02  32 03  33 04  34 05  35 06
  36 07  37 08  38 09  39 0A  3A 0B  3B 0C
F7

# Darklight the same keys — palette slots 14–25 (dim × 0.75, same hues)
F0 05 30 7F 3F 20 00 71 0C
  30 0E  31 0F  32 10  33 11  34 12  35 13
  36 14  37 15  38 16  39 17  3A 18  3B 19
F7

F0 05 30 7F 7F 20 00 71 00 F7

F0 03 1E <numColors> 01  <R G B> × N  F7

# Example: upload red, green, blue into slots 1–3
F0 03 1E 03 01  7F 00 00  00 7F 00  00 00 7F  F7

F0 03 20 <numPairs>  <lampID paletteSlot> × N  F7

# PartyKeys Project Conventions

Apply the explicit device profiles and safety rules below. The reusable
Codex skill is $partykeys-protocol. Keep its three ESM files together and
integrate with the existing input/connection lifecycle; do not replace audio
or scoring just to add lighting.

You are implementing PartyKeys / 音乐密码 lighting. Select an explicit device
profile before constructing any packets. Do not guess unknown MIDI outputs.

VERIFIED WEB MIDI PROFILE — fruit-webmidi-palette71-v1 (2026-10-10)
User-confirmed in PartyKeys ChordCut: phone USB to the PartyStudio APP port,
then wireless to keyboard. Recognized relay aliases: PartyStudio, SAM5704.
Ordinary MIDI input is allowed for playing/scoring; proprietary output is not.

Reuse the complete Skill and dependency-free modules:
https://protocol.partykeys.ai/downloads/partykeys-protocol.zip
https://protocol.partykeys.ai/skills/partykeys-protocol/SKILL.md
https://protocol.partykeys.ai/skills/partykeys-protocol/references/verified-web-midi.md

Wire sequence (hex):
1. Open selected output, mode: F0 7F 30 7F 7F 20 00 0F 05 F7
2. After 8 ms, all off: F0 05 30 7F 7F 20 00 71 00 F7
3. Settle 120 ms, query: F0 05 30 7F 7F 20 00 01 F7
4. Palette target:
   F0 05 30 <channel> <address> 20 00 71 <count> <note color pairs> F7
   Actual MIDI notes 48–83, color 08 (cyan), 00 off.
   Maximum THREE pairs / 16 bytes; pace packets by at least 8 ms.
   Raw Web MIDI SysEx only. Do not append BLE timestamps.
   Mode device-type byte is 7F; key-color device-type byte stays 05.

Routing:
- Select a recognized connected output and unambiguously pair its input.
- Learn channel/address from CMD 02 reports; assign unassigned main-keyboard
  channels only as the bundled controller does, then wait for its response.
- Broadcast 7F/7F on the selected bus until the route is known.
  Do not hard-code 3F for every device.
- CMD 04/05: debounced topology query; CMD 18: octave update.
  Do not send idle mode during play, or CMD 19 to reset the player's octave.
- Query silence is not proof of disconnect.

Lifecycle and transport:
- Keep existing Web MIDI / native-injected access. App owns USB/BLE pairing.
- A successful {sysex:true} request is required. If an injected access object
  omits sysexEnabled, accept only that successful request without explicit
  denial. Normal MIDI fallback does not grant lighting permission.
- Frame data must be 7-bit; reject out-of-range notes rather than transposing.
- Delta updates use actually written notes. Recompute each small packet;
  rapid changes and pause cancel stale unsent targets.
- Pause/stop: clear. Reconnect: init, clear, restore CURRENT active target.
  Exit: dispose timers and clear best effort, without closing shared ports.
- "sent" means MIDI API writes completed, NOT a physical LED acknowledgment.
- Preserve velocity, channels, multi-message packets, running status and CC64.
  Screen and lighting use the same actual MIDI target notes.
- Never use Note On for lighting: echo can create false player input.
- No global mute. If audio routing is separately requested, confirmed external
  speaker presence may mute web PIANO ONLY, never SFX/BGM. CMD 05 is not proof.
- MidiBrowser's 256-byte ceiling does not supersede the relay's 16-byte limit.
  Future MIDI timestamps may be ignored. 120 ms settle is NOT LED latency;
  do not blindly delay all audio by the old 200 ms direct-device estimate.

SEPARATE DIRECT RGB PROFILE (not a speaker-relay fallback)
Only for explicitly verified direct RGB devices:
mode F0 05 30 7F 7F 20 00 0F 01 F7; command 15; key indices 0–35.
Each RGB group: R_hi R_lo G_hi G_lo B_hi B_lo count key...
8-bit color v -> floor(v/128), v%128. Data bytes <=127; frame <=256.
Historical 12-pair / fixed-3F / dim-palette examples require firmware checks;
do not transplant them into the verified relay.

SEPARATE POPUPIANO 29 PROFILE
Manufacturer 03; MIDI notes 48–76; lamp IDs 0–28.
CMD 1E uploads 7-bit RGB palette; CMD 20 assigns lamp/slot pairs.
No PartyKeys mode packet. Not covered by the relay hardware confirmation.

Validate with the bundled 25 offline tests plus target-project checks.
Real-hardware coverage is limited to the user-confirmed chain; do not claim
every phone, firmware or multi-keyboard setup has passed.
Integration does not authorize unrelated deployment or account changes.
Docs: https://protocol.partykeys.ai/#verified-lighting