Main Menu

Recent posts

#82
Help and Questions / MIDI Export Volume Discrepency
Last post by wallh4x - August 13, 2025, 19:20:50
Hi everyone, I have an issue relating to MIDI export in OpenMPT.

I've begun by opening a .mid file (MIDI_ORIG.mid) and making no modifications to it, then using the MIDI Export feature and saving to MIDI_EXPORT.mid with no changes and default settings.

Upon opening MIDI_EXPORT.mid in OpenMPT, the volume set lane has been significantly altered despite no changes being made to either the input or output format.

Does anyone have any advice on how to remedy this issue? Any assistance would be greatly appreciated, I've attached screenshots and a zip of the .mid files.
#83
Help and Questions / Re: 1.32.02, creating and expo...
Last post by Marwellus - August 13, 2025, 07:53:10
Yep, I figured that one out myself quite quickly, hehe. I made several changes and it plays fine now, export is working perfect, which makes me really happy. It means I can stick with OpenMPT, it's the perfect tool for the job. :-)

Alas, I "only" have to debug my own built-in midi player now, that's a different topic. The MID-file itself is fine, there's no problem reading it but I still have some issues there, I need to fix. ;-)

I mark this thread as solved, thanks again for your help!

#84
Help and Questions / Re: 1.32.02, creating and expo...
Last post by Saga Musix - August 12, 2025, 17:24:13
One thing I can add here about your sample file: You are running into one of the fundamental differences between modules and MIDI: The only way to modify a note's volume after it has been triggered is through MIDI channel volume, and all notes playing on the same channel at the same time are affected by this (as the name implies). You cannot set the "volume command handling" option to "MIDI volume" if you have more than one note playing on a channel at a time, because then each note will update the MIDI channel volume, also affecting other any notes on that MIDI channel!
#85
Help and Questions / Re: when there would be suppor...
Last post by Saga Musix - August 12, 2025, 17:21:26
AHX is not "just like" a standard ProTracker MOD - it's much more complicated as it involves synthesized samples and complex instruments. The good news is that half a year ago or so I was working on experimental AHX import based on the new synth instruments feature in OpenMPT. It wasn't even halfway done, though, so it's impossible to tell if in the end it will be possible to play AHX files without issues. Hence no promises that this will ever be possible in OpenMPT - if the playback isn't going to be accurate, I won't add it.
#86
Help and Questions / Re: Is there any way to conver...
Last post by Saga Musix - August 12, 2025, 17:18:53
Note that you don't need to do this step in OpenMPT at all - saving an IT file with a different extension in OpenMPT won't change its contents - it's still an Impulse Tracker module. You can just as well change the file extension from .it to .mo3 in Windows Explorer, the effect is the same.
#87
Help and Questions / Re: Is there any way to conver...
Last post by bagine09 - August 12, 2025, 17:14:33
saving .it as an mo3 file worked on openmpt
#88
Help and Questions / when there would be support fo...
Last post by bagine09 - August 12, 2025, 17:12:55
winahx is deleted from amiga scene like i dont understand why
can you tell me when there would be support for ahx file in openmpt
because ahx is also a tracker just like protracker mod
#89
Help and Questions / Re: 1.32.02, creating and expo...
Last post by Marwellus - August 12, 2025, 14:23:12
Thanks!

Your answer clarified a few important facts for me already, and I think, there's no need to take a look at my ("bugged") song anymore. The hint at the midi-input/-output plugin is already helping me, the instruments are now routed to VirtualMIDISynth and it behaves like the midi export - I simply need to figure out, what I'm doing wrong and need to understand a bit more about MIDI, before I'll waste more of your time ;-)

Again, thanks! I might report back, if I made progress and the export result is satisfying enough or if I still need some more specific advice. :-)





#90
Help and Questions / Re: 1.32.02, creating and expo...
Last post by Saga Musix - August 12, 2025, 13:33:46
I will have a look at the file in question later, here are some quick answers to what I can tell you without looking at the file itself:

QuoteI took a deeper look into the exported MIDI myself now and for what I can say, the issues I have here are the volume per note / delay and cut settings that just get "overwritten". The song is "compressed" to 4-rows/beat (its 8 in the .mptm) and especially the volume settings look quite different and "weird" in certain parts.

MIDI files have no concept of "rows". As such, the fact that you wrote the original pattern data at 8 rows per beat is not encoded in the MIDI file at all. The detail level at which MIDI files is imported can be configured in OpenMPT's MIDI settings. Please note that there is absolutely no way that OpenMPT could ever guarantee a clean module -> MIDI -> module round-trip, so even after adjusting this setting a lot of things will look different.

QuoteThey do reflect settings like "volume commands with note are velocities" (if I checked this option in the instrument panel) but the export gets it kinda wrong, muting the drums completely after a drum roll for example or setting the volume to a far to low value. Another issue is the mixing of instruments in the channels, drums are mostly effected by this and it kinda breaks things sometimes.
This sounds like you mix and match between instruments with different volume command handling on the same MIDI channel. This is not a bug in the MIDI export per se; that's simply how OpenMPT's internal plugin architecture works. If one instrument modifies the MIDI channel volume, and another instrument is not configured to do so, then the second instrument will continue to use the MIDI channel volume set by the previous instrument.

QuoteIt would be cool, if OpenMPT could just send the notes with their commands straight to a (virtual) MIDI device, it would help figuring out what I'm doing wrong.
The MIDI Input / Output Plugin does exactly that. In fact, this is the only way I can recommend writing a MIDI score in OpenMPT, because plugin-based instruments and MIDI export share identical behaviour, while sample-based instruments behave different in many ways (e.g. the MIDI volume command handling setting you found are specifically meant for plugins, not sample-based instruments, so you would have no way of judging their behaviour while working with sample-based instruments).

QuoteOr an option in the export to just parse the notes and commands as they are, without changing anything - even if this means the exported MIDI might not work at all and I've to figure it out myself what's going wrong.
MIDI export really doesn't do much more than that anyway. If you don't set any specific MIDI volume command handling, it cannot affect the exported output, for instance.