Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

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

Thread

Make BCR2000 into a Kiwi Patch Editor -- Common / Default parameters across multiple synths / presets

Make BCR2000 into a Kiwi Patch Editor -- Common / Default parameters across multiple synths / presets

2014-03-29 by <djo3yk@...>

Has anyone attempted to come up with a common/standardized default parameter layout to map the most commonly used parameters to the same encoder/button destinations across multiple presets? I'm looking to turn my BCR2000 into a Kiwi Patch Editor so that it the same encoder will control the same parameter as you switch from preset to preset to control synthesizer to synthesizer. I know this will have to be done on a preset by preset basis, but has anyone already laid the groundwork to determine the most common parameter locations or have already done this on some presets? It seems like the Kiwi PE just took the layout of the PG-800 and disables any parameters that aren't available for a given synth/preset.

If this is too much of a hassle then I'll probably go the Kiwi PE route but I think this would be really cool because I could get parameter value feedback as you change patches (unlike the PE which only lights up which parameters are editable -- not the values themselves -- from my understanding). I was then thinking of adding images under the encoders for all parameters that don't go up to full scale to denote multiple states (much like the PG-800 oscillator waveforms, Chorus Modes, etc.). My goal would be so that you can edit pretty much any synth without having to look at the synth/module itself for most of the common parameters and you could tell what state its in simply by the button and encoder LEDs and the LED digit/character display would be used for finer control/resolution.

Re: Make BCR2000 into a Kiwi Patch Editor -- Common / Default parameters across multiple synths / presets

2014-03-29 by <rpcfender@...>

As there are no standards in either CC control of VSTs or hardware synths it would be a bit hard to create a standard for a controller.
It would be great if they just all called the setup of patches a Performance or the components of a patch (or Preset if you prefer) tones not voices.

Although it works OK for a car to have standard controls or a violin or a piano, different synths work differently.
How do you set up a standard that will be OK for a Jupiter8 and a DX7?

In my attempts to close couple the BCR2000 and hardware synths, www.bwalk.com.au, the control layouts were a significant amount of work, but I feel sure that many who have tried my programs for the TQ5 or the DW6000 could feel the layout is rubbish.

So there is difference in synths, difference in personal style and difference in what you want to acheive in performance. I think people think I am joking when I say the hardest part of programming the BC is working out the layout.

Because I learnt synthesis through building hardware instruments I still think of them as modular and so that is a convenient way for the controls to be layed out for me. I'm not sure that is true for other players.

I usually approach the problem by programming the BC to my standard workflow and understanding.
Here is the screen of my current project showing the layout.as if it is a JP8
https://groups.yahoo.com/neo/groups/bc2000/photos/albums/961897953
The whole thing is setup using a XML file so different synths can use the same program.
The XML file contains the details of what sysex (or NRPN or ???) the program puts out when it receives the CC messages from the BCR .

So if I were you I would play around with a BCR patch until it works for you and then just do a 'save as' and modify the new version for your next synth.

All the best
Royce

Re: Make BCR2000 into a Kiwi Patch Editor -- Common / Default parameters across multiple synths / presets

2014-03-29 by <djo3yk@...>

Yeah, I was thinking of doing the layout for dual osc subtractive synths with similar architecture (ex. Mks-50, Jx-3p, Jx-8p, ex-8000, mircoQ, Matix 6r, etc) as opposed to LAS or additive synths. Granted certain features will have to be left off or put on a second preset (for example, the modulation matrix for the 6r) but I think for the most part there should be a lot of commonality especially for the tones, envelopes, lfos, etc and using the PG-800 as a base template much like how the Kiwi PE does the same. I'm thinking the same supported synthesizers for Kiwi PE should have enough common features for a similar layout to work on the BCR2000 as well. I was just wondering if someone has already embarked on this approach and has already devised/suggested a common layout theme (perhaps based on the PG-800 as the Kiwi PE does) for similar subtractive dual osc synths. Thank you for the XML, that should hopefully make my quest much easier. Cheers!

Re: Make BCR2000 into a Kiwi Patch Editor -- Common / Default parameters across multiple synths / presets

2014-04-03 by <ad.vangerven@...>

Interesting Idea,

However when you intend to support the same set of synths as Kiwi does, that is not going to work!

Using the BCR-2000 will use only when transferring data in one direction. This is sufficient to support most modern synths.

JX3P: Support by BCR-2000 will work only after modifying the JX3P with the Kiwi processor, which adds some great features when it works, but is very tricky trying yourself (I blew my JX-3P trying it).


Other older synths like Oberheim Matrix series, Sequential Circuits, Waldorf Microwave 1.0 require a midi dialog for transferring these parameters, which is not possible using the BCR. I'm using the Kiwi PE with success on the Oberheim Matrix 6 and Waldorf Microwave 1.0, which works nicely. The Kiwi PE simply has the dedicated transfer protocols for these sets of synths built in.

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.