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 BCR Mackie Emu with 16 vPots uploaded!

2008-09-10 by k5kip_1999

Awesome!

I can't wait to try it out!
I like the idea of combining the two.

Kip


--- In bc2000@yahoogroups.com, "stefan_soundstudies"
<stefan_soundstudies@...> wrote:
>
> Hi fellows,
> 
> i just finished my new BCR-Mackie�"Setup for Live, with a nice new
> trick (imho), that gives me another set of 8 vPots!
> 
> So now I can use two plugins at once, or two different pages of plugin
> parameters at once, and all that without any needed routing.
> 
> How this works?....   just read on ...
> 
> If you ever have used your BCR in Live assigned as “BCR 2000”, not as
> mackie control, than you know about the usage of the “device
> parameters”. (these are always instantly connected to the currently
> selected device)
> 
> I copied those ‘device parameter’ encoders to our beloved
> “BCR2000+Live_ver4_1” preset, and therefor kicked out some Mackie
> functions that I don’t need really often.
> 
> Whereas you have to press at least 3 ‘mackie’-buttons to route the
> vPots to any plugin, you have just to select(by mouseclick) any plugin
> to have the 2nd row of vPots routed to that plugin.
> 
> Since these parameters are called ‘device parameters’ in live, I will
> call our 2nd row of pots “dPots” from now on.
> 
> The plugin-parameters are assigned over different pages for the dPots
> in the same way as you allready know it from the standard mackie
> emulation, and i made an encoder that selects the pages for the dPots 
> ....
> 
> 
> more info inside 'readme.pdf' inside 'bcr_live_MCE_16v.rar'
> which you can find at the files section/presets
> 
> also included is a nice overlay... 
> so maybe have a look
> 
> (the overlay is just a customized version from Magos cool BCF overlay)
>

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.