-
Notifications
You must be signed in to change notification settings - Fork 0
feat: griff split — one corpus chunk per phrase (auto-split #2a: core + CLI) #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4c238f3
test(core): red — slice::extract_bars for phrase-split keystone
claude 3486980
feat(core): green — slice::extract_bars extracts a bar run as a Score
claude 3c8e8d6
feat(core): split::bar_segments — phrase-boundary ticks to bar ranges
claude a96e411
feat(cli): griff split — one chunk per detected phrase
claude a43ddc1
test(cli): red — inclusive bar_range and silent-segment skip for split
claude 8a79674
fix(cli): green — inclusive bar_range, skip silent split segments
claude 2d6ba25
test(cli): red — split stays on the detected track
claude 65e1751
fix(cli): green — split measures the detected track, drops its rests
claude File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For pause boundaries,
start_tickis the beginning of the rest whileend_tickis where the next phrase resumes; feedingstart_tickintobar_segmentsmakes a mid-bar pause snap to the start of that containing bar. In a tab where a phrase has notes early in a bar and then a long rest until the next bar, this moves that whole bar (including the pre-rest notes) into the following chunk and stamps the wrongbar_range, silently corrupting the phrase chunks used for training. Use the resume tick for pause boundaries (for example whenend_tick > start_tick) before snapping to bars.Useful? React with 👍 / 👎.