View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000919 | OpenMPT | General | public | 2017-02-12 18:50 | 2017-02-12 20:25 |
Reporter | pigdevil2010 | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | no change required | ||
Platform | x64 | OS | Windows | OS Version | 10 |
Product Version | OpenMPT 1.27.00.* (old testing) | ||||
Summary | 0000919: MIDI export is broken | ||||
Description | Continuing from Issue 916, where I forgot to give an example of a broken midi export and you seems to renamed and fixed it as arpeggio problem. However, the hold notes problem are still not fixed and I got an example of a broken export.
01: 080: Ocarina 3: The resulting midi is a mess of hold notes and non-stop retrigger drums. (This can be avoided by not having an instrument change in the same tracker channel but it would be nice to see this handled properly.) | ||||
Tags | No tags attached. | ||||
Has the bug occurred in previous versions? | Yes, since like 1.25 | ||||
Tested code revision (in case you know it) | 7588 | ||||
This is also documented and intended behaviour. OpenMPT is not a MOD to MIDI converter. MIDI export (as clearly written in the manual) is intended as a means of e.g. creating remixing stems, not to produce listenable MIDI files. As such, we expect that the user will be loading each exported MIDI track into a separate channel of their DAW in which they want to continue with editing the MIDI file. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-02-12 18:50 | pigdevil2010 | New Issue | |
2017-02-12 20:25 | Saga Musix | Status | new => closed |
2017-02-12 20:25 | Saga Musix | Resolution | open => no change required |
2017-02-12 20:25 | Saga Musix | Note Added: 0002879 |