Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "morin_luc" <luc@...> wrote:
...
> How is the feedback feature implemented ? Is it simply a
> matter of sending CC messages to the BCR2000's MIDI port ?

Yes. If you send let say CC 90 to the BCR, the encoder
programmed to send a CC 90 will 'move' to the received value.

> Assuming that it's relatively easy to send such messages,
> how come there seems to be so little support for the BCR2000
> within the DAW world ?

Because they did not manage to cross-breed a electronician and
a programmer... ;) There is still two separate worlds:
hardware and software.

> My reasoning is that if the OPX-Pro is capable of "simply"
> dumping its parameters on Program Change, why don't others ?

Lazyness i suppose... :(

> And in the case where there's really no feedback support,
> for example in a DAW, how could one "hack" this ? Would it be
> possible to listen to Program Change messages and react to them
> by reading the VST synth parameters and send them back to the BCR?

Yes it is possible. But it is a long story...

If you config is : BCR -> Midiport A -> DAW

Install Midi Yoke to have 'virtual ports'. Then modidy you config
to: BCR -> Midiport A -> ? -> Virtualport B -> DAW

Replace the ? in the above config with a piece of programme.
This program would listen to 'program change' from the BCR.
Pass it to the DAW through the virtual port. Then it could
get patch data and send it back to the BCR in the form of
multiple control change messages.

You 'only' have to develop this program yet ;)