Align music crop sampling with rhythmic grid candidates
Constraint: Music queries often begin near stable pulse locations, but beat tracking can fail on sparse or synthetic signals and must degrade safely Rejected: Depend on beat tracking alone for all rhythmic sampling | too brittle when beat extraction is weak or absent Confidence: high Scope-risk: moderate Directive: Keep beat_aware as a lightweight candidate generator with onset fallback; future chorus/repeated-section logic should compose with beat-aware rather than bypass it Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/src/data/dataset.py acr-engine/src/data/manifest_tools.py acr-engine/train.py acr-engine/src/data/external_adapters.py; synthetic_v2 dry-run with --segment-strategy beat_aware; handcrafted 20s pulse-track fixture with beat_aware and hybrid offset checks Not-tested: Full retraining/evaluation impact on open/internal datasets using beat_aware end-to-end
Showing
6 changed files
with
97 additions
and
11 deletions
-
Please register or sign in to post a comment