OpenMPT Wiki - Recent changes [en]

Development: Foreign Bugs

Manx — Sat, 06 Jun 2026 08:06:36 GMT

Foreign Bugs

← Older revision		Revision as of 08:06, 6 June 2026
Line 7:		Line 7:
	\|-		\|-
	! Project !! Status !! affects !! Description !! Link		! Project !! Status !! affects !! Description !! Link
			\|-
			\| cross-platform-actions \|\| open \|\| libopenmpt \|\| Cleaner orthogonal API \|\| https://github.com/cross-platform-actions/action/discussions/150
	\|-		\|-
	\| MSVC \|\| open \|\| OpenMPT \|\| LNK4279 warning when building ARM64EC projects with VS2026 18.6.0 Compiler 19.51 \|\| https://developercommunity.visualstudio.com/t/LNK4279-warning-when-building-ARM64EC-pr/11090020 https://developercommunity.visualstudio.com/t/LNK4279-icall-thunk-mismatch-on-ARM64EC-/11087716#T-N11092812		\| MSVC \|\| open \|\| OpenMPT \|\| LNK4279 warning when building ARM64EC projects with VS2026 18.6.0 Compiler 19.51 \|\| https://developercommunity.visualstudio.com/t/LNK4279-warning-when-building-ARM64EC-pr/11090020 https://developercommunity.visualstudio.com/t/LNK4279-icall-thunk-mismatch-on-ARM64EC-/11087716#T-N11092812

Development: Formats/IT

Saga Musix — Sun, 24 May 2026 19:08:51 GMT

← Older revision		Revision as of 19:08, 24 May 2026
Line 220:		Line 220:
	A compressed stream is made of multiple "blocks" of compressed data, where the ''uncompressed'' size of every block is 32768 bytes (32768 sample points for 8-bit samples, 16384 for 16-bit), except for the last block, which may be shorter, depending on the length of the sample.		A compressed stream is made of multiple "blocks" of compressed data, where the ''uncompressed'' size of every block is 32768 bytes (32768 sample points for 8-bit samples, 16384 for 16-bit), except for the last block, which may be shorter, depending on the length of the sample.

	The format conversion specified by the <tt>Cvt</tt> flags in the sample header must be applied to each block individually rather than the whole sample. This is important for the delta encoding flag, which ~~is set for modules saved with~~ Impulse Tracker 2.~~15+~~. If the delta decoding is applied to the whole sample rather than each block individually, there will be audible pops at block boundaries.		The format conversion specified by the <tt>Cvt</tt> flags in the sample header must be applied to each block individually rather than the whole sample. This is important for the delta encoding flag, which was introduced by later registered versions of Impulse Tracker 2.14. If the delta decoding is applied to the whole sample rather than each block individually, there will be audible pops at block boundaries.

	Each block starts with a 16-bit integer which is the ''compressed'' size of the blocks (in bytes, excluding the two bytes for the size).		Each block starts with a 16-bit integer which is the ''compressed'' size of the blocks (in bytes, excluding the two bytes for the size).

Development: Formats/IT

CS127 — Sun, 24 May 2026 19:07:09 GMT

Compressed Samples: unnecessary

← Older revision		Revision as of 19:07, 24 May 2026
(One intermediate revision by the same user not shown)
(No difference)

User:Prayerie

Prayerie — Wed, 20 May 2026 20:37:02 GMT

User account Prayerie was created

Development: Foreign Bugs

Manx — Sun, 17 May 2026 18:26:20 GMT

Foreign Bugs

← Older revision		Revision as of 18:26, 17 May 2026
Line 8:		Line 8:
	! Project !! Status !! affects !! Description !! Link		! Project !! Status !! affects !! Description !! Link
	\|-		\|-
	\| MSVC \|\| open \|\| OpenMPT \|\| LNK4279 warning when building ARM64EC projects with VS2026 18.6.0 Compiler 19.51 \|\| https://developercommunity.visualstudio.com/t/LNK4279-warning-when-building-ARM64EC-pr/11090020		\| MSVC \|\| open \|\| OpenMPT \|\| LNK4279 warning when building ARM64EC projects with VS2026 18.6.0 Compiler 19.51 \|\| https://developercommunity.visualstudio.com/t/LNK4279-warning-when-building-ARM64EC-pr/11090020 https://developercommunity.visualstudio.com/t/LNK4279-icall-thunk-mismatch-on-ARM64EC-/11087716#T-N11092812
	\|-		\|-
	\| Vorbis \|\| open \|\| OpenMPT \|\| Fix typos in tonal masking curve level adjustments \|\|https://gitlab.xiph.org/xiph/vorbis/-/merge_requests/41		\| Vorbis \|\| open \|\| OpenMPT \|\| Fix typos in tonal masking curve level adjustments \|\|https://gitlab.xiph.org/xiph/vorbis/-/merge_requests/41

Development: Formats/XM

Saga Musix — Fri, 15 May 2026 20:55:29 GMT

