Repository navigation
Open
Labels
enhancementNew feature or requestNew feature or request
Milestone
Description
Goal
The LC6000's jog display shows which Syndicate deck the controller is on right now. That means the deck number on the deck's color, and later the track's artwork or title. Today the display shows the unit's idle "pie", or whatever djay left there.
The protocol was found and verified on hardware in #121: our own PNG shows on the jog.
Behavior
- On connect, the bridge says hello as a host on the Controller port, then uploads the active layer's image to the WD port and shows it.
- When the active layer changes (note 51, LC6000 deck layers: MIDI channel N drives Syndicate deck N #79), or the deck color changes (Deck colors are a user setting (app badges and jog ring) #123), the bridge uploads that deck's image and shows it.
- On quit, the bridge sends the Serato goodbye, so the unit returns to standalone.
- Settings gets an on/off switch, "Show the deck on the jog display". Default to be decided; see the open questions.
- If the unit refuses (an ack of
06, or no ack), the bridge logs it and doesn't retry in a loop. The LEDs and controls are unaffected.
The protocol (from #121; see its recipe comment)
- Hello, on the Controller port:
F0 00 02 0B 7F 10 60 00 04 04 01 01 00 F7, thenF0 00 20 7F 01 F7. - Upload, on WD:
90 01 00, then0A 01 00 06 0D, then0C(size), then0Dchunks (21-bit offset plus an MSB-first 7-bit bitstream, 14332 bytes per chunk), then0E(slot01plus the PNG's byte-sum as 8 nibbles). Each step is acknowledged with01 10 0F 00 01 00. - Commit, on WD:
7E 00 06 01, then10. The unit answers01 10 10. - Show, on WD:
0A 01 00 01 0D, which displays image index 01. - Goodbye, on the Controller port at quit:
F0 00 20 7F 02 F7.
- Image: a 198×198 RGBA PNG.
- Upload time: about 5 s per 16 KB chunk on the wire. A 17–30 KB image takes about 7–11 s. While an upload is in flight, a newer request replaces the queued one, so only the latest deck's image is sent.
Plan: test-first, slice by slice
- Kit, pure:
JogImageUpload: from PNG bytes to the exact message list. Tested against djay's captured upload, byte for byte; the encoder already reproduces it. The test needs a small checked-in synthetic PNG, not djay's.- The checksum rule.
- The ack parser:
00,06, commit.
- Kit, Coordinator: a
JogDisplayport (fake in tests) that receives "show deck N in color C". Cases to cover:- It fires on connect, on a layer handover and on a deck-color change.
- It is debounced while an upload is in flight.
- A refusal is logged, with no retry storm.
- The goodbye is sent on stop.
- App: render the deck badge as a 198×198 PNG (CoreGraphics), plus a CoreMIDI SysEx sender with completion and ack listening on the WD source.
- Settings switch, with the help text.
Bisect first (hardware, each send OK'd by the CoS)
The working run replayed djay's whole first second. Before building, find the minimal handshake by dropping one part at a time:
- The CTL LED paint and identity requests: probably not needed, since they went out after the upload.
- Denon
cmd 60, keeping only the Serato hello. 90 01 00, and the pre-upload0A.- Whether the goodbye clears the stored image or keeps it, and what a power cycle does.
- Whether the first byte of
0E, slot01, can be02, so two images can be stored for a fast deck switch.
Safety
- The hello changes the unit's mode. After it, the unit answers
9F 37 7Fand acts as host-attached. Before shipping, re-verify the layer and LED logic (LC6000 deck layers: MIDI channel N drives Syndicate deck N #79, LC6000 layers as the hardware really behaves: note 51 sets the layer, ch1 controls follow it, one layer's LEDs (#79) #120) in host mode. Check:- normal vs multi-channel mode;
- the note 51 handovers;
- LEDs on ch1 vs chN;
- the ch16 note 55 overlay messages (
8F 37 00/9F 37 7F) seen in capture 2.
- Never write anything except the image messages to WD. LEDs go to the LC6000's jog display (WD) port when layer 2-4 is in front #143 showed that a stray
90 01 xxthere resets the display. - djay may share the unit: don't upload while another app is attached as host.
- No captured djay assets in the repo: test vectors are synthetic.
Open questions
- Default on or off? On risks surprising a DJ who also runs djay. Off hides the feature.
- Artwork and track title: does Syndicate expose them over OSC? Separate issue.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Activity
Skeyelab commentedon Nov 16, 2026
Rendering note from #121. Orientation (user observation): our icon's notch, drawn pointing up-right, shows pointing down-left on the jog, and the image doesn't turn with the platter. So the display shows uploads transformed:
Rule for now: pre-rotate the PNG 180° before upload.
Pending confirm (needs an OK to send): an upright F with a red square in the top-right corner, 198×198, 2.1 KB, which uploads in about 1 s. The plan is ready.
Skeyelab commentedon Nov 16, 2026
User decisions (2026-11-16):
What that implies for the design:
Skeyelab commentedon Nov 16, 2026
Bisect and probe plan (hardware; every send OK'd by the CoS)
Measured so far: upload speed is fixed by the wire. Every run moved about 3.1 KB/s of SysEx: 16,393 B in ~5.3 s, 2,458 B in ~0.78 s, and djay's 29.7 KB PNG in ~11 s. Wire bytes are the PNG size × 8/7, plus about 12 B of framing per chunk.
Steps
02(0E 02 …), then show it with0A 01 00 02 0Dand switch back with index01.0Aper layer change.10: the0Belement color, the7Cbacklight, and0Atext codes (1/64…64, A–D, "--").E0/E1, 14-bit). Probe on the WD port for a live track-position indicator, then compare with what the LED ring on the Controller port already shows.cmd 60,90 01 00, and the pre-upload0A, one at a time.Defaults (user's decision): the feature is on by default. The long-term goal is real-time feedback on the jog, so the design keeps a fast path (element messages and pre-stored slots) separate from the slow path (image uploads).
Skeyelab commentedon Nov 16, 2026
Orientation confirmed by the F test: the user saw the F upside down, with the red square in the lower left. That is a 180° rotation, not a mirror.
Rule: rotate the image 180° before encoding the PNG. The checksum in
0Eis then computed over the rotated PNG's bytes.Skeyelab commentedon Nov 16, 2026
What Denon's own software shows on the LC6000 platter display (from the Denon manual, as quoted in search results):
A Native Instruments forum post adds that the display can show artwork, track position, jog position and numbers 00–99 without modification.
So the display likely has built-in elements for position and a two-digit number, which are exactly the cheap real-time paths to probe after the image work: 0A visible-element mask, text and number codes, and a position value (maybe pitch bend on WD, as on the Prime 4). Candidates to drive from Syndicate feedback: Progress → playhead marker; loop size or deck number → the 00–99 number; Loaded/TrackInfo → an artwork or deck image upload.
Merge pull request #166 from ericdahl-dev/lc6000-display-tools
Skeyelab commentedon Nov 16, 2026
User check (2026-11-16): djay Pro does not draw a needle or position marker on the LC6000 display while a track plays, so djay can't teach us the position or number elements. Ways forward: (1) probe directly with Prime 4–style messages (0A element masks and the number/text codes, 0B colors, pitch bend on WD), with the user watching, one change at a time; (2) optionally capture VirtualDJ (free for home use, supports Denon displays) or Serato, if they draw position on the LC6000.
Skeyelab commentedon Nov 16, 2026
Position marker found (user capture, djay playing, 2026-11-16). djay draws the platter marker with Pitch Bend on the WD port, ch1:
djay also mirrors the play/cue state to WD as note 1 on ch1 (vel 127/0, toggling about every 0.5 s while cued: the blink), at the same time as the Controller LEDs.
So the cheap real-time marker is: send a pitch bend on WD ch1 with angle = (playback position in seconds × 33⅓/60 revolutions) mod 1 × 16384 − 8192, at ~30–50 Hz while playing. Syndicate's Progress feedback times the track length gives the position, interpolated between feedback messages with the tempo. No image upload needed.
Skeyelab commentedon Nov 16, 2026
First real-time slice: the platter marker (pitch bend on WD)
Rewritten after the second capture (comment below): the marker is a stateful angle, not a function of the track position.
From the captures, djay keeps a virtual record angle and sends it as pitch bend on WD ch1:
Slice 1, Kit, pure, test-first
PlatterAngle, a value type holding the angle in turns (0 ≤ a < 1):advance(seconds:rate:): a += seconds × (5/9) × rate, where 33⅓ rpm is 5/9 turn per second and rate is the tempo ratio, 1.0 at 0%.turn(jogCounts:): a += counts / 3600, using the jog's 14-bit position change and the profile'scounts_per_rev(3600).pitchBend: ⌊a × 16384⌋, on the wire 0…16383. 8192 is center, so the values read signed −8192…+8191, which gives the capture's …8036, −8179… wrap.Tests, with literal values:
turn(jogCounts: 900)turn(jogCounts: -900)Slice 2, Coordinator, with a fake WD port
E0 lsb msbat ~30 Hz when the value changed.Slice 3, App
The WD port opens next to the Controller port, under the same "show the deck on the jog display" switch (on by default).
Hardware probe first (needs an OK)
jogseqallows both messages on WD now (PR #167).Skeyelab commentedon Nov 16, 2026
Second paste (djay: paused, hand on the platter, then play): this confirms and adds detail.
So the bridge's marker model is: angle += Δplayback-time × 33⅓/60 × 16384 (wrap to ±8192), driven by our position/tempo while playing and by the jog position deltas (CC 17/49) while the platter is touched. Send ~50 Hz only when the angle changes.
Skeyelab commentedon Nov 16, 2026
Track-load capture (djay, 2026-11-16): cover art loads FAST.
02 15 6E= 35,566 B → 0D×3 (16393, 16393, 7902) → 0E02 | 00 00 04 05 06 00 04 0A→ 0A0D 00 02 0D(show index 02)02 2A 47= 38,215 B → 0D×3 → 0E02 | …→ 0A0D 00 02 0D(Note: 0C's 3 bytes are the 21-bit size; the leading byte isn't a slot. The slot is the first byte of 0E, and 0A's third byte picks which slot to show.)
0A … index 02.Impact: per-track artwork and fast per-deck images are realistic (~0.5–1 s). A 2-slot design: slot 01 for the deck badge or idle image, slot 02 for the current track's cover (from Syndicate TrackInfo, if we can get artwork) or a rendered title card.
Merge pull request #167 from ericdahl-dev/jog-pitchbend-tool
Skeyelab commentedon Nov 16, 2026
Upload speed, corrected (from the djay track-load capture on #165): the ~3.1 KB/s I measured came from my sender's API, not the unit.
MIDISendSysexpaces SysEx at MIDI 1.0 speed (31,250 baud). djay hands about 74 KB to CoreMIDI in about 40 ms, and the unit acks it within about 1.1 s: roughly 60–70 KB/s. So a cover-art upload takes about 0.5 s, not 10 s.Slots:
0C's three bytes are only the 21-bit size. The slot is0E's first byte and0A's image index: the logo is in slot 01, and cover art goes into slot 02, shown with0A 0D 00 02 0D. The tools now support both (jogseq burst,jogbuild plan … [slot]).This revises the plan's "uploads are only for what changes rarely": at ~65 KB/s, per-track artwork or a title image is practical, about 0.5 s per load. The marker stays pitch bend.
Skeyelab commentedon Nov 16, 2026
Confirmed on hardware: a burst upload of our deck-ring icon (rotated 180° by
jogbuild) to slot 02, shown with0A 01 00 02 0D. The user sees our icon on the jog.9F 37 7F,90 33 7Fand8F 37 00.00×4, at +0.097, +0.104, +0.106 and +0.561 s. Then the identity reply, and the commit acked01 10 10at +0.585 s.0Dto the last ack, for 20.3 KB on the wire. That's about 37 KB/s including the unit's processing; the last ack, about 0.45 s after the third, looks like the PNG decode. The pacedsendtook about 7 s for the same image.jogseq burst(UMP SysEx7 viaMIDISendEventList), from PR tools/lc6000-display: burst sends at USB speed, upload slot in plans (#165) #168.#165 is unblocked for implementation planning. The protocol is confirmed end to end: the hello, upload at USB speed, the checksum, commit, show by slot, and the 180° rotation. Still open from the probe list, but none of it blocks the design: slot persistence across the goodbye and a power cycle, and the minimal handshake.
Skeyelab commentedon Nov 16, 2026
Pre-rotation confirmed: with the 180° pre-rotation from
jogbuild, the user sees our icon upright, with its notch up-right as drawn. The slot 02 switch (0A 01 00 02 0D) showed it.Next session's probes (each needs an OK):
0Aindex message: instant images on a layer change.Merge pull request #168 from ericdahl-dev/jog-burst