Hi Eugene
sounds like you are ready to jump in the deep end. 8)
> All I did so far was copy/paste your example command into the default
> script, replacing what was already there for encoder 49.
>
>
> $encoder 49 #Osc 1 Waveform - DW on channel 2
> .minmax 0 16
> .tx $F0 $42 $31 $03 $41 $02 val $F7
By the way I think parameter 2 is Osc1 level according to the manual not the Osc1 waveform - the parameter numbers do start at 0 unlike the MIDI channel (0 means MIDI channel 1)
The value can be 0 to 32 so
$rev R1
$encoder 49 #Osc 1 Volume - DW on channel 2
.showvalue on
.resolution 96 96 96 96
.minmax 0 32
.default 0
.tx $F0 $42 $31 $03 $41 $02 val $F7
$end
Copy and send this and try it out.
It doesn't change anything else on the BCR except encoder 49 (bottom left most one)
The leds around the encoder should light as you turn it and if you have the BCR set to any of the Solo modes you should see the MidiOut (A or B or both) light up
>
>
>
> I then pressed "send" at which point I see the midi in light on the
> bcr2000 light up for a couple seconds. I have midi-out of the
> bcr-2000 going into the midi-in on the DW-8000. Rotating encoder 49
> isn't changing OSC1 waveform.
>
> The Midi Channel is set to 2.
What mode is the BCR in? If you have just unpacked it, it will likely be in USB-1 mode. Good to download the script, but it won't output your data from turning the encoder to the Midi ports at the back.
What is your setup?
I'll assume that you using the BCR as your only MIDI interface .
(My PC has a MidiSport 4x4 connected as well as the BCR)
Do either of the MIDI Out (A or B) Leds light up on any of the other BCR patches.?
If not nothing is coming out of you BCR change to Solo-1 (S-1)
Hold down Edit, press Store. Now you are in global edit mode.
Turn the top left encoder (1) till the display shows "S-1".
Press Exit and the unit takes a few seconds to get itself together and you should be in business. In S-1 mode Midi comes out both the A and B ports
If you don't already have it, get a copy of MidiOx (it will let you look at what is going in and out of the MIDI ports.)
It's great, free and just about everyone uses it.
http://www.midiox.com/ Unfortunately there is no mode that sends the data (from the encoder) out the Midi ports and the USB port.
USB-3 will work if you use MidiOx
In this mode when you look at the Midi Devices option in the MIDIOx menu you will see BCR2000[01] in the output list as well as the input list. These are the in and out of the USB. There will also be BCR2000[01] OUT A and BCR2000[01] OUT B. Obviously the the 2 MIDI plugs on the back and finally BCR2000[01] IN A (the other plug on the back).
Connect from BCR2000[01] (the input) to BCR2000[01] OUT A
(Note that if you change the mode on the BCR you will have to close MidiOx and start it again. You are also likely to see a different number of interfaces in the list)
When you twist the encoder the data should be displayed on the PC and it will echo out the MIDI A port to the Korg
When you get the BCR patch(es) all sorted out, change the BCR to the S-1 mode and you can work the Korg without the PC.
.tx $F0 $42 $31 $03 $41 $02 val $F7 should give you a stream of sysex messages like....
SYSEX: F0 42 31 03 41 02 00 F7
SYSEX: F0 42 31 03 41 02 01 F7
SYSEX: F0 42 31 03 41 02 02 F7
SYSEX: F0 42 31 03 41 02 03 F7
SYSEX: F0 42 31 03 41 02 04 F7
SYSEX: F0 42 31 03 41 02 05 F7
with the MIDI port details between each line
(MidiOX iusually displays in Hex but without the "$")
>
> I still don't really understand that sysex string.... but I just
> noticed that you uploaded a DW-6000 patch. I'm going to try and study
> that to see what I can figure out. Thanks
If you send rubbish to the BCR it just ignores it and flashes 'Err" so just hack away, you'll get it.
Royce
