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

Thanks for your help Aaron!

Unfortunately for me using a footswitch to change songs is a pain for 
me.  I don't want to change the order of my songs every night when 
I'm on tour.  Also, initializing everything inside the sequence 
doesn't work for me either, because some of the huge sample libraries 
in Kontakt on my Muse Receptor take 10-15 seconds to load.

IN ANY CASE a couple questions:

#1. I'll try the Program Change with bank select msb and lsb, but 
what MIDI channel am I sending this on?

#2. In the MIDI implementation guide there is code to COPY a song.  I 
was thinking that if I could get this working, I could just have a 
song location that all the new songs I want to load get copied to.

Here's what's in the manual

Copy Song EXAMPLE:> {F0h, 18h, 0Fh, dd, 55h, 2Eh, xx, xx, yy, yy, zz, 
zz, F7h}
F0h = sysex message
18h = EMU ID
0Fh = Proteus ID
dd = Device ID
55h = Special Editor designator byte
2Eh = Command::Copy Pattern
xx, xx = Source Song number (ROM or RAM) LSB first
yy, yy = Destination Song number (RAM only) LSB
first Song Number of -1 bis the Edit Buffer.
zz, zz = Source ROM ID
F7h = EOX


The only thing I'm not sure of is my SOURCE ROM ID.  Can someone help 
me out with this?  Actually if someone could spell this out for me.  
While I know what sysEx DOES, I'm kinda new to coding in it.  Can 
someone spell out the exact code I would use to copy song 1 to song 0 
in SONG mode.  My Device ID is set to 0 on the XL-7.


Thanks!!
Jamie


--- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@...> wrote:
>
> I thought I implemented song select.  Really, it doesn't work?  
Also,
> you *can* load multisetups via program change - it's MSB 80, LSB 
00, PC
> xxx where xxx is the multisetup number.  At least that's the combo I
> remember off hand.  I thought there was also another bank select for
> sequences too, perhaps MSB 81?  I'm out of town at the moment, but 
I'll
> try and look up the code when I get home on Tuesday.
> 
> -Aaron
> 
> --- steve_the_composer <smw-mail@...> wrote:
> 
> > Insults are like spam--you just gotta ignore them. (Besides, the 
> > optimist in me says it may not have been intended as an insult; 
it 
> > may just have been a poor choice of words.) 
> > 
> > There is a very simple solution I thought I referenced in my 
first 
> > reply: use momentary contact footswitches.  For example, have one 
> > set to Sequence+ and the other set to Play. If the tunes in your 
set 
> > are sequenced consecutively (eg, 001^1, 002^1, 003^1 . . . 088^1) 
> > one footswitch will start the tune. When its over, press the 
other 
> > switch to advanced to tune # 2. etc. If you prefer, you could 
have 
> > one footswitch set to Play/Stop which alternates between the two.
> > 
> > Lotsa parameters, including channel assignments, preset 
assignments 
> > for 32 channels, etc. are stored in sequences. When you switch to 
a 
> > particular song, those settings are "booted up" if you will 
before 
> > the song starts. So, for example, all preset channel assignments 
> > should be ready to go when you press Play. 
> > 
> > Keep in mind that in song edit mode, you have a sub menu system 
for 
> > EVENT SOURCE (tempo, preset, volume, pan, mix, arp, fx). Each of 
> > these has 4 possible choices: song events only, 1st pattern only, 
> > all patterns, and song & patterns). So, if your song consists of 
> > chained patterns which each have different test fx settings (for 
> > example), you can use 1st pattern only or song events only to 
> > override the pattern settings.   
> > 
> > Unfortunately, while Song Position Pointer is implmented in the E-
Mu 
> > sequencer, Song Select is not. If it were, that would be the 
easiest 
> > solution to switch songs. 
> > 
> > (If Song Select were implemented, you could switch songs and 
thereby 
> > switch presets with one button. One work around, is to use one 
foot 
> > switch to step through songs sequentially and another to play the 
> > song (a two-button solution). There are other work arounds--
> > including the use of sysex.)
> > 
> > As for me, I had fun browsing the FC-300 manual. 
> > 
> > Whether or not the XL-7 will work for you, you asked a valid 
> > question. Let the motto be: IGNORE SPAM; IGNORE PERCEIVED INSULTS.
> > 
> > To quote King Gustavus Adolphus III: "Excelsior!!!!! 
> > 
> > 
> > --- In xl7@yahoogroups.com, "Jamie Orlando" <jamie@> wrote:
> > >
> > > You didn't have to insult me in responding to this the way you
> > > did.  I've used MIDI gear for years.  My whole set up is MIDI-
> > > ized.  I have 6 pieces of gear that get their presets changed
> > > with one button from my foot controller.  I was assuming when I
> > > bought the XL-7 that I'd be able to send a program change 
command
> > > to load a song.  But this isn't the case.  Usually a work-around
> > > can be accomplished with some sysEx.
> > > 
> > > Seems simple enough.  Can someone else help me out???
> > > 
> > > The Proteus Midi chart sucks, and I'm having a hard time reading
> > > it.  If this can't be done, I'm selling my XL-7.
> > > 
> > > Thanks,
> > > Jamie
> > > 
> > > --- In xl7@yahoogroups.com, "scodoha04" <scott.d.harvey@> wrote:
> > > >
> > > > Too bad you don't have the slightest clue as to what sysex is
> > > > or does huh? There can't be a one button solution when 
multiple
> > > > equipments exist.
> > 
> > > >   The stuff regarding how you write the code starts on page 
36.
> > > > However sending known, well documented sysex data to the xl-7 
is
> > > > problematic....(documentation being a real stumbling block) 
> > 
> > > >   The midi implementation on the fc-300 only pertains to 
Roland
> > > > equipment and more specifically to the fc-300; useful if you
> > > > want to talk to the fc-300 by way of some other device using
> > > > sysex.
> > 
> > 
> > 
> > 
> >  
> > Yahoo! Groups Links
> > 
> > 
> > 
> > 
> 
> 
> 
>       
______________________________________________________________________
______________
> Tonight's top picks. What will you watch tonight? Preview the 
hottest shows on Yahoo! TV.
> http://tv.yahoo.com/
>