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

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:
>
> 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> > >> >>
>