Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

Re: Daisy chaining BC2000's

2010-10-10 by stiffler

--- In bc2000@yahoogroups.com, "Royce" <rpcfender@...> wrote:
>
> Hi
> 
> > I have 2 BCF2000's that up until now I have used separately, trouble free, to control some lighting software. Last week I had the idea of using them together to expand their usefulness, and followed the instructions provided in the user manual.
> 
> How have you connected them??
> 
> > Unfortunately, as soon as I switch out of USB mode 1 my software no longer recognizes the BCF and gives me an error.
> 
> What is the Software??
> 
> > It is as if the BCF has stopped communicating with my computer, and I can't figure out why. Any help would be much appreciated!!
> 
> Does your software know about BCF's or just about midi control?
> Does the software expect to see the BCF as a Midiport??
> 
> What are you actually trying to do??
> Are you trying to make a 16 channel lighting mixer?
> 
> 
> You need to be very specific when asking these types of questions.
> 
> 
> All the best
> 
> Royce
>
Hi,

I am using the BCF to control Martin Lightjockey via a program called Faders For Lightjockey. The software will work with any MIDI device that is hooked to my computer, and I can chose my device from a list of installed hardware from inside the program. Using the software I am able to use the faders & rotary encoders to control assigned channels inside Lightjockey; the more faders I have, the more control. To daisy chain them I have switched the first BCF to U4 and the second BCF to S3. When I do this, I get an error from Faders, and it tells me there are no devices installed. I have used other MIDI devices with no such problems, so I am a little confused; am I missing something in the BCF settings??

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.