Bc2000 (for the BCF2000 & BCR2000)

> The fact that the BCR was in S-1 probably explains your original feedback problem: as the diagram in Behringer's BCF/BCR manual shows, in S-1 anything sent to the BCR's MIDI IN is passed on to MIDI OUT A and B/THRU, which is undesired in a situation like yours, where Cubase is both at MIDI IN and MIDI OUT A (or B/THRU).
> 
> In a bidirectional connection with Cubase you should definitely use S-4 (and only MIDI OUT A, not B/THRU). (S-3 would be possible too, but only via MIDI OUT B/THRU.)

Yepp, I can confirm, that S-4 works propperly now. After totally removing doubbled controllers fom the BCR, it runs more smoothly

 > It may indeed be a good idea to have EITHER the BCR OR the Faderport control a particular parameter, to avoid interference and jumps.


this was the solution!

> On the other hand, you might try to "integrate" the BCR and the Faderport via a setup with virtual MIDI ports (e.g. MIDI Yoke). You could then run MIDI-OX in the background to connect Cubase, the Faderport and the BCR in a triangle, where each of the three sends data to both the other devices. This would guarantee total parameter synchronization.


I tried that today for several hours, but got lost with it and turned to the seperated setup finally. 

> One other advantage of a setup via MIDI Yoke would be that you could insert a MIDI diagnostics program (e.g. MIDI-OX, MIDI Tools or BC Manager) into any connection between Cubase, the Faderport and the BCR, so that you can find out exactly which messages are sent when.


I implemented the MIDI monitor in Cubase to get a clue of what is going on. Seems to run flawless for the moment...

Thanks a lot for your help.

Greetings from Germany,

Uwe Manns