[A6] midiox question

[Geoff Moehrke]

What you need to do is make sure you are sending the edit buffer to/from
midiOx rather than the program (as it resides in the bank).  The A6
sysex command for sending/receiving programs is different that that for
sending/receiving the edit buffer.  When you send it back to the edit
buffer (the sysex should start as follows (hex):  F0 00 00 0E 1D 02
10...) it will not save the received data to a location, only to the
edit buffer where you can then save manually back to a bank location.

-Geoff Moehrke

>-----Original Message-----
>From: a6-bounces at code404.com [mailto:a6-bounces at code404.com] 
>On Behalf Of Tom Moravansky
>Sent: Friday, July 11, 2003 6:12 AM
>To: a6 mailing list
>Subject: Re: [A6] midiox question
>
>
>On Fri, 11 Jul 2003, Richard wrote:
>
>> midiOx seems to work well with win2000 but am I right in thinking it 
>> is only good for banks rather than patches?.
>> 
>> I load an individual patch from the PC with midoix it always goes to 
>> the destination it originally came from eg user 80, overwriting 
>> whatever patch I had there
>> 
>> I'm assuming there is no way to control this bad habit?
>> 
>
>Ummm, my A6 is down for repair at the moment, and I may be getting it
>confused with the Ion, but....   at least on one of these synths you
>have the ability to specify the destination patch number 
>during the save process.
>
>If not, you can always edit the sysex and put in the number you want.
>
>How can you find the info?  Do this -- save the exact same 
>patch to two different locations.  Do a sysex dump of each 
>one.  Compare the data and you should be able to see exactly 
>which bytes are used for the patch number.
>
>I know -- it's a low-level hack to the problem, but on the 
>other hand, you (or someone) can write a simple Perl front end 
>to prompt for the location number and update the sysex file.
>
>
>_______________________________________________
>A6 mailing list
>A6 at code404.com
>http://code404.com/mailman/listinfo/a6
>
>