Thanks again Mark.
I tried it in S4 mode with MIDI Out A and in S3 mode with MIDI Out B. Same thing - "No response from B-Control" and "B-Controls detected: 0".
I hear you on the dangerous part; I was attempting a complete reset as a last ditch attempt at recovery! ;-) The error message was exactly the same though, in both of the scenarios listed above.
Looks like it's time to replace it :'-(
Cheers for your help.
To: bc2000@yahoogroups.com
From: markwinvdb@...
Date: Thu, 13 Dec 2012 08:04:54 +0000
Subject: [bc2000] Re: BCR2000 no longer sending MIDI?
From: markwinvdb@...
Date: Thu, 13 Dec 2012 08:04:54 +0000
Subject: [bc2000] Re: BCR2000 no longer sending MIDI?
--- In bc2000@yahoogroups.com, dave watkinson wrote:
> I reconnected the BCR to my MIDI interface and put it into S3 mode. BC Manager can't detect it.
In mode S-3 anything received at the BCR's MIDI IN is directly routed to the BCR's MIDI OUT A.
So in S-3 you shouldn't use MIDI OUT A in a bidirectional setup with your computer; instead, you should use MIDI OUT B.
Alternatively, use MIDI OUT A under S-4.
(MIDI IN is routed to MIDI OUT B in this case.)
> Despite the lack of BCR detection (I disabled all my other USB / MIDI devices) I tried to open the Behringer default sysex file in BC Manager, and was greeted by this message:
> Error: MIDI system exclusive error
> Wrong command
> Send Memory ($34)
> This may be the result of a feedback loop
> Message 1
This is in line with what I wrote above: in S-3, BC Manager gets any message it sends to the BCR's MIDI IN straight back from MIDI OUT A.
Incidentally, the "Send Memory ($34)" messages contain BCR firmware data: if the BCR shows "1.10" upon power-up, there is no need whatsoever to try to update its firmware. (In fact, it's a bit dangerous.)
Hope this helps,
Mark.
> I reconnected the BCR to my MIDI interface and put it into S3 mode. BC Manager can't detect it.
In mode S-3 anything received at the BCR's MIDI IN is directly routed to the BCR's MIDI OUT A.
So in S-3 you shouldn't use MIDI OUT A in a bidirectional setup with your computer; instead, you should use MIDI OUT B.
Alternatively, use MIDI OUT A under S-4.
(MIDI IN is routed to MIDI OUT B in this case.)
> Despite the lack of BCR detection (I disabled all my other USB / MIDI devices) I tried to open the Behringer default sysex file in BC Manager, and was greeted by this message:
> Error: MIDI system exclusive error
> Wrong command
> Send Memory ($34)
> This may be the result of a feedback loop
> Message 1
This is in line with what I wrote above: in S-3, BC Manager gets any message it sends to the BCR's MIDI IN straight back from MIDI OUT A.
Incidentally, the "Send Memory ($34)" messages contain BCR firmware data: if the BCR shows "1.10" upon power-up, there is no need whatsoever to try to update its firmware. (In fact, it's a bit dangerous.)
Hope this helps,
Mark.