-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix MIDI export #3733
Fix MIDI export #3733
Conversation
Wonderful! Issues: http://computermusicresource.com/midikeys.html |
#1857 (comment) Another issue of this PR: actually master pitch is ignored now. I'll put master pitch support if needed. |
👍
Yes. I think master pitch needs to go in there. |
I tried automation of master pitch. Maybe this isn't intended to work yet but here goes... Automation of master pitch: midimasterpitch.mmp.zip |
Yes. Processing automation is difficult, so current method(based on previous one) only exports notes. |
Maybe that's a good idea actually. The basic functions are there and midi export works. |
I need to change some things:
So there's two choices about automation:
|
I vote this. With 'later' here meaning in |
I vote on this too, midi automation can happen when we expose the midi CC messages in the instruments #1159 (part of #1472)
That's a tricky one, I usually use the base note to tune the actual instrument, but I also sometimes use it to actually shift an instrument a couple of octaves up or down, so I don't really know about this, we could do it as an option, but midi export doesn't have any dialog so far. |
I'm trying to implement automation export. If it is finished before rc4 is released, I'll merge this PR with automation support.
It should be. However, MIDI export without automation support will be buggy for some projects. |
I want to remove MidiFile.hpp from this project and write a new class for this purpose. That file doesn't support MIDI CC and have some bugs. I want to implement a better exporting plug-in :) |
I think you should solve this the simplest possible way and leave rewrites to a later release. |
Do I need to update README.md in this PR? |
Good catch. Sure. |
Is there anything to do? |
A way to choose the exported instrument for each track would be really useful. It could be selected in the misc section, below the master pitch toggle, along with a check for the track to be exported in the first place. |
It will be a good feature, but won't be in this PR because it is a fix for broken MIDI export, not a enhancement. Furthermore, it will be merged into However it can be done in |
I think it's good enough to merge. Just one observation when exporting shorties/Crunk(Demo). Tracks |
Yes. I will take a look at it and fix it soon. |
This is the only thing left for rc4 now. I will fix the issue above and merge it tomorrow. No objection? |
No objection. There is also the issue with recording single stream instruments. |
As a simple workaround, I'm considering cutting notes at the end of last BBTCO, or something similar. |
I'm not that bothered by it. I think we can ship RC4 without a fix for this. MIDI export is a complex function and there will be a bunch of things that needs to be fixed anyway. |
... Sounds like a good idea. 👍 |
Yes, maybe. Anyway, cutting notes at the end of last BBTCO or whole song will be much better. More things should be done in |
May I merge it tomorrow? |
If you are happy with the last commit I think you should just go ahead and merge it now. |
* Re-enable MIDI export * Fix logic for processing BB tracks and BB notes * Consider master pitch and base note in MIDI export. * Cut BB notes at the end of BB pattern.
Fixes #2384.
Zero-length note support needs some work, per #2074. See #2074 (comment).
Also
MidiFile.hpp
needs correct copyright information. See #2384 (comment).