This page is read from MIDI Instrument Definitions, a Python library used in the author's other projects, in which every number is traced to a document its maker published. Its source is on GitHub.

UDO Audio Super 6 MIDI implementation

The MIDI implementation of the UDO Audio Super 6: what it answers to, and the 86 controls it offers.

At a glance

Firmware

Not recorded.

MIDI channel

1 to 16.

MPE

Received: its voices are spread across its MIDI channels, a note to each.

Voices

12, or 6 as set on the instrument.

Note range

Not recorded.

Velocity

Received. Release velocity is received.

Aftertouch

Channel pressure and polyphonic, each answered. It sends aftertouch too.

Pitch bend

12 semitones, and the range can be changed.

Program change

Received and sent, with 128 presets.

MIDI clock

Sent and received.

Start and stop

Sent and received.

Control change

81 controls, in the tables below.

NRPN

Supported. 46 of the controls below have one.

System exclusive

Not recorded.

Controls

In the order the definition gives them, by group. Under each control is the name a program calls it by, once pymidiinstrumentdefs.load("udo_audio/super_6") has loaded them.

Global

Without a group

Where these facts come from

Source documents

• UDO Super 6 Owner's Manual, 1.4, dated 24 May 2024, its user manual, read on 4 October 2026 (the file read).
• Super 6 | Support & Downloads, its download page, read on 4 October 2026.

How they were read

Owner's Manual, 140 pages, the PDF's own title Super_6_Manual_1.4: the MIDI Specifications chapter at pp. 120-132, which is where every number here comes from; the connections for both models at pp. 25-26; the patches at p. 16; the bender at pp. 70 and 77; the voice modes at pp. 54 and 93; the global settings at p. 103; and MPE support at pp. 105-106. And UDO's Super 6 support page, for the firmware on offer.

THE FRONT MATTER IS NUMBERED IN ROMAN NUMERALS AND THE BODY IN ARABIC, WHICH IS A TRAP THE CITATION GATE CANNOT CATCH. Sheets 1 to 13 print x, xi, xii, xiii; sheet 14 prints 14 and every sheet after it prints its own number. So page_offset is 0 for everything this file cites - and a citation to p. 12 would pass the gate while being wrong, because the arithmetic lands on sheet 12 and the text is there, under a folio the document calls xii. The clearest statement of the voice count is on that sheet and is not cited for exactly that reason; two others on numbered pages are cited instead.

THE MIDI SPECIFICATIONS CHAPTER IS IN FIVE TABLES AND THREE SHAPES:

p. 120 System Real-Time Messages, and Channel Messages - a direction for each

pp. 121-127 Continuous Controller Messages - CC # | Value Range | Parameter Name

pp. 127-128 Registered Parameter Numbers

p. 128 Non-Registered Parameter Numbers, Global Parameters

pp. 129-132 Non-Registered Parameter Numbers, Patch-Related Parameters

THE CONTROLLER TABLE GIVES EVERY NUMBER FROM 0 TO 127 A ROW, whether it does anything or not, with - in the other two columns where it does not. That is asserted rather than noticed, and it is what makes this table complete rather than selective: 97 of its 128 rows name a parameter and 31 are blank, and a blank row is the maker saying nothing rather than the reading losing something.

THE NRPN NUMBER IS PRINTED TWICE AND THE TWO FORMS CHECK EACH OTHER. A row gives the number in decimal and then its MSB and LSB in hexadecimal - 1027, 08H, 03H - and 8 x 128 + 3 is 1027, which is how this format holds an NRPN. All 46 rows that carry a pair agree, which is a free assertion and the one the PRO-800's hexadecimal column taught one rank earlier.

AND THE PATCH-RELATED NRPN IS THE CONTROLLER NUMBER PLUS 1024. Measured, not assumed: of the 41 patch-related NRPNs that name a parameter, 40 name the same parameter as controller N minus 1024, and the pairing below is made on those names rather than on the arithmetic. The 41st is joined anyway - see below - so 41 controls carry both numbers.

AND THE NRPN BLOCK IS A MIRROR OF THE CONTINUOUS PARAMETERS ONLY, which the second reader put more sharply than the arithmetic does: not one of the 40 controls whose value bands are named has an NRPN at all - every one of them is a blank row in the NRPN table. So the pattern is not that every parameter comes twice, but that every continuous patch parameter does, at two resolutions, and the switched ones, which have nothing to gain from fourteen bits, are left out of it. That is an observation about every row printed and not a rule the maker states.

THE ONE PAIR THE TWO TABLES NAME DIFFERENTLY IS NRPN 1119 AND CONTROLLER 95. The controller table says HPF Fix Cutoff Frequency and the NRPN table says HPF Cutoff Frequency - the word Fix in one and not the other. They are joined on three grounds: it is the only unmatched name on either side, the arithmetic puts it exactly where the other forty sit, and one name contains the other. The label below is the controller table's, because that is the table the control's number comes from.

