> Another (probably slightly better) workaround would be to set >AddressLength to 3 and put the RM50's two parameter address bytes ? >("Parameter 1" and "Parameter 2") at the front of the "Data"/"value" >group; this wouldn't force you to use multiple files.
I tried that, but when I put values over 09 there, it gave me an error message.
> It may be easiest to send the high parameter byte as a fixed value (representing fixed choices for all that's in this parameter); of course this would only give the user a choice of 128 values (as defined by the low byte), but at least that's something.
> So the definition in the BC Manager ini file would then look like:
> <5-byte address> | 00 - 7F | <high byte: fixed value> val0.6 ;<description>
> (Actually you could use "val" instead of "val0.6", since these are equivalent.)
OK, so the way to go is basically to set up different knobs for each high-val (which in this case is specifying the voice bank -- and low-val specifies the voice number), since the last-used knob will just overwrite the previous one (i. e. jump to a different bank. Since I am actually just interested in the user bank anyway, this is not a problem. The RM50 is set up kind of strangely in that different banks have different numbers of voices in them -- some 27, some 60, etc.Message
Re: SysEx String Programming / Syntax Help for BCR2000
2013-08-21 by evanlong@ymail.com
Attachments
- No local attachments were found for this message.