The instrument "type" byte

@@ Line 42: / Line 42: @@
 The instrument header size (first field of the instrument header) must be respected, otherwise some files will not load correctly. If the size in the file is smaller than the actual header size, pad it with zeros. However, the sample header size is completely ignored by FastTracker 2. Early versions of Sk@leTracker wrote 0 in this field, and there are files in the wild with other, completely arbitrary values (e.g. [https://modarchive.org/module.php?178448 cybernostra weekend.xm]). Hence, ignore this value completely.
 == The mysterious "reserved" byte ==
 In each sample header, there is a "reserved" byte right before the sample name. In fact, FT2 stores the sample name as a Pascal string, so the byte before the name tells the length of the string. FT2 always writes space-padded strings, but if the user manually adds space characters at the end of the sample name, they will count towards the string length, so it's not possible to simply compare the length byte against the string length after trimming space characters. Instead, we can probably be sure that a file was ''not'' made with FT2 if the actual string length is longer than the length indicated by the reserved byte, or if the reserved value is larger than 22.
 == ADPCM samples ==

Development: OpenMPT Format Extensions

Saga Musix — Fri, 15 May 2026 20:48:12 GMT

← Older revision		Revision as of 20:48, 15 May 2026
(2 intermediate revisions by the same user not shown)
Line 14:		Line 14:
	** [] is a variable-length array (length is deduced from some other attribute)		** [] is a variable-length array (length is deduced from some other attribute)
	** [42] denotes an array with 42 entries.		** [42] denotes an array with 42 entries.

			== Additional ModPlug Header Flags ==

			* Extended Filter Range: Doubles the frequency range of the resonant filter. In both IT and XM files, it is bit 12 (<tt>1000</tt>) of the song flags in the header.

	== ModPlug Song Extensions ==		== ModPlug Song Extensions ==
Line 130:		Line 134:

	By default, the last four bytes of an IT instrument (right after the pitch envelope) are unused. If they read <code>MPTX</code> or <code>XTPM</code>, 120 extra bytes follow, one for each note in the sample map. These bytes are the high byte of the sample index, i.e. they need to be multiplied by 256 and then added to the already read sample index.		By default, the last four bytes of an IT instrument (right after the pitch envelope) are unused. If they read <code>MPTX</code> or <code>XTPM</code>, 120 extra bytes follow, one for each note in the sample map. These bytes are the high byte of the sample index, i.e. they need to be multiplied by 256 and then added to the already read sample index.

			Before OpenMPT's (legacy and new) ways of storing the instrument output plugin, ModPlug Tracker already had a different way: The MIDI channel field in the instrument header contains the output plugin slot if its high bit (<code>80</code>) is set. OpenMPT keeps doing this for backwards compatibility if the instrument has no MIDI channel assigned, unless compatibility export is chosen. Impulse Tracker may hang when trying to play such instruments.

			== ModPlug Instrument Extensions (XM only) ==

			ModPlug Tracker stores the instrument's MIDI program in the unused <tt>type</tt> field. OpenMPT keeps doing this for backwards compatibility, but also fills in the standard MIDI fields in the instrument header.

	== OpenMPT Extensions (General Information) ==		== OpenMPT Extensions (General Information) ==

Development: Foreign Bugs

Manx — Wed, 13 May 2026 12:42:21 GMT

Foreign Bugs

← Older revision		Revision as of 12:42, 13 May 2026
(One intermediate revision by the same user not shown)
Line 7:		Line 7:
	\|-		\|-
	! Project !! Status !! affects !! Description !! Link		! Project !! Status !! affects !! Description !! Link
			\|-
			\| MSVC \|\| open \|\| OpenMPT \|\| LNK4279 warning when building ARM64EC projects with VS2026 18.6.0 Compiler 19.51 \|\| https://developercommunity.visualstudio.com/t/LNK4279-warning-when-building-ARM64EC-pr/11090020
	\|-		\|-
	\| Vorbis \|\| open \|\| OpenMPT \|\| Fix typos in tonal masking curve level adjustments \|\|https://gitlab.xiph.org/xiph/vorbis/-/merge_requests/41		\| Vorbis \|\| open \|\| OpenMPT \|\| Fix typos in tonal masking curve level adjustments \|\|https://gitlab.xiph.org/xiph/vorbis/-/merge_requests/41
Line 81:		Line 83:
	\|-		\|-
	\| MSVC \|\| open \|\| OpenMPT/libopenmpt \|\| std::chrono::get_tzdb_list() memory leak \|\| https://github.com/microsoft/STL/issues/2504 https://developercommunity.visualstudio.com/t/stdchronoget-tzdb-list-memory-leak/1644641		\| MSVC \|\| open \|\| OpenMPT/libopenmpt \|\| std::chrono::get_tzdb_list() memory leak \|\| https://github.com/microsoft/STL/issues/2504 https://developercommunity.visualstudio.com/t/stdchronoget-tzdb-list-memory-leak/1644641
	\|-
	~~\| MSVC \|\| open \|\| OpenMPT/libopenmpt \|\| <chrono>: Implement fallback mechanism for chrono's [time.zone] \|\| https://github.com/microsoft/STL/issues/1911~~
	\|-		\|-
	\| MSVC \|\| open \|\| OpenMPT/libopenmpt \|\| <chrono>: Cannot parse "23:59:59" as system_clock::time_point on older Windows versions \|\| https://github.com/microsoft/STL/issues/2163		\| MSVC \|\| open \|\| OpenMPT/libopenmpt \|\| <chrono>: Cannot parse "23:59:59" as system_clock::time_point on older Windows versions \|\| https://github.com/microsoft/STL/issues/2163
Line 103:		Line 103:
	\|-		\|-
	\| --- \|\| --- \|\| --- \|\| --- \|\| ---		\| --- \|\| --- \|\| --- \|\| --- \|\| ---
			\|-
			\| MSVC \|\| wontfix 2026-05-13 \|\| OpenMPT/libopenmpt \|\| <chrono>: Implement fallback mechanism for chrono's [time.zone] \|\| https://github.com/microsoft/STL/issues/1911
	\|-		\|-
	\| MSVC \|\| ignored 2023-02-21 \|\| OpenMPT \|\| no Release Notes for Windows 11 SDK 10.0.22621.0 \|\| https://developercommunity.visualstudio.com/t/no-Release-Notes-for-Windows-11-SDK-100/10061520		\| MSVC \|\| ignored 2023-02-21 \|\| OpenMPT \|\| no Release Notes for Windows 11 SDK 10.0.22621.0 \|\| https://developercommunity.visualstudio.com/t/no-Release-Notes-for-Windows-11-SDK-100/10061520

Development: Formats/IT

CS127 — Mon, 11 May 2026 18:24:33 GMT

MIDI Macro Configuration

← Older revision		Revision as of 18:24, 11 May 2026
(One intermediate revision by the same user not shown)
Line 193:		Line 193:
	! Event !! Default value		! Event !! Default value
	\|-		\|-
	\| ~~MIDI~~ start \|\| <tt>FF</tt>		\| Playback start \|\| <tt>FF</tt>
	\|-		\|-
	\| ~~MIDI~~ stop \|\| <tt>FC</tt>		\| Playback stop \|\| <tt>FC</tt>
	\|-		\|-
	\| ~~MIDI~~ tick \|\| (empty)		\| Playback tick \|\| (empty)
	\|-		\|-
	\| Note on \|\| <tt>9c n v</tt>		\| Note on \|\| <tt>9c n v</tt>
Line 207:		Line 207:
	\| Change pan \|\| (empty)		\| Change pan \|\| (empty)
	\|-		\|-
	\| Bank select \|\| ~~(empty)~~		\| Bank select \|\| <tt>Bc 0 a 20 b</tt>
	\|-		\|-
	\| Program change \|\| <tt>Cc p</tt>		\| Program change \|\| <tt>Cc p</tt>
	\|}		\|}

			"Bank select" and "program change" are sent before every "note on" message for instruments that have a MIDI bank and/or program assigned respectively.

	=== Compressed Samples ===		=== Compressed Samples ===

