Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "k5kip_1999" <k5kip_1999@> wrote:
> > Yes - it can be edited, however, it should probably be shot again.
> > By shot i mean winked. 
> > Wink <http://www.debugmode.com/wink/download.php> is what I used to 
> > created the "getting started" vids.
> > I was still learning how to use this program and how to record mouse
> events.
> > 
> > You apparently don't like what I have done...
> 
> Haha, I didn't say that! Basically I was just curious, and I was
> wondering what problems I would cause you if I changed something
> fundamentally in BC Manager that would require a change to one of your
> videos...

Don't sweat the vids... let your program develop as it may.
We the users will adapt as necessary.

> 
> > I do _/not/_ get the error on Verify.
> > All works fine on Verify - however, that is after I have already
> detected.
> > When I do *"scan enabled ports  *" I get the Midi sysex error wrong 
> > model address 004962B8.
> > This happens every time  I do this when "scan" is on.
> > "If I go to "verify" all is well.
> > Also - I don't have a  BCF, just a BCR, so I cannot comment on
multiple 
> > devices.
> 
> > Ok - "scan"  I set wait time from 300, 500, 1000 and still get the
same 
> > error on startup.
> > So - ?
> 
> It would appear that it is not a timing problem then, if you still get
> it at 1000 msec. E.g. my own BCF and BCR (connected via USB) tend to
> respond within 10 msec, so even 100 should be more than enough in most
> situations.
> 
> > What is the default on first run? none, verify or scan?
> 
> During the first run (i.e. if BCMan.ini doesn't exist yet) BC Manager
>  version 1.4.0 performs a full scan using 100 msec per MIDI output
> port. So this scan sends an Identity Request to the first MIDI output
> port, then listens for 100 msec on all MIDI input ports, then sends an
> ID request to the next MIDI output port, etc.
> 
> What I still don't understand is how you can get "wrong model" during
> scans, since the scan's Identity Request messages are generic, and the
> routine processing any replies should accept both BCF and BCR.
> (That's why I thought the "wrong model" error could only occur during
> the "verify" operation: that operation specifically targets all the
> previously defined BCFs and BCRs, and does produce "wrong model" if
> e.g. a BCF responds when a BCR has been targeted.)
> 
> Just some ideas:
> 
> - Do you get the same error message when you execute "Detect
> B-Controls" from the MIDI pull-down menu of the B-Controls window? If
> you do, you could first start "Record" in the "MIDI input messages
> (general)" window (open via the main window), then execute "Detect
> B-Controls", upon which any actual incoming MIDI SysEx response
> messages should be recorded in the MIDI input messages window - I'd be
> very interested in the actual response message(s). And what happens to
> the B-Controls list, in particular the "Identity" column?

Mark, I am no following you.
I have attempted, it just does not seem to scan anything unless, I
restart, then I can't record the midi.
If I close all the devices, then scan it does not do anything.
If I then add a bcr, then go to scan it does not do anything, until i
restart he prog, then I can't recored because record is not recording
until I open the program.
Ok got it... working... the detect ...

results -

bcr2000(1) 183.533 sysex 20 followed by data "F0 00 20 32 00 15 02 42
43 52 32 30 30 30 20 31 2E 31 30 F7"
Midi Yoke NT:1  183.639 sysex 8 data "F0 00 20 32 7F 7F 01 F7"

You are on to something with midiyoke....
Let me disable that port from the scan.

You have it!

When all midiyokes are disabled in, MidiDevices menu, the there is no
scan error.

So... unless we disable those midiyoke midiports we will get that
error. Let me try it with just midiyoke2... the answer is yes. The
error returns with midiyoke2 enabled.  Now the message comes from
Midiyoke NT:2. 
So it scans the first midiyoke port gets the error than leaves it.
Try it.
My bcr mode is U-1.
I don't have my midiyokes routing to anything. They are just installed.

Kip


> 
> - Do you have some other Behringer device (non-BCF/BCR, perhaps a
> BCA2000?) that might produce this error?
> 
> - Is there some strange loop in your setup, possibly because of your
> BCR's U-mode or MIDI cables, or your MIDI Yoke setup?
> 
> - What USB driver are you using for your BCR? Windows' standard "USB
> Audio Device" or Behringer's 1.1.1.0/1.1.1.1/1.2.1.3? (Yeah, I know,
> I'm getting desperate...)
> 
> Mark.
>