Bc2000 (for the BCF2000 & BCR2000)

Hi rpcfender, or anyone else familiar with his excellent BCReditor.

I'm not quite getting the results I expect when changing a script and then attempting to upload it to my BCF.  I'm using Windows 7 if that makes any difference.

What I thought would happen is this:

1) make change to a script
2) save script with a name

These 2 steps work fine.  I can go to another script, then when I want to reload any script, the correct script loads into BCReditor.  The issue is with how to store that script as a patch, then upload that patch onto the BCF (BC with faders, if that makes any difference).

3) upload script/patch using either SEND or Store Patch.
4) different results happen, none of which are the script I loaded

The BCReditor correctly gets the patch info (a patch is the same as a preset, correct?).  But it doesn't load the script into the BCF...?

Hi psionic11

> I'm not quite getting the results I expect when changing a script and then attempting to upload it to my BCF.  I'm using Windows 7 if that makes any difference.

Can't say as I am only an XP user on Windows, but I doubt it.

>The issue is with how to store that script as a patch, then upload that patch onto the BCF (BC with faders, if that makes any difference).

Not really

> 
> 3) upload script/patch using either SEND or Store Patch.
> 4) different results happen, none of which are the script I loaded

So your Midi connections are OK? The display whizzes around as you send the data?

> 
> The BCReditor correctly gets the patch info (a patch is the same as a preset, correct?

yep

).  But it doesn't load the script into the BCF...?

The BC has an edit buffer. When a preset is selected with the <> keys or by Midi it is loaded into this edit buffer. 

This is now the current preset. 

If you load something from the PC editor into the BC it overwrites this buffer and so will function straight away, but if you select a different preset with the <> keys you will overwrite the edit buffer with this preset from memory and the script preset will be lost. 

If the script is not correctly downloading try....
On the Script page there is a sub-page "Save & Get"
On the right make sure the "Sysex Header Bytes" is either BCF or Universal
Under that there is a button called "Device ID" is that isn't "All" press the button and select "All"

In the script the first line for a BCF is "$rev F1" without the ""
and should finish with "$end"

When you press the send button (top right) the program should format the script and send it to the BCF. The BCF display should whizz around as the Midi is transmitted.

To save the preset in to a slot in the BCF ...
Once the script is in the BC edit buffer press STORE.
Use the <> keys to select what preset you will overwrite.
Press STORE again and it will be saved to the flash memory in the BC

If you are still having problems take a preset file from the groups file and try that.

Let me know if there are still problems.

Royce

I'm still having issues, but I think I'm closer to understanding the work flow.  At the moment I'm not even concerned with saving my own scripts; I'm just practicing copying/pasting Behringer presets and slight changes to them. 

The key seems to be: double-click STORE on the actual B-control itself after a transfer is made.

My BCF responds with the whizzing lights, but it's still unpredictable as to what will happen.  It may be that one of the experimental preset I made was faulty.  The preset only went up to fader1.  I copied and pasted fader1 twice, re-naming is fader2 and fader3.  These saved successfully as scripts, but loading a script into the BCF did not result in this 3-fader preset... it yet again had only one fader, despite the script showing all 3 initially...

For example, say I wanted to do something super simple, like copy a blank INIT patch from preset 9, and overwrite it onto another filled preset, like 11....

1) double-click 9 from Save & Get list
2) click Get Patch
3) script sections warns you it will overwrite; say yes
4) script section now shows basic INIT preset

5) go back to Save & Get
6) single-click on 11
7) now what?...

any combination of double-clicking or single-clicking or STORE PATCH or SEND doesn't result in the loaded 9 script simply over-writing the 11 preset... the 11 preset remains the same....?

I must be missing something fundamental in my understanding.  Thanks for your patience...

> For example, say I wanted to do something super simple, like copy a blank INIT patch from preset 9, and overwrite it onto another filled preset, like 11....
> 
> 1) double-click 9 from Save & Get list
> 2) click Get Patch
> 3) script sections warns you it will overwrite; say yes
> 4) script section now shows basic INIT preset
> 
> 5) go back to Save & Get


Method 1........

Double click on 11 to select it on the BCF

This loads the preset 11 into the edit buffer on the BCF
The BCF should read "P-11"

Now you want to overwrite the edit buffer with the script in the PC
Press the editor's "Send" button on the top right.

