Bc2000 (for the BCF2000 & BCR2000)

Just an addendum to my findings about ".tx" and ".request":

The ".snapshot" parameter (under "$preset") works in a similar way to
".request":

".snapshot on" causes the BCF/BCR to send all the preset's initial
control values at the moment you select the preset. (To be precise:
this is done AFTER the ".tx" message is sent, if ".tx" is defined and
".request" is "on".)

Mark.

Does anyone know a .tx sequence that will store a preset at the 
location currently indicated on the BCR/BCF?

The *Store command* works only by specifying a specific location in the 
script. I'd like the *user* to be able to select (on hardware) the 
preset 
location and for the new preset to be auto-stored to that location.

This is only a problem because I've reprogrammed the 4 function keys so 
that "Store" is no longer available.

Right now I'm using Store in the script specifying 01 as location, and 
telling users how to edit the sysex to enter a different storage 
location. I'd sure like to make this unnecessary.

Any ideas?

I think this would give the same result as simply using $store 1 (no 
request preset required).

What I need is for the *user* to select on the BCF/R the location 
where he/she wants the new preset stored, for the script to pick up 
that number so that the preset can be stored in that location.

--- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@...> wrote:
>
> F0 00 20 32 00 7F 22 00 F7  to request a preset (preset 1 in this 
case)
> Now you know the current preset use .store 0 (or it might be .store 
1 ?
> )
> 
> Does this help?
> 
> --- In bc2000@yahoogroups.com, "abhunkin" <abhunkin@> wrote:
> >
> > Does anyone know a .tx sequence that will store a preset at the
> > location currently indicated on the BCR/BCF?
> >
> > The *Store command* works only by specifying a specific location 
in
> the
> > script. I'd like the *user* to be able to select (on hardware) the
> > preset
> > location and for the new preset to be auto-stored to that 
location.
> >
> > This is only a problem because I've reprogrammed the 4 function 
keys
> so
> > that "Store" is no longer available.
> >
> > Right now I'm using Store in the script specifying 01 as 
location, and

> > telling users how to edit the sysex to enter a different storage
> > location. I'd sure like to make this unnecessary.
> >
> > Any ideas?
> >
>