Bc2000 (for the BCF2000 & BCR2000)

Yes - I think that was something I had even asked for, wasn't it?
If it wasn't me I had thought about it.



Kip

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "k5kip_1999" <k5kip_1999@> wrote:
> k5kip_1999 wrote:
> > Mark correct me if I am wrong here.
> 
> Your wish is my command...
> 
> > if you want to make your own presets to distribute to others - 
> > there are a couple of things to consider.
> > 2. If they are on a mac, bcmanager won't work for those people so they
> > will probably be doing a sysex dump back to the bcr2000.
> > It that case you can use bcmanager's bcl editor to add the store
> > command at the 2nd to last command.
> > So add $store 02 (to store to preset #2, 
> > followed by $end.
> 
> Of course BC Manager's BCL editor does work in the way you describe.
> However, there is another, probably simpler way, which doesn't involve
> the BCL editor at all:
> 
> In the "Presets" window, select (highlight) the preset(s) you want to
> save, and choose "Export selected preset(s)" from the "File" pulldown
> menu. In the dialog box you can then select the output file type (syx,
> txt or bc2) via the "Save as type" box.
> 
> The saved file will contain all the presets' respective "$store"
> commands. However, if preset 0 (the temporary preset) is among the
> selected presets, preset 0 will be saved LAST, and will NOT be
> followed by a $store command. This protocol is similar to what happens
> when you send a bunch of presets to a BCF or BCR: the BCF and BCR use
> the temporary preset as a gateway to any memory presets. So formally
> ANY preset definition concerns the TEMPORARY preset, and is only
> COPIED to a memory preset the moment a $store command is encountered.
> 
> Mark.
>