| Namespace | Windows.Devices.Midi2.Utilities.Files |
|---|---|
| Type Name | MidiFileWriteResult |
| Type | WinRT Runtime Class |
| IDL | MidiFileWriteResult.idl |
MidiFileWriteResult is what every write method on MidiStandardFileWriter returns. Check Succeeded before telling anyone the file was saved.
| Property | Description |
|---|---|
Succeeded |
True when the file was written |
Status |
The MidiFileWriteStatus describing what happened |
TrackCount |
How many tracks were written |
ByteCount |
How large the file is |
SkippedEventCount |
How many messages were left out because MIDI 1.0 can’t express them |
SkippedEventCount is zero for any sequence that came from a Standard MIDI File, because everything in it is already MIDI 1.0. It only matters when the sequence has Universal MIDI Packets. A per-note controller, a per-note pitch bend, and 8-bit System Exclusive have no MIDI 1.0 form, so there’s nothing to write for them.
A count above zero isn’t a failure. The rest of the file was written, and Succeeded is still true. Whether to tell people depends on what they were saving. For a recording of a MIDI 2.0 device, it’s usually worth telling them.
Windows MIDI Services is an open source project with all source available on GitHub. We have a great community on Discord as well. Between GitHub and Discord, you should find the information you are looking for.
