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

Hello,

I want to store sysex messages in my patterns, preferably whole
multi instrument dumps.
What is the theoretical maximum data size allocated for a pattern ?
And in fact how much extra data fits there under average conditions ?
Is anybody successfully storing Yamaha FS1R performance banks
in an Emu command station box ?

Thanks,

    Zsolt

I don't know for sure, but I can tell you what I know.  I would assume 
in theory, you could use 100% of available sequence memory. However, I 
though think that would be very practical. 

I have dabbled with embedded sysex commands. (See files section.) I am 
reasonably sure you can embed plenty of sysex for your purposes using 
a small portion of the sequencer memory.

Years ago, I embeded a large patch dump (Casio CZ banks, I believe) 
into a pattern that ran longer than 32 measures. It can be done, but I 
don't recall if it intruduced any OS anomolies.

If you are simply trying to get sequencers to call up all the data you 
would have in a multisetup, that is much easier to do, though you have 
to be careful.  For example, if you change some of the settings, you 
could in effect turn off the ability to receive further messages; or 
you could turn off the internal clock with nothing to turn it back on.

If you don't need to recall ALL the data from a multisetup, OR, if you 
want to change things other than what a multisetup saves, I recommend 
you look at my material on embedded sysex (if you haven't done so 
already).

I am not familiar with the Yamaha FS1R, but if you can manipulate 
parameters on the fly like you can with the P2K synth engine, you 
might consider that.

