Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "k5kip_1999" <k5kip_1999@...> wrote:
> I loaded selected presets into the bcl.  When I select 11-16 presets,
> they all load but so does the 0 preset which is tacked on the end. Was
> that your intention?

Yes:

When sending presets to the BCF/BCR, BC Manager first sends (to use
your example) memory presets 11-16, then preset 0 (the temporary
preset). This is necessary for restoring preset 0 to the current
values maintained by BC Manager, because preset 0 on the BCF/BCR is
used as a gateway for presets 11-16.

So when I developed the BCL editor window, it seemed logical to copy
this behavior - which is why preset 0 is appended. The idea is that
the user can edit the BCL text, then send it directly to the BCF/BCR
with the same "automatic" restoration facility of preset 0.

But I admit that in other situations (such as yours) it might be
easier to leave out preset 0 at the end. I can build in an
on/off-switch in the BCL editor window's menu, or simply add another
menu-item that leaves out preset 0.

I assumed that you simply wanted to export a SINGLE preset at a time,
so then you can simply use preset 0 itself for this - then you
obviously don't get an extra, appended preset.

HOWEVER (in fact, this makes all my above blabbing a bit pointless):
you can also export presets directly from the preset list window - in
that case you DON'T get the extra preset 0 !

A related, conceptual issue:
If you export presets 11 to 16 to a single syx file, the output file
by definition contains $store (11/12/etc.) statements: doesn't this
conflict with your philosophy of preset files that are totally
flexible (e.g. for Mac users etc.)? I mean: it would be "dangerous"
for a user to upload a file containing fixed memory presets directly
to the BCF/BCR, since it would overwrite BC's memory presets. To
guarantee this particular type of "total flexibility", only a file
containing a single temporary preset would be possible.
On the other hand, files containing memory presets are no problem for
users of e.g. BC Manager; in fact, it would be simpler than having
multiple files: the user simply creates an additional B-Control
context, opens the file containing the memory presets into that
context, and then copies and pastes the presets to the desired
locations in the B-Control context linked to the actual BCF/BCR.

Before I forget: thanks very much for your videos! (To anybody else
reading this: NO, this is not what you're thinking...) I'll look at
them as soon as I can; in particular: as soon as I have installed
shockwave flash: last week I had a harddisk crash - it's already taken
me about two days to install a new OS plus my main applications...

Mark.