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: New BCF2000 Owner, Almost Totally Lost

2008-10-20 by libraclassic2

OMG.  This is EXACTLY the information i'm looking for!  I still have
to understand certain terminology, but I've just found out enough to
apply - I can't wait til you come from lunch!!!


--- In bc2000@yahoogroups.com, "goyya76" <goyya76@...> wrote:
>
> --- In bc2000@yahoogroups.com, "ashwinkumar" <ashwinkumar_m@> wrote:
> >
> > I went into Devices/Midi Device Manager to install the .xml file that
> > came with the .zip Cubase file d/l from the Behringer site (this may
> > be what's wrong, i dont' know)
> > 
> > 
> > 
> > u need not do that at all mate. just power up bcf2000 in ncc . switch 
> > on huskervu. opencubase and configure a mackie control under device 
> > manager and configure outputs/ inputs in it as i said. and then click 
> > apply. thats all.ur bcf will be working. in cubase mixer. u need not 
> > load any xml/ sys files at all into cubase or bcf vice versa
> >
> Hi guys, as soon as i have some spare time (maybe tomorrow evening) 
> i'll try to post some clearer information on how to configure the 
> generic remote....in the meantime some background (i hope it's not 
> redundant):
> 
> - the Generic Remote configuration panel has two parts: the upper one, 
> which lists the MESSAGES sent by the hardware controller, the lower 
> one, in which those messages are mapped to cubase actions
> - above the upper part there's the self explaining midi in/out selection
> - on the right of the lower part there's a button to add banks: given 
> ONE list of MESSAGES in the upper part, each message in the list can be 
> assigned to different actions, depending on the selected bank
> - on the upper left corner there are +/- buttons to add/delete a 
> generic remote (you can use as many GR devices as you want)
> 
> an example:
> 
> *BCF2000
> - faders have been programmed to send CC1 - CC8 on channel 1, min value 
> is 0, max value is 127
> - encoders (first group) has been assigned C9 - CC16, same as above
> *GENERIC REMOTE
> - add a new generic remote
> - in the upper panel, a default list appear - it can be cancelled (self 
> f explaining buttons on the right)
> - we can create 16 new rows and fill them with the correct data:
> - we name them 
> Fader1,Fader2,...Fader8,...,Encoder1,Encoder2,...,Encoder8
> - we select the correct message type (drop down menu)
> - we select the correct midi channel (drop down menu)
> - we select the correct midi CC number (typing)
> - we select the correct max value (typing)
> - we select any combination of the following letters (drop down 
> menu):R,T,R
> R: receive: cubase will receive the message
> T: transmit: cubase will send the message to the controller when you 
> move on the GUI the mapped element (you pull up the fader, the HW fader 
> will move up)
> R: relative: select it if you programmed the BCF with relative CC 
> (let's stick to absolute messages - easier!)
> *IMPORTANT: you can add a row, then use the learn function and save 
> time (though some manual editing may be required since the Generic 
> Remote is somewhat buggy...)*
> 
> now let's move to the lower panel
> - 16 rows have appeared; via drop down menu you can choose which 
> actions will be mapped to the 16 controllers
> 
> more to come after lunch!
>

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.