-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Will you consider optimize this progrgam for Black MIDIs in the future? #365
Comments
@happymimimix Thank you for requesting. Since I don't know much about Black MIDI and I can't implement them all at once, could you please create a different issue for each feature and describe them in detail? |
The most critical feature that Black MIDI needs is the performance. It's all about how fast can a program process large amount of midi data. To make a good black midi, the program must at least be capable of stretching notes. Alter the length of the selected section. This is the second most important feature besides performance. With the above three most critical features needed for black midi production implemented, we can then announce that Signal is ready for black midi production! Going beyond just "ready", below is what Signal would need to reach the next level: With the above feature implemented, Signal can then be announced to be fascinating for black midi! To achieve the best black midi editor of all times, below is what Signal need to have: At last, bring over whatever tools you would expect in a paint app to Signal with a feature that allows the user to import an image and convert it into midi note arts. |
I mean, use signal to make something like this:
Currently, the efficiency of your midi editor is already an outstanding level for normal midi editors.
This could possibly become the future of Black MIDI if you can optimize it even further and implement some flipping and stretching tools.
The text was updated successfully, but these errors were encountered: