[PD] Patch for Akai EWI (was "Reading and writing binary files")
ingo at miamiwave.com
Thu Mar 10 11:53:07 CET 2011
just out of curiosity I checked the dump requests in order to see if there
is any reason for transmission of these NRPN controllers.
There is absolutely no reason for them!
I've attached my updated SysEx chart for the EWI-USB in case you want to
mess around with anything.
BTW the NRPN controllers are only being sent when there is a dump request
from the Aria software to the EWI. Not when data is being sent to the EWI.
After the dump is transmitted to the EWI the software sends another full (3
part) dump request and everything on page 1 of the chart is repeated.
To me it looks like "Plogue" - who wrote the software - simply forgot to
take out the NRPNs.
This got me confused in the beginning, too. It's just a general problem when
people like ewi-usb.com put some incorrect information on the web and don't
correct this information anymore after it turns out to be wrong. Then guys
like you and many others get confused.
> -----Ursprüngliche Nachricht-----
> Von: David [mailto:dfkettle at gmail.com]
> Gesendet: Mittwoch, 9. März 2011 20:00
> An: Ingo
> Cc: pd-list at iem.at
> Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary
> See below.
> On Wed, Mar 9, 2011 at 1:36 PM, Ingo <ingo at miamiwave.com> wrote:
> > Hi David,
> >> I looked at your code, and I think I understand it, more or less. But
> >> I couldn't see where you're sending the 6-byte NRPN message before and
> >> after the SysEx message. Isn't it necessary?
> > No! SysEx doesn't require any NRPN message to get enabled. I have no
> > what the Aria software is sending out but it is definitely not
> > There are a lot of strange things with the Garritan / Plogue software.
> Thanks. I agree, the software is a little weird. For example, when you
> save the settings, why does it save them in two different files? I
> assumed at first that all the settings would be saved in a single
> file. It doesn't explain that anywhere, I just discovered it by poking
> around and opening the files in a text editor that can handle binary
> >> I got this information from a web site created by someone who
> >> reverse-engineered the SysEx messages for the EWI USB:
> >> http://www.ewiusb.com/
> >> According to him, you have to send the '63 01 62 04 06 20' before each
> >> SysEx, and '63 01 62 04 06 10' after the last one. You're not doing
> >> that? I haven't tested any of this stuff yet, I'm a little paranoid
> >> about screwing up my EWI. I can probably recover just by pressing the
> >> reset button if something goes wrong, but I'd rather not take the
> >> chance.
> > I had double checked my information with that website. It turned out
> > there are several things that are wrong in this article. I wrote the guy
> > from ewiusb.com an email and told him about the errors but never got any
> > answer. He never corrected anything either. It doesn't look like the
> site is
> > active anymore.
> I think you're right, I sent him an email a couple of weeks ago and
> never got a reply.
> > BTW, you cannot break anything by sending sysex messages to an
> > I am using this editor daily with no problem.
> > I don't know which reason you have to trust one guy more than any other
> Sorry, I didn't mean any offense. I was only erring on the side of
> caution. I was just afraid of "bricking" my EWI.
> > However I did discover an error in the patch this morning when I
> > a modified version into my hardware machine. "Pitchbend down" doesn't
> > restored correctly from the file. So there is a fixed version attached.
> > also writes the 6th value of the shorter sysex strings into the file
> > was ignored before. Just in case it would have any undocumented (ha, ha,
> > meaning.
> Thanks again.
> > Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 22489 bytes
Desc: not available
More information about the Pd-list