musical thoughts

Akai EWI USB

I spent my first day yesterday with the Akai EWI USB, the newest model they make. I thought I’d record my thoughts and findings because I suppose anyone looking to purchase one will benefit from hearing what another player thinks about it.

I’m not an owner of any previous EWI model, so my perspective is looking at this as a midi controller in its own right, not comparing it to the rest of the more expensive EWI models. I had some significant frustrating experiences with it up front, but I finally got to where I was making music with the thing.

Installation
The EWI ships with a CD with the driver and included software. My drive would not read that disc. I was able to work around that by reauthoring it as a DVD. I had to go to another machine with a newer drive that would read it, copy off the installation files (845 MB) and burning a DVD. Luckily, I had read deathshadow’s page about his EWI USB experience, so I was aware of the issue. Nonetheless, it was an irritating step. Akai should have just burned a DVD. The specs say it’s a DVD, but it ain’t.

So other than that, running the installer was straightforward. I got the chance to change the paths to my liking, important to me since I keep plugins in a specific folder structure. The bundled Garritan Aria software installs as both a standalone and a VSTi (optionally–selectable at install time). But there is no way to avoid installing the standalone. Akai bundled the utility that loads EWI configuration into the Aria software. So the first thing to do is run that bundled standalone.

With the Aria software running, you go and make config settings that allow it to read and write midi from the EWI, which is a class-compliant midi controller. Interestingly, the config settings written to the EWI persist, so you won’t need to run this each time. And with it being class-compliant, you can plug it in to a DAW and use it like a generic midi controller. So you wouldn’t need to install Aria on your main DAW if you had a reason not to.

One mistake that caused me frustration: I set up the EWI for midi in but not midi out in Aria at first. So it couldn’t store the settings correctly. I think it’s annoying that there is no indication that settings are being stored nor any explicit “write to EWI” button that makes it obvious what is happening. That’s an irritating user interface choice. I spent a couple hours of frustration with the EWI running stock settings (EWI fingering, all gains set to the midpoint of the range) before I realized to set the midi out and that fixed it.

Once I got that right, I set up my fingering system preference (flute), along with gain for the breath and bite controllers. I disabled pitch bend from the plate since I’m an EWI n00b. I will very likely remap it to a different controller and learn to use bite instead. The manual says it’s a good idea to leave all the performance settings alone, but I think that’s insane. It offers a reset button so you can’t really go too far wrong or make the thing unplayable.

Speaking of fingerings, there are multiple systems to pick from. Flute system is pretty familiar to me except for the fingering for C. I struggled vainly on EWI standard fingering, but I think I could get used to it if I had to. Fingering maps are not editable, at least with the included apps, but you have to figure it’s done in software.

The sounds in the included software are pretty damn good. They all have aftertouch mapped, so chomping on your mouthpiece will produce some variation. Most of them are based on real instrument samples, and they are categorized into woodwinds, brass, strings, percussion, and synth. My secret weapon (shh don’t tell) is the xylophone patch. The Aria software lets you layer up four samples, with gain, pan and reverb control of each separately. Putting a soft xylo hit on the stack with a synth is wicked. Done right it is not even perceptible as a separate instrument.

But I was very eager to see how it worked with my favorite VST instruments that I already know and love. And the short answer is make sure that aftertouch is enabled, and it is a beautiful experience. I played the hell out of some sounds on MinimogueVA. I’m finding new possibilities in these sounds that I have been playing thanks to the aftertouch on the EWI.

But stacking up sampled instruments in the Aria software is also really nice. The flute sucks if you use it alone, but layered with a bass clarinet for example, it’s a lot more convincing. So I think I may explore using the included samples in the manner of the old school Roland D-50 which layered a cheap and cheesy sample attack with a synthesized sustained instrument tone. That axe did it to make the most of what was at the time insanely expensive sample memory. But in the process of working around that limitation it created some of the most memorable sounds of that era.

Additional sounds can be loaded into Aria–they want to be SFZ files. I have not seen this point mentioned in other reviews. The Aria is very very light on CPU. It compares very favorably to other soundfont players in that regard.

I was surprised at the resistance to airflow. I’ve heard playing oboe described as “blowing into your thumb,” and this is a pretty apt description for EWI too. I am used to moving at least ten times as much air as the EWI uses, but it does allow longer phrases than a flute does. I can not play it if I seal my embouchure and direct all my air into the mouthpiece. I leak a decent amount of air intentionally, and I think this is typical from watching some other EWI players.

I do not have a natural inclination to chomp the mouthpiece. I am used to recorder style, just putting my embouchure on the edge of it. But the bite sensor adds a lot of depth to sounds. I did turn my bite gain way way down and even so it makes most of the Aria sounds go totally crazy when you chomp. I have yet to get comfortable with the EWI-specific performance gestures like bite and pitch bend plate and octave roller. I think I’ll fall into line with enough practice.

The keys that on a flute would correspond to Ab, Eb, low C# and low C are adjustable by loosening a screw and pivoting the key around its attachment point. this helped me immensely with the low keys. I couldn’t work the Eb reliably until I made significant adjustments. I dialed this in while playing over the course of an hour or so and I think I’m happy with it now.

Everything considered, I am more than satisfied. This is a professional quality instrument. I have a keyboard midi controller that is not (cheap junk may be a more apt term for the keyboard), so I am acutely aware of the differences. I got my EWI from JRR Shop, and they did a good job. Looking at their channel on Youtube you can get a coupon code, or you’ll also get a discount coupon for signing up, so this is available for less than the $299 list price, and they shipped it free. I am most pleased and will be a return customer for JRR Shop.

I find the thing pretty comfortable to hold. I’ll probably replace the neckstrap that it came with. Placing it upright on a stand is hampered by the USB cord that exits the bottom of the instrument.

Rob @ April 11, 2009 9:17 am Comments (2)

[prev: video: soulful machine] [next: video: EWI demo]

2 Comments »

  1. Rob, so you know I’ve launched http://www.ewiusb.com – On several pages in the site I address some issues you mention such as airflow, ways to make Aria and other VST’s work better under windows (ASIO4ALL)

    Now that you’ve had yours a month or so, I’d be interested in hearing any issues you may have come across. I’m currently writing a how-to set up page, and a troubleshooting page since the ones provided by Akai is a bit… lacking.

    Comment by deathshadow — May 17, 2009 @ 11:05 am

  2. I left my review here:
    http://www.patchmanmusic.com/forum/viewtopic.php?f=37&t=1923

    Comment by ProDigit — September 9, 2009 @ 3:57 pm

RSS feed for comments on this post.

Leave a comment

You must be logged in to post a comment.

>