Yahoo Groups archive

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

Index last updated: 2026-03-31 23:44 UTC

Thread

Next hit on the sysex question parade - how to write a patch?

Next hit on the sysex question parade - how to write a patch?

2011-05-12 by S. Lepore

Steve's pointers on how to send sysex to the different multi-mode presets worked beautifully. However, selecting a new multi-mode preset clears the edit buffer and erases any changes I have made. I'm thinking I can get around this by writing the current preset before selecting the new one.

Can this be done via sysex? (I know. I know. I've been looking through the manuals and can't find it.) I don't think I want to go into remote mode as my tests with show it's super bandwidth intensive.

Thanks.

Scott

Re: Next hit on the sysex question parade - how to write a patch?

2011-05-14 by stimresp

Page 37 of the sysex spec / remote control button event...
mimics front/panel button presses



--- In xl7@yahoogroups.com, "S. Lepore" <sleporester@...> wrote:
Show quoted textHide quoted text
>
> Steve's pointers on how to send sysex to the different multi-mode presets worked beautifully. However, selecting a new multi-mode preset clears the edit buffer and erases any changes I have made. I'm thinking I can get around this by writing the current preset before selecting the new one.
> 
> Can this be done via sysex? (I know. I know. I've been looking through the manuals and can't find it.) I don't think I want to go into remote mode as my tests with show it's super bandwidth intensive.
> 
> Thanks.
> 
> Scott
>

Re: Next hit on the sysex question parade - how to write a patch?

2011-05-14 by steve_the_composer

Thanks for adding that info. 

Could you use dedicated user slots, say for example 000^0 -> 032^0 and just do your edits there instead of the edit buffer? I haven't tested this, but I was under the impression that when you write parameters directly to RAM, you are changing the User presets themselves. Hence, no need to save. Again, I haven't tested this yet. (See possible caveat at the bottom.)

If that works, you would probably want to use the copy utilities to assign those 32 real-time presets. In fact, maybe you could have something like a macro [a set of presets] that copies 32 presets at a time into the real-time preset array.

Perhaps you can assign them with one command:
F0 18 0F dd 55 20 xx1 xx1 yy1 yy1 zz1 zz1 xx2 xx2 yy2 yy2 zz2 zz2. . . xx32 xx32 yy32 yy32 zz32 zz32 F7
where xx xx = source preset, yy yy = destination [user slots], and zz zz = Source ROM ID

If this method works, then you could have up to 32 presets being manipulated in real-time with your software. I suppose (again, assuming this works) you could take snapshots of the last state of the 32 presets--say for example, store them in user bank 1 [000^1 -> 031^1, 032^1 -> 063^1, etc.]. (Or you could have banks of 16 or 8.)

There is a possible caveat based on what someone in one of the forums reported back from Jan, designer of Prodatum. It might be that with each direct edit, you are shortening the life of your E-Mu. As I understand it, flash RAM writes are finite. So if you use the edit buffer, I believe you are using RAM, but if you edit directly you are writing to flash RAM.

Perhaps someone else with more knowledge of these kinds of issues can comment on this.

Steve 




--- In xl7@yahoogroups.com, "S. Lepore" <sleporester@...> wrote:
Show quoted textHide quoted text
>
> Steve's pointers on how to send sysex to the different multi-mode presets worked beautifully. However, selecting a new multi-mode preset clears the edit buffer and erases any changes I have made. I'm thinking I can get around this by writing the current preset before selecting the new one.
> 
> Can this be done via sysex? (I know. I know. I've been looking through the manuals and can't find it.) I don't think I want to go into remote mode as my tests with show it's super bandwidth intensive.
> 
> Thanks.
> 
> Scott
>

Re: Next hit on the sysex question parade - how to write a patch?

2011-05-14 by steve_the_composer

This might be better that writing directly to user slots for real-time performance--just use remote control to save the presets. If there is an issue with using up flash RAM writes, this would cut it down.

See question below.

