::::terrauniversalis::::
midi innovation awards 2026 · software prototype · non-commercial
mayan mapper brings pads, keys, knobs and faders into a shared performance language. two mirrored maschine mk2 units, traktor pro 4 and djay pro form the musical core; light, image and the wider terrauniversalis architecture extend it.
the page reads in full in any order. these paths only signal the route that matters to each visitor; they hide nothing and block nothing.
::public
watch and listen→grasp the benefit→meet the project→official entry
::jury
proposal→innovation→evidence→implemented vs. planned
::status legenddocumentedin validationplanned
documented06:53 · existing project recording
the recording could not load. open the original file directly with the link below.
traktor, the two maschine units and djay pro in the same control environment. press play and enable sound. this is a recording, not a live connection to the studio: it documents musical operation and is not a physical end-to-end midi 2.0 test.
5
registered midi controllers
32
pads · two 16-pad maschine mk2 surfaces
139
registered mapping actions
the counts describe the project’s documented inventory and mappings, not 139 individually benchmarked actions. read the preserved project dossier.
the musician’s problem is practical: several surfaces and applications should feel like one instrument without losing which device, pad or channel produced the gesture. bastion addresses that with mapping universalis and its mayan mapper.
documented01 · mirrored performance
the left unit addresses decks 1 and 3; the right uses a horizontal mirror for decks 2 and 4. equivalent functions can sit symmetrically while the devices retain separate endpoint and channel identities. the musical benefit: a coherent two-handed layout, not a second controller that simply duplicates the first.
documented02 · multi-application control
the project documents simultaneous operation of both applications in its performance environment. transport, mixing, loops, effects and other actions depend on the selected application mapping. the musical benefit: a physical performance language that can address different musical destinations.
documented03 · reuse, not replacement
2× maschine mk2, traktor kontrol x1, komplete kontrol m32 and hercules djcontrol mix form the registered rig. the five-device setup demonstrates the approach; it is not a proprietary hardware ceiling. the musical benefit: build around equipment already in the studio.
a physical controller’s identity, the performed gesture and its destination are separate responsibilities. mapping universalis keeps them associated so that page, orientation and application can change without turning every control into an anonymous shortcut.
a pad, key, knob or fader produces midi. the registered controllers originate midi 1.0.
mayan mapper associates device, endpoint, channel, control, page and orientation with the chosen mapping.
the route that configuration supports. windows midi services carries ump on the documented station.
it reaches the mapped traktor or djay pro action. other audiovisual destinations have their own state.
::a precise distinction
equipment inventory, maintenance, location and custodian information are application-level records associated with a midi source or event. an ordinary note on does not itself contain the complete equipment record. mayan nomenclature supplies that meaning; it does not redefine the midi packet format.
the dossier describes djay pro setups on iphone, ipad, macbook, windows 10/11 and surface duo 1. these are distinct configurations, not a claim that every device ran in the same session or that all platforms use the same midi api. usb, virtual midi, coremidi and network midi are route choices according to host and application support. compatibility references do not imply vendor sponsorship.
three different things deserve three different labels: the musical performance, midi 1.0 carried in ump, and locally generated midi 2.0 channel voice packets. one is not proof of the others.
documented
the existing recording and dossier document the controller and application environment. they do not constitute a latency benchmark, a user study or a physical type 4 interoperability test.
documented
the preserved json reports successful local decoding of note on, control change and note off with the windows midi services sdk. it explicitly records that transmission was not requested.
planned
the recorded validation has no destination endpoint. physical type 4 transmission, midi-ci, profiles and property exchange are not presented here as completed capabilities.
::protocol and evidence boundaries
| layer | what is documented | what it does not establish |
|---|---|---|
| existing hardware | midi 1.0 output from the registered native instruments and hercules sources. | native midi 2.0 controller hardware. |
| windows transport | midi 1.0 messages carried in universal midi packet format by windows midi services. | automatic conversion into midi 2.0 channel voice protocol. |
| type 4 proof | software construction and local decoding of three 64-bit midi 2.0 channel voice packets. | a synthesizer receiving them, audible playback or a hardware round trip. |
::the three published packets, field by fieldpreserved validation · 31 august 2026 utc
40903C00FFFF0000
note on · note 60 · 16-bit velocity 65535.
mt
4
group
0
status
9 · note on
channel
0
note
60 (0x3c)
velocity
65535
40B0070080000000
control change · controller 7 · 32-bit value 0x80000000.
mt
4
group
0
status
b · cc
channel
0
index
7 (volume)
data
0x80000000
40803C0000000000
note off · note 60 · release velocity 0.
mt
4
group
0
status
8 · note off
channel
0
note
60 (0x3c)
release
0
this is an inspection of the values published in midi2-vcm-proof.json, not live midi monitoring. group 1 / channel 1 in human-readable numbering. the source json retains its original civic action labels; these are application semantics, not evidence that the actions were executed.
::reproducibility · the evidence is on this domain
validation: passed sendResult: not_requested destinationEndpointDeviceId: null midiCiImplemented: false
validation json ↗ original powershell proof ↗ protocol explanation (microsoft) ↗
the script requires powershell 7.4+ and the windows midi services module. without -Send it validates locally; sending is a separate action and was not performed in the preserved result. no tunnel, login or studio connection is needed to read this page, open the recording or inspect the published files.
documented
registered controller rig, mapping inventory, dual-maschine geometry, musical recording and the separate local midi 2.0 packet result. the source files remain available and the result has not been rewritten to imply a new test.
in validation
reproducible end-to-end routing tests and receiver-side type 4 evidence. the test that would verify it: repeat the script with -Send to a real endpoint and record the receiver result.
planned
measured latency and error recovery, midi-ci work, accessible interaction testing and a documented mapping sdk. no accessibility outcome, universal compatibility or unrecorded benchmark is asserted here.
terrauniversalis contains sixteen universes. mayan os is its operational protocol; bastion universalis is the infrastructure and operating trunk containing the institutional grp. citoyen is the citizen arm, kukulkan the regenerative orp and warrior a contextual security expression within shield. those identities remain intact: the musical interface is the focus of this presentation, not a replacement for the architecture.
a controller gesture can express a request or signing intent; midi is not itself a cryptographic signature. protected actions depend on identity, authorization and cryptographic controls. planned civic workflows and incomplete subsystem bindings must not be mistaken for finished midi demonstrations.
the complete earlier presentation, its illustrations, acknowledgments, module descriptions and access references are retained in the dossier files. this page changes the reading order without deleting those files or their evidence.
complete preserved presentation · en presentación completa conservada · es architecture-review.json remote-comparison.json operational-evidence.json
the institutional data foundation and its recorded row counts are background evidence, not a musical-performance benchmark. the preserved dossier also contains optional development-system links, which may require separate access or show a tunnel warning: they are not required for the review path on this page.
documented03:52 · project identity and ecosystem. kept separate from the musical evidence.
the recording could not load. open the original file directly with the link below.
with gratitude to tobias erichsen, creator of rtpmidi, for enabling networked midi on windows. bastion carries that spirit of connecting existing devices and people into its own work. a midi innovation need not be limited to music: the official rules also welcome lighting, installations and automated systems. this page leads with music because that is the clearest documented demonstration of this project.
return to the musical performance ↑ official entry on midi.org ↗