the_og/clicktrack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
5 Commits 1 Branch 0 Tags
6de0d98dee7832f08e984fd8f3630ad6133323c9
Commit Graph

3 Commits

Author SHA1 Message Date
AJ Avezzano
986f30d8cc fix: wrap WAV Buffer in Uint8Array for NextResponse compatibility 
NextResponse's BodyInit type doesn't accept Node.js Buffer directly.
Wrapping in Uint8Array satisfies the type and works at runtime.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-04-01 11:26:38 -04:00
AJ Avezzano
2d12160e39 fix: remove unnecessary @ts-expect-error in page.tsx 
Next.js 14 types correctly handle async server components — the
directive was unused and caused a type error during build.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-04-01 11:25:26 -04:00
AJ Avezzano
5b772655c6 feat: initial scaffold for ClickTrack monorepo 
Full self-hosted click track generator for cover bands.

Core technical pieces implemented:
- CTP (Click Track Protocol) TypeScript schema, Zod validator, and WAV
  renderer (44.1 kHz, 16-bit PCM, accented downbeats, ramp sections)
- MusicBrainz API client with 1 req/s rate limiting
- PostgreSQL schema (songs, tempo_maps, registry_sync_log) with triggers
- Git registry sync logic (clone/pull → validate CTP → upsert DB)
- Next.js 14 App Router: search page, track page, API routes
  (/api/songs, /api/tracks, /api/generate)
- UI components: SearchBar, SongResult, TempoMapEditor, ClickTrackPlayer
  (Web Audio API in-browser playback + WAV download)
- Docker Compose stack: app + postgres + redis + nginx + registry-sync
- Multi-stage Dockerfile with standalone Next.js output
- .env.example documenting all configuration variables
- README with setup instructions, CTP format spec, and API reference

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-04-01 11:14:46 -04:00