BCR controlling Soundcraft Qu mixer

5 posts / 0 new
Last post
nottooloud
nottooloud's picture
BCR controlling Soundcraft Qu mixer

I'm trying to control channel sends on my Soundcraft Qu mixer.

It speaks NRPN, but it needs a fixed number in the Data LSB.

For instance, sending Channel 1 to Mix 1 on MIDI channel 1 would need B0 63 20, B0 62 20, B0 06 nn, B0 26 00.

63 20 specifies Channel 1, 62 20 specifies that it's a send, 06 nn is the value of the send, and 26 00 specifies Mix 1.

 

Assuming I have understood all that correctly, which is not at all certain, am I also correct in thinking that my BCR can't do that?

 

Also a minor note for the doc, I'd have saved a bunch of time if it mentioned in FAQ 31 that BCM's MIDI Thru doesn't exist on Macs.

Mark van den Berg
Mark van den Berg's picture

am I also correct in thinking that my BCR can't do that?

Unless I'm missing something (which is very possible, since I don't have access to my BCR at the moment), there are three ways your BCR can do that:

  1. A "standard output" definition ('.easypar' in BCL) with Type = NRPN and Mode = absolute/14. (Cf. section 16.4 of BC MIDI Implementation.pdf.) The trick is to set the Value1 and Value2 parameters and the encoder's resolution(s) (cf. section 17.3) to multiples of 128, so that the DataLSB byte is always 0.
  2. A "custom output" definition. To use your example:.tx  $B0 $63 $20 $B0 $62 $20 $B0 $06 val $B0 $26 $00. (Cf. BCMI section 14.6.1.) In this case you can simply set Value 1 and 2 on BC Manager's "Custom output" tab (cf. '.minmax' in BCL, BCMI section 14.5) to the Data MSB's range. However, there's one drawback to this (which may or may not pertain to your situation): the encoder won't respond to incoming MIDI messages (cf. BCMI section 14.6).
  3. A hybrid standard + custom output definition: the standard output definition has Type = NRPN and Mode = absolute (i.e. 7 bits!), the custom output definition is .tx $B0 $26 $00. So you trick the BCR into thinking it's dealing with a 7-bit NRPN, and the custom output definition adds the fixed Data LSB message.

Also a minor note for the doc, I'd have saved a bunch of time if it mentioned in FAQ 31 that BCM's MIDI Thru doesn't exist on Macs.

Thanks for pointing this out!
Nearly(?) all items in the FAQ section were created when the Mac edition of BC Manager was only a distant dream, so that's why some of these items don't take care of the Mac perspective.
Actually the answer to question 31 does start by mentioning Windows, but I've now added an extra mention that the proposed setup can only be made on Windows. This will be included in the next version of the manual, though of course that's no consolation to you...

Mark.

nottooloud
nottooloud's picture

Ohhh, #3 looks like it could work. 

re the docs, more than consolation. I well understand the nuisance of maintaining docs, so it makes me happy when someone makes the effort.

nottooloud
nottooloud's picture

#3 totally works.

Edit in mode U2. Operate in mode S3, using MIDI output B to avoid the MIDI feedback loop.

Thank you, sir.

nottooloud
nottooloud's picture

Whoops, no, there's a hitch. While the mixer understands that the different custom output means a different bus, the BCR doesn't know that coming back. So while the BCR correctly sends one channel to one bus, it's knobs show that channel going to all the buses. Time to bust out Bomes. That's OK. I figured I'd have to do that anyway. And I understand a lot more about the system now.