OpenMPT Issue Tracker - Issues

0001984: make the hierarchy menus easier to use

Sat, 08 Aug 2026 17:15:58 +0000

For starters, you should be able to select multiple items in there, it's very annoying when I want to delete a bunch of samples or patterns at once and I have to go one at a time instead of just box selecting and pressing delete all at once, might be even faster than using the cleanup menu in certain circumstances! Even if box selecting isn't possible, it's very annoying when I instinctively shift or ctrl click to select multiple items on there only to unselect the first thing I clicked, so that could be added instead

In the same vein as that, being able to drag samples or instruments would make working a lot faster, so instead of having to open the sample tab in one song, copying, going to the other song, and pasting, you could just grab the sample and bring it over, not to mention if you want to use multiple from a sample or instrument bank you could just select them and drag them all across instead of pasting one at a time.

Finally, being able to "add" patterns into the hierarchy should probably be added, it seems so weird that you can Edit, Delete, Set, Rename, but not make a new one.

0001983: Accidental quadratic complexity in C API metadata retrieval

Tue, 04 Aug 2026 18:47:50 +0000

`openmpt_module_get_*_name` functions return individual item names, but use the C++ APIs that return entire vectors of items under the hood to retrieve the item name. Listing for example all sample names thus introduces quadratic complexity.

The internal implementation (`mod->impl`) should probably offer both single-name and multi-name variants for the the C++ and C APIs to use, with the multi-name variant using the single-name variant under the hood to avoid inconsistencies in string conversion etc.

0001982: Parameter editor screen doesn't update properly if updated row is not visible in pattern view

Tue, 28 Jul 2026 12:45:59 +0000

The parameter editor / "visualize effect" window is not redrawn when the mouse is clicked on a certain region. The position and size of this region seems to be random. The window is properly redrawn again if resized, or if the mouse is clicked somewhere else outside the region.

I was able to reproduce this on my main computer on both Wine 11.13 and a Windows 10 virtual machine, but it works fine on a different machine running Windows 10 natively. So this might only be an issue on Wine and virtualized systems?

0001981: Cue points playability via keyboard

Sun, 26 Jul 2026 17:19:43 +0000

Hello Saga,

Would it be a feasible idea to make the cue points playable and recordable via the pattern editor? I had this idea that within the sample map in the instrument tab a third column could be added representing the cue point number. This way you could assign them to a key and a root note and "jam" with the cue points to come up with ideas and record them.

I know you can preview cue points within the sample editor via Shift + cue number, but you can't record this into the pattern editor. And I am aware that you can slice a sample at cue points and make a new instrument with those samples but this means you have to commit to the slices and with two sliced samples or more the sample pool can become quite unwieldy. The only way at the moment is to "program" the cue points in the pattern editor via the "o" command in the volume column.

Again it's just an idea I had and I'm not a programmer so I have no idea if this fits the roadmap or if its realistic within the scope of the development of openmpt.

Greetings,

FWL

0001980: Auto adjust sample volume after normalizing it

Fri, 24 Jul 2026 20:41:05 +0000

The "normalize" function in the sample editor could adjust the sample's global volume, like the "remove DC offset" function. (or maybe add a separate variant of the normalize function that does this.)

0001042: Render pattern channels to separate buffers

Thu, 16 Jul 2026 19:46:20 +0000

Suggested by emoon (and some other people in the past): Provide a libopenmpt interface for rendering each channel separately, e.g. so that you can draw scopes for each pattern channel.
OpenMPT could also benefit from this.
Plugins make this more complicated because if two channels feed their output into one plugin, we cannot tell them apart anymore. Renoise "solves" this by only showing the plugin output on one of the channels (the last one that triggered a note, I think).
We can already render channels to different buffers (e.g. for plugins or reverb), so the infrastructure is there, it just cannot be used to its full extent at the moment.

0001979: Loop-vision mode in sample editor.

Wed, 08 Jul 2026 15:27:26 +0000

Loop overlay mode.
When mode is activated, if you are looking at loop start/end, corresponding waveforms are overlayed with different color.
This is less pressing with technological advancements such as crossfading, but personally, I'd rather butcher as little as possible.
Caveat: cannot see properly if at the very start/end of sample.
For this I propose: split view. Draw another sample view in line with the real sample view, but dedicated to loop viewing, own zoom, only activates with mode.

