bump

Thanks rncmkg--

So to clarify, this is the same order as they're exposed via the envelopes dialog?

...for the sonitus EQ:

a) 1-4: gain || 5-8: frequency
b) 1-4: Q || 5-8: type
c) 1-4: band enable || 5-8: unused
d) 1-8: unused.

Thanks!

Yup, that's correct. (gosh, my very own little user group......!).

Parameters are in the order reported by the plugin. I am considering a new revision of the control surface which would potentially allow the order to be remapped but I've found in practice that accepting the mapping, as is, appears quite workable, particularly if you print off a scribble strip for the EQ assignments and put that on the BCR (as the other plugins generally aren't so confusing wrt parameters).

Plugins which expose > 24 parameters are mapped over multiple 'sub pages' accessed via the 'page' key, up to (from memory, I think), six or seven pages, which should be sufficient for most plugins except some of the really weird examples e.g Wusikstation mapped as an insert, (2000+ parameters!)

Coming soon (I hope). New version with meter bridge support. Am still struggling with the ergonomics of how this will work, exactly, but at least I have Sonar 6.2 now thanks to a killer deal at the Sounds Expo show earlier this year, so I can implement this......

This sounds very interesting, it seems that BCR2000 doesn't support Windows XP x64 though. Can someone please confirm this?
Otherwise, I'd buy this controller right away. Or maybe I should just ditch the 64-bit Windows.

.auski

Never mind...I programmed it manually per the .doc file in the release notes. Not too difficult.

Notes: the behringer BCedit program is picky about what version of the Java Runtime Environment it will work on. I needed to remove six prior versions of Java (no kiddin', taking a half gig of space, too, whoohoo!), and install an earlier version from Sun's website. Look at their archives for version 1.4.2, it works fine.

Summation:
After failing to get BCedit to work with newer Java software, I tried ACT. Next step: review zzounds' return policy and get rid of it. Not worth the grief.

But after finding the Java version that works (KVR forums), I programmed a preset on the BCR2k with the necessary CC and channel info, and was off to the races. Super cool.

I'm very satisfied (nay, stoked, dude! sorry, couldn't resist) with how this works with plugins. Parameters grouped in fours (or eights) maps very gracefully. Channel EQ, Cake's FX delay / chorus, and anything like a gate or compressor with under 24 parameters are logical. The only strangeness are some plug GUI elements do not update properly (I've seen this with every controller I've used, FWIW), and you have access to greyed out parameters.

AJ, the GUI is brilliant in its simplicity. Calling it from the control surface is even better. Much more natural than the BCview app for the BCF units.

Tip: while foot switches are not directly supported, programming them to the same values as the play and record buttons, you pick up play and punch ability from the ground, which I'd suspect is what most folks would want.

And not having the surface tied to an emulation like the BCFs means you can change modes to control something else (I'm aiming for TotalMix next), without needing to power down the unit, nor losing control over Sonar.

Thanks AJ!

Here's a pic of the surface in action with the per-channel EQ:

I just bought myself a BCR2000 at long last.


gonna try this plug

ORIGINAL: aj ...I do think that Cakewalk should step back from adding more and more features and now look at overall ergonomics. The key to this is better control surface integration.

Amen.

Kudos to you, aj, it's great to see people such as you doing great things and sharing.

I wish you owned a FW-1884...

F@KKER

How does one open the GUI for this?

I have followed all instructions to the letter but hitting key60 twice 9I assume this is the Shift key) on the BCR2000 does absolutely nothing.

It's OK I sorted it.

Don't forget to assign the I/O ports when adding the surface under options/control surface........I thought i'd done that but Sonar seemed to have forgotten.

Ah -- you're right, sorry! I could've sworn it was on the PC keyboard...

It's the shift key on the BCR2000. - ie the bottom right encoder group key and it works now that i've reminded sonar which midi port it's on!!

Thanks-

-Susan

Hi Twigman (responded separately to your install Qs)....

You should not need to uninstall it because if you leave it running it is only listening on MIDI channel 16 to the BCR (and that's why I used that channel). Therefore any other BCR preset that doesn't transmit on MIDI channel 16 will be completely ignored and can control other things. So you could switch to another BCR preset which you've set up for other purposes and the control surface plugin will just sit idly there and not do anything. When you switch back to the control surface preset on the BCR, all the knobs will suddenly synchronise with your current settings in the project.

Thanks!!!

I am trying out the BCR2000 with Project5 to see if how it will work. Everything appears to be good, except I am not seeing the Console. No virtual BCR, what am I doing wrong?

Hmmm....

This is likely not a software fault. It looks like the same problem that happened to me recently.

I'd noticed for a long time that the BCR wasn't altogether reliable about reconnecting under USB if I turned the power off, but although this was an annoyance a reboot cured the problem.

Then one day about 2 weeks ago, a reboot didn't cure it. Just like yours, the unit would receive but it didn't seem to transmit. I tested this by trying to record MIDI from the unit and nothing got recorded. At this point I knew it wasn't a software problem.(worth checking this in case your problem is different)

After a little while it became clear that the USB port on the BCR2000 had developed a fault. At first it would receive MIDI but not send it - just like your problem. Then it got slowly worse and after a day or so the unit simply no longer was recognised by either of my two computers.

At this point I tried everything - powering off all the kit, and back on, reinstalling the drivers, and so forth... but no, it would not come back. I even tried to reload the firmware but no luck.

Since the unit was long out of warranty I cursed quietly and then inspiration struck. All I needed was a cheap and reliable USB to MIDI interface - I like the Edirol UM-2's which are just over 20 quid - and connect the BCR via MIDI instead (configure it for mode S3).

This I have done and it is now dead reliable. You can turn it off and on and it is always available, because the USB interface remains on all the time. Of course, you do need two short MIDI cables as well.

This may not be your problem, of course, but it certainly got me back up and running. I'm wondering if there's a design weakness in this area with these units....

it does appear to be transmitting MIDI when I use other presets to control plugins.

It's just the aj control surface that seems not to respond.

Hi kwazi,

You need to 'ungroup' the bank switches so they aren't performing their normal function of switching around the encoder banks. Then they can be reprogrammed as regular switches. If they are still doing that - you can tell because the LED on each switch comes on when you press it, then when you press one of the other four, its LED comes on and the other switch LED turns off - then you still need to ungroup them. You can either send the SYSX file that is included in the download to do that - use Sonar's SySX transmit functionality to do that - or the BCEdit utility has an option to ungroup the bank switches. Unfortunately I can no longer run this on my system to check because my BCR2000 is now connected via MIDI after the USB port failed and the BCEdit utility seems unable to detect it.

Once you have the switches ungrouped, simply reprogram them as per the instructions (and save the BCR preset). Now they should work as expected. You can cross-check that all is well by putting a Sonar MIDI track into record mode with the BCR connected and recording MIDI events, then press all the buttons etc. and check the event list. This should confirm that you have it all set up correctly.

Note there is a minor misprint in the instructions. All controls should be programmed for MIDI channel 16. At one point the instructions are a little ambiguous because they refer to MIDI channel 1. This is due to finger trouble; ignore it.

And have faith. It does work, for lots of people. (I think well over 2,000 downloads now).