Emu XL-7 & MP-7 User's Group

>So, don't know why the id would screw things up, but now I know to 
>run eLoader with 
>sysex id=0 from now on.

Is that the ID of the command station unit itself? If so that would 
make sense. Say if you had 2 command stations connected you could 
dump/receive sysex dumps from just one. (both set with differant ID 
numbers..)
If they were both set to the same ID number they would both try to 
respond at the same time..  
Does that make sense?
Regards
Gonz

still waiting on the post for my XL-7.... :o(




--- In xl7@yahoogroups.com, "Greg" <golerage@y...> wrote:
> Hello Steve,
> thanks for the reply. That was all the sysex I got. And with your 
> interpeting of it gave the clue to change the device id back to 0 
and 
> try it again. And low and behold. It works again. So, don't know 
why 
> the id would screw things up, but now I know to run eLoader with 
> sysex id=0 from now on.
> 
> Thanks,
> _greg
> 
> 
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@p...> 
> wrote:
> > Not sure what the probem is.  Let me try figuring out sysex.  
> Hmmmm.  
> > Is this all you got or did you just list some one what you got?
> > 
> > =========================================================
> > Does anyone have a suggestion on how I can fix this?
> > 
> > Here is the reading I get from the Midi Monitor
> > sysex end count: 28 data: f0 18 0f 01 55 0b ...
> > 
> > >> looks like the name of one song is being sent from an E-Mu 
unit 
> > who's device ID is set to 01. 
> > 
> > sysex end count: 137 data: f0 7e 00 07 02 07 ...
> > 
> > >> looks like it could be song data packet number 7 with a device 
> ID 
> > of 00.
> > 
> > 
> > sysex end count: 6 data: f0 7e 00 7d 07 f7
> > 
> > >> looks like a cancel command [ie, stop the sysex transfer]
> > 
> > sysex end count: 6 data: f0 7e 00 7d 00 f7
> > 
> > >> looks like another cancel command
> > 
> > OOps thunder--gotta shut down