Quote:
Originally Posted by MalcolmG
Thanks. Didn't realise there was a sysex to go with it. If nothing else, figuring out the changes to get mine working was educational.
|
Sorry about that. The BCF2000 CSI was a spin-off from the BCR2000 CSI I put together previously and it was the BCR download page that had all the support info.
I'll update the page when I get a chance or combine it with the BCR page.
Quote:
So if I get it correctly, state is always managed by the DAW. Where I was getting into issues was I also had state managed in the controller.
|
Yes, the LED state is always managed by the DAW, But here's what confuses me about the BCR (and probably also the BCF, I don't have one to try).
When I created the BCR settings, I started by trying to get the encoders to work in a 'relative' mode (ie increment/decrement) because this is what I was familiar with on the Mackie C4 and because I couldn't see how the feedback from the DAW was going to work when the LEDs were controlled by the BCR itself. I got nowhere.
So I figured I'd give 'Absolute' a try, not really expecting it to work. It worked like a charm and I still don't really understand why
Without Reaper running, the BCR does indeed control the LEDs on the surface (unlike the C4, where nothing happens if you turn a control) When you launch Reaper (with the appropriate CSI files installed) the controls map properly according to the .mst and the feedback works to control the surface LEDs.
Somehow the BCR knows to not use its local connection and only update the status with what it receives from the DAW.