Bc2000 (for the BCF2000 & BCR2000)

That sounds very interesting.   I had previously made 'touch' buttons by looping the output of my BCF though cubase changing the monitor buttons into touch buttons, but your solution sounds so much more eloquent.  I would definitely be interested in helping you test your program. I'm on win7 x64 running Cubase 32.  Get in touch if you would like so help testing.

yeahtunatuna*at*gmail*dot*com
--- In bc2000@yahoogroups.com, "salomon_nn" <salomon_nn@...> wrote:
>
> My BCF2000 arrived just a few days ago, I was very thrilled at first, but disappointed a bit later when I found out what "is not touch sensitive" means when you are actually working with it.
> I didn't know much about the Midi protocol at first, but during the last 3 days I have developed a program that intercepts the midi messages (I am working with Cubase), knows the "snapshot" function of the BCF and does some neat things.
> 
> The next paragraph is only about why I did what I did, and you can skip it, if you are not really interested.
> Basically I wanted my program to find the moments, when the user is changing the fader physically while Cubase tries to move the fader with the motor. The problem seems to be (as I found out later), that the BCF does not read its actual fader position within ~350-400 ms after the last a motor command.
> So you have no problem as long as Cubase does not want to change the position of the motor (a flat automation line), but the second the motor moves, you have to fight against it and Cubase will still not register in which direction you moved you fader.
> So if Cubase sends a new fader position to the BCF and sends another and another, each within 300 ms or so, and the BCF moves the fader with its motor all the time, it does not read the actual position of the fader (I will try to get in touch with Behringer if this can be changed [or if you guys have any suggestions ...], but I guess not).
> Therefore, even if you use the snapshot function and force the BCF to send all its current sensor data, you don't get the actual position of the fader.
> ---
> 
> To make a long story short: My program listens for a BFC-button, gets the current snapshot and forwards only those fader and encoder positions that are in "write" mode.
> This way you can push a button and Cubase instantly stops to move the fader that is in write mode (or several if you want to simultaneously change their values) and you can move around freely without having to fight the motor (and not getting recognized by Cubase), or changing the mode Cubase is in.
> Another problem that is solved with this is: if you want to use the touch mode in Cubase and you want to "write" a steady automation line, the BCF doesn't send any new position updates to Cubase, because you are not moving your fader. So Cubase "thinks" you have let go and uses the old values of the automation track.
> With the button you override this, by sending new updates to Cubase.
> 
> I don't know, whether anyone has already done this, but I haven't found anything. And btw, thanks for the BC Manager and BCF Midi Manual, without it, it hadn't worked ...
> 
> In conclusion I can say, that I wouldn't want to work without it, now I have a "touch sensitive" (emulated) DAW for a bargain price ..
>