Bc2000 (for the BCF2000 & BCR2000)

BC Manager 1.2.2 is now available from the file section under
Applications.

By popular request, you can now request a BCF/BCR snapshot directly from
the LEARN/custom output recording dialog box via the new "Snapshot"
button. (This has the same effect as pressing EDIT + "PRESET<" on the
BCF/BCR.)

There are also a few VERY minor improvements to the user interface.

Mark

Beautiful. I will download and test tomorrow morning (along with five
million other things I want to try...). A technical question -- have
you (or someone else) used a USB sniffer to figure out the Behringer
coding language? I suspect that there are a few tricks one could pull
off with the KSP 88 if its communication protocol could be figured
out. I don't think it's as flexible as the Behringer, but perhaps it
could do more than just the usual cc assignment thing. For instance,
you can assign some predefined sysex messages to various controls. I
strongly suspect that these messages aren't the only bits of sysex
that KSP could save...

    -Andrew-

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:

>
> BC Manager 1.2.2 is now available from the file section under
> Applications.
> 
> By popular request, you can now request a BCF/BCR snapshot directly from
> the LEARN/custom output recording dialog box via the new "Snapshot"
> button. (This has the same effect as pressing EDIT + "PRESET<" on the
> BCF/BCR.)
> 
> There are also a few VERY minor improvements to the user interface.
> 
> Mark
>

--- In bc2000@yahoogroups.com, "poser_p" <poserp@...> wrote:
> A technical question -- have
> you (or someone else) used a USB sniffer to figure out the Behringer
> coding language?

I haven't, at least: the MIDI implementation document (and BC Manager
in its wake) is completely based on straightforward testing at MIDI
level (so having nothing to do with USB specifically).

"USB sniffer"? I must admit I'm completely out of my depth as to what
this is and does, so you'd have to enlighten me on this point.

And what do you mean by "the Behringer coding language"?
There is of course BCL (probably standing for "B-Control Language"),
which has already been described (almost completely) in the MIDI
implementation document.
Then there is the USB communication protocol, but that's not
specifically Behringer - although it might be interesting to look at
the Behringer USB drivers for Windows (vs. 1.1.1.0/1.1.1.1 etc.)
And finally there is the machine language of the BCF/BCR's
microprocessor: the firmware syx files (1.07, 1.10) contain the
encrypted machine code that makes the BCF and BCR work.

Mark.

A USB sniffer detects all "packets" that are sent over USB to a
device. I assume (I don't know for sure yet) that USB devices
communicate using some sort of packet messaging protocol, like TCP/IP
(have to double-check that though... I'm downloading the spec right
now). Hence whatever the "payload" is will be viewable via the
sniffer. So, whether it's a MIDI sysex message or data being copied to
a USB drive, the sniffer will show it and it's up to the user to
figure out how to interpret it. 

I've only seen it referred to as "BCL", hence I thought that might
mean "Behringer Coding Language", but "B-Control Language" makes more
sense. Anyways, I didn't know if users found out about BCL via
Behringer and Behringer's documentation or by sniffing USB
communications and reverse-engineering it. The former would be far
easier than the latter, of course, but I will probably need to do the
latter if I'm going to make heads or tails of what the Enigma editor
sends to a Keystation 88. The reason being that recording the Sysex
data when patches are transfered between the computer and the KSP
didn't show anything useful -- certainly not the data I'd expect to
see. This suggests to me that all the Sysex messages do is set memory
blocks in the KSP to "write" mode or something similar. Unless I'm
missing something, of course, which could easily be the case.

    -Andrew-

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
...
> "USB sniffer"? I must admit I'm completely out of my depth as to what
> this is and does, so you'd have to enlighten me on this point.
...
> And what do you mean by "the Behringer coding language"?
> There is of course BCL (probably standing for "B-Control Language"),
> which has already been described (almost completely) in the MIDI
> implementation document.
...

> 
> Mark.
>