Bc2000 (for the BCF2000 & BCR2000)

Hi all,

I'm working on a SY77 implementation file and got stuck. Apparently
there are three parameters packed into a single byte: 3 - 1 - 1. I
know it's not a problem to use only specific bits of "val", but what
bothers me is that all the others bits would be zeroed - or fixed in a
different way - since I cannot emit part of the byte. As far as I can
understand it's not possible to compose a value of say, a knob and two
buttons, am I right?

Thanks,

Bruno

Hi Bruno
there is currently no way to access the values of other controls and add them to a button or encoder value.

I have the same problem with my Korg DW6000 layout.

You need to have a PC or Mac with a program that will convert, say, CC messages into sysex strings.

You need to write the program yourself or perhaps Bome's classic midi converter will do what you want.

All the best
Royce


--- In bc2000@yahoogroups.com, Bruno <brunorc@...> wrote:

>
> Hi all,
> 
> I'm working on a SY77 implementation file and got stuck. Apparently
> there are three parameters packed into a single byte: 3 - 1 - 1. I
> know it's not a problem to use only specific bits of "val", but what
> bothers me is that all the others bits would be zeroed - or fixed in a
> different way - since I cannot emit part of the byte. As far as I can
> understand it's not possible to compose a value of say, a knob and two
> buttons, am I right?
> 
> Thanks,
> 
> Bruno
>

Hi Royce,

thanks for a quick reaction.

2012/8/8 Royce <rpcfender@...>:
> Hi Bruno
> there is currently no way to access the values of other controls and add them to a button or encoder value.

That would simplify things a lot. One operator eats 12 knobs for EG
only, which means I can only squeeze three operators per preset. In
one AFM Element (layer) there are six operators, so I would need at
least two presets per AFM Element... with a button specifying which
operator/element I'm working on I could probably fit everything in one
preset.

But this is still OK with me.

> You need to have a PC or Mac with a program that will convert, say, CC messages into sysex strings.

Yes, but this in turn defeats the idea of having a hardware
controller. What I found is the SY behaviour - which at the first
glance was annoying for me - of always showing the menu page where the
modified parameter can be edited, can be the key to facilitate the
workflow. It's enough to put the more important params under knobs,
and access the rest from the menu.

Thanks,

Bruno

Hi Bruno

I would add to what Royce said in that if, like me, you also like to have stand alone (ie no obvious computer in the loop) then you could go down the microprocessor route.

For example, the Miniak I love needs "-ve" NRPNs.
So I made up the hardware/software to convert a bias and hence allow BCR to act in +8192 mode, with transforms to/from the BCR done by a Arduino and a few 5 pin dins/opto isolators/not chips/220ohm resistors/diodes.

The nice thing about Arduino is it is relatively trivial to do.
PIC would be cheaper, but given Arduino is meant to be used by artists to bring their sculpture to life it is easy.

I am glad I took the plunge (well used to program MIDI via Atari STFM so showing my age) with the microprocessor.

It has allowed me to add so many extra features to my controller / BCR combo

1 - NRPN transform
2 - Keyboard zoning (I chose up to 8, independent transpose, layer or split or both, channel assignment)
3 - Arpeggiator unit (just working on the timing now)
4 - I am adding in midi sync (both slave and master)
5 - midi merge
6 - LCD display of Miniak parameters (persistent unlike Miniak!)

Makes a perfect combo.
The sorts of thing you are asking could be done relatively easily. Use Mark/Royce's excellent BCR internals to get 90% of the way there, and a midi transform engine to get the final 10%.

Regards

Steve H

--- In bc2000@yahoogroups.com, Bruno <brunorc@...> wrote:

>
> Hi Royce,
> 
> thanks for a quick reaction.
> 
> 2012/8/8 Royce <rpcfender@...>:
> > Hi Bruno
> > there is currently no way to access the values of other controls and add them to a button or encoder value.
> 
> That would simplify things a lot. One operator eats 12 knobs for EG
> only, which means I can only squeeze three operators per preset. In
> one AFM Element (layer) there are six operators, so I would need at
> least two presets per AFM Element... with a button specifying which
> operator/element I'm working on I could probably fit everything in one
> preset.
> 
> But this is still OK with me.
> 
> > You need to have a PC or Mac with a program that will convert, say, CC messages into sysex strings.
> 
> Yes, but this in turn defeats the idea of having a hardware
> controller. What I found is the SY behaviour - which at the first
> glance was annoying for me - of always showing the menu page where the
> modified parameter can be edited, can be the key to facilitate the
> workflow. It's enough to put the more important params under knobs,
> and access the rest from the menu.
> 
> Thanks,
> 
> Bruno
>