How to convert MusicXML to Sequence format?

Use the MusicXML-to-Sequence converter included in the repository, which parses MusicXML files and outputs Sequence JSON, enabling interoperability with notation software. This tool is part of the reference implementation and supports core music events.

Sequence vs MIDI: which is better for web audio projects?

Sequence is better for web audio due to its direct WebAudio API alignment and JSON flexibility, while MIDI is more established for hardware control but suffers resolution loss in MIDI 1.0. Sequence also supports nested sequences and extensible events, unlike standard MIDI.

Can Sequence be used for real-time music performance?

Yes, but with caveats: it's designed for timed events and works with WebAudio for playback, but MIDI 1.0 compatibility involves resolution loss, and binary serialization can aid efficiency. However, it lacks built-in low-latency optimizations compared to dedicated protocols.

How to handle nested sequences in Sequence JSON?

Define sequences with unique IDs in the 'sequences' array and reference them using 'sequence' events in the events array, specifying the ID and duration. This allows reusable sub-sequences for complex arrangements, as shown in the README example.

What tools can render Sequence data as sheet music?

Scribe, a reference implementation, is a music notation interpreter that consumes Sequence JSON and renders it as HTML, and it also parses ABC notation. However, visualization tools are limited compared to mature notation software.

Is Sequence compatible with OSC for controlling hardware?

Yes, Sequence is designed to be transmittable via OSC, making it suitable for controlling hardware synthesizers or other OSC-enabled devices. The event structure maps to OSC messages, though specific mappings may require custom implementation.

Sequence JSON — Timed Musical Event Format

What is Sequence JSON?

Sequence is a JSON-based specification for representing sequences of timed musical events, such as notes, chords, and audio parameter changes. It provides a structured way to store, transfer, and playback music data that aligns with WebAudio API features and is compatible with MIDI and OSC protocols. The format is designed to be minimal, extensible, and interoperable across different music applications.

Target Audience

Audio developers, music technologists, and creators building WebAudio-based sequencers, notation renderers, or music data interchange tools. It's also relevant for those integrating music sequencing into web applications or converting between formats like MusicXML.

Value Proposition

Developers choose Sequence for its clean JSON structure, direct WebAudio alignment, and interoperability with standards like MIDI and OSC. Its extensible event system allows for custom use cases while maintaining backward compatibility, and the reference implementations provide a solid foundation for building music applications.

A way of creating music sequence data in JSON

Use Cases

Best For

Building WebAudio-based sequencers or playback engines
Converting MusicXML or ABC notation to a lightweight JSON format
Storing and transferring music sequence data between applications
Creating interoperable music tools that work with MIDI or OSC
Developing music notation renderers that consume structured event data
Implementing nested or layered music arrangements with reusable sequences

Not Ideal For

Applications requiring detailed sheet music notation with graphical elements beyond chords and meter
Low-latency MIDI performance systems where resolution loss with MIDI 1.0 is critical
Projects needing a fully standardized, widely-adopted format with extensive tooling and community support
Systems that require built-in audio synthesis or sound generation, as Sequence is solely a data format

Pros & Cons

Pros

JSON and Binary Flexibility

Sequences can be stringified to human-readable JSON for debugging or serialized to compact binary data for efficient transfer, as highlighted in the README's examples and specifications.

WebAudio Integration

Event types like 'param' directly align with WebAudio API AudioParams, enabling precise control over audio parameters in web-based music applications, as described in the event definitions.

Extensible Event System

The format supports core events while allowing extensions; consumers silently ignore unknown types, ensuring backward compatibility and adaptability for custom use cases.

Nested Sequencing Support

Sequences can reference and play back other sequences by ID, enabling complex, layered arrangements, as demonstrated in the 'sequence' event and sequences array.

Cons

MIDI 1.0 Resolution Loss

The README explicitly notes that transmission via MIDI 1.0 involves some resolution loss, making it less suitable for applications requiring high-precision MIDI data.

Incomplete Event Specifications

Key elements like the 'sequence' event's targetId are marked as TBD in the README, indicating unresolved details for instrument targeting, which can hinder interoperability.

Minimal Error Handling

The format allows silent ignoring of unsupported events and has vague recovery rules for invalid 'meter' events, potentially leading to inconsistent behavior across implementations.

Frequently Asked Questions

What is Sequence JSON?

Target Audience

Value Proposition

Use Cases

Best For

Building WebAudio-based sequencers or playback engines
Converting MusicXML or ABC notation to a lightweight JSON format
Storing and transferring music sequence data between applications
Creating interoperable music tools that work with MIDI or OSC
Developing music notation renderers that consume structured event data
Implementing nested or layered music arrangements with reusable sequences

Not Ideal For

Applications requiring detailed sheet music notation with graphical elements beyond chords and meter
Low-latency MIDI performance systems where resolution loss with MIDI 1.0 is critical
Projects needing a fully standardized, widely-adopted format with extensive tooling and community support
Systems that require built-in audio synthesis or sound generation, as Sequence is solely a data format

Pros & Cons

Pros

JSON and Binary Flexibility

Sequences can be stringified to human-readable JSON for debugging or serialized to compact binary data for efficient transfer, as highlighted in the README's examples and specifications.

WebAudio Integration

Event types like 'param' directly align with WebAudio API AudioParams, enabling precise control over audio parameters in web-based music applications, as described in the event definitions.

Extensible Event System

The format supports core events while allowing extensions; consumers silently ignore unknown types, ensuring backward compatibility and adaptability for custom use cases.

Nested Sequencing Support

Sequences can reference and play back other sequences by ID, enabling complex, layered arrangements, as demonstrated in the 'sequence' event and sequences array.

Cons

MIDI 1.0 Resolution Loss

The README explicitly notes that transmission via MIDI 1.0 involves some resolution loss, making it less suitable for applications requiring high-precision MIDI data.

Incomplete Event Specifications

Key elements like the 'sequence' event's targetId are marked as TBD in the README, indicating unresolved details for instrument targeting, which can hinder interoperability.

Minimal Error Handling

The format allows silent ignoring of unsupported events and has vague recovery rules for invalid 'meter' events, potentially leading to inconsistent behavior across implementations.

Frequently Asked Questions

Sequence JSON

What is Sequence JSON?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

Sequence JSON

What is Sequence JSON?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?