Sample RC Sequence:
->Start
(0) Open RC Session
->Initialize Save mode
(1) Assume save button is not pressed.
(2) Press Save button.
(3) Rotate Main Encoder 16 clicks left [to SAVE PATTERN menu].
(4) Rotate Main Encoder 4 clicks right [to SAVE PRESET menu].
(5) Cursor down to bottom line.
(6) Rotate Main Encoder 128*4 clicks left [to 000^0]
->Select detination user slot
(7) Rotate Main Encoder n clicks right [to get to destination]
(8) Press Enter/Home button.
->End
(9) Close RC Session

One question:
Will this actually save the preset that's in the edit buffer?

I ask because p.53 of the sysex manual (under PRESET_SELECT) seems to indicate that there are two editing systems--remote [ie., via sysex] and front panel. 

Again, I may have tested this years ago, but I don't remember.

Steve 


--- In xl7@yahoogroups.com, "stimresp" <stimresp@...> wrote:
Show quoted textHide quoted text
>
> 
> Page 37 of the sysex spec / remote control button event...
> mimics front/panel button presses
> 
> 
> 
> --- In xl7@yahoogroups.com, "S. Lepore" <sleporester@> wrote:
> >
> > Steve's pointers on how to send sysex to the different multi-mode presets worked beautifully. However, selecting a new multi-mode preset clears the edit buffer and erases any changes I have made. I'm thinking I can get around this by writing the current preset before selecting the new one.
> > 
> > Can this be done via sysex? (I know. I know. I've been looking through the manuals and can't find it.) I don't think I want to go into remote mode as my tests with show it's super bandwidth intensive.
> > 
> > Thanks.
> > 
> > Scott
> >
>

Re: Next hit on the sysex question parade - how to write a patch?

2011-05-14 by S. Lepore

Thanks again for the responses Steve. Apologies for the second posting on the subject - it was a glitch on my end.

As you suggested I've been playing with the remote function to automagically save the edit buffer just before changing the multimode basic channel and editing the next sound. Apart from some issues determining the machine state when I start a remote session, this method works reasonably well. BTW your excellent sysex posting in the files section was invaluable in this. Did you identify all of the undocumented remote controls through trial and error? I am impressed. You really must love your MP.

Interesting you should mention the issue of flash RAM lifespan. My creative partner mentioned the same thing last night. Have you any idea of what this lifespan is (I guess measured in writes)?

Your posts seem to suggest that there are two types of volatile storage. Are they flash and battery backed up? Is the edit buffer written to flash while user presets are written to battery backed up RAM?

I also read about addressing and editing presets directly in RAM. I gather that doing this "pokes" values and immediately saves changes?

I've uploaded a couple of screen shots of my TouchOSC interface to the photos section for those who are curious.

Scott


--- In xl7@yahoogroups.com, "steve_the_composer" wrote:
>
> This might be better that writing directly to user slots for real-time performance--just use remote control to save the presets. If there is an issue with using up flash RAM writes, this would cut it down.
>
> See question below.
>
> Sample RC Sequence:
>; ->Start
> (0) Open RC Session
> ->Initialize Save mode
> (1) Assume save button is not pressed.
> (2) Press Save button.
> (3) Rotate Main Encoder 16 clicks left [to SAVE PATTERN menu].
> (4) Rotate Main Encoder 4 clicks right [to SAVE PRESET menu].
>; (5) Cursor down to bottom line.
> (6) Rotate Main Encoder 128*4 clicks left [to 000^0]
> ->Select detination user slot
> (7) Rotate Main Encoder n clicks right [to get to destination]
> (8) Press Enter/Home button.
> ->End
> (9) Close RC Session
> ;
> One question:
> Will this actually save the preset that's in the edit buffer?
>
> I ask because p.53 of the sysex manual (under PRESET_SELECT) seems to indicate that there are two editing systems--remote [ie., via sysex] and front panel.
>
> Again, I may have tested this years ago, but I don't remember.
>
> Steve
>
>
> --- In xl7@yahoogroups.com, "stimresp" wrote:
> >
> >
> > Page 37 of the sysex spec / remote control button event...
> > mimics front/panel button presses
> >
> >
> >
> > --- In xl7@yahoogroups.com, "S. Lepore" wrote:
> > >
> > > Steve's pointers on how to send sysex to the different multi-mode presets worked beautifully. However, selecting a new multi-mode preset clears the edit buffer and erases any changes I have made. I'm thinking I can get around this by writing the current preset before selecting the new one.
> > >
> > >; Can this be done via sysex? (I know. I know. I've been looking through the manuals and can't find it.) I don't think I want to go into remote mode as my tests with show it's super bandwidth intensive.
> > >
> > > Thanks.
> > >
> > > Scott
> > >
> >
>

