Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
T
Tidal
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PLN
  • Tidal
  • Repository

Switch branch/tag
  • Tidal
  • TASKS_DUMP.md
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    docs+fix(lcxl3): the surface register, and a control PLN commented out no longer glows · 15c2c86a
    PLN: "ok lets list my demands not handled yet and ensure we track all tasks and
    ergonomic issues to improve". So the register: every open ask with his own words
    attached, stable IDs, grouped by what unblocks what — and the honest note that
    ONE probe run at the desk unblocks five screen items at once.
    
    The fix came out of writing it. nouvelle_couleur.tidal carries a parked tempo
    knob, a commented `# cps ((range 60 180 "^29")/60/4)`, and the mapped-set
    scanner read commented lines — so B1 glowed on a board whose oldest rule is
    "dark = unmapped". parse_context already skipped comments; parse_track now does
    too. Live: 12 controls -> 11, 18 lit cells -> 17, B1 dark. Uncomment the line
    and the next follow tick (under a second) lights it and the tempo readout
    appears with it.
    
    Also recorded: the v2 lcxl-leds-watch service has been logging "no LCXL
    sequencer port" every 30 s since 22:39 — its name regex cannot match "LCXL3 1",
    so it has never touched the v3 board. It was my prime suspect for the
    paint-reset mystery and it is innocent; that mystery is reopened with no
    suspect. The Midi-Through to SuperCollider re-add is explained though:
    MIDIIn.connectAll, re-running on sample reload, exactly as
    midi-autoconnect.sh's own header warned it would.
    PLN (Algolia) authored Aug 29, 2026
    15c2c86a
TASKS_DUMP.md 68.3 KB
EditWeb IDE
×

Replace TASKS_DUMP.md

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.