BMS (File Format) - Revision history

Louis Miles: /* Tools */

2025-07-01T12:12:35Z

Tools

← Older revision		Revision as of 12:12, 1 July 2025
Line 687:		Line 687:

	== Tools ==		== Tools ==
	[https://github.com/~~vgmtrans~~/vgmtrans VGMTrans] (analyses and converts BMS to MIDI)<br>		[https://github.com/magcius/vgmtrans VGMTrans Fork] (analyses and converts BMS to MIDI)<br>
	[https://cdn.discordapp.com/attachments/421356154795458570/1291660143758413824/BMS_DEC.zip?ex=6719f440&is=6718a2c0&hm=f44c5197a070f30a00283858942f9e4ae5066034862eba006f8abe87a228a6aa& BMS_DEC] (converts BMS to MIDI)<br>		[https://cdn.discordapp.com/attachments/421356154795458570/1291660143758413824/BMS_DEC.zip?ex=6719f440&is=6718a2c0&hm=f44c5197a070f30a00283858942f9e4ae5066034862eba006f8abe87a228a6aa& BMS_DEC] (converts BMS to MIDI)<br>
	[https://github.com/XAYRGA/JaiSeqX JaiSeqX] (playback for JAudio1 and JAudio2 BMS files)		[https://github.com/XAYRGA/JaiSeqX JaiSeqX] (playback for JAudio1 and JAudio2 BMS files)

Louis Miles: /* Structure */

2025-06-10T12:23:53Z

Structure

← Older revision		Revision as of 12:23, 10 June 2025
Line 19:		Line 19:
	**OpenTrack command that starts playing the following track		**OpenTrack command that starts playing the following track

	*'''Channel Specific Track''' a kind of management track for channel definitions		*'''Channel Specific Track''' a kind of management track for channel/Main Track definitions
	**Usally contains '''C1''' OpenTrack events for each channel. For some unknown reason, the exact same looping and duration events from the global track need to be repeated here, otherwise some events such as pitchwheel will not work in the song.		**Usally contains '''C1''' OpenTrack events for each executor track (channel). For some unknown reason, the exact same looping and duration events from the global track need to be repeated here, otherwise some events such as pitchwheel will not work in the song.

	== Data ==		== Data ==

Louis Miles: Better explanation

2025-06-10T12:21:30Z

Better explanation

← Older revision		Revision as of 12:21, 10 June 2025
Line 4:		Line 4:

	== Structure ==		== Structure ==
	BMS ~~works very similar to Midi Format 2, with 16 channels (0-15)~~, ~~as well as a variety of possible independent tracks~~ containing events such as notes, patch changes, etc.		BMS consists of pure assembly code, where each track containing events such as notes, patch changes, etc. is an independent executor thread with opcodes to execute.
			In contrast to Midi, events are read linearly per channel in a data stream and interpreted byte by byte. This means that multiple tracks within the same channel cannot be played back synchronously and would therefore have to be baked onto one track. However, BMS tracks can jump or call to different places in the file, e.g. to loop the song or to ensure a very high storage efficiency.

	~~In contrast~~ to ~~Midi, events are read linearly per channel in a data stream and interpreted byte by byte. This means that multiple~~ tracks within the same channel cannot be played back synchronously and would therefore have to be baked onto one track. However, BMS tracks can jump or call to different places in the file, e.g. to loop the song or to ensure a very ~~high storage efficiency~~.		The game's audio engine can only play up to 16 tracks at a time - very similar to MIDI with its 16 channels.

	BMS also includes extended MIDI operations, such as more powerful versions of controllers, with fade-in capability, and higher resolution control values. However, no song in either Galaxy game makes use of this.		BMS also includes extended MIDI operations, such as more powerful versions of controllers, with fade-in capability, and higher resolution control values. However, no song in either Galaxy game makes use of this.

Louis Miles at 13:26, 8 June 2025

2025-06-08T13:26:37Z

← Older revision		Revision as of 13:26, 8 June 2025
Line 497:		Line 497:
	\| {OpCode[1]} {Program[1]}<br />OpCode: one byte, E3.<br />Program: one byte with range 0x00 through 0xFF. This byte represents a LIST entry in the [[IBNK]] belonging to the defined WSYS ID.		\| {OpCode[1]} {Program[1]}<br />OpCode: one byte, E3.<br />Program: one byte with range 0x00 through 0xFF. This byte represents a LIST entry in the [[IBNK]] belonging to the defined WSYS ID.
	\| E3 0B<br /><br />E3: OpCode<br />0B: IBNK LIST entry 11<br />(In relation to Megahammer, this Program holds movement related sounds)		\| E3 0B<br /><br />E3: OpCode<br />0B: IBNK LIST entry 11<br />(In relation to Megahammer, this Program holds movement related sounds)
	\| Defines the Instrument Patch / Keyboard of an [[IBNK]] bank. If no E2 Bank Select Command was used before, it will default to Bank 0.</br>		\| Defines the Instrument Patch / Keyboard of an [[IBNK]] (bank). If no E2 Bank Select Command was used before, it will default to Bank 0.</br>
	Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the chord to be used from the [[CIT (File Format)\|CIT]].		Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the chord to be used from the [[CIT (File Format)\|CIT]].
	\|-		\|-

Louis Miles: /* Filestructure */

2025-06-08T13:18:14Z

Filestructure

← Older revision		Revision as of 13:18, 8 June 2025
Line 19:		Line 19:

	*'''Channel Specific Track''' a kind of management track for channel definitions		*'''Channel Specific Track''' a kind of management track for channel definitions
	**Usally contains '''C1''' OpenTrack events for each channel. For some unknown reason, the exact same ~~setting that follows the PPQN setting on~~ the ~~tempo~~ track ~~must~~ be repeated here ~~after the C1 events~~, otherwise some events such as pitchwheel will not work in the song.		**Usally contains '''C1''' OpenTrack events for each channel. For some unknown reason, the exact same looping and duration events from the global track need to be repeated here, otherwise some events such as pitchwheel will not work in the song.

	== Data ==		== Data ==
	BMS files contain raw instructions for the audio engine without any headers or filesize checks. Each instruction (OpCode) stands for its own function in the engine. The following table lists all JAudio2 OpCodes that have functions in SMG2:		BMS files contain raw instructions for the audio engine without any headers or filesize checks. Each instruction (OpCode) stands for its own function in the engine. The following table lists all JAudio2 OpCodes that have functions in SMG2:

Louis Miles: Improved explanations

2025-06-08T13:14:46Z

Improved explanations

← Older revision		Revision as of 13:14, 8 June 2025
Line 4:		Line 4:

	== Structure ==		== Structure ==
	BMS works very similar to Midi Format 2, with 16 channels (0-15), as well as a variety of possible independent tracks containing events such as notes, patch changes, etc..		BMS works very similar to Midi Format 2, with 16 channels (0-15), as well as a variety of possible independent tracks containing events such as notes, patch changes, etc.

	In contrast to Midi, events are read linearly per channel in a data stream and interpreted byte by byte. This means that multiple tracks within the same channel cannot be played back synchronously and would therefore have to be baked onto one track. However, BMS tracks can jump or call to different places in the file, e.g. to loop the song or to ensure a very high storage efficiency.		In contrast to Midi, events are read linearly per channel in a data stream and interpreted byte by byte. This means that multiple tracks within the same channel cannot be played back synchronously and would therefore have to be baked onto one track. However, BMS tracks can jump or call to different places in the file, e.g. to loop the song or to ensure a very high storage efficiency.
Line 12:		Line 12:
	=== Filestructure ===		=== Filestructure ===
	There are no headers or filesize checks. The file usually starts with the following:		There are no headers or filesize checks. The file usually starts with the following:
	*'''~~Pointer to Channel Creator Events~~''' BMS always starts directly with ~~a '''C1''' channel creator event with channel 0~~ containing ~~pointer~~ to the ~~actual channel creator section.~~		*'''Global Track / Tempo Track''' BMS always starts (very similary to Midi's "Tempo Track" or "Conductor Track") directly with track containing Meta-Events, which only contains global control data, typically:
	*'''~~Tempo~~ Track''' ~~This usually starts with a PPQN set, and then with~~ a track ~~with BPM changes and loop events.~~		**Pulses per Quarter Note (PPQN) set
	*~~'''Channel Creator Section''' This~~ contains '''C1''' ~~channel creator~~ events for each channel. For some unknown reason, the exact same setting that follows the PPQN setting on the tempo track must be repeated here after the C1 events, otherwise some events such as pitchwheel will not work in the song.		**Tempo (BPM)
			**Looping commands (to keep BPM changes synchronized during the song if necessary)
			**OpenTrack command that starts playing the following track

			*'''Channel Specific Track''' a kind of management track for channel definitions
			**Usally contains '''C1''' OpenTrack events for each channel. For some unknown reason, the exact same setting that follows the PPQN setting on the tempo track must be repeated here after the C1 events, otherwise some events such as pitchwheel will not work in the song.

	== Data ==		== Data ==
Line 277:		Line 282:
	\| {OpCode[1]} {ChannelNumber[1]} {TrackPointer[3]}<br />OpCode: one byte, C1.<br />ChannelNumber: one byte with range 0x00 through 0x0F. 0x00 = Channel 0, 0x0F = Channel 15.<br />TrackPointer: three bytes with range 0x000000 through 0xFFFFFF. Defines a start offset in the file to play.		\| {OpCode[1]} {ChannelNumber[1]} {TrackPointer[3]}<br />OpCode: one byte, C1.<br />ChannelNumber: one byte with range 0x00 through 0x0F. 0x00 = Channel 0, 0x0F = Channel 15.<br />TrackPointer: three bytes with range 0x000000 through 0xFFFFFF. Defines a start offset in the file to play.
	\| C1 04 05 B4 73<br /><br />C1: OpCode<br />04: Channel 4<br />05 B4 73: Offset to track		\| C1 04 05 B4 73<br /><br />C1: OpCode<br />04: Channel 4<br />05 B4 73: Offset to track
	\| ~~Creates~~ a channel ~~with a start pointer to a track with notes to be played~~. Channel 15 is usually reserved for Yoshi Drums. [[SMR.szs#~~MAIN_BGM~~\|~~When~~ enabled in the SMR.szs]], channel 0 can be used for timing and ~~chord~~ usage ~~and will~~ not play any instruments from the ~~soundbank~~.		\| Starts playing a certain track on a certain channel. Channel 15 is usually reserved for Yoshi Drums. [[SMR.szs#BGM_parameters\|If enabled in the BGM parameter table in SMR.szs]], channel 0 can be used for timing and chords usage that do not play any instruments from the sound bank.
	\|-		\|-
	\| C2		\| C2
Line 479:		Line 484:
	\| {OpCode[1]} {Bank[1]} {Program[1]}<br />OpCode: one byte, E1.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.<br />Program: one byte ranging from 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.		\| {OpCode[1]} {Bank[1]} {Program[1]}<br />OpCode: one byte, E1.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.<br />Program: one byte ranging from 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.
	\| E1 01 0F<br /><br />E1: OpCode<br />01: WSYS ID 1<br />0F: IBNK LIST entry 15<br />(01 0F is the percussion set for Yoshi Drums)		\| E1 01 0F<br /><br />E1: OpCode<br />01: WSYS ID 1<br />0F: IBNK LIST entry 15<br />(01 0F is the percussion set for Yoshi Drums)
	\| Defines ~~Instrument~~ and ~~Soundbank~~ to be ~~used in a Track~~. A combination of E2 and E3.		\| Defines/changes patch and bank to be played on the target channel. A combination of E2 and E3.
	\|-		\|-
	\| E2		\| E2
Line 485:		Line 490:
	\| {OpCode[1]} {Bank[1]}<br />OpCode: one byte, E2.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.		\| {OpCode[1]} {Bank[1]}<br />OpCode: one byte, E2.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.
	\| E2 53<br /><br />E2: OpCode<br />53: WSYS ID 83<br />(This bank holds sounds for Megahammer)		\| E2 53<br /><br />E2: OpCode<br />53: WSYS ID 83<br />(This bank holds sounds for Megahammer)
	\| Defines the WSYS/IBNK bank whose sounds are to be used in a ~~Track~~.</br>		\| Defines/changes the WSYS/IBNK (bank) whose sounds are to be used in a channel.</br>
	Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the note scale to be used from the [[CIT]].		Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the note scale to be used from the [[CIT (File Format)\|CIT]].
	\|-		\|-
	\| E3		\| E3
	\| JASSeqParser::cmdPrg		\| JASSeqParser::cmdPrg
	\| {OpCode[1]} {Program[1]}<br />OpCode: one byte, E3.<br />Program: one byte with range 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.		\| {OpCode[1]} {Program[1]}<br />OpCode: one byte, E3.<br />Program: one byte with range 0x00 through 0xFF. This byte represents a LIST entry in the [[IBNK]] belonging to the defined WSYS ID.
	\| E3 0B<br /><br />E3: OpCode<br />0B: IBNK LIST entry 11<br />(In relation to Megahammer, this Program holds movement related sounds)		\| E3 0B<br /><br />E3: OpCode<br />0B: IBNK LIST entry 11<br />(In relation to Megahammer, this Program holds movement related sounds)
	\| Defines the Instrument Patch / Keyboard of an IBNK bank. If no E2 Bank Select Command was used before, it will default to Bank 0.</br>		\| Defines the Instrument Patch / Keyboard of an [[IBNK]] bank. If no E2 Bank Select Command was used before, it will default to Bank 0.</br>
	Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the chord to be used from the [[CIT]].		Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the chord to be used from the [[CIT (File Format)\|CIT]].
	\|-		\|-
	\| E4		\| E4

Louis Miles at 17:31, 6 June 2025

2025-06-06T17:31:12Z

← Older revision		Revision as of 17:31, 6 June 2025
Line 17:		Line 17:

	== Data ==		== Data ==
	BMS files contain raw instructions for the audio engine. Each instruction (OpCode) stands for its own function in the engine. The following table lists all JAudio2 OpCodes that have functions in SMG2:		BMS files contain raw instructions for the audio engine without any headers or filesize checks. Each instruction (OpCode) stands for its own function in the engine. The following table lists all JAudio2 OpCodes that have functions in SMG2:

	{\| class="wikitable"		{\| class="wikitable"

Louis Miles: Filestructure and more info

2025-06-06T17:07:25Z

Filestructure and more info

← Older revision		Revision as of 17:07, 6 June 2025
Line 3:		Line 3:
	BMS files are '''B'''inary '''M'''usic '''S'''equences that store commands for the audio engine to play notes, similar to the MIDI file format.		BMS files are '''B'''inary '''M'''usic '''S'''equences that store commands for the audio engine to play notes, similar to the MIDI file format.

			== Structure ==
			BMS works very similar to Midi Format 2, with 16 channels (0-15), as well as a variety of possible independent tracks containing events such as notes, patch changes, etc..

			In contrast to Midi, events are read linearly per channel in a data stream and interpreted byte by byte. This means that multiple tracks within the same channel cannot be played back synchronously and would therefore have to be baked onto one track. However, BMS tracks can jump or call to different places in the file, e.g. to loop the song or to ensure a very high storage efficiency.

			BMS also includes extended MIDI operations, such as more powerful versions of controllers, with fade-in capability, and higher resolution control values. However, no song in either Galaxy game makes use of this.

			=== Filestructure ===
			There are no headers or filesize checks. The file usually starts with the following:
			*'''Pointer to Channel Creator Events''' BMS always starts directly with a '''C1''' channel creator event with channel 0 containing pointer to the actual channel creator section.
			*'''Tempo Track''' This usually starts with a PPQN set, and then with a track with BPM changes and loop events.
			*'''Channel Creator Section''' This contains '''C1''' channel creator events for each channel. For some unknown reason, the exact same setting that follows the PPQN setting on the tempo track must be repeated here after the C1 events, otherwise some events such as pitchwheel will not work in the song.

	== Data ==		== Data ==
	BMS files contain raw instructions for the audio engine~~. There are no headers or filesize checks~~. Each instruction (OpCode) stands for its own function in the engine. The following table lists all JAudio2 OpCodes that have functions in SMG2:		BMS files contain raw instructions for the audio engine. Each instruction (OpCode) stands for its own function in the engine. The following table lists all JAudio2 OpCodes that have functions in SMG2:

	{\| class="wikitable"		{\| class="wikitable"
Line 663:		Line 676:
	\|		\|
	\|}		\|}

			== Trivia ==
			* Many BMS filenames contain the suffix ''midi_cnv''. This could indicate that Midis were first converted to a (perhaps text-based) CNV file, which was then converted to the BMS format. A similar situation applies to Nintendo's SDK tool for converting the Nintendo DS's SSEQ sequence format, which first converts Midis to a text-based SMFT format, which is then converted to the final SSEQ format.

	== Tools ==		== Tools ==
			[https://github.com/vgmtrans/vgmtrans VGMTrans] (analyses and converts BMS to MIDI)<br>
	[https://cdn.discordapp.com/attachments/421356154795458570/1291660143758413824/BMS_DEC.zip?ex=6719f440&is=6718a2c0&hm=f44c5197a070f30a00283858942f9e4ae5066034862eba006f8abe87a228a6aa& BMS_DEC] (converts BMS to MIDI)<br>		[https://cdn.discordapp.com/attachments/421356154795458570/1291660143758413824/BMS_DEC.zip?ex=6719f440&is=6718a2c0&hm=f44c5197a070f30a00283858942f9e4ae5066034862eba006f8abe87a228a6aa& BMS_DEC] (converts BMS to MIDI)<br>
	[https://github.com/XAYRGA/JaiSeqX JaiSeqX] (playback for JAudio1 and JAudio2 BMS files)		[https://github.com/XAYRGA/JaiSeqX JaiSeqX] (playback for JAudio1 and JAudio2 BMS files)

Louis Miles at 14:22, 3 June 2025

2025-06-03T14:22:22Z

← Older revision		Revision as of 14:22, 3 June 2025
Line 262:		Line 262:
	\| C1		\| C1
	\| JASSeqParser::cmdOpenTrack		\| JASSeqParser::cmdOpenTrack
	\| {OpCode[1]} {ChannelNumber[1]} {TrackPointer[3]}<br />OpCode: one byte, C1.<br />ChannelNumber: one byte with range 0x00 through 0x0F. 0x00 = Channel 0, 0x0F = Channel 15.<br />TrackPointer: three bytes with range 0x000000 through 0xFFFFFF. Defines an offset in the file.		\| {OpCode[1]} {ChannelNumber[1]} {TrackPointer[3]}<br />OpCode: one byte, C1.<br />ChannelNumber: one byte with range 0x00 through 0x0F. 0x00 = Channel 0, 0x0F = Channel 15.<br />TrackPointer: three bytes with range 0x000000 through 0xFFFFFF. Defines a start offset in the file to play.
	\| C1 04 05 B4 73<br /><br />C1: OpCode<br />04: Channel 4<br />05 B4 73: Offset to track		\| C1 04 05 B4 73<br /><br />C1: OpCode<br />04: Channel 4<br />05 B4 73: Offset to track
	\| Creates a channel with a start pointer to a track with notes to be played. Channel 15 is usually reserved for Yoshi Drums.		\| Creates a channel with a start pointer to a track with notes to be played. Channel 15 is usually reserved for Yoshi Drums. [[SMR.szs#MAIN_BGM\|When enabled in the SMR.szs]], channel 0 can be used for timing and chord usage and will not play any instruments from the soundbank.
	\|-		\|-
	\| C2		\| C2

Louis Miles: CIT info and more.

2025-06-03T14:18:45Z

CIT info and more.

← Older revision		Revision as of 14:18, 3 June 2025
Line 262:		Line 262:
	\| C1		\| C1
	\| JASSeqParser::cmdOpenTrack		\| JASSeqParser::cmdOpenTrack
	\| {OpCode[1]} {~~TrackNumber~~[1]} {~~Pointer~~[3]}<br />OpCode: one byte, C1.<br />~~TrackNumber~~: one byte with range 0x00 through 0x0F. 0x00 = ~~Track~~ 0, 0x0F = ~~Track~~ 15.<br />~~Pointer~~: three bytes with range 0x000000 through 0xFFFFFF. Defines an offset in the file.		\| {OpCode[1]} {ChannelNumber[1]} {TrackPointer[3]}<br />OpCode: one byte, C1.<br />ChannelNumber: one byte with range 0x00 through 0x0F. 0x00 = Channel 0, 0x0F = Channel 15.<br />TrackPointer: three bytes with range 0x000000 through 0xFFFFFF. Defines an offset in the file.
	\| C1 04 05 B4 73<br /><br />C1: OpCode<br />04: ~~Track~~ 4<br />05 B4 73: Offset		\| C1 04 05 B4 73<br /><br />C1: OpCode<br />04: Channel 4<br />05 B4 73: Offset to track
	\| Creates a ~~Track which can play Notes~~. ~~Track~~ 15 is usually reserved for Yoshi Drums.		\| Creates a channel with a start pointer to a track with notes to be played. Channel 15 is usually reserved for Yoshi Drums.
	\|-		\|-
	\| C2		\| C2
Line 466:		Line 466:
	\| {OpCode[1]} {Bank[1]} {Program[1]}<br />OpCode: one byte, E1.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.<br />Program: one byte ranging from 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.		\| {OpCode[1]} {Bank[1]} {Program[1]}<br />OpCode: one byte, E1.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.<br />Program: one byte ranging from 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.
	\| E1 01 0F<br /><br />E1: OpCode<br />01: WSYS ID 1<br />0F: IBNK LIST entry 15<br />(01 0F is the percussion set for Yoshi Drums)		\| E1 01 0F<br /><br />E1: OpCode<br />01: WSYS ID 1<br />0F: IBNK LIST entry 15<br />(01 0F is the percussion set for Yoshi Drums)
	\| Defines ~~the~~ Instrument to be used in a Track.		\| Defines Instrument and Soundbank to be used in a Track. A combination of E2 and E3.
	\|-		\|-
	\| E2		\| E2
Line 472:		Line 472:
	\| {OpCode[1]} {Bank[1]}<br />OpCode: one byte, E2.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.		\| {OpCode[1]} {Bank[1]}<br />OpCode: one byte, E2.<br />Bank: one byte with range 0x00 through 0xFF. This byte represents a WSYS ID.
	\| E2 53<br /><br />E2: OpCode<br />53: WSYS ID 83<br />(This bank holds sounds for Megahammer)		\| E2 53<br /><br />E2: OpCode<br />53: WSYS ID 83<br />(This bank holds sounds for Megahammer)
	\| Defines the WSYS/IBNK whose sounds are to be used in a Track.		\| Defines the WSYS/IBNK bank whose sounds are to be used in a Track.</br>
			Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the note scale to be used from the [[CIT]].
	\|-		\|-
	\| E3		\| E3
Line 478:		Line 479:
	\| {OpCode[1]} {Program[1]}<br />OpCode: one byte, E3.<br />Program: one byte with range 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.		\| {OpCode[1]} {Program[1]}<br />OpCode: one byte, E3.<br />Program: one byte with range 0x00 through 0xFF. This byte represents a LIST entry in the IBNK belonging to the defined WSYS ID.
	\| E3 0B<br /><br />E3: OpCode<br />0B: IBNK LIST entry 11<br />(In relation to Megahammer, this Program holds movement related sounds)		\| E3 0B<br /><br />E3: OpCode<br />0B: IBNK LIST entry 11<br />(In relation to Megahammer, this Program holds movement related sounds)
	\| Defines the Keyboard ~~which holds more specific sounds to~~ an IBNK.		\| Defines the Instrument Patch / Keyboard of an IBNK bank. If no E2 Bank Select Command was used before, it will default to Bank 0.</br>
			Timing Channel: If the track is on a channel for timing and chord usage, this command instead defines the ID of the chord to be used from the [[CIT]].
	\|-		\|-
	\| E4		\| E4