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
  • tide-table
  • set_crossmatch.json
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    feat(tide-table): a recovered CosmicFest tracklist, with the evidence attached · 930f6ca5
    Two independent lenses over a 63-minute handheld stage-mic MP3, for a night with
    no stems and no gig-log. They agree where they can both see, and where they
    disagree the reason is structural rather than mysterious.
    
    Confirmed by both lenses, independently:
      0:00-5:04   bombe                 z=2.33 margin 0.67 + diams_dj 85% offset consistency (1056/1244)
      31:27-35:46 take5_drops           z=1.91 margin 0.58 + take5 cons 0.38
      8:54-11:28  something_about_drums              + movie_paris cons 0.49
    
    Crossmatch alone, but with margins strong enough to stand:
      11:33-16:58 am_i_doing_it_right   margin 0.87
      18:13-22:32 you_my_sunshine       margin 0.82
      48:25-51:20 punkachien            margin 1.06  <- only findable because Montreuil supplied the render
      38:31-41:41 piment_bresilien      margin 1.19
      51:30-54:10 mafia                 margin 0.69
      57:29-60:29 vague_de_crime        margin 0.82
    
    The two disagreements are the interesting part, because they are predictable.
    crossmatch can only name a track it holds a prior render of, and  is
    confident about two banks that have none: rose @31:20 at 0.602 consistency
    (rose_rouge played neither gig) and love_parade @56:10 at 0.399 (livecode_parade
    is NEW — its .tidal was created in the CosmicFest prep commit itself, so no prior
    render can exist). Trust locate there. The fix for next time is one render per
    new track and the reference set covers it forever.
    
    Recorded as gaps rather than answers: blue_gold wins four short scattered
    segments at margins 0.11-0.44, and that scatter is the signature of a fallback,
    not a performance — material with no matching reference lands on whatever is
    nearest. Segment edges come from a 45s median filter so they are +/- 20s and are
    NOT cut points; bounds.html and ears do that job.
    PLN (Algolia) authored Aug 28, 2026
    930f6ca5
set_crossmatch.json 5.67 KB
EditWeb IDE
×

Replace set_crossmatch.json

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.