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: BCF2000 and control of Cubase 6.0.5 "Quick Control" Sliders

2012-02-27 by cubasesix

Updating: I see there is a "request data" function that may be of help here - I would be able to stay in Mackie emulation mode ... when I reenter a Cubase project that had quick control sliders set at specific values, before I touch the buttons/pots I maybe could use that "request data" function to have the BCF2000 values set to match the Cubase project.

I don't know if this would be better than leaving the Mackie Emulation mode to enter the native mode, where I know the P-UP function is available, or possibly even motorized faders for the Cubase Quick Control sliders. 

Thanks for any thoughts you may want to throw my way!
***************************************************************

--- In bc2000@yahoogroups.com, "cubasesix" <cubasesix@...> wrote:
>
> Hello - I have learned that when set to Mackie Emulation mode, the BCF 20000 motorized faders will not control the Cubase 6.0.5 "Quick Control" sliders. 
> 
> Does anyone here control the Cubase "Quick Control" sliders via a BCF2000? Would you be able to please give a quick summary of how you are doing that? I'm wondering if entering another mode ("Native"?) would allow the faders (motorized or otherwise) to control those sliders, or if I should just stay in Mackie Emulation mode and use the buttons/pots. 
> 
> I think I understand the advantage to using the faders (even if the motorized function is not available for some reason) is that I can activate the "P-UP" feature so the Cubase sliders don't jump every time the BCF 2000 control is moved a bit (such as if I come back from working on a different project). Please correct me if that is not the right way to think about this ... :-) 
> 
> Thank you!
>

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.