0001978: Sample editor modes for amplitude and DC, using instr envelope semantics with realtime update

Mon, 06 Jul 2026 20:28:09 +0000

I propose three new buttan/tools in sample editor.

1. Live amplitude editor.
Enable mode to add envelopes in the sample editor, by points. Same semantics as instruments, except tied to middle axis(amp or decrease vol).
These update waveform live so you can see what you are doing. Optionally, affect playback live.
When you are done, can discard or apply to sample.
Use: fiddle with sample dynamics.

2. Live DC offset editor.
Similar to above in operation.
Use: correct wobbly DC offset before fiddling with dynamics, impromptu half-sample distortion!

0001977: Rendering X and Y cursor axis in sample view when drawing enabled.

Mon, 06 Jul 2026 12:29:04 +0000

Render an X and an Y axis at cursor position in sample view when sample-drawing pencil is enabled.
This is like a ruler.

Serves two purposes.
1. Helps you eye amplitudes faster when looking at the other cycles of the waveform.
2. Is warning signal that you left drawing mode on. Too many times I was dingus and accidentally drawn spikes into sample. Derp.

Adendum:
We have a measurement bar on top of sample. What if we add a second vertical axis, adjustable to be in front or behind cursor position by X amount?
This improves eyeing even more.
Now the ruler has become a caliper!

0001971: Looping problem in OpenMPT

Thu, 25 Jun 2026 07:35:24 +0000

Hi )
Now available problem and as I think not correct work OpenMPT plugin , what I want mean...
If I not want use repeating and looping file I check repeat never , with this setting all files will play once and next will stoped
If I want do looping playlist , me need check this setting and check repeating or looping playlist in player and this logical . but if module available jump to back with looping zone - I can not hearing correct result if do set repeat never , if I set repeat once - I get one replay and all , but what if I want not do looping all modules , but want recive corretly forever looping separate modules ?
Examples :
https://disk.yandex.ru/d/9O5NXOqieNhnFA - this without looping
https://disk.yandex.ru/d/WsIPhuqDNAOtMA - this file must be looping , but in currently settings absent option auto , I mean sayd what OpenMPT can not detect is it necessary to loop the module?
Please , add option besides Never , Forever , Once , method Auto , I offer do auto as automatic detect is there any need looping in data of tracker

0001976: Add the ability to estimate length of certain patterns.

Wed, 24 Jun 2026 20:43:27 +0000

There's been a few times now where I'm dealing with songs of abnormal pattern lengths where I want to get an easy idea of how long sections are without having to constantly do subtraction in my head, so being able to select certain patterns to estimate it's song length (the same way you're able to do with selecting patterns to export only certain sections of a song) would be a really nice addition to the program. If you don't want to clutter the UI with an extra button in the Player drop down, you could just add a second line under "Approximate song length:" that says "Approximate selection length:", and it'd also be nice to select rows and be able to do it for that, but given that it's not currently possible to export certain rows I'd understand if it doesn't make sense to add.

0001975: Instrument Bake for notes

Sat, 13 Jun 2026 08:24:14 +0000

> (render samples for several notes and tune them as one instrument)

A new DIALOGEX with a Sample Map:

input several notes to play and numbers them (or names them), map the notes, and finally override an instrument.

## new DIALOGEX:

- A GROUPBOX for managing builtin and custom mapping presents. builtin: buttons per set, cyclic arrangement, single sample (range supported). Maybe create new file extension.
- A ??? for inputing notes and IDs.
- A Piano Key Map like the Sample Map.
- A GROUPBOX with widgets used to select the sampling range, duration, and samples mapping interval.
- A GROUPBOX used to select rendering settings and instrument slots.

0001017: Tick boundary rendering (was: Provide access to next play position)

Thu, 11 Jun 2026 12:06:32 +0000

PoroCYon asked on IRC if it's possible to retrieve the next play position (row/pattern). We already have this information, but it is currently not exposed.

0001373: Fasttracker 2 Custom Sync Event (Wxx) not implemented in OpenMPT

Thu, 11 Jun 2026 06:05:25 +0000

I've seen ms-dos demos that have events that are triggered by this effect command for syncing to the beat for the .xm files. Protracker also does that by using 8xx for syncing too. Can you implement that please? Thank you

0001662: Real stereo channel VU meter

