Overview
The ENO M2 Digital Wind Instrument is a beginner-level woodwind-style electronic wind instrument (EWI) with a form factor resembling a recorder.
Features
The M2 features 12 built-in sounds that can be played through the built-in speaker, or via a headphone jack on the side of the instrument. It also supports connection to a computer via Bluetooth MIDI, or via a USB cable.
Ten keys on the front are used for note selection, and these can be configured for fingering as a recorder, flute, or hulusi, an Asian wind instrument. All keys are touch-sensitive.
The instrument has a three octave range that is controlled via an octave-up and octave-down key on the rear. The rear also features function keys for controlling the built-in sounds, transposition (up/down 12 semitones), and breath sensitivity. A two-digit alphanumeric display aids in navigation of these parameters.
Playing the Instrument
The M2 is played by blowing into the mouthpiece, like a recorder, and fingering the desired note. Breath response is good, and notes can be articulated quickly. Some skill is required when changing fingerings, due to the touch-sensitive keys, and it’s import to move all fingers at the same time to avoid unwanted notes from sounding. This is not unique to M2; even expensive instruments like the $1000+ Yamaha, Akai, and Roland EWIs require this of the player.
The real creative possibilities of the M2 emerge when it is connected to a software synthesizer on a computer via Bluetooth or MIDI USB. When played, the M2 sends note on/off events, and breath information is transmitted via MIDI Continuous Controller (CC) number 11 (expression controller). All notes are sent with a MIDI velocity of 120. This is not configurable, but isn’t really necessary as the breath data is sufficient to provide a lot of expressiveness.
Here is a recording I made, using the HaLION Symphonic Orchestra library. You can see the MIDI CC data below the piano roll notation.
The Teardown
My main goal in buying this instrument was to see if I could extract the mouthpiece and breath sensor for use in other projects. The body of the instrument is easily opened by removing two screws. Once open you can see two circuit boards. The top board holds the main keys of the instrument, and the bottom board contains the electronics.
Build quality looks fine, with good solder joints. The screws that hold the touch-sensitive keys in place a stainless steel and feel solid.
I haven’t had much success in identifying the CPU by its part number (CM146CUF). It may be an NXP Semiconductor MCXA146VMP, an ARM Cortex running at 48 MHz. I’ve been unable to locate a JTAG header for external programming so far, but I may be missing it. Locating that might allow for development of custom firmware. The part number on the chip at the bottom (BOY52CUP) also doesn’t come up in a Google search, but since it’s adjacent to an on-board antenna trace, I assume it’s the Bluetooth radio. Here are all the chip part numbers and my best guess as to their usage:
- CM146CUF - CPU
- 324 R-K6A (14 pin) - unknown - possibly data for onboard samples?
- XPT4809 083CAA or maybe OBECAA (8 pin). - audio amplifier
- HT6873 B5J40A (8 pin) - also an amplifier - class D audio amp
- 4056H B2444 (8 pin) - unknown
- BOY52CUP (12 x 4 pin) - near bluetooth antenna, so probably the bluetooth radio
- TM74HC138 (16 pin) - driver for the alphanumeric display
Summary
The ENO M2 Digital Wind Instrument is a beginner-level woodwind-style musical instrument that offers a surprising level of functionality and build quality for a low price. While it won’t satisfy the requirements of a professional woodwind player looking for an electronic instrument, it is well-built instrument that is satisfying to play, either via the built-in sounds, or when connected to an external synthesizer or softsynth running in a DAW.
I think I’ll be able to make use of this instrument in my studio as an input device for wind parts in my DAW. And at $60, harvesting one for parts is definitely not out of the question. It may also turn out to be hackable via rewriting the device firmware, if I can find a way.