Re: Next hit on the sysex question parade - how to write a patch?

2011-05-14 by steve_the_composer

Yes; I mined additional remote control commands by hand--sending numbers, seeing what they did, looking for replies from my P2500, etc. I also spent some time writing RC command strings in addition to the demos I posted. One project involved automating the creating of a bank of 128 randomized presets by simulating the button presses. Glad the RC sysex files were helpful.

I have no idea about the maximum flash RAM writes.

The TouchOSC thing looks cool.

Steve 



--- In xl7@yahoogroups.com, "S. Lepore" <sleporester@...> wrote:
Show quoted textHide quoted text
>
> Thanks again for the responses Steve. Apologies for the second posting
> on the subject - it was a glitch on my end.
> As you suggested I've been playing with the remote function to
> automagically save the edit buffer just before changing the multimode
> basic channel and editing the next sound. Apart from some issues
> determining the machine state when I start a remote session, this method
> works reasonably well. BTW your excellent sysex posting in the files
> section was invaluable in this. Did you identify all of the undocumented
> remote controls through trial and error? I am impressed. You really must
> love your MP.
> Interesting you should mention the issue of flash RAM lifespan. My
> creative partner mentioned the same thing last night. Have you any idea
> of what this lifespan is (I guess measured in writes)?
> Your posts seem to suggest that there are two types of volatile storage.
> Are they flash and battery backed up? Is the edit buffer written to
> flash while user presets are written to battery backed up RAM?
> I also read about addressing and editing presets directly in RAM. I
> gather that doing this "pokes" values and immediately saves changes?
> I've uploaded a couple of screen shots of my TouchOSC interface to the
> photos section for those who are curious.
> Scott
> 
> --- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@> wrote:>>
> This might be better that writing directly to user slots for real-time
> performance--just use remote control to save the presets. If there is an
> issue with using up flash RAM writes, this would cut it down.> > See
> question below.> > Sample RC Sequence:> ->Start> (0) Open RC Session>
> ->Initialize Save mode> (1) Assume save button is not pressed.> (2)
> Press Save button.> (3) Rotate Main Encoder 16 clicks left [to SAVE
> PATTERN menu].> (4) Rotate Main Encoder 4 clicks right [to SAVE PRESET
> menu].> (5) Cursor down to bottom line.> (6) Rotate Main Encoder 128*4
> clicks left [to 000^0]> ->Select detination user slot> (7) Rotate Main
> Encoder n clicks right [to get to destination]> (8) Press Enter/Home
> button.> ->End> (9) Close RC Session> > One question:> Will this
> actually save the preset that's in the edit buffer?> > I ask because
> p.53 of the sysex manual (under PRESET_SELECT) seems to indicate that
> there are two editing systems--remote [ie., via sysex] and front panel.
> > > Again, I may have tested this years ago, but I don't remember.> >
> Steve > > > --- In xl7@yahoogroups.com, "stimresp" <stimresp@> wrote:>
> >> > > > Page 37 of the sysex spec / remote control button event...> >
> mimics front/panel button presses> > > > > > > > --- In
> xl7@yahoogroups.com, "S. Lepore" <sleporester@> wrote:> > >> > > Steve's
> pointers on how to send sysex to the different multi-mode presets worked
> beautifully. However, selecting a new multi-mode preset clears the edit
> buffer and erases any changes I have made. I'm thinking I can get around
> this by writing the current preset before selecting the new one.> > > >
> > > Can this be done via sysex? (I know. I know. I've been looking
> through the manuals and can't find it.) I don't think I want to go into
> remote mode as my tests with show it's super bandwidth intensive.> > > >
> > > Thanks.> > > > > > Scott> > >> >>
>