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
  • armada
  • ui
  • src
  • bounds
  • BoundaryLab.tsx
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    feat(bounds): a `noise` mark, because a defect between two tracks belonged to neither · d17228a1
    PLN, auditioning CosmicFest: "at 22:42 its end of reose_rouge, theres a loud blip
    noise, at 22:44.9 its the start of rose rouge, could we cut noise and blend
    better?"
    
    The lab could only ever answer one question — where does the next track start —
    so garbage living in the 2.9 s BETWEEN two tracks had nowhere to go. It survived
    as prose in a comment box, which no downstream tool reads.
    
    `n` marks the playhead as noise and deliberately leaves the cut call untouched: a
    blip between two tracks is not an opinion about where either begins, and forcing
    it through the cut field would corrupt the one number the mastering chain trusts.
    `N` clears them, because a mis-tapped defect marker you cannot remove is worse
    than no marker at all.
    
    They render in warm orange, distinct from every existing mark colour: those are
    all CANDIDATES for a cut, and this one is the opposite — a place to avoid.
    
    Exported from both the decided and skipped blocks, so a seam PLN rejects can still
    carry "and there is garbage at 22:42". That combination is exactly what happened
    here and exactly what the old export could not represent.
    PLN (Algolia) authored Aug 29, 2026
    d17228a1
BoundaryLab.tsx 13.6 KB
EditWeb IDE
×

Replace BoundaryLab.tsx

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.