Bc2000 (for the BCF2000 & BCR2000)

This console, for midi remote, needs to be prepared via a file called MIDIMAP.TXT . In this file , most midi parameters ( notes & controllers) are defined by strings like:
fader_val = controller:65
go:9 = note:28
...etc...
in format: <operation type>:<index> = <message type>:<value>

The problem is that the <index>, for the faders, isn't always known 
"Dmx faders uses fader:33  to fader:56 , for expansion wing, fader:57 to fader:90".

A bit complicated for me :-)

G.


--- In bc2000@yahoogroups.com, sghookings@... wrote:
>
> http://forums.highend.com/archive/index.php/t-4600.html
> 
> and
> 
> MitchOctober 30th, 2007, 03:56 PM
> The midi implementation for the Wholehog2 was primarily designed for slaving
> two consoles together rather than controlling the system with an outboard
> midi controller, though for simple button pushes it is quite adequate. It
> is a little more complex for fader events though.
> 
> For these the console sends a "fader_val" message (controller) to describe
> what value from 0-255 the fader should have and then a "fader" message
> (note) to describe which fader that value should be assigned to. It does
> this for every increment of the fader.
> 
> The best way to see this is to connect two consoles together, enable "midi
> in" on one and "notes out" on the other. Then enable the "event monitor" on
> the first console so you can see the actual messages (though I appreciate
> that not everyone has two consoles!).
> 
> 
> 
> 
> If I were to move fader 1 up from 0 to 7 I would see the following messages:
> 
> B04000 (Fader value 1)
> 900A00 (Fader 1)
> B04001 (Fader value 2)
> 900A00 (Fader 1)
> B04001 (Fader value 3)
> 900A00 (Fader 1)
> B04002 (Fader value 4)
> 900A00 (Fader 1)
> B04002 (Fader value 5)
> 900A00 (Fader 1)
> B04003 (Fader value 6)
> 900A00 (Fader 1)
> B04003 (Fader value 7)
> 900A00 (Fader 1)
> 
> As you can see the Hog 2 outputs the same message for pairs of values so 255
> actually corresponds to a fader_val controller message of 127.
> 
> Or to put it another way the fader_val controller message of B04000 is sent
> for both 0 and 1 and B04001 is sent for both 2 and 3.
> 
> 
> BUT even this info looks suspect?
> There doesnt seem to be any state change and yet apparently one is controlling different fades.
> 
> Try to monitor the output via MIDI OX and see if you can emulate what it does?
> 
> --- In bc2000@yahoogroups.com, "greg_zeubest" <zeubest@> wrote:
> >
> > Thank you very much for your help.
> > 
> > Tks to you, I'v understood how to add this velocity parameter. It's not working, but I think there's parameters I don't have for this console... the correct velocity reference to all faders is unknown... even in the manual.
> > 
> > So, i'll continue to search for it.
> > Tks again.
> > 
> > G.
> > 
> >  
> > --- In bc2000@yahoogroups.com, "Royce" <rpcfender@> wrote:
> > >
> > > Hi
> > > I'm a bit lost on the messages you want to send.
> > > 
> > > Do you need to select the fader with a Note on message with the velocity being the fader number then send a CC64 message on channel 1? 
> > > 
> > > Fader 3 set to 100
> > > $90 xx 3       ;xx is the global note number
> > > $B0 64 100 
> > > 
> > > Assuming this is correct, to send multiple messages like this you should use something like the following...
> > > 
> > > encoder 33 is for fader 1 ie velocity =1(?) or should it be 0 
> > > global note = 60 
> > > 
> > >  $encoder 33
> > >  .showvalue on
> > >  .mode 1dot
> > >  .minmax 0 127
> > >  .resolution 96 96 96 96
> > >  .tx $90 60 01
> > >  .tx $B0 64 val
> > > 
> > > You can use my editor in the files section or Mark's editor from his web site to convert this text file (we use the *.bc2 file extension) to sysex and send it to the BC.
> > > 
> > > 
> > > All the best
> > > Royce
> > > 
> > > --- In bc2000@yahoogroups.com, "greg_zeubest" <greg_zeubest@> wrote:
> > > >
> > > > Hi, :)
> > > > 
> > > > I'm trying to use a bcr to control a wholehog2 console. I used the "learn" function, and it seems ok for the buttons, but I can't use it for faders.
> > > > I can make a fader work, but they are all working together, as there's a missing parameter : velocity.
> > > > For this console, we can set faders only to one global note, CC will change the value of the fader, and velocity will choose a specific fader.
> > > > I've been searching on the net, but bcedit.jar doesn't seem to handle velocity, and perhaps BC manager can do it, but i don't know how, and I haven't found in the manual.
> > > > 
> > > > I Wonder if it's possible to modify a text version of the sysex to add it ?
> > > > 
> > > > $encoder 33
> > > > .easypar CC 1 64 0 127 absolute
> > > > .showvalue on
> > > > .mode 1dot
> > > > 
> > > > So, can you please help ? 
> > > > 
> > > > Thank you.
> > > >
> > >
> >
>