Manual: Frequently Asked Questions

Saga Musix — Sat, 09 May 2026 19:05:28 GMT

← Older revision		Revision as of 19:05, 9 May 2026
Line 161:		Line 161:
	=== Why is there no Dark Mode in OpenMPT? ===		=== Why is there no Dark Mode in OpenMPT? ===

	Except for [[Manual: Setup/Display\|~~Pattern Colors~~]], OpenMPT does not support any kind of custom colors or skinning/theming. OpenMPT uses standard Win32 widgets which are provided by Windows. Since Windows 10, Windows itself does not provide a configuration dialog to change these colors any more. The ~~modern~~ light/dark mode does not apply to these widgets. You can still change the widget colors with [https://www.wintools.info/index.php/classic-color-panel Classic Color Panel] though. Note that this will affect all applications that make use of standard Win32 widgets. In Wine, the colors can be adjusted with winecfg.		Except for a number of [[Manual: Setup/Display\|user-definable colors]] particularly for the pattern, sample and instrument editor views, OpenMPT does not support any kind of custom colors or skinning / theming. OpenMPT uses standard (Win32) widgets which are provided by Windows. Since Windows 10, Windows itself does not provide a configuration dialog to change these colors any more. The operating system′s light / dark mode setting does not apply to these widgets. You can still change the widget colors with [https://www.wintools.info/index.php/classic-color-panel Classic Color Panel] though. Note that this will affect all applications that make use of standard Win32 widgets. In Wine, the colors can be adjusted with <tt>winecfg</tt>.

	=== Why is previously usable Feature X unavailable in the latest version of OpenMPT? ===		=== Why is previously usable Feature X unavailable in the latest version of OpenMPT? ===