Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand how to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files") To: PD List pd-list@iem.at Message-ID: AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really need sysex. Attached [nrpnout] (original version by David McCallum) and [nrpnout-yamaha] where CC numbers are modified according to Yamaha specs. You may need to match two of the four CC numbers with your gear (the other two are always the same), and check if your gear needs MSB and LSB address or just one "NRPN number".
Andras
Sorry, it seems i didn't read your first mail carefully. So you need NRPN and sysex. NRPN is easy then, you just have to check that you use the right CC numbers. Sysex is easy too if you have a functional [midiout] :o) otherwise it doesn't work. I couldn't find (i don't have the first mails anymore), which OS are you using? On Linux, it works for sure, on other OSs, give it a try because it may just work. I recommend that you use a physical loopback to test the throughput: you send out the MIDI from your interface and feed it back to its input and see [midiin] if it arrives and if it arrives in its entirety. BTW the second inlet of [midiout] and the second outlet of [midiin] are for port numbers, which is not exactly the same as channel number: channel 3 of your second MIDI interface would be 19 and so on. And you'll have to send a comma separated list of decimals(!) to the first inlet of [midiout]: something like [240, 1, 2, 3, 4, 5, 6, 247(
Andras
On Tue, Mar 8, 2011 at 03:07, David dfkettle@gmail.com wrote:
Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand how to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files") To: PD List pd-list@iem.at Message-ID: AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really need sysex. Attached [nrpnout] (original version by David McCallum) and
[nrpnout-yamaha]
where CC numbers are modified according to Yamaha specs. You may need to match two of the four CC numbers with your gear (the other two are always the same), and check if your gear needs MSB and LSB address or just one "NRPN number".
Andras
Hi David,
here's a full EWI-USB editor. However, it only works one way! Pd -> EWI-USB. It cannot retrieve data from the EWI.
If you want to save your data you should specify a path (marked with red "bangs") twice for loading and saving and you need to set the midi port. Nothing else to do.
I have tested it with Linux (Ubuntu). Not sure if it works on any other OS.
Hope it's useful for some people!
Cheers Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag von David Gesendet: Dienstag, 8. März 2011 03:07 An: pd-list@iem.at; muranyia@gmail.com Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand how to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files") To: PD List pd-list@iem.at Message-ID: AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really need sysex. Attached [nrpnout] (original version by David McCallum) and [nrpnout-
yamaha]
where CC numbers are modified according to Yamaha specs. You may need to match two of the four CC numbers with your gear (the other two are
always
the same), and check if your gear needs MSB and LSB address or just one "NRPN number".
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thanks, I'll give it a try! I really only need it for Linux, because I can use the bundled software from Akai on Windows.
David.
On Tue, Mar 8, 2011 at 12:35 PM, Ingo ingo@miamiwave.com wrote:
Hi David,
here's a full EWI-USB editor. However, it only works one way! Pd -> EWI-USB. It cannot retrieve data from the EWI.
If you want to save your data you should specify a path (marked with red "bangs") twice for loading and saving and you need to set the midi port. Nothing else to do.
I have tested it with Linux (Ubuntu). Not sure if it works on any other OS.
Hope it's useful for some people!
Cheers Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag von David Gesendet: Dienstag, 8. März 2011 03:07 An: pd-list@iem.at; muranyia@gmail.com Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand how to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files") To: PD List pd-list@iem.at Message-ID: AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really need sysex. Attached [nrpnout] (original version by David McCallum) and [nrpnout-
yamaha]
where CC numbers are modified according to Yamaha specs. You may need to match two of the four CC numbers with your gear (the other two are
always
the same), and check if your gear needs MSB and LSB address or just one "NRPN number".
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Oops, I just loaded the patch on a Windows XP machine. Looks like [midiout] is not working here. I guess the way to go would be NRPN on Windows. Unless there is another object that could handle SysEx that I am not aware of.
Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag von Ingo Gesendet: Dienstag, 8. März 2011 18:35 An: 'David'; pd-list@iem.at Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Hi David,
here's a full EWI-USB editor. However, it only works one way! Pd -> EWI-USB. It cannot retrieve data from the EWI.
If you want to save your data you should specify a path (marked with red "bangs") twice for loading and saving and you need to set the midi port. Nothing else to do.
I have tested it with Linux (Ubuntu). Not sure if it works on any other OS.
Hope it's useful for some people!
Cheers Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag
von
David Gesendet: Dienstag, 8. März 2011 03:07 An: pd-list@iem.at; muranyia@gmail.com Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand how to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files") To: PD List pd-list@iem.at Message-ID: AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really
need
sysex. Attached [nrpnout] (original version by David McCallum) and [nrpnout-
yamaha]
where CC numbers are modified according to Yamaha specs. You may need
to
match two of the four CC numbers with your gear (the other two are
always
the same), and check if your gear needs MSB and LSB address or just
one
"NRPN number".
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi!
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?
I got this information from a web site created by someone who reverse-engineered the SysEx messages for the EWI USB:
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.
David.
On Tue, Mar 8, 2011 at 12:48 PM, Ingo ingo@miamiwave.com wrote:
Oops, I just loaded the patch on a Windows XP machine. Looks like [midiout] is not working here. I guess the way to go would be NRPN on Windows. Unless there is another object that could handle SysEx that I am not aware of.
Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag von Ingo Gesendet: Dienstag, 8. März 2011 18:35 An: 'David'; pd-list@iem.at Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Hi David,
here's a full EWI-USB editor. However, it only works one way! Pd -> EWI-USB. It cannot retrieve data from the EWI.
If you want to save your data you should specify a path (marked with red "bangs") twice for loading and saving and you need to set the midi port. Nothing else to do.
I have tested it with Linux (Ubuntu). Not sure if it works on any other OS.
Hope it's useful for some people!
Cheers Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag
von
David Gesendet: Dienstag, 8. März 2011 03:07 An: pd-list@iem.at; muranyia@gmail.com Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand how to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files") To: PD List pd-list@iem.at Message-ID: AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really
need
sysex. Attached [nrpnout] (original version by David McCallum) and [nrpnout-
yamaha]
where CC numbers are modified according to Yamaha specs. You may need
to
match two of the four CC numbers with your gear (the other two are
always
the same), and check if your gear needs MSB and LSB address or just
one
"NRPN number".
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
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 idea what the Aria software is sending out but it is definitely not necessary.
There are a lot of strange things with the Garritan / Plogue software.
I got this information from a web site created by someone who reverse-engineered the SysEx messages for the EWI USB:
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 that 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.
BTW, you cannot break anything by sending sysex messages to an instrument. 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 one?
However I did discover an error in the patch this morning when I transferred a modified version into my hardware machine. "Pitchbend down" doesn't get restored correctly from the file. So there is a fixed version attached. It also writes the 6th value of the shorter sysex strings into the file which was ignored before. Just in case it would have any undocumented (ha, ha, ha) meaning.
Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im Auftrag
von
Ingo Gesendet: Dienstag, 8. März 2011 18:35 An: 'David'; pd-list@iem.at Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Hi David,
here's a full EWI-USB editor. However, it only works one way! Pd -> EWI-USB. It cannot retrieve data from the EWI.
If you want to save your data you should specify a path (marked with
red
"bangs") twice for loading and saving and you need to set the midi
port.
Nothing else to do.
I have tested it with Linux (Ubuntu). Not sure if it works on any other OS.
Hope it's useful for some people!
Cheers Ingo
-----Ursprüngliche Nachricht----- Von: pd-list-bounces@iem.at [mailto:pd-list-bounces@iem.at] Im
Auftrag
von
David Gesendet: Dienstag, 8. März 2011 03:07 An: pd-list@iem.at; muranyia@gmail.com Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
Thanks. I'm not sure I understand what you mean when you say "you don't really need sysex", though. I have to send a 6 byte NRPN message, followed by a 14 byte SysEx message. I think I understand
how
to send the NRPN message, but I'm still confused about the SysEx message. Would I use [midiout] to do that? According to the help file in PD, this object is still undocumented and is only supported on Linux. Is that still true? And it only has two inlets, which I'm guessing would be an arbitrary 1 byte value and a channel number, but I'm not sure.
Unfortunately, none of these messages are documented in the owner's manual or on their web site, but someone has reverse-engineered the messages and posted his findings here:
http://www.ewiusb.com/sysex_page1 http://www.ewiusb.com/sysex_page2
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again, another 19 byte SysEx, and a final NRPN) would look like this, for example:
// sysex enable : 63 01 62 04 06 20 // sysex message : F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7 // sysex enable : 63 01 62 04 06 20 // sysex message : F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7 // sysex done : 63 01 62 04 06 10
David.
Message: 1 Date: Sun, 6 Mar 2011 18:07:59 +0100 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing
binary
files") To: PD List pd-list@iem.at Message-ID:
AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com
Content-Type: text/plain; charset="iso-8859-1"
NRPNS are interestingly made up of CC messages so you don't really
need
sysex. Attached [nrpnout] (original version by David McCallum) and
[nrpnout-
yamaha]
where CC numbers are modified according to Yamaha specs. You may
need
to
match two of the four CC numbers with your gear (the other two are
always
the same), and check if your gear needs MSB and LSB address or just
one
"NRPN number".
Andras
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
See below.
On Wed, Mar 9, 2011 at 1:36 PM, Ingo ingo@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 idea what the Aria software is sending out but it is definitely not necessary.
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 files.
I got this information from a web site created by someone who reverse-engineered the SysEx messages for the EWI USB:
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 that 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 instrument. 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 one?
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 transferred a modified version into my hardware machine. "Pitchbend down" doesn't get restored correctly from the file. So there is a fixed version attached. It also writes the 6th value of the shorter sysex strings into the file which was ignored before. Just in case it would have any undocumented (ha, ha, ha) meaning.
Thanks again.
Ingo
Hi David,
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.
Ingo
-----Ursprüngliche Nachricht----- Von: David [mailto:dfkettle@gmail.com] Gesendet: Mittwoch, 9. März 2011 20:00 An: Ingo Cc: pd-list@iem.at Betreff: Re: [PD] Patch for Akai EWI (was "Reading and writing binary files")
See below.
On Wed, Mar 9, 2011 at 1:36 PM, Ingo ingo@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
idea
what the Aria software is sending out but it is definitely not
necessary.
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 files.
I got this information from a web site created by someone who reverse-engineered the SysEx messages for the EWI USB:
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
that
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
instrument.
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
one?
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
transferred
a modified version into my hardware machine. "Pitchbend down" doesn't
get
restored correctly from the file. So there is a fixed version attached.
It
also writes the 6th value of the shorter sysex strings into the file
which
was ignored before. Just in case it would have any undocumented (ha, ha,
ha)
meaning.
Thanks again.
Ingo
-
András Murányi -
David -
Ingo