Bc2000 (for the BCF2000 & BCR2000)

Hey, 

Well finaly i got it working sort of. I've tried the CC 08 but it didn't do what i hoped it would do. I've then looked at the sysex output of both midiquest and the bitcontrol vst again and noticed that they both changed the program to either #74 or #00(bitcontrol). After reading the manual it became clear that after a full program dump you have to switch programs back and forth before you can actually use your program. I found out i could load programs into the Bitcontrol vst, so i've searched the web for the sysex presets of the Crumar bit01 and found them, uploaded them into this VST and noticed the output still changed the program to #00 after each change, this is enough i guess to make the changes work. At the end you keep working on program #1 and change programs on the vst, this uploads the changes to program #1 and does a program change to program #1 at the end of the sysex... nifty. 

Next step would be to program the bcr when i isolated all the parameters i guess. I'm re-routing the midi-output trough midi-ox to my bcr-out at the moment, so i get an easy view of the sysex output, but its still going to be some work. 

L

--- In bc2000@yahoogroups.com, "Royce" <rpcfender@...> wrote:
>
> Hi
> 
> > I guess your right. Its strange though that Midiquest and Sounddiver do support the 01 but don't include the sound patches so the info seems always incorrect. 
> > 
> As I don't have a Bit01 it is really hard to say with certainty. Perhaps there is a way.
> In the document the command byte CC goes from 07 for the dump to 09 to request the dump and it looks like the 09 stuff was hand typed, not part of the type set page.
> Perhaps this is an undocumented code found by a user and so perhaps there are others.
> I would try 08 and then the parameter number from the list then some data bytes. 
> It doesn't look like you have to worry about a checksum byte as there are on other synths.
> 
> Both Mark and I spent many hours independently trying to work out the BC this way and we found a raft of non-documented features.
> 
> 
> > there is a Bitcontrol vst out there, which of course aint working for me but i know its working for people. There is even a explicit bit01 settings to choose from. So this tool could somehow edit the parameter and is somehow smart enough to send the sysex out to the Bit01. If i could somehow output the sysex string going out from the Bitcontrol vst i might get a better view of what its doing. I also tried the learn function on the bcr and output the vst to the bcr but its not working, grrrrr. 
> 
> You are well past doing stuff with the learn function on the BC.
> You need to look at Mark's BCL document as well as his editor from his web site and perhaps have a look at SecretBC.pdf in the files section here.
> 
> > 
> > Most of the patches can be found on the net, maybe i can integrate them into midiquest so it does know the rest of the sysex parameters hmm
> 
> Keep hacking. It sounds like there should be a way.
> Once you sort out the sysex messages feel free to ask questions on how the BC can output sysex (which can be over 120 bytes long)
> 
> All the best
> Royce
> > 
> > --- In bc2000@yahoogroups.com, "Royce" <rpcfender@> wrote:
> > >
> > > Hi
> > > >
> > > > Well i could use Sounddiver or Midiquest but the problem is, these
> > > tools are so old and buggy that its not working for me. It crashes or
> > > hangs up, or even fucked up some of the synth programs. So using these
> > > tools is not an option. I did look at the output from Midiquest and for
> > > Cutoff its sending this:
> > > >
> > > > 01312.577 (+005.679) C1 00
> > > > 01312.577  C1 4A
> > > > 01312.577  F0 25 11 07 4A 00 00 00 00 00 00 00 00 00 00 00
> > > > 01312.577  00 00 00 0C 0F 00 00 00 00 00 00 00 00 00 00 00
> > > > 01312.577  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 01312.577  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > > > 01312.577  00 00 00 00 00 00 00 00 00 0F 0F 00 00 0C 0A F7
> > > > 01312.577  C1 4A
> > > 
> > > I find Midi Quest buggy too.
> > > 
> > > I gather the Bit01 (not Bit1) is the same as the Bit99.
> > > From the manual found http://www.vintagesynth.com/misc/bit99.php
> > > <http://www.vintagesynth.com/misc/bit99.php>
> > > Sysex Bit01  message has the format
> > > 
> > > F0 25 1c CC DD DD... F7
> > > 
> > > c= channel (I assume it is 0 to F)
> > > CC is command - 07 is bulk dump
> > > DD is the data
> > > 
> > > If you have all the 00s in the data, as above, you will change the all
> > > the other parameters so MidiQuest is wrong.
> > > Perhaps as you build up a patch it will keep your earlier changes to
> > > fill in the details.
> > > 
> > > The only thing I can think of is writing a program that has a default
> > > patch (or can select from all the patches).
> > > When it receives a CC message from the BC it places the value in the
> > > correct slot based on the CC channel and controller number and then
> > > outputs the sysex.
> > > 
> > > An extension to the program would be to create a library and select the
> > > patch from a list.
> > > 
> > > Not having the ability to output a patch on the Bit01is a pain. The Bit
> > > 99 can do it.
> > > But you could save your newly created patch into the library as the
> > > program would know the data.
> > > 
> > > Best of luck
> > > Royce
> > >
> >
>