Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

Re: [bc2000] Korg Prophecy and new progress

2013-03-02 by Jason Hosier

well, ok. I may have jumped the gun a bit. I just found bc manager so theres that. I keep you updated on my progress. thanks.




________________________________
 From: Jason Hosier <h.jason3@...>
To: "bc2000@yahoogroups.com" <bc2000@yahoogroups.com> 
Sent: Saturday, March 2, 2013 1:38 PM
Subject: Re: [bc2000] Korg Prophecy and new progress
 

  
hi y'all , Im going to run down a list of methods ive used to attempt to link up the bcontrol to the prophecy without a computer interface. I havent got it working yet and i figure if we work together we can fill the knowledge gap.

my first experiment involved looking up the control change numbers in the midi spec chapter which resulted in the realization that the CC numbers Go Way above 127. Ok. After some digging i found what i discoverd to be relevant CC numbers in the same chart. which were few and far between. Tried to program these by simply 1)inputting CC in edit 2)hitting learn 3)tweaking a knob and pressing a key at the same time. The result was that the BCR recorded the key hit information but not the program tweak. For example, i tried to change the cutoff and press a key in learn mode at the same time. the
 cut-off information  did not translate but the key hit did. so when i turned a pot i got weird glitchy arp crap and not in a good way. turning on the arp was a bad idea too. had to restart the machine to stop it. Ok. dead end.

experiment number two. I attempted to program basic functions such as volume pitch wheel and mod function so on. i did this by hitting learn and just manually moving knobs and wheels without inputting any CC information which i tried to keep at zero for everything. It actually kinda worked. Step two in this process involved learning the BCR to the 5 parameter knobs under the prophecy display. I seemed to be making progress but soon discovered the BCR was translating my request through the same CC (according to my observations). so if i tweaked the filter in the parameter knobs on the BCR the clock would get confused and think i was tweaking the pitch wheel. This also had the affect of linking up the lcd lights on all
 the BCR buttons i edited. Im sure we have all made this mistake by now. ok. dead end.

experiment three simply involved digging a bit deeper into the proph manual to find CC numbers in the midi section i somehow missed before. which leads me to basically where i am now. If i attempt to learn the CC numbers in the book with the BCR by manually turning the parameter buttons but not hitting a key the red midi light on the BCR doesnt even come up. which would lead me to believe the BCR isnt even recieving midi information from anything thats not a key hit. that is unless your manually programming the pitch or mod wheel to it. dead end.

I read davids previous entry on BC manager and my question is, is BC manager a generic name for any software program that works? or is there a specific BC manager software im not privy to? I got my bcontrol off ebay so if software came with it i didnt get it.

outline for experiment four. I finally gave up
 trying to program the korg prophecy with the Bcontrol without the aid of a computer. I downloaded midi OX and the BCR version 1.10 which is supposed to be somehow helpful. I read your entry about using non registered program numbers and will admit that im lost when it comes to deciphering that information. do i need a prophecy editor/ librarian? Ive looked around and cant seem to find one on the net. In the mean time ive found that the BCR works just fine with reason so until more information on programming the korg prophecy becomes available ill just be tinkering around with my VS. 

Anybody that wants to discuss how this works, i appreciate your input. Thanks.









________________________________
 From: Hobson David <enarke01@...>
To: bc2000@yahoogroups.com 
Sent: Thursday, February 28, 2013 11:12 PM
Subject: [bc2000] Korg Prophecy and new progress
 

  
Hello,
I have , after an all day study, figured out how to use the BC Manager Program to program my Korg Prophecy parameters (important parameters) into the BCR2000. You see, the Prophecy is one expansive little synth..It has well over 600 midi parameters, and that is where my problems began. I could not figure out what to do with, lets say, the filter parameters which range from about 271 to 295. Royce offered me some code for the cutoff parameter (thank you Royce) but that did little to help me learn what to do with those "over 127 midi parameters", so I had to do what I was advised to do and carefully learn the BC Manager program...That, with alot of googling led me to understand that those parameters above 127 were "Non-Registered Parameter Numbers"...i.e. NRPNs. So, with that bit of info all I did was to learn each knob on the BCR2000 by adjusting the important parameters in the Korg Prophecy and then to switch to usb mode and upload all of that info into
 BC Manager. From there I opened rotary encoders edit window and began changing the types of parameters to nrpns and adjust their parameter values accordingly...that and some knob value changes changed the lines of auto-created sysex codes and all of the knobs I programmed were dumped back to the BCR2000...and it all works. Of course, not all of the midi parameters will be nprn, some will remain cc, but when I am done I will upload to this site a new file for the programming of the Korg Prophecy.
However, the BCR2000 does not play well with the arpeggiator...it messes up the octave scaling...but that is ok for now, I do not mind programming my sounds without a 2 octave arp.
So thanks again Royce,
And a big thanks, and contribution coming to Mark.
Regards,
David

P.S. My MOSS Board in my Triton Extreme is next and then my Rhodes Chroma!

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.