This will send the script to the BCF's edit buffer.

Press "Store Patch".
This sends a command to the BCF to write whatever is in the edit buffer to the currently selected preset. In your case Preset 11.

Method II....
The current preset on the BCF is 23
Send the script to the edit buffer with the "Send" button.
You have just overwritten a copy of preset 23 that was in the edit buffer with the script in the PC.
You want to write the modified edit buffer to Preset 11.
Single click 11, then press "Store Patch"
When the Patch list is "Restored" you should see the name of the Script in the preset 11.
The current preset should be 11 "P-11"

So...
Double click selects a preset on the BCF.
A quick way to get around the presets to try them out, but this will overwrite the edit buffer each time, but that's OK because you haven't sent the preset script from the PC yet.
Or...
Use single click to select a different preset that you want to write to. You use this when there is something in the edit buffer that you want to keep.

"Preset" and "patch". Roland calls them Patches on their synths. It comes from Patch cords that were used to join sections of modular synths together to make a sound. Confusing? - 

Now to rearrange presets...
Preset 32 will be the 'don't care what happens to it' preset
Double click on the preset 1 . (Loads on the BCF)
Single click on 32 then press "Store Patch". A copy of 1 is now in 32.
Double click on 17 because that needs to go to 1
Single click on 1 and press "Store Patch" - now  a copy of 17 is in 1

2 is blank
Double click 32 so we can store that copy of the old 1 to preset 2
Single click 2 and press "Store Patch" etc........

There is no need to load a preset into the PC to rearrange.

Note: There are some scripts that can be written to the BC that when you load them back the script will be wrong. 
The checksum in .tx lines for example.

If you do the above without bringing them into the PC they copy correctly.

Hope this helps
Royce

Thank you, rpcfender, that cleared up a lot of points.  For one, I had the concept of what sends to what backwards.  Your examples are all self-consistent, and so I understand the principles now.

Unfortunately, I'm still not getting the results I should expect.  And this is just trying to re-arrange patches on the BCF, nevermind transferring custom scripts to the machine.  A couple times the BCReditor closed unexpectedly.  Also, an "undefined external error" popup box comes on when trying to use BCF MIDI port 2 OUT.  This is reproducible with MIDI-OX as well.

This leads me to think that the BCF MIDI driver isn't behaving correctly.  I'll focus on correcting that for now and come back and confirm when all is working as intended.  Thanks again =)

Hi Royce, I'm making some progress despite my BCf's erratic behavior.  I've managed to write an .easypar script for one encoder, and upload it to the BCF.

For reference, here's the successful .easypar script I sent to the BCF which the BCF then successfully controlled my synth:

$encoder 1
  .easypar CC 2 7 0 127 absolute
  .showvalue on
  .mode bar
  .resolution 96 96 96 96
  .default 100

That script turned encoder 1 into a volume (MIDI CC 7) knob for the synth, which is on MIDI channel 2.

From that, I managed to convert the script from .easypar to .tx with the following:

$encoder 1
  .minmax 0 127
  .default 100
  .tx $B1 7 val
  .resolution 96 96 96 96
  .showvalue on
  .mode bar

Nifty proof of principle.  But I don't want to use 7-bit CC commands; I need to use NRPN commands for some extra functionality that CC commands can't give me.  After a bit of fumbling, I managed to get another script working, which uses the MIDI CC's 98 (or $62 in hex) and 99 (or $63 in hex) for NRPN LSB and MSB.  

The a-ha! moment for me here was when I realized that the 99 MSB needed a data parameter, which is MIDI CC 38 (or $26 in hex), and likewise for the 98 LSB CC.  This script uses NRPN 0, values 0 to 1, switch the voice mode from polyphony to unison:

$encoder 1
  .showvalue on
  .mode bar
  .resolution 96 96 96 96
  .default 0
  .minmax 0 1
  .tx $B1 $63 $00 $26 $00 $62 $00 $26 val


So, that's all good so far.  I'm understanding the potential I can get if I can consistently convert all my synth's NRPN parameters -- both continuous/switch and positive/negative.

The thing that is bugging me still is why sometimes when I go to save a preset/script, it seems to chop off that last set of commands... that is... where I used to have 8 faders of info, the script suddenly somehow chops off at fader 1, with faders 2-8 vanished into limbo...