Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- 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:

Ok - I was just wondering.

> 
> 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 don't think that is necessary.

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


Yes - that makes sense.

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


Yes - and that is what I did!  Great!


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

Yeah - I thought about this. Yes I do want flexibility, however, I
also want simplicity more. My philosophy on flexibility was more for
me, the creator of the preset. 
I don't want a user to get bogged down with the details of where and
what so much.  (Granted - I don't know if anyone has even downloaded
this preset or ever will!) Unless you are a programmer or really into
this stuff, you are a musician and you don't want to know, you want
the tools to help you do you work, not how they work.  I am just
trying to make it streamlined for that person. I have made it easy.
Download the .syx send it with whatever sysex utility you have.  If
you are on a mac no problem, just send it, it just overwrites 11-16.
Also - I warn in several places, in red and bold that it will do this
and to make sure you have backed up your presets.
I also encourage them to try bcmanager. 

I remember finding the mackie preset two years ago and learning that I
had to send a separate .syx the store.syx files to get the preset
saved. This was a bit cumbersome and unsettling. This was before I
know what I know now.  Do we want users educated? Resounding Yes!
However, how much music have I made sense finding that preset?
Then getting so into mackie emulation, building my own translator,
then finding your program and building a few presets.  I know you
understand.

So my using presets 11-16, I would have liked to use 1-6 to be the
most obvious, however, the all controls are on 1 usually...  So 11 =
voice 1, 12=voice 2 etc.  Makes it easy to see (bcr led readout) which
voice you are on and 11 is pretty far down the line of presets to not
interfere with most other stuff that might be on a bcr. 
I know, I know... but life is compromise.


> 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

Yes - I see this as a great solution. For the user of bcmanager. 
I need to do another short flash movie on this and capturing sysex for
synth control.  

> 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

Hahahahaha.
Yeah I put them in the files section there.
They are also on my site.
I used a program called Wink. However, they were my first with that
program and the mouse moves around somewhat erratically.  Perhaps my
next one will be a bit more stable.

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

Bummer, I hate that.

Again, thanks for all the changes.
Kip