there is an easier way. if you are on chrome, edge or firefox on a computer,
the midi mapper does all of this for you and produces a file to send.
this page is the fallback for safari, for anyone who would rather use a midi monitor they
already trust, or for anyone the mapper does not work for.
what this is for
lfo hero drives the op-1 field, with tx-6 and
tp-7 support in testing. every one of those was mapped by measuring real
hardware, because the published midi references turned out to be wrong in at least six places.
to support any other teenage engineering device — op-1 (original), op-z,
ep-133, ob-4, po series — we need someone who owns one to record what it actually sends. that
is what this page asks you to do. you do not need to know anything about midi.
plug your device in over usb, open the monitor, and select your device as the input. if you see
nothing at all in later steps, check the nothing is showing up section —
several te devices transmit nothing until you change a setting on the device itself.
2 — two rules that make or break this
a midi log does not say where a message came from.
it records that cc 7 appeared, not that it was track 2's fader. these two rules are
the only thing that lets us tell them apart afterwards:
do the steps in order, and skip none. if your device has no such control,
that is a useful answer — note skipped 6 — no pan and move on. just don't
silently leave it out.
pause about 3 seconds between steps, touching nothing. the gaps are what
chop the log back up into one block per control. without them the log is close to
unreadable.
start recording in the monitor, do every step below, then stop and export. one continuous log
for the whole run is what we want — please don't export one file per step.
3 — the steps
the list below updates to match. if your device has no per-track mixer at all, set this to 1.
4 — answer these too
the log alone doesn't tell us everything. please send answers to these as well:
what is the device, and what firmware version is it running?
what does the monitor call the port — copy the name and
manufacturer exactly as shown, including capitals and punctuation
how many tracks did you set above?
which steps did you skip, and was it because the control doesn't exist or because you
couldn't find it? (these mean very different things to us)
did you have to change any setting on the device to make it send midi?
this one matters a lot — the tx-6 sends nothing until you set midi control = in
and clock src = usb, and we would never have guessed that
if your monitor can send midi and you tried it: did the device visibly react?
(a fader moving on screen, a value changing.) don't worry if you skipped this
paste your questionnaire answers into the message, and attach the exported log. if the forum
won't accept the log as an attachment, rename it to .txt — that is almost always
allowed where .json is not.
would rather use github? open an issue and attach them there instead.
thank you — genuinely. this is the only way devices we don't own ever get supported.
nothing is showing up
try a different usb cable. plenty of usb-c cables are charge-only and carry
no data at all.
check the device's midi settings. several te devices ship with midi output
off, or have mutually exclusive in/out modes where selecting one disables the other.
a recorder may only transmit while rolling. the tp-7, for instance, sends
nothing at all while the tape is stopped — which looks exactly like broken hardware.
if you unplugged and replugged, the monitor may still be listening to the
old, dead port. reselect the input, or restart the monitor.
op1 lfo hero