Choose MidiStreamPlayer when MIDI messages are created live at runtime.

Use MidiStreamPlayer when your application generates MIDI messages dynamically. It is the best fit when notes depend on user input, game state, procedural rules, or simulation data available only at runtime.

Compared with MidiFilePlayer:

MidiFilePlayer is optimized for complete MIDI song playback.
MidiStreamPlayer is optimized for event-by-event live control.

Quick Start

Place the MidiStreamPlayer prefab in your scene, get a reference in script, then send messages with MPTK_PlayEvent().

Decision Guide

Prefer MidiStreamPlayer when:

timing is driven by gameplay code,
MIDI messages are generated one by one or in small batches,
you need immediate control over channels/controllers/notes.

Prefer MidiFilePlayer when:

you want full-song sequencing from existing MIDI files,
transport controls (seek, loop, timeline) are central,
you consume events from loaded MIDI content.

See also: Real-Time MIDI Messages Workflow; MPTKEvent Concept and Data Model; MidiPlayerTK.MidiStreamPlayer.MPTK_PlayEvent; MidiPlayerTK.MidiStreamPlayer.MPTK_StopEvent