BCR2000 querie
Hi list,
I'm interested to know if anyone has been able to achieve parameter feedback from max to the BCR2000, or if it is at all possible. So far i've only been able to parse data from the device, however not back to the device. Reasons for this is that I'd like to have a variety of stored settings within max (rather than the bcr), such that when the playback environment changes, the rotaries on the bcr2000 reflects this. I've been able to achieve this with the motormix device, but not the bcr.
any advice welcome,
cheers
jdh
Quote: jdh wrote on Wed, 29 August 2007 13:05
----------------------------------------------------
> I'm interested to know if anyone has been able to achieve
> parameter feedback from max to the BCR2000
Sure. Send the same data as the encoder or button is sending.
But note that the BCR (and BCF?) has a hardware feedback "dead time" - if a control is being moved, feedback will not be accepted for that control until X milliseconds after it stops moving.
I believe the default is 100ms or 200ms, which is quite high. You can change this in the (undocumented) global parameter edit - hold EDIT, press STORE (the display will show "EG"), turn encoder 7.
Also note that the unit still insists on updating its own LEDs and encoder rings in hardware, so in addition to the above, you may need to delay your feedback so it goes to the unit after the hardware has updated internally.
Sigh. Cheap unit, stupid implementation, bad documentation.
just sed back midi datas to bcr by midiout.
it' works for me.
>
> I'm interested to know if anyone has been able to achieve parameter
> feedback from max to the BCR2000
great thanks for the info John, the 'deadtime' may be the reason why its not updating.
cheers
jdh
Baaaaaahhumbug. I canna giet this bcr to update from max. I guess I'm expecting to see the leds shift as the parameter changes in max. Unfortunately I thought this would be a rather simple implementation... but no! Am I missing something? Thwated by the daft bcr.
cheers
jdh
Your problem is that you're sending $1 81 1, which is correct for a ctlout object, to midiout, which needs the raw MIDI hex bytes - 176 81 $1.
ahhh ok its expecting hex, thanks again John, much appreciated.
bests
jdh