Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "k5kip_1999" <k5kip_1999@...> wrote:
> I used a program called Wink. However, they were my first with that
> program and the mouse moves around somewhat erratically.

Yeah, I noticed that. Glad to hear it wasn't because of my computer
(at least in this case!).

> Perhaps my next one will be a bit more stable.

I've been wondering: can you edit a video after you've recorded it?
Cut certain scenes, replace them etc.? Or is it just a "one-go" deal?

I have played your first video, but I only got as far as the bit about
the "Invalid model" message: in the video you treat it as a "fact of
life", but of course it's something that shouldn't happen, and since
someone else reported something similar a few weeks ago, I've now
spent quite some time studying this problem:

I think this error message can occur ONLY (but correct me if I'm
wrong) if "Startup detection" has been set to "Verify identity...".
The problem is probably caused by an Identity Reply message coming
back from e.g. a BCF too late, namely when BC Manager has already sent
an Identity Request to e.g. a BCR: BC Manager is then expecting a
reply from that BCR, not any more from the BCF.

So if you get this error message regularly, you might try increasing
"Waiting time" in the "Detect B-Control options" dialog box (accessed
from the main window's Options pull-down menu). Let me know if this
helps - if it doesn't, there is something even more sinister going on...

Related to this, and perhaps even more important:
If a BCF or BCR reports back too late during a full connection scan
(cf. "Scan enabled MIDI ports"), this may cause the assignment of an
invalid "MIDI output port", as displayed in the B-Controls window. So
if the "Identity" column in the B-Controls window is empty for one of
your B-Controls, and if running "Receive identity" doesn't fix this
(i.e. if you get no reply), it might mean that the previous full
connection scan has assigned the wrong MIDI output port. You could try
to correct this manually (via MIDI -> Options in the B-Controls
window), or set "Waiting time" to a higher value and run "Detect
B-Controls" manually.

Version 1.4.1 (or 1.5.0!) will probably have an increased default
waiting time, so that these problems become much less likely to occur.

Mark.