Bc2000 (for the BCF2000 & BCR2000)

Hi !

Mark van den Berg <markwinvdb@...> a \ufffdcrit:

> As I see it, the issues can be categorized as follows:
>
> 1. Hardware: better faders, buttons, etc.
> This would basically amount to NEW devices. Definitely an interesting
> and relevant subject, but (as I think someone has already pointed out)
> this is a side issue in terms of the BCFs and BCRs we've already spent
> our money on.

Yes, this is a totally different story. Of course, I was thinking about 
improving the already existing hardware. I am not sure lots of "already" 
users would spend more money into another - even an improved one - device.

> 2. Firmware:
>
> a. Bugs: Royce and I have found quite a few bugs in the BC language
> protocol. Of course Behringer should fix these bugs, but I'm afraid
> we'd have to reverse-engineer the existing firmware and write our own
> version. Very difficult and laborious, but I'd be willing to
> participate.
>
> b. Improvements, i.e. new, "cool" features.
> We'd DEFINITELY have to write our own firmware to get this realized.

Yes, probably.

As a Cubase user, I wish Behringer had used the Steinberg Remote SDK to 
create a native Cubase mode. To understand what I mean, just look at what 
Frontier did for their Tranzport and Alphatrack.

> 5. The MIDI implementation.
> Behringer have been very unforthcoming in this respect; basically they
> haven't published ANYTHING.
> While developing BC Manager, I've been forced to analyze the BCF/BCR's
> MIDI implementation in great detail. I've written down my findings in
> a document describing (as far as I know) all aspects of the BCF/BCR's
> MIDI implementation (except the BCF's emulation modes). This includes
> detailed descriptions of the SysEx messages to which the BCF and BCR
> respond, in particular the syntax of BCL (the language used in the
> script lines embedded in SysEx messages), and also the precise MIDI
> messages sent by the BC when the user moves a control (button,
> encoder, fader). The document is currently about 85 pages long; it's
> perhaps 90% complete - I'm hoping to publish it by the end of the
> month as well.

This is an enormous amount of work, just for the community. Respect to that 
!

Again, if any testing is required - and the integrity of the hardware is not 
at risk - I'll be happy to help.

Cheers.
J\ufffdr\ufffdme.