utaformatix-data

1.1.0indexed

Serves as a common data container for singing synthesis software, using JSON format. Supports multiple programming languages with conventions for timing, pitch, and musical notation.

JSJVMNative·sdercolin/utaformatix-data

Stars

—

Used by

dependents

—

Health

/ 100

UtaFormatix Data (.ufdata)

Common data container for singing synthesis softwares used by UtaFormatix.

Language-specific interfaces

Kotlin Multiplatform: Kotlin implementation for JVM/JavaScript/Native
TypeScript: TypeScript definitions
Python: Python implementation
C#: C# implementation

Value conventions

The .ufdata format doesn't prescribe detailed specifications for the values it contains, but there are common conventions for some types based on the support of most formats by UtaFormatix:

Tick: Each tick represents 1/480 of a beat, aligning with a typical MIDI resolution of 480 ticks per beat. This resolution facilitates precise timing details in musical data. If working with other formats (e.g., Standard MIDI) that use different resolutions, it is crucial to convert tick resolutions accordingly.
Key: The key values correspond to MIDI key numbers, with . This standard provides a reference point for middle C, facilitating an understanding of note pitches in relation to standard musical notation.

Data structure

The data is stored as JSON with file extension .ufdata.

Sample

Root (Document) object

Variable name	Description	Type
formatVersion	The version code of the ufdata structure	int32
project

Project object

Track object

Note object

Pitch object

Only points with changed values are included.

e.g. [(1, 1.0), (4, 3.0)] implies ticks between (in this case, 2 and 3) have the same value of 1.0.

Time signature object

Variable name	Description	Type
measurePosition

Tempo object

Variable name	Description	Type
tickPosition	Tick position of the tempo change	int64
bpm	Tempo in beats-per-minute	int32

Related libraries

Surfaced from shared tags and platforms — no rankings paid for.

kson★ 171

kson-orgCombines JSON and YAML features for a robust, readable, and toolable data format. Offers flexible syntax, native JSON Schema support, and code embed functionality. Supports multiple platforms and IDE environments.Shared: serialization, json, fileformat

protobufs★ 168

meshtasticProtobuf message definitions for a mesh radio network, documented with API reference and prebuilt TypeScript, Rust and cross-language client packages for app and firmware integration.Shared: typescript, serialization, fileformat

geok★ 48

piruinProvides a small geometry library for handling basic geometric operations and data exchange using GeoJSON. Supports various geometries like Point, LineString, and Polygon with utilities for distance, area, and serialization.Shared: serialization, json, fileformat

name	Project name	string
tracks	Track list. See Track object for details	array<object>
timeSignatures	Time signatures. See Time signature object for details	array<object>
tempos	Tempo changes. See Tempo object for details	array<object>
measurePrefix	Count of measure prefixes (measures that cannot contain notes, restricted by some editors)	int32

name	Track name	string
notes	Note list. See Note object for details	array<object>
pitch	Pitch data. See Pitch object for details	nullable object

key	Semitone value of the note's key (Center C = 60)	int32
tickOn	Tick position of the note's start	int64
tickOff	Tick position of the note's end	int64
lyric	Lyric	string
phoneme	Phoneme (if available)	string

ticks	Tick positions of the data points	array<int64>
values	Semitone values of the data points. When `isAbsolute` is true, `null` can be included to represent default values.	array<double?>
isAbsolute	Whether the pitch values are absolute or relative to the note's key	bool