feat: add local auto-chart pipeline - #1
Conversation
Add a one-click local chart flow with optional official YouTube metadata, OCTAVE/STRUM processing, review-before-import, progress, cancellation, retry, and live end-to-end coverage. User-Request: встроенный локальный импорт и авто-чарт из SightKick | codex:019f9237-cca9-78e3-a7b7-c821f2bc1581
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Superseded: the auto-chart pipeline shipped in the kb.7-kb.12 line on main (see release notes 1.2.0-kb.9 onward). |
why
SightKick can import prepared charts, but creating one still requires leaving the app and manually operating OCTAVE. This adds the smallest legal, local-first path from a song reference and owned local audio to a reviewed playable chart.
This is stacked on the import/provenance work currently proposed upstream in tonygoldcrest#42. It should be rebased and proposed upstream as one coherent feature after that foundation lands.
what changed
proof
product boundary
YouTube is discovery metadata only. The user must select audio they own or are allowed to process. CPU/GPU work stays on the Mac; a future shared catalog can store metadata and user-authored chart artifacts without turning free serverless tiers into an unreliable ML worker.