> You COULD define a range of 0-127 here, but that would of course include many undesired values too; how bad that is, depends in part on how the RM50 reacts to these invalid values.
>
> However, if this is actually a FIVE-bit 2's complement notation (unlikely, since the manual says "7-bit"; but you never know), 0-31 WOULD work: e.g. -1 would then be represented as 11111 (decimal 31, hex $1F). You'd have to try this out.
I'll definitely try 0-127, possibly both.
5) Looks like I don't have this one after all. When there's a split high val/low val variable with an odd-numbered range, how do you break up the high and low ranges? Example, with range being 211 ("Tempo" parameter in the "System" group):
High Value:
high 1 bit
Low Value
low 6-0 bit (0-210)
I know on the 0-255 split variable, it was "00 00 - 01 7F" so that the first range effectively multiplied the second (2 x 128 = 256), but of course an odd number doesn't divide by two evenly.
At first, I thought I was interpreting it incorrectly, and that 0-210 should just be the range for the low variable. Then I realized that the maximum range for any one-byte variable is 00-7F. This also brings me to my next question:
7) What is the best way to set this one up, voice element wave selection:
High Value
bit 6-5 mem
00 = preset
01 = wave card
10 = internal
bit 4-3 card num
00 = 1, 01 = 1, 10 = 2
bit 0 num high
Low Value
bit 7-0 num low 7bit
What I want to do is only use preset waves (internal and wave card waves are very rare, since they require the installation of optional ROM cards or sample-loading RAM), so bit 6-5 should be 00. The other problem is that the range on the wave number is 1-133, just a few too many to fit into a byte, and of course, some of the most appealing waves (pulse, saw, and triangle) are in the 129-133 range.
At first, I was thinking, since I want to use only preset waves, I could just set the hi-val to 00, and then I realized that it's more complicated than that because it's actually specifying bits there, not hi val values directly.
Aside from these questions, the definition is pretty much done; that's the good news. The bad news is, if wave selection is impossible on the BCR2000 due to the 1-133 range, there is basically no point to the project from my current point of view, since I was intending to use this to set up the BCR primarily as a voice editor.Message
Re: SysEx String Programming / Syntax Help for BCR2000
2013-08-25 by evanlong@ymail.com
Attachments
- No local attachments were found for this message.