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
  • tools
  • tests
  • test_v3_translation_is_shared.py
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    surface: the v3 map belongs to the grid, so any reader of the board is right · 56fa3937
    The translation from the LCXL3's DAW-mode numbering to the corpus's lived
    inside lcxl3-driver.py, which made the driver the only process able to read
    the board correctly. Everything else that fell through to the raw port drew
    v3 indices into v2 cells: row C's knobs lit row B, the faders lit nothing at
    all and rained instead, E5-E8 lit E1-E4. One cause, four symptoms, and a
    picture confident enough that the drawing looked like the bug.
    
    The table is now lcxl_grid.V3_ROWS / V3_TO_V2 and midiviz translates for
    itself whenever it is on the raw port, so the cells and the rain are correct
    whether or not the driver is up. The driver keeps its own copy: it is the
    surface's nervous system and this is the day before a gig. Two tests hold the
    two copies together instead.
    PLN (Algolia) authored Sep 23, 2026
    56fa3937
test_v3_translation_is_shared.py 2.75 KB
EditWeb IDE
×

Replace test_v3_translation_is_shared.py

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.