-
Notifications
You must be signed in to change notification settings - Fork 25
Fix Attack Command Number; Add Chorus & Portamento Time #49
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
Conversation
deckerego
commented
Mar 26, 2022
- Fixed ATTACK_TIME value
- Added CHORUS value
- Added PORTAMENTO_TIME to match the PORTAMENTO on/off value
- Fixed ATTACK_TIME value - Added CHORUS value - Added PORTAMENTO_TIME to match the PORTAMENTO on/off value
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.
I know very little about MIDI so I don't know if I'm qualified approve this or not, but a quick search about it lead to the above comments. Thanks for submitting!
Okay, coming back to this after doing a little more digging. So it looks like |
The putative norms and actual practice of which CCs should be used for which controls diverges widely, and this file by and large defines just the most commonly implemented assignments; many synthesizers won't even implement all of them thus. (It might be wise to add a comment to the file to this effect.) My comments address these common usages. PORTAMENTO_TIME should be 5, not 37. Theoretically CCs 32--63 are reserved for LSB (7 bits) of the MSB (7 bits) of the controller values for 0--32, but in practice very few synthesizers implement LSB for any of these values. (CC37 would be the LSB of CC5.) I certainly don't think it's worthwhile defining names for any of them. Another relatively common controller is BANK SELECT, CC 0. This is used to select which bank of patches a Program Change message references. The assigments for CCs 75--78 are not common -- they're normatively just Sound Controller 6--9 -- and I'd be happy to see them removed from this file. (These comments are based on my having studied, owned, and used a wide variety of synthesizers, hardware and software, since the 1980s, with particular attention to CC implementation.) |
Switch to coarse portamento time controls based on feedback at adafruit/Adafruit_CircuitPython_MIDI#49 (comment)
Changed from fine to coarse control of portamento time based on feedback at #49 (comment)
Updated to coarse adjustment |
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.
So based off everything here, I think this is good to go. If we ever want to clean this up by removing things, we can do so knowing that it is (I would say) a breaking change for the library. Thanks y'all!
Updating https://github.com/adafruit/Adafruit_CircuitPython_SCD30 to 2.2.3 from 2.2.2: > Merge pull request adafruit/Adafruit_CircuitPython_SCD30#31 from cHemingway/readme_example_sck > Update Black to latest. > Fixed readthedocs build > Consolidate Documentation sections of README Updating https://github.com/adafruit/Adafruit_CircuitPython_SGP30 to 2.4.0 from 2.3.7: > Merge pull request adafruit/Adafruit_CircuitPython_SGP30#35 from benthorner/main > Update Black to latest. > Fixed readthedocs build > Consolidate Documentation sections of README Updating https://github.com/adafruit/Adafruit_CircuitPython_ESP32S2TFT to 1.0.1 from 1.0.0: > Merge pull request adafruit/Adafruit_CircuitPython_ESP32S2TFT#2 from tekktrik/dev/use-f-strings > Update Black to latest. > Corrected pylint version Updating https://github.com/adafruit/Adafruit_CircuitPython_MIDI to 1.4.8 from 1.4.7: > Merge pull request adafruit/Adafruit_CircuitPython_MIDI#49 from deckerego/update_control_values > Update Black to latest.