Out of curiosity, you you have a sysex manual for the FS1R? (If it is 
available in PDF, I'd be interested in taking a look.) Also, how big 
(in bytes) are the performance banks? If a bank is not too big, you 
might be able to send it out all at once.  If you are wanting to send 
a large amount of data, you could send it out over time.

Here's a link to the section on embedded sysex. I don't have anything 
specific on embedding patch/preset dumps for external gear, though I 
know I have written about it in the archives. I will see if I can find 
the reference(s).

http://groups.yahoo.com/group/xl7/files/Embedded%20Sysex%20Demos/

Hope this helps.

--Steve


--- In xl7@yahoogroups.com, Zsolt Szabó <Zsolt.Szabo@...> wrote:

>
> Hello,
> 
> I want to store sysex messages in my patterns, preferably whole
> multi instrument dumps.
> What is the theoretical maximum data size allocated for a pattern ?
> And in fact how much extra data fits there under average conditions ?
> Is anybody successfully storing Yamaha FS1R performance banks
> in an Emu command station box ?
> 
> Thanks,
> 
>     Zsolt
>

Hi Steve,

yes, I want complete dumps to store in the patterns.
I asked the FS1R because the biggest sysex chunks originate from there,
very-very much parameters...

Preferably I would send single banks data but multi is also
a must so larger chuncks are expected...

I put up the FS1R documents on my ftp area.
The file you want to consult is fs1re2.pdf an look at MIDI implementation
at the end.
Now I'm in the process to completely remote the FS1R from my BitStream
MIDI controller so I use them frequently.

ftp://pub:pub001@...


Thanks,
    Zsolt





----- Original Message ----- 
From: "steve_the_composer" <smw-mail@...>
To: <xl7@yahoogroups.com>
Sent: Saturday, August 26, 2006 5:06 PM
Subject: [xl7] Re: XL7 and in-pattern sysex storage


I don't know for sure, but I can tell you what I know.  I would assume
in theory, you could use 100% of available sequence memory. However, I
though think that would be very practical.

I have dabbled with embedded sysex commands. (See files section.) I am
reasonably sure you can embed plenty of sysex for your purposes using
a small portion of the sequencer memory.

Years ago, I embeded a large patch dump (Casio CZ banks, I believe)
into a pattern that ran longer than 32 measures. It can be done, but I
don't recall if it intruduced any OS anomolies.

If you are simply trying to get sequencers to call up all the data you
would have in a multisetup, that is much easier to do, though you have
to be careful.  For example, if you change some of the settings, you
could in effect turn off the ability to receive further messages; or
you could turn off the internal clock with nothing to turn it back on.

If you don't need to recall ALL the data from a multisetup, OR, if you
want to change things other than what a multisetup saves, I recommend
you look at my material on embedded sysex (if you haven't done so
already).

I am not familiar with the Yamaha FS1R, but if you can manipulate
parameters on the fly like you can with the P2K synth engine, you
might consider that.

Out of curiosity, you you have a sysex manual for the FS1R? (If it is
available in PDF, I'd be interested in taking a look.) Also, how big
(in bytes) are the performance banks? If a bank is not too big, you
might be able to send it out all at once.  If you are wanting to send
a large amount of data, you could send it out over time.

Here's a link to the section on embedded sysex. I don't have anything
specific on embedding patch/preset dumps for external gear, though I
know I have written about it in the archives. I will see if I can find
the reference(s).

http://groups.yahoo.com/group/xl7/files/Embedded%20Sysex%20Demos/

Hope this helps.

--Steve


--- In xl7@yahoogroups.com, Zsolt Szab\ufffd <Zsolt.Szabo@...> wrote:

>
> Hello,
>
> I want to store sysex messages in my patterns, preferably whole
> multi instrument dumps.
> What is the theoretical maximum data size allocated for a pattern ?
> And in fact how much extra data fits there under average conditions ?
> Is anybody successfully storing Yamaha FS1R performance banks
> in an Emu command station box ?
>
> Thanks,
>
>     Zsolt
>

Looks like an interesting module. I took a quick look at the sysex 
docs. It looks like you should be able to send both small and large 
dumps from the E-Mu.

My experience is that small sysex commands can be sent on the fly. 
The only time I sent large amounts of data, I sequenced the data 
over time. (I used Cakewalk to sequence the banks of sysex data into 
a *.mid file and e-loader to put it in my E-Mu.)

Single banks (400 bytes for performance dump; 608 bytes for voice 
dump; etc. [not including sysex header/eox]) should be no problem 
for the E-Mu to send.

Best wishes with the project. 

--Steve


--- In xl7@yahoogroups.com, Zsolt Szabó <Zsolt.Szabo@...> wrote:
>
> Hi Steve,
> 
> yes, I want complete dumps to store in the patterns.
> I asked the FS1R because the biggest sysex chunks originate from 
there,
> very-very much parameters...
> 
> Preferably I would send single banks data but multi is also
> a must so larger chuncks are expected...
> 
> I put up the FS1R documents on my ftp area.
> The file you want to consult is fs1re2.pdf an look at MIDI 
implementation
> at the end.
> Now I'm in the process to completely remote the FS1R from my 
BitStream

> MIDI controller so I use them frequently.
> 
> ftp://pub:pub001@...
> 
> 
> Thanks,
>     Zsolt

sweet. never even thought of that.



--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> 
wrote:
>
> Looks like an interesting module. I took a quick look at the sysex 
> docs. It looks like you should be able to send both small and 
large 
> dumps from the E-Mu.
> 
> My experience is that small sysex commands can be sent on the fly. 
> The only time I sent large amounts of data, I sequenced the data 
> over time. (I used Cakewalk to sequence the banks of sysex data 
into 

> a *.mid file and e-loader to put it in my E-Mu.)
> 
> Single banks (400 bytes for performance dump; 608 bytes for voice 
> dump; etc. [not including sysex header/eox]) should be no problem 
> for the E-Mu to send.
> 
> Best wishes with the project. 
> 
> --Steve
> 
> 
> --- In xl7@yahoogroups.com, Zsolt Szabó <Zsolt.Szabo@> wrote:
> >
> > Hi Steve,
> > 
> > yes, I want complete dumps to store in the patterns.
> > I asked the FS1R because the biggest sysex chunks originate from 
> there,
> > very-very much parameters...
> > 
> > Preferably I would send single banks data but multi is also
> > a must so larger chuncks are expected...
> > 
> > I put up the FS1R documents on my ftp area.
> > The file you want to consult is fs1re2.pdf an look at MIDI 
> implementation
> > at the end.
> > Now I'm in the process to completely remote the FS1R from my 
> BitStream
> > MIDI controller so I use them frequently.
> > 
> > ftp://pub:pub001@
> > 
> > 
> > Thanks,
> >     Zsolt
>