experiments/piano_recital: piano voice test case and demo #283
Conversation
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
Lowercase v is velocity. Capital V is volume.
This resulted from a piano player "tracking" to MIDI files and then trying to get the best sound from AMY seen as a batch-renderer. The Chopin ones double as a stress test for voice stealing under heavy sustain and variable velocity.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This resulted from a piano player (yes, me) "tracking" to MIDI files and then trying to get the best sound from AMY seen as a batch-renderer.
The Chopin ones double as a stress test for voice stealing under heavy sustain and variable velocity.
It might also be a good starting place for making voice stealing steal the quietest note instead of the oldest.
Also note there's a bug fix hiding in it. I found
amy.send(volume=value). I guess it would properly be tracked by a separate issue, but it's a one-character change...