Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

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

Thread

BCF2000 & Cubase 5

BCF2000 & Cubase 5

2009-09-24 by vras23

Is here anyone who has suitable setup for Cubase 5? I found there are two (3 ways) to control Cubase with BCF2000:
1) using Mackie Control protocol emulation - this is very confortable with switching through 8-channel banks and setting levels with motorized faders(Cubase shows selected banks with white stripe across ch 1-8, 9-16, 17-24 etc.), however pots are mapped to functions that are completely 99% useful /like embedded EQ that I do not use at all - I often use external VST EQs, or for example channel panorama - this is what I usualy set once in the project and do not want to control it through remote controller! And finaly, the nightmare is a risk that these unwanted functions and parameters will be changed 
in Cubase project unintentionaly after random touching of some BCF pot!) Just the faders, solo, mute and start/stop are usable functions, almost everighing else is unwanted.

2) using Macie Hui  - dtto.

3) using Generic remote protocol (sysex and xml) seem to be the most  usable - this offers good ways to customize. My question is related with transport functions like forward/backward - Cubase uses separate control for Forward and Backward commands, scrub up, scrub down, zoom in, zoom out, nnudge right, nudge left etc...Using this scheme, there is a way to control zoom (for example) with two BCF pots - the first for Zoom_In and second for Zoom_Out. There is very nice behringer script language to create sysex file for BC?2000 and easy way to map these settings inside Cubase, but my question is: is there any way to associate BCF rotary controller (pot) with two CC messages - send one CC(1) when turing right and send another CC(2) when turning left?? This would be great to control transport or zoom confortably, each function with its one pot...

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.