Sat, 06 Jun 2026 06:17:05 +0000

The channel VU meters are fake, (mostly Scream tracker, Schism Tracker [to 2009 version]), This feature needs to make real VU meter mostly like (IMAGO Orpheus, Impulse Tracker, Schism Tracker [from 2010 version])
```
L 100 75 50 25 0 25 50 75 100 R
[[]][[]][[]][[]][[]][[]][[]][[]]|[[]][[]][[]][[]][[]][[]][[]][[]]
```
Can you make this feature and put to Miscellaneous Options

0000569: Unicode strings in CSoundFile.

Sat, 06 Jun 2026 06:07:58 +0000

Use Unicode strings for all strings (samples/instrument/channel/pattern names and other general metadata) in CSoundFile.

0000783: cross-platform OpenMPT

Sat, 06 Jun 2026 06:07:38 +0000

This is a meta-issue, collecting various other issues related to making OpenMPT itself cross-platform.

0001957: libopenmpt API for MIDI output data

Wed, 27 May 2026 15:34:14 +0000

It might be desirable to, in addition to the rendered PCM output, provide access to realtime MIDI data that would be sent to external devices or unavailable plugins.

0001972: XM instrument rendered significantly quieter with libopenmpt than inside OpenMPT

Wed, 27 May 2026 11:55:35 +0000

I noticed a specific instrument/note sounding much clearer/louder while playing in OpenMPT (Windows) than on a app (actually 2) using libopenmpt.
I have a website that plays mods, this issue occurs there, in any OS.
The global volume of the song seems similar but this particular instrument sounds different.
I already turned the world around but couldn't find the cause.

0000779: Allow certain playback-related flags to be set as load-time ctl or during playback

Wed, 27 May 2026 11:53:02 +0000

Some internal flags should be able to be chosen by the user (e.g. the currently unimplemented flag for playing Amiga MODs as mono, force-enabling VBlank timing for ProTracker MODs or super-smooth ramping for XM files).
It would be rather simple to allow those things to be specified through ctl values, but ultimately it would be very useful to also be able to get and set them in real-time (e.g. through openmpt_module_*_render_param), as e.g. a module player should be able to change some of these settings in real-time.

0001772: Move MIDI output off audio thread

Sat, 16 May 2026 15:10:05 +0000

While working on [Beyond](https://sagamusix.de/download/beyond/) my ASIO driver was struggling due to the MIDI driver taking its time to process outgoing MIDI messages to seven different devices. I modified the MIDI code locally to run on a separate thread (one per device actually), but that solution is not quite in a merge-able state yet (there are still some random deadlocks when closing a module). But the direction is right and should be used for more stable MIDI output.

0001968: Accessibility issues with new sample grid settings

Tue, 12 May 2026 16:01:36 +0000

The new sample grid options have a few accessibility and keyboard usability problems:
1. The "grid segments" static text is wrongly presented by screen readers as belonging to the segment size edit field.
2. The "Divide every" radio button seems to be keyboard-unreachable.

0000612: Sample Tab: Allow separate selection of sample channels

Sat, 25 Apr 2026 17:55:41 +0000

It should be possible to edit the right and left channel of a sample individually. Right now, it is only possible to edit both channels at the same time.

0001967: UltraTracker bug

Tue, 21 Apr 2026 21:16:09 +0000

Available bug , yes , all in UltraTracker , if you play this melody from 2:10 , so you can hearing as on 2:30 - 2:38 not accurately reproduced note with pitch shifting , pitch rises too sharply

Source melody https://disk.yandex.ru/d/V65d4Ly1uh-RAw

Modplug Player 1.46 https://disk.yandex.ru/d/QOk0U2JLxT6Dtw

OpenMPT plugin 8.6 for XMPlay https://disk.yandex.ru/d/SwO6uLKYzAn-cA

0000917: Virtualize MIDI I/O

Sun, 19 Apr 2026 14:53:42 +0000

Currently each MIDI I/O plugin instance as well as the separate MIDI recording feature directly access RtMidi or the WinAPI. This makes it impossible to re-use a device, e.g. to create to MIDI I/O instances reading MIDI data from the same MIDI device and then passing it on to different plugins.

The actual MIDI I/O should be moved to a separate component (using RtMidi in the background) that sends the inputs to all listeners and processes all outputs.