-
Notifications
You must be signed in to change notification settings - Fork 2
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
there should a list of recommended of best downstream practices #61
Comments
Yes perhaps later on this could be useful |
If there are any best practices, I will add them here rather than clutter the issue list. I could also make this a discussion. Essentially, I'm posting downstream issue requests for sites that use OAS but should be added to the best practices part of the spec. |
For extra files for a plugin that are officially made by the plugin developer, an official stamp should be attached. Requires: #24 |
https://www.pgmusic.com/tutorial_gm.htm We could encourage sfz instruments creators to use the general midi mapping standards, but I feel like that is an entirely separate project from this #64 |
#24 ability to connect to an OAS account |
Originally posted by @RustoMCSpit in #23 (comment)
#60
despite being studiorack / owlplug issues above, having a short documentation upstream (here) on nice practices for other implementations could be beneficial
The text was updated successfully, but these errors were encountered: