1Arrange & Preview
Click cells to place notes on a 16th-note grid, then press Play. Arranging and previewing runs entirely client-side with Tone.js — nothing reaches the server until you export.
2Exporting a Content Credential
Pressing Export to MIDI sends the pattern to the server, where it’s built into a real Standard MIDI File and signed. The manifest isn’t a sidecar or a different-format stand-in — it’s embedded directly in the .mid file itself, as a Sequencer-Specific Meta Event placed just before the track’s End of Track event, per the “Embedding manifests into Standard MIDI Files” section of the C2PA specification draft.
A pattern created this way, from nothing, with no prior ingredients, is a straightforward c2pa.created action. Since it was assembled by placing notes in a tool rather than performed or captured, digitalSourceType would typically be digitalCreation — the same value used for anything composed directly in digital form, as covered in Actions and digitalSourceType.
{
"assertions": {
"c2pa.actions.v2": {
"actions": [
{
"action": "c2pa.created",
"description": "Built a step-sequenced Standard MIDI File.",
"digitalSourceType": "http://cv.iptc.org/newscodes/digitalsourcetype/digitalCreation",
"softwareAgent": "Mix-O-Tron MIDI Arranger"
}
]
}
}
}If the arrangement were instead built from an AI-generated pattern, digitalSourceType would move to trainedAlgorithmicMedia — see the AI Disclosure Assertion for how to layer on richer disclosure.