Sorry, it seems i didn't read your first mail carefully.<div>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.</div>
<div>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(</div>
<div><br></div><div>Andras<br><br><div class="gmail_quote">On Tue, Mar 8, 2011 at 03:07, David <span dir="ltr"><<a href="mailto:dfkettle@gmail.com">dfkettle@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks. I'm not sure I understand what you mean when you say "you<br>
don't really need sysex", though. I have to send a 6 byte NRPN<br>
message, followed by a 14 byte SysEx message. I think I understand how<br>
to send the NRPN message, but I'm still confused about the SysEx<br>
message. Would I use [midiout] to do that? According to the help file<br>
in PD, this object is still undocumented and is only supported on<br>
Linux. Is that still true? And it only has two inlets, which I'm<br>
guessing would be an arbitrary 1 byte value and a channel number, but<br>
I'm not sure.<br>
<br>
Unfortunately, none of these messages are documented in the owner's<br>
manual or on their web site, but someone has reverse-engineered the<br>
messages and posted his findings here:<br>
<br>
<a href="http://www.ewiusb.com/sysex_page1" target="_blank">http://www.ewiusb.com/sysex_page1</a><br>
<a href="http://www.ewiusb.com/sysex_page2" target="_blank">http://www.ewiusb.com/sysex_page2</a><br>
<br>
The whole stream (an NRPN, a 14 byte SysEx, the same NRPN again,<br>
another 19 byte SysEx, and a final NRPN) would look like this, for<br>
example:<br>
<br>
// sysex enable :<br>
63 01 62 04 06 20<br>
// sysex message :<br>
F0 47 7F 6D 00 00 06 40 40 40 40 08 7F F7<br>
// sysex enable :<br>
63 01 62 04 06 20<br>
// sysex message :<br>
F0 F7 7F 6D 02 00 0B 00 00 40 20 02 00 00 7F 00 7C 7D F7<br>
// sysex done :<br>
63 01 62 04 06 10<br>
<br>
David.<br>
<br>
> Message: 1<br>
> Date: Sun, 6 Mar 2011 18:07:59 +0100<br>
> From: Andr?s Mur?nyi <<a href="mailto:muranyia@gmail.com">muranyia@gmail.com</a>><br>
> Subject: Re: [PD] Patch for Akai EWI (was "Reading and writing binary<br>
> files")<br>
> To: PD List <<a href="mailto:pd-list@iem.at">pd-list@iem.at</a>><br>
> Message-ID:<br>
> <<a href="mailto:AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com">AANLkTimf2TztoeqGx38BLvs_Rphk5YQLi6NnFnB2Uu0j@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
<div><div></div><div class="h5">><br>
> NRPNS are interestingly made up of CC messages so you don't really need<br>
> sysex.<br>
> Attached [nrpnout] (original version by David McCallum) and [nrpnout-yamaha]<br>
> where CC numbers are modified according to Yamaha specs. You may need to<br>
> match two of the four CC numbers with your gear (the other two are always<br>
> the same), and check if your gear needs MSB and LSB address or just one<br>
> "NRPN number".<br>
><br>
> Andras<br>
</div></div></blockquote></div><br><br>
</div>