THE VALUE RANGE COLUMN IS REAL, which most are not. Most rows read 0-127 or 0-16383, and 40 of the controls below have their bands named - 0 = Triangle, 21 = Square, 43 = Random, 64 = Saw, 85 = HF, 107 = HF TRK - which is what values holds, each band by its lowest number. A row reading a plain range is continuous and carries nothing.

SIXTEEN OF THE 97 NAMED CONTROLLER ROWS ARE THE PROTOCOL AND NOT THIS INSTRUMENT, and this table is unusual in listing them at all: controller 6 is Data Entry MSB and 38 is LSB for Control 6 (Data Entry), 96 and 97 the data increment and decrement, 98 and 99 the NRPN selects, 100 and 101 the RPN selects, and 120 to 127 the channel mode messages, which the validator refuses outright. The maker is being complete rather than claiming them - which is the opposite of the instrument one rank earlier, where the maker put its own MIDI track solos on 120 to 127. Bank Select on controller 0 is kept, as two other definitions here keep theirs. That leaves 81 controls off the table, plus the five global settings below.

AND THE SECOND READER FOUND THAT 38 BELONGED IN THAT LIST WHEN I HAD KEPT IT. The guide beside this corpus says to leave 6 and 38 out where they are only how an NRPN's value travels - and this maker names 38 in as many words - so keeping it was keeping half of a pair. The two readings agreed about the table and a second reader is for more than the numbers.

THE FIVE GLOBAL NRPNs ARE CONTROLS AND THAT IS A JUDGEMENT. They are this instrument's own MIDI settings - its channel, its clock transmit and receive, its program change transmit and receive - addressable over NRPN like anything else, and 2054 is absent from an otherwise contiguous run of 2051 to 2056, which the maker does not account for. Two of the five are the same facts midi.clock and midi.program_change record from the other side, which is not a contradiction: a field says what the instrument does and a control says how to change it from outside.

EVERY NUMBER WAS READ TWICE AND THE TWO READINGS AGREE. The second reading, made without sight of the first, used a different library's layout mode on a different interpreter and then checked itself against four of the sheets rendered and read by eye.

AND THE GRID HAD TO BE BOUNDED TWICE OVER, WHICH IS THE READING LESSON HERE. Every sheet of this manual carries a navigation sidebar down its left edge with its own ruled lines, so the grid is bounded by x - including the sidebar put the table's first column inside a cell forty points wide. And printed p. 127 holds the last ten rows of the controller table and the start of the Registered Parameter Numbers table, which has five columns where the controller table has three, so the grid is bounded by height as well: without that, controllers 118 to 127 were silently lost. A third bound was needed because the sheet the controller table opens on draws its heading row's cells differently from its data rows, adding two column edges that belong to nothing - so a column edge is one that recurs on many rows, measured at 21 to 52 times each against the spurious pair's once.

WHAT THE MESSAGE TABLES SAY, AND THEY SAY IT WITH DIRECTIONS. MIDI Timing Clock, Start and Stop are all Yes in both columns (manual p. 120); so are Note On, Note Off, Channel Pressure and Pitch Bend. Polyphonic Key Pressure is No transmitted and Yes received - it answers to polyphonic pressure and never sends it. Control Change and Program Change both read "See Global Settings" (manual p. 120), which is where their switches are.

CONTINUE IS NOT IN THE TABLE AT ALL. Start and Stop are there and Continue is not listed - which is an absence rather than a No, and is recorded as one. The S-1 in this corpus has Continue marked x in both columns, which is the maker saying so; this is the maker not saying.

AND THE QUOTATION GATE CAUGHT TWO SENTENCES THIS FILE HAD WRONG, WHICH IS WORTH RECORDING AGAINST THE METHOD THAT PRODUCED THEM. Reading a page by taking its words and sorting them by position - which is how the sidebar was dropped while this instrument was being read - puts a run set in a different style where its coordinates fall rather than where it is read. On p. 105 that turned "set the DYNAMICS switch in the VCA section to either 1/2 or ON." (manual p. 105) into set the switch in the VCA section to either DYNAMICS 1/2 ON, because DYNAMICS, 1/2 and ON are styled differently from the words around them. Both velocity sentences were quoted that way and the gate refused both. Reading order is what get_text() gives and what a quotation needs; sorting by position is for a table.

EVERY QUOTATION IN THIS FILE'S PROSE CARRIES A LOCATOR, AUDITED BY PAIRING THE QUOTE MARKS: 25 quotations, 25 locators - 24 citing a page and one naming the unpaginated support page - with the six remaining pairs being field values. The gate checks all 25 and none is under the twelve characters it requires, so the two counts reconcile exactly.

NOT RECORDED: system exclusive, and the mode. The words System Exclusive and SysEx appear nowhere in these 140 pages - but system exclusive is neither a channel message nor a system real-time message, so the two tables that do enumerate would not have listed it either. So its absence here is a silence and not an enumeration, and nothing is recorded. With no implementation chart in the classic form there is no omni or poly mode row to read, though controllers 124 to 127 are listed as the protocol's own.

ALSO NOT RECORDED: the note range, which no page states.