Bc2000 (for the BCF2000 & BCR2000)

If anyone has had any luck chaining two BCR's together for MCE purely with midi cables and a separate midi interface, please give me a shout!

I'm one of these people who's had major problems with the USB driver. So I don't use it.

How's it done and how does it work in operation.

Any help appreciated.

Dan

Not that I have done this since I only have 1 bcr... however, I do have some advice.
If you want to run mce on both -
I have done this with GenMce and genmceXT from other controllers(I do not recommend that at this time and I wrote those programs, unless you don't mind not having fader feedback)I digress...

You will be using your bcrs to be 1st one like a mackie control universl, the 2nd one will be mackie control XT.
Now you could use the same presets in both, but be aware that the second bcr (mackie control XT) will only work with faders, vpots, mutes arms solos.  Bank keys, page keys as well as others will not function as they are already set in the mackie control universal emulation...

Ok - what is he talking about?

In your software you will set up 
1 bcr input/output control surface as mackie control universal. 
The second bcr input/output control surface will be mackie control XT.
(provided your software has both of those and allows more than one control surface, what daw will you be using this setup with?)

Now as for the question of how to physically wire it...
You won't, as far as I know be able to daisy chain them.  If both bcrs have the same preset, then they will send out the same messages, and the xt (in control surface) looks for the same messages, but interprets them differently.
So - depending on your midi interface, as it sounds like you are not using usb on the bcrs... 
You would need two separate midi input/output pairs.
1 pair for the first bcr and the second pair for the second bcr.

Am I making any sense to you.
You won't be able to run one thru the other, afaik, because the messages will be the same.  The daw needs to differentiate the messages, thereby needing input to daw control surface on different ports.  1 for mackie control universal and 1 for mackie control XT...

When you do that then you would have control over 16 tracks.




--- In bc2000@yahoogroups.com, "danberridge@..." <danieltberridge@...> wrote:

>
> 
> If anyone has had any luck chaining two BCR's together for MCE purely with midi cables and a separate midi interface, please give me a shout!
> 
> I'm one of these people who's had major problems with the USB driver. So I don't use it.
> 
> How's it done and how does it work in operation.
> 
> Any help appreciated.
> 
> Dan
>

Dan - I'll reply to each question.

--- In bc2000@yahoogroups.com, Dan Berridge <danieltberridge@...> wrote:
>
> Ok Great. So, will the two MCE and XT work in collaboration with each other?

Yes.

> 
> Essentially what I mean is that if I move through the banks on one machine,
> will it show up on the other? Will it move through 16 banks not 8 (yes I do
> use a lot of tracks)?


Yes. That was mackie's intention. for mackie + XT.


> If this is the case, am I to take it that the XT BCR will be the slave?

Yes - something like that. (not sure if I understand all of what it is doing under the surface tho)

> I can live without bank/transport controls, etc on one machine if those
> controls on the original bcr affect the XT BCR?

Yes - the "master", I'll stick to their terms - the mackie vs XT,
the mackie will have the daw controls and bank and pages and transports and flip - basically the XT is just mixer stuff (faders, vpots, mutes/solos/arms/ch select/ vpot select (not sure about vpot select way out there.)
 

> Will Plug-in controls work on the 2nd bcr? I guess thats not actually
> important, but it would be nice if it mapped out 16 plug-in v-pots in a row.

Yes - I think so, however, it has been along time since I messed with this.

> However, the main thing is to have as many track levels in front of me as
> possible.

I think you can even step this out XT1,XT2,XT3 if you really wanted, but don't quote me on that one...

> How will all this effect Huskervu and/or MidiYoke visual feedback?

Well - as I recall in my experiments, I just ran two instances of Huskervu - one picking feedback from mackie, one feedback from XT.

The nut of this is making sure your midi routing is sound.
I would try it without huskervu first.

Well for live you would only need feedback for knowing if you are fliped, or on sends or returns or plugins.
So just start simple. Get both bcrs working in pan mode, since you don't really need visual feedback for that.  Then expand and add in husker on mackie then when that is working add in husker on XT.

Remember - you will need separate midi inputs/outs into live.
Two different control surfaces. Mackie and XT

Here is a link about what I was doing. Ignore all the stuff about savihost and vst host, that was only for me in my case where I was using the tmd1000 as my controller.

It is not that informative but it will at least give you some images.
Also - I did not cover setup of Live in this website... I don't remember if I wrote it in the documentation for GenMceXT or not?
Nope it does not look like it did.

http://shoshin.110mb.com/genmce/genmceXT/GenMcext.htm

> 
> I'm working on Live 8 btw.
> 
> thanks for this,
> Dan
> 
> 
> On Sat, Jan 30, 2010 at 3:51 PM, - <k5kip_1999@...> wrote:
> 
> >
> >
> > Not that I have done this since I only have 1 bcr... however, I do have
> > some advice.
> > If you want to run mce on both -
> > I have done this with GenMce and genmceXT from other controllers(I do not
> > recommend that at this time and I wrote those programs, unless you don't
> > mind not having fader feedback)I digress...
> >
> > You will be using your bcrs to be 1st one like a mackie control universl,
> > the 2nd one will be mackie control XT.
> > Now you could use the same presets in both, but be aware that the second
> > bcr (mackie control XT) will only work with faders, vpots, mutes arms solos.
> > Bank keys, page keys as well as others will not function as they are already
> > set in the mackie control universal emulation...
> >
> > Ok - what is he talking about?
> >
> > In your software you will set up
> > 1 bcr input/output control surface as mackie control universal.
> > The second bcr input/output control surface will be mackie control XT.
> > (provided your software has both of those and allows more than one control
> > surface, what daw will you be using this setup with?)
> >
> > Now as for the question of how to physically wire it...
> > You won't, as far as I know be able to daisy chain them. If both bcrs have
> > the same preset, then they will send out the same messages, and the xt (in
> > control surface) looks for the same messages, but interprets them
> > differently.
> > So - depending on your midi interface, as it sounds like you are not using
> > usb on the bcrs...
> > You would need two separate midi input/output pairs.
> > 1 pair for the first bcr and the second pair for the second bcr.
> >
> > Am I making any sense to you.
> > You won't be able to run one thru the other, afaik, because the messages
> > will be the same. The daw needs to differentiate the messages, thereby
> > needing input to daw control surface on different ports. 1 for mackie
> > control universal and 1 for mackie control XT...
> >
> > When you do that then you would have control over 16 tracks.
> >
> >
> > --- In bc2000@yahoogroups.com <bc2000%40yahoogroups.com>, "danberridge@"
> > <danieltberridge@> wrote:
> > >
> > >
> > > If anyone has had any luck chaining two BCR's together for MCE purely
> > with midi cables and a separate midi interface, please give me a shout!
> > >
> > > I'm one of these people who's had major problems with the USB driver. So
> > I don't use it.
> > >
> > > How's it done and how does it work in operation.
> > >
> > > Any help appreciated.
> > >
> > > Dan
> > >
> >
> >  
> >
> 
> 
> 
> -- 
> www.broadwayproject.co.uk
> www.myspace.com/broadwayproject
> 
> Daniel Berridge
> 14 Bruce Avenue
> Bristol BS5 6EF
> UK
> 0044(0)7786371011
> 
> ---------------------------------------------
> 
> This email is confidential and intended solely for the use of the individual
> or organisation to whom it is addressed. If you are not the intended
> recipient of this email, you should not copy, modify, distribute or take any
> action in reliance on it. If you have received this email in error please
> notify the sender and delete this email from your system.
> This email and any attachments are also subject to copyright.
> No part of them may be reproduced, adapted or transmitted without the
> written permission of the copyright owner.
>