[A6] Saving mix over sysex

[Geoff Moehrke]

>-----Original Message-----
>From: a6-bounces at code404.com [mailto:a6-bounces at code404.com] 
>On Behalf Of Robert van der Kamp
>Sent: Monday, October 27, 2003 10:43 AM
>To: a6 at code404.com
>Subject: Re: [A6] Saving mix over sysex
>
>Restoring the data back to the Andro, however, doesn't seem 
>to work. I didn't get my own mix + programs restored.
>
>When restoring my dumped mix while an empty mix is selected 
>on the Andro, I can see how the mix channels get enabled 
>when the mix dump is restored, but the name of the mix, and 
>the name of the 16 sounds are *not* changed.

Hmmm - did you send the Mix edit buffer first in the sequence?  If so, I
would think the name would be updated .  I'm not sure if the mix would
be in an 'edited' state at this point - that would depend on how the OS
handles it.  When the OS loads a mix from an internal source (i.e.
PRESET or User bank), the initial state is 'not edited' until something
in the edit buffer is modified.  The OS might treat a sysex dump the
same way, this does not explain why the name wasn't updated correctly
though...

>
>Also, after restoring, none of the edit buffers have the 
>'edited' state, indicating that they need to be saved.
>
>And worst of all, the audible result is not equal to the 
>original data. I also tried it on a preset mix, and when 
>restoring the data while an empty mix is selected 
>beforehand, the result is some weird low noise, suggesting 
>that *some* data has been received, but not all of it.
>
>Possible causes are:
>1. My MIDI system cannot send/restore sysex messages without 
>corrupting the data.
>2. The Andro needs some switches toggled to make this work.
>3. My MIDI router (AMT8) needs some switches toggled.
>4. The dump/restore scheme described above is not correct.
>5. An Andro OS bug.
>
>Causes 1, 2 and 3 can be eliminated because *some* sysex 
>data *does* seem to come through when restoring the dumps 
>(like the channel assignments in the mix). 
>
>Any suggestions?
>
My first thought is that maybe it is a timing issue.  Do you give the A6
any time to process the incoming sysex commands before sending the next
one?  Could be that the incoming sysex buffers are pre-empting work
needed to completely load the previous one. 

Again, just for the record, I have not tested this with the A6 - my MIDI
setup is not in a state where I can easily do this at the moment.  I can
say that based on my experience with the QS series Mix edit buffers,
this would seem to be the correct method. 

I would start with just the Mix edit buffer and explore why the Mix Name
does not seem to be set correctly.  Then maybe send the program edit
buffers one at a time and investigate what happens to the mix after each
one.

-Geoff