OpenMPT released

The latest version of OpenMPT has been released today.
This update is mostly a bug fix release which addresses some new issues found in OpenMPT 1.20, but also brings some new features and other improvements. Here is a list of notable changes:

  • Middle-clicking or Ctrl-right-clicking a channel header opens the new quick channel settings dialog, which can be used to quickly adjust volume, panning and channel names.
  • Improved support for AIFF samples (loop points, up to 32-Bit PCM and floating point audio as well as little-endian PCM samples) and WAV samples with arbitrary bit resolutions up to 32-Bit (e.g. 20-Bit).
  • Effect plugins are now sorted into plugin categories (as reported by the plugins) in the plugin selection dialog. Delete the plugin.cache file in OpenMPT's settings directory to rebuild the plugin cache with categories. Loading a plugin into a module will also update the cache.
  • The current playback position is now also reported correctly to plugins when jumping around in the order list. Previously, it was always reset to the song start. This enhances support for sequencer plugins like Maschine.
  • The Korg Wavestation GUI did not work until song was played for the first time since OpenMPT 1.20. This may also fix the GUI of older versions of the Korg M1 plugin.
  • Suport for AMS (Velvet Studio) modules is finally back (not crashing the tracker this time :). AMS (Extreme's Tracker) support has been improved as well.
  • The WAV Loader also imports loop points when reading a WAV file as a module.
  • Improved support for S3M, STM, UMX, MDL and MED modules.
  • In the Keyboard Settings dialog, shortcuts can now also be found by pressing the sought-after key combination.
  • Song Length Estimation also takes per-pattern time signatures into account now.
  • F1 was accidentally hardcoded to opening the help file.
  • Fixed some small issues with the MIDI Input / Output plugin.

For a complete list of changes, have a look at the release notes and the full version history.

In other news, Inno Setup, the tool that is used to create the OpenMPT installer, has dropped support for Windows 9x in its latest version. The OpenMPT 1.20 installer is still compiled with an older version (and thus with Windows 9x support), but future versions will probably use the lastest version of Inno Setup.
How important is Windows 9x support for you? Please post a comment and tell us your opinion!


zeta says:

Windows 9x is dated enough that an installer won't matter. As long as the zip file still works, that should be enough.

Moltres Rider says:

I see there still is no 'find only in pattern range' that has been in the feature requests with a lot of hits for God knows how long!!! don't you guys EVER listen to us???

Saga Musix says:

You're not the only person using OpenMPT and suggesting features (hint: there are currently more than 100 unassigned feature requests and bug reports). My time for working on OpenMPT is limited and I can only implement a limited amount of features, fix bugs or whatever in my spare time (I have a live too, you know). Mind you, there are even older feature requests by myself that I don't have time for.
I prioritise to those requests that I am most interested in or that sound very useful to have. So yes, I listen to the people on the issue tracker, but I cannot fulfill everyone's wishes.
And I don't see you how can so surprised about this anyway - this particular feature request's status is still "unassigned" on the issue tracker, meaning that noone has considered implementing it yet. The status will remain "unassigned" until someone implements it, and until this happens, you don't have to wonder why it hasn't been implemented yet. If this feature is so extremely important to you, consider learning C++ and implement it for yourself.

Oleg says:

Don't know if this caused because i'm using windows 7 or vst plugin without gui (mda tracker/dynamics). But entering a plugin and pressing [Randomize parameters] does nothing.

Saga Musix says:

Some time ago I have changed the randomize params behaviour so that it would only affect params which are reported to be automatable. The plugins in question do not advertise their params to be automatable, so OpenMPT will not try to modify them. I guess I'll have to change the behaviour back to randomize all parameters...

Michael Lou says:

When I use the portamento effect on any type of mod, s3m, xm ...
I put the the portamento on the first note, let it continue across the pattern, and no sound. Ive checked hacks, Ive checked if I did anything wrong.
It has worked before, I have tried it on 5 different computers..
When I remove the effect, it workes fine.
I dont want to downgrade my software though. :(

Saga Musix says:

Portamento is working perfectly here. Portamento effects are not supposed to be put on the first note, though, only on the notes you want to slide to. If you put a portamento effect next to a note and no other note is playing on that channel yet, the note will not sound in the XM format (the portamento effect is simply ignored in other formats). Basically using portamento should look like this:
C-5 01 ... ...
E-5 01 ... G10
G-5 01 ... G10

There are many possibilities why you wouldn't hear a note in this example (volume envelopes, sample default / global volume, etc...), so it would probably be best if you just sign up on the forums and post the module in question there.

Saga Musix says:

Actually thinking of it, you are probably working at 1 tick per row, which previously (in OpenMPT 1.17-1.19) allowed normal portamentos to work, however at speed 1 only fine and extra-fine slides are supposed to work. ModPlug Tracker 1.16 did this correctly so I removed that "fix" that actually introduced wrong behaviour.

conrad murray says:

Been using modplug for years, and know of producers whom have record contracts and have done pretty well using. I myself had a record deal with Polydor records and publishing labels all from modplug...its an amazing programe