Thanks to Roland's own XV-5080 editor I can figure out what exact string to send to the module to control a particular parameter.įor example, Tone 1 Filter Cutoff is: F0 41 10 00 10 12 1F 00 20 49 F7 But it's quite limited in that you can only send a set of fixed hex values, when the actual parameter value in encoded in one 2-letter hex word (0x00 to 0x7F for 128 data increments). So I was trying to have my access virus TI2 to control the XV5080 because it has a mode where you can configure the knobs to send Sysex strings. Hope this can I ask you how you set up your BRC to send appropriate sysex strings? The big thing with sysex is you can get to everything. (Not always useful)Īlso true, but the XV responds as fast for sysex as CC to some parameters.Īll the 'destinations' in the Matrix seem to be some of these types of parameters.
The synth also responds to certain CC messages even when not programmed in the Matrix - Mod Wheel(CC1)Breath (CC2) Portamento, Volume, Pan, Expression, Sustain, Sostenuto, Reverb and Chorus send, Resonance(CC71), Cutoff(74), Envelope settings and others Check out page 173, 174 in the XV manual.ī) the sysex in the Roland synths allows you to change multiple parameters in a single sysex and so you don't have to repeat the start and end of the sysex. This is true but there are a few things you can do about it.Ī) the XV has a Modulation matrix that you can program to map a CC message to a parameter (eg Filter freq) and so you could use CC messages for those sort of parameters. You can program it so when you turn it quickly it will jump over the in between values while still allowing you fine control by putting out every value if you turn it slowly.Ģ) Sysex is a bigger message and will therefore take longer. The encoders are the main problem and there is another solution for the quick turn.Įach encoder can be programed to have 4 settings for 4 different rotational speeds. When the timer has reached the wait duration it puts out the last message. If another message arrives from that knob or switch before the time is up, the BC just drops the earlier message and resets its timer to 0. You can program the BC to thin the number of messages with a time delay so that it waits a certain time (in milliseconds) before it outputs Midi.Įach controller seems to have it own timer, but the duration is set as a global setting.Įvery time a new message from an encoder (knob) or button (switch) arrives to be sent, the BC sets the timer for that knob or switch to 0 and waits. This usually occurs when you turn the control quickly and you get a sysex message for the in between values.
The XV buffer can fill and miss midi messages including note on or off. I guess there are two issues with apparent responsiveness.ġ) too many sysex messages in a short time. Perhaps there is already one you can grab for your synth.
There is also a Yahoo group and both sites have presets. It's called, dramatically, "SecretBC.pdf" and is on my website. Perhaps you might like to read my (now somewhat old) little doc for some idea. Strangely Behringer has not acknowledged all the extra stuff it can do. Which is a lot and is much more than you can edit through the front panel of the BC. It's called "BC Manager" and allows you to get to every aspect of the BC. There is an editor (don't even bother downloading Behringer's piece of rubbish) and detailed documentation at Mark's website It can do just about every thing (including sysex with checksums that many Roland synths need) and it really only has 2 limitations for old synths, but neither of them should affect you. Some have complained about how robust it is, but can only say that mine work everyday, all day and I have had very little trouble. I am yet to find anything that can do as much. I have been using the BCR and (the BCF) for many years and it is a testament to the machine usefulness that it is still being made and sold and that I am still using them.