ChromaTalk Archives: June 2014

• Multi-timbrality only 2 channels with CC+?? (3 messages)
• anybody got an unstuffed voice board PCB? (2)
• WTB: Chroma Expander
• Numeric display + general restoration question (7)
• Chroma control professional overlays (63)
  • EPROM of Latest Firmware
  • Update of parameters in LCD Display
  • BCR2000 Programmer Overlays
  • BCR2000 Programmer Overlays - Pricing
• Trying to get #0501 running (11)
• Ser No: 21030620 @ ebay
• TouchOSC iPad (3)
  • OSC iPad Editor
• Rhodes Chroma #21010100

Multi-timbrality only 2 channels with CC+??

William Santana [21030244] · Thu, 5 Jun 2014 16:15:21 -0700 (PDT)

Before receiving the CC+, I had explored the multitimbral options with the Syntech interface. After the CC+ was installed, I expected the function to be the same as before. It seems the Omni mode option in P2 being changed to the Play mode has neutered multi-timbrality down to 2 channels. Is this correct or am I missing a function of the CC+?

David Clarke [21030085++] · Thu, 5 Jun 2014 21:54:51 -0300

William - the "P2" configuration options between the Syntech interface and the CC+ interface are not 1:1 equivalent (by design).

Specifically - with the Syntech interface, this parameter is a switch to turn Omni on or off.

With the CC+, the parameter chooses between 'Play' and 'Normal'.

'Normal' mode is essentially the same as they Syntech 'Omni Off' mode.

'Play' mode differs from the Syntech 'Omni On' mode in that it does not listen to all MIDI channels. Specifically - if P2 is set to 'Play', then the CC+ only listens to the 'base' MIDI channel. That is true for any/all MIDI messages (including CC's, note on/off messages, program changes, etc.). That means that messages to any other channels will simply be ignored.

In Play mode the Chroma takes the base channel messages and treats them as if they were from a single-source keyboard and will 'play' that single stream of data, taking into account the details of the patch on-board the Chroma and (whether it has links or not, transpose or not, etc.)

So - if you you had your keyboard set up to have one patch on the lower part of the keyboard - and another patch on the upper part of the keyboard - this mode would allow you to have one patch (or the other) sound depending on the notes sent. This is different than 'normal' mode where there isn't the concept of a 'split' or 'transpose' via MIDI.

Play mode is intended to function as if you were 'playing' the Chroma from the keyboard via an external MIDI stream (and since the local keyboard can only control 2 instruments - in Play mode you really only have control of up to two instruments, from one MIDI channel).

David Clarke

William Santana [21030244] · Fri, 6 Jun 2014 08:15:36 -0700 (PDT)

Hey, thanks for the clarification. I totally had things mixed up on my end. I am eventually looking to access each channel while using Mono mode from an external controller. This will give sort of an Oberheim xVS kind of behavior where the voices will allocate in a cyclical fashion. I am also going to add a MIDI channel output control on the programmer so I can access each instrument's parameters instantly with the turn of an encoder.

Thank you again,
William Santana

anybody got an unstuffed voice board PCB?

Eric Frampton [21030501] · Fri, 13 Jun 2014 00:57:13 -0400

Hi all - first post here. I’m now the proud owner of Chroma #0501. It needs lots of attention, and I’m just starting down the road of getting things sorted out. There’s a ton of battery acid and cat pee damage, for starters.

I’ve got one irreparably acid-damaged voice board. I thought I might try having a new board or two made using David Clarke’s artwork, but after soliciting lots of advice and doing some poking around, I’ve decided I’m really not up to the challenge (yet) of making that happen.

Meanwhile, I’ve ordered a spare used board from Doug at Synthparts so the immediate need is covered, but I’m interested in trying to get the remaining pieces from my damaged board on to a new one as a spare. The CEM3350, 3360, and tempcos all appear unharmed and I was able to get them desoldered intact, and I’ve got enough bits lying around from other projects that to stuff the rest of the board is going to be pretty cheap (assuming the 3350 and 3360 made it out alive). So now I just need the bare board, itself.

All that said, does anybody have one, maybe from an earlier run or something, that they’d be willing to part with?

Eric

William Santana [21030244] · Fri, 13 Jun 2014 08:40:57 -0700 (PDT)

I have a board. I pulled the CEMs to repair other boards but, everything else is there.

WTB: Chroma Expander

Michael McInnis [21030027] · Sun, 15 Jun 2014 11:40:21 -0400

I am interested in finding one, if anyone is willing to sell.

Regards,

MM

Numeric display + general restoration question

Roel D. [21010092] · Tue, 17 Jun 2014 20:33:16 +0200

Hi all,

I just finished getting my Chroma in full working order. I replaced the power supply, installed CC+ and then did some repairs on 4 channel boards (2 with logic problems, other 2 both had C13 failing). And the tapper was going crazy because of a broken flipflop (io board Z38).

Now there's just one led of the numeric display (B2) that doesn't work/works/is very dim (depending on unknown circumstances, changing). From what I read in the schematic the 2 digits are multiplexed, so I presume that it's not a problem with the logic chips if the corresponding led in the other digit is working? Any ideas? I also noticed that in the led test DP2 is not working, but this could be because it's not used at all. Am I right about this?

Next questions, since I have it working now, I would like to do a recap (starting with elco's, and channel motherboard as C2 and C3 look rather funky with a blueish goo on top of them...) and some small adaptations. I found this post by Luca [21010226] (see Voice Board and Channel Board Recap & Rechip Kit on eBay, December 2012). A few questions on this:

1. How necessary is rechipping? I suppose it makes more sense to just leave it in working order and repair when needed?
2. Non polarized caps will stay for the moment, I prefer to start small. Or bad idea?
3. What and why audio-grade caps? I don't really get what the characteristics of audio-grade caps would be, as audio signals are not very demanding frequency-wise and I'm not sure if one capacitor would get the S/N ratio down significantly? I assume that I'm missing something?
4. These cermet trimmers, do they fit the holes on the PCB? Does anyone have a part number for these? Or a hint on what to look for pin-wise?
5. And by any chance, can anyone provide some pictures of a fully restored channel board just as a reference?

Lastly: I saw quite a few posts about OLED displays passing in the archives. Since I already have the code for an Arduino based serial to LCD convertor, I might give these OLEDs (Serial: UART/I2C/SPI True Color OLED160x128 OLED Module) a go in the near future. I have to take the normal serial LCD input as a starting point, so in a first version it'll be just a color version of that. To get a more advanced display the arduino will have to interpret the data sent out and take it from there, so that will 1. be time consuming to figure out and 2. might have a small delay. Working from the midi output might be another option. Any ideas?

Anyway, after I finish working on the Chroma I'll try to restore my Arp Pro Soloist/Little Brother/Synare/... first before getting to this. But it might happen... ;o)

Sorry for the lengthy post and thanks for helping me out!
Roel

Luca Sasdelli [21010226] · Tue, 17 Jun 2014 23:19:16 +0200

Hi Roel,

about recapping, it’s just a matter of choice, if the Chroma is working well. Recapping means to bring all timings at the intended value, reducing leakages and perhaps to reach better conditions than the initial ones: this because nowadays it’s quite common to find 5% or better tolerance capacitors. I suggest polypropylene caps (PLYP), for stability, precision and low cost. Better tolerance could be chosen for VCO capacitors (I used 1%).

Audio-grade caps: I decided to use them as the feedback capacitors on VCF (C13 and 14): it’s not a matter of S/N ratio, but of good self-oscillation instead.

The cermet trimmers I’ve used are common blue square units, with side terminals: it is needed to bend them a bit, but they could be properly soldered at the original holes, leaving the adjustment screw on top as it should be. A drop of glue helps to hold the trimmer stable on the board, otherwise it can bend pins when tuning with heavy hands.

(the picture simply to show the trimmer shape)

Unfortunately I don’t have pictures right now; when I’ll have enough time for recapping all my Chroma’s boards, I’ll do some photos and I’ll post them on the mailing list. The recapping did took about 45’ each board to me, including cleaning after component removal.

Cheers
Luca

David Clarke [21030085++] · Tue, 17 Jun 2014 21:06:13 -0300

...I also noticed that in the led test DP2 is not working, but this could be because it's not used at all. Am I right about this?

Roel - when you issue [Set Split][30] (Test LEDs), it is intended that all of the LED segments will turn on - and that includes both decimal points in the large 2-digit LED display (the MAN6740).

That having been said - seeing only the right-most decimal point will be correct behaviour with the CC+.

The reason for this is that the CC+ uses the left-most decimal point of the big 2-digit display as a incoming MIDI indicator (e.g., it mirrors what the green LED on the CC+ MIDI cable set shows).

So while [Set Split][30] turns the LED on, the MIDI activity monitor just as quickly turns it off.

... Now there's just one led of the numeric display (B2) that doesn't work/works/is very dim (depending on unknown circumstances, changing). From what I read in the schematic the 2 digits are multiplexed, so I presume that it's not a problem with the logic chips if the corresponding led in the other digit is working? Any ideas?

The display unit is not soldered in; rather, it sits in a socket. If the behaviour is somewhat variable, then you may be lucky and it may just be a bad/poor connection on that socket pin. Removing and reaseating the MAN6740 LED module may be all that is required to fix the behaviour. If not, then it is most likely the single element diode for that segment is failing - an so replacing the MAN6740 would correct that (there's currently some for sale on eBay - approx. $6 for qty 2).

Roel D. [21010092] · Date: Fri, 20 Jun 2014 12:26:47 +0200

Thanks for the answers, Luca and David. Very helpfull!

I noticed one discrepancy in the schematic and layout of the voice boards. Perhaps this has been noted before. R1 in the schematic is 10K, while on the layout both R1 and R2 are 5K. This doesn't make a big difference as all values of the 5K trimmer can be realised on a 10K trimmer as well, only precision is lost.

Can anyone confirm what is used on the actual boards? I will very probably replace mine with multiturn trimmers and 5K's are cheaper! :oD

Did anyone replace the trimmer on the IO board (R1?) with a multiturn trimmer?

Cheers,
Roel

Roel D. [21010092] · Fri, 20 Jun 2014 16:56:50 +0200

Hi all,

Coming back to the failing led in the numeric display: I also noticed that 2 of the switches (maybe more, I didn't check all of them yet) have problems with readout. Switch 18 gives a mostly a respons "23" and switch 23 gives "28" mostly. As these are using the same circuitry I assume that there's something funky going on there. (Switch/display matrix in the schematic.

Any ideas? Is there a diagram with the wiring of all the switches on the matrix? Or is there a good way to debug this? (I have a scope, but no logic analyser.)

Thanks!
Roel

Luca Sasdelli [21010226] · Fri, 20 Jun 2014 17:44:26 +0200

Hi Roel,

did you check this? Service Manual: Schematics & Drawings - Interconnection Diagram 2

Cheers
Luca

David Clarke [21030085++] · Sun, 22 Jun 2014 20:13:58 -0300

... I noticed one discrepancy in the schematic and layout of the voice boards. Perhaps this has been noted before. R1 in the schematic is 10K, while on the layout both R1 and R2 are 5K. This doesn't make a big difference as all values of the 5K trimmer can be realised on a 10K trimmer as well, only precision is lost.

Roel - the original 'ARP' version of the schematic has these both as 5K, with a 12K fixed resistor in series.

The Fender/CBS version of the schematic changed the VCO1 settings to 10k variable and 10k fixed (leaving the VCO 2 value alone) - but you're quite correct that the Fender/CBS drawing shows both to be 5k.

Can anyone confirm what is used on the actual boards? I will very probably replace mine with multiturn trimmers and 5K's are cheaper!

While the schematic only shows that the values for one of the VCOs was updated to 10k + 10k (and left the other at 5K + 12k), I can confirm that the later voice cards did actually use 10k +10k for both VCOs.

(As an aside, the 12k fixed + 5k variable is what the datasheet for the 4151 part itself uses as a reference implementation).

Unless you wanted to dig into the design details for the part, I'd suggest that the easiest approach will just be to review what's currently on the revision of boards you have, and just match those values.

Did anyone replace the trimmer on the IO board (R1?) with a multiturn trimmer?

I've tended to find that trimmer much less sensitive/much less prone to changing over time, and so I've personally not used a multi-turn for this - but it certainly wouldn't hurt - and would likely make the adjustment itself less touchy.

Chroma control professional overlays

Rob Belcher [21030095+] · Fri, 20 Jun 2014 20:53:13 +0100

Hi Guys,

Ive been talking with Justin @ Synth Graphics about producing a professional Chroma overlay for the Behringer BCR2000 controller. For examples of Justin's work have a look at this here: Tetra overlay.

The plan is to use the existing template created by Matt Thomas [21010021] (I assume that's ok Matt?) and Justin will adjust it accordingly to fit his overlay template, perhaps jazz it up a little bit.

I had initially printed Matts overlay design, laminated it and carefully cut holes out, I spent a fair amount of time and although it fits ok is far from professional looking and then you have to consider how to attach it to the Behringer with some adhesive without making a mess. I spent quite a lot of time doing this and am not really satisfied with the results. So I really think some professional looking overlays would be awesome....

Justin has said he would be prepared to make some providing he got a minimum order of 10-15, im going to get 2, so if we shoot for the minimum number of 10, that just need another 8 people....

Even if you don't have a BCR2000, I would highly recommend Chroma owners give some thought to getting one of these overlays, second hand BCR2000's are really cheap I got mine for just over £50.... and you then have an awesome controller that really opens the Chroma up.

He hasn't specified the cost as yet im waiting for him to get back to me with that..

Anyway, perhaps if people could send me a message expressing an interest that would be great. I wont be the middle man in this, all payments would go to Justin and he would ship them out.

It will be lovely to finally have a **cheap** professional looking controller for the Chroma! That was always my biggest gripe with this otherwise superb instrument.

Cheers,
Rob.

Matt Thomas [21010021] · Fri, 20 Jun 2014 21:12:35 +0100

Absolutely fine by me - I may even buy one myself

Matt

Joe Porter [21030058] · Fri, 20 Jun 2014 20:48:25 +0000

Hi Rob,

Put me down for one please. Do you want me to contact them direct?

Also, is anyone on the forum able to help me out by putting the latest firmware on a chip for my CC+ board? I don't have the chip facilities to update it & am on a version that doesn't support the controller. Thanks.

Best,
Joe

Enrico Dibennardo [21030494] · Sat, 21 Jun 2014 00:27:39 +0200 (CEST)

You can count me in too.

Philippe [21010227] · Sat, 21 Jun 2014 00:35:04 +0200

Hi,

That's an excellent idea and I would be interested to buy some, however I have to admit that I have always preferred David Clarke's [21030085++] overlay choices where the 2 envelopes are one right above the other making the display more readable. At least to my taste: Behringer BCR2000: BCR2000 Set Up

Which could yet be improved by bringing ENV2 Delay 1 pot to the left where there is currently a blank pot, and use the last pot (now blank) of that line for the output selection or the pedal mode...

Phil

Rob Belcher [21030095+] · Sat, 21 Jun 2014 00:23:38 +0100

Hi Joe,

I think for now its probably easier if you let me work this out with Justin rather send him messages, otherwise it will get confusing.

Let's see if we can get to 10 orders and i'll shoot him a message asking for prices and paypal info etc, then we can all send him some funds.

Matt Thomas did you want to commit to 1? Phil A you said you wanted a few, are you committing to 2? I'll take 2, Enrico x1, Joe x1 so that's 7 so far. So getting there..

Regarding changing/tweaking the template, this is not something I can do I have no experience with photoshop, I think as the template is done and the behringer control program mapped to it, lets go with what we have.

Cheers,
Rob.

Philippe [21010227] · Sat, 21 Jun 2014 01:56:08 +0200

Thanks Rob, but I'm interested in David's overlay only so count me out. Nevertheless I'm sure you will reach 10 units and certainly more.

Best,
Phil

Michael McInnis [21030027] · Fri, 20 Jun 2014 20:09:50 -0400

1 for me please.

Regards,

MM

Michael McInnis

Doug Terrebonne [21030114] · Fri, 20 Jun 2014 17:15:39 -0700

Any idea what the price of them would be? I may be interested in 1 or 2 although if they are a bit pricey I'll probably just print them out myself... Also I assume he's in the UK...

Doug

David Hobson [21030506] · Sat, 21 Jun 2014 00:59:47 -0400

I would be very interested in 4 overlays, for the right price. Great idea!

~David

Luca Sasdelli [21010226] · Sat, 21 Jun 2014 10:03:59 +0200

I'm interested too in one of them, thanks!

Moreover, it would be nice to take into account the Michele Majorano's Chromatrol II (The Chroma CPU Plus (CC+): Alphanumeric Display, bottom of the page) including the alpha display in a single modified BCR2000 case. It should include the MIDI ports on its rear, with a single round cable going to Chroma MIDI connector. I plan to make the front and back panels with an on-line service like Schaeffer AG.

Cheers
Luca

Roel D. [21010092] · Sat, 21 Jun 2014 12:28:20 +0200

Whoopwhoop! I'm interested in one too.

Yeah Luca, now we're talking! If we're going this way, it might be interesting to open up the discussion on which parameter should be where. I read somewhere that there's another layout. It seems that alot of people are interested, why not discuss it a bit. I'm sure we can easily find someone to change the layout to whatever we get out of the discussion. And I will provide new sysex-files if needed.

If you design a Schaeffer panel, I would love to hear about that. I have a display working with an arduino as the backpack, so I'm playing with the idea adapting the code to get a full color oled display (1.8" Serial: UART/I2C/SPI True Color OLED160x128 OLED Module(CN) DS160128COLED-35 is affordable) to work with it. Which is not too difficult to program really, for a very basic version at least. Later on the code can be updated for more advanced features probably, maybe even with graphical routings etc. (Which eventually might need a bigger arduino than a mini.) Anyway, if there is interest in this, I will move it forward on my todo-list.

On that note, at this moment the display doesn't change if I alter a parameter via midi, is that a setting that I missed?

Cheers,
Roel

John Simmons [21030454] · Sat, 21 Jun 2014 11:53:54 +0100

Hi

I'd also like 2 overlays. I used the original template which is great but found it difficult to fix to the VCR without a bit of mess!

Best regards

John

Chris Smalt [21010280+] · Sat, 21 Jun 2014 13:34:08 +0200

Ive been talking with Justin @ Synth Graphics about producing a professional Chroma overlay for the Behringer BCR2000 controller.

I'm interested, however I would order at least two, so that I can cut one up to relabel the other one for a custom setup. I feel that the existing layouts are upside down. There's a reason that oscillator and filter control are on the bottom row on the Chroma: you want easy access to those parameters. Also, the Chroma nicely groups Detune, Glide and Sweep.

So my custom layout would have Cutoff on the bottom row, then Pitch, then Detune/Glide/Sweep (in this order) on the third, and the envelopes on the top row. In case someone wonders why Cutoff is at the bottom: the best sounding filter sweeps are done with parameter 45 (Cutoff mod depth), which would be the bottom right pot. In the current setups, I find it very tiring to have your arm hover over the BRC while playing to control a pot in the top row.

Cal Lockard [21030691] · Sat, 21 Jun 2014 11:58:31 +0000 (UTC)

Please sign me up for 2 overlays as well.

Thanks

Richard Sales [21030644] · Sat, 21 Jun 2014 09:30:51 -0700

I'll take one of those overlays if doesn't cost a fortune!

Thanks

Richard

Frank McGing [21010198] · Sat, 21 Jun 2014 22:36:53 +0100

Anyway, perhaps if people could send me a message expressing an interest that would be great.

I have a pair of BCR2000s and a (still not yet connected!) Sparkfun red on black LCD for my Chroma, so I would definitely be interested in a pair of overlays.

I really like the custom enclosure idea!

Frank

Frank McGing [21010198] · Sat, 21 Jun 2014 23:44:22 +0100

Anyway, perhaps if people could send me a message expressing an interest that would be great.

I'd be interested in a pair of overlays. I have a pair of BCR2000s for my Chroma, along with a Sparkfun red-on-black LCD. Still haven't gotten around to putting it all together though!

I'm also interested in the idea of a custom enclosure for the BCRs.

Frank

Rob Belcher [21030095+] · Sat, 21 Jun 2014 23:51:20 +0100

I've sent a message to Justin to let him know we have around 15-30 orders, pending prices.... so just waiting to hear back from him with the details and will let everyone know

Cheers,
Rob.

Enrico Dibennardo [21030494] · Sun, 22 Jun 2014 11:46:48 +0200 (CEST)

The price of a second hand brc2000 will raise a lot with all these orders :-)

David Clarke [21030085++] · Sun, 22 Jun 2014 19:18:22 -0300

... Also, is anyone on the forum able to help me out by putting the latest firmware on a chip for my CC+ board? I don't have the chip facilities to update it & am on a version that doesn't support the controller.

Joe - if you can let us know generally where you are (geographically), that will let the folks on the list better determine who might be able to best assist.

Also, as an aside - all version of the CC+ firmware can successfully be used with the Behringer BCR2000 or other external controllers. It's just that a few of the 'nice to have' items (such as the ability to BCR2000 to automatically request and display the patch settings - added in firmware 215, or the ability for the Chroma to automatically send new patch parameters to the external controller - added in firmware 217) might not be there with older firmware.

David Clarke [21030085++] · Sun, 22 Jun 2014 19:18:22 -0300

EPROM of Latest Firmware

... Also, is anyone on the forum able to help me out by putting the latest firmware on a chip for my CC+ board? I don't have the chip facilities to update it & am on a version that doesn't support the controller.

Joe - if you can let us know generally where you are (geographically), that will let the folks on the list better determine who might be able to best assist.

Also, as an aside - all version of the CC+ firmware can successfully be used with the Behringer BCR2000 or other external controllers. It's just that a few of the 'nice to have' items (such as the ability to BCR2000 to automatically request and display the patch settings - added in firmware 215, or the ability for the Chroma to automatically send new patch parameters to the external controller - added in firmware 217) might not be there with older firmware.

Joe Porter [21030058] · Mon, 23 Jun 2014 08:57:42 +0000

Re: EPROM of Latest Firmware

Thanks David. I'm in UK. Any EUers able to help me out with the latest Firmware on a chip?

Best,
Joe

Luca Sasdelli [21010226] · Mon, 23 Jun 2014 11:01:11 +0200

Re: EPROM of Latest Firmware

Hi Joe,

I live in Italy: should you not find a user in UK (lowest shipping cost), I could ship an updated EPROM to you.

Cheers
Luca

David Clarke [21030085++] · Sun, 22 Jun 2014 19:02:13 -0300

Update of parameters in LCD Display

... On that note, at this moment the display doesn't change if I alter a parameter via midi, is that a setting that I missed?

Roel - whether data is automatically shown on the LCD will depend on the setting of the Continuous Controller Mode ([Set Split 36][P24]) as well as whether the MIDI messages are directed to the base MIDI channel or not.

Some further background is available in the "Automatic LCD decoding of MIDI Continuous Controller Data" section of the post here: CC+ firmware release 217: User-defined MIDI Velocity Mapping, Auto-send of Patch Parameters and more.

If there are still questions about what is occuring or being seen, just let us know what the settting of [Set Split 36][P24] is, the MIDI base channel ([Set Split 36][P5]) and the channel the MIDI messages are being sent to the Chroma on.

Best regards,

David Clarke

Roel D. [21010092] · Mon, 23 Jun 2014 12:16:08 +0200

Re: Update of parameters in LCD Display

I was not aware that [Set Split 36][P24] also influenced the chroma and external display behaviour. Now it works.

Thanks David!

Roel

Rob Belcher [21030095+] · Tue, 24 Jun 2014 12:03:12 +0100

Hi Chaps,

I got a reply from Jamie, he's been working away on the design but has a couple of questions:

QUOTE:

I'm working on the layout now (adapting to my die cut). I have a few questions, mainly about the top panel part. I'm a little confused how you (or whomever) has set this up. Example, the top row of 8 encoders parameters are assigned depending on the 4 group buttons below the numerical display. But there are only one group of names, yet all four buttons are labeled to do something different.

Maybe there is more to be accessed by using the 8x4 matrix, and don't forget 8x4 clicking the encoder, like I use in the my other BCR programmer overlays. Not having a Chroma I don't know what is all programmable over MIDI. I did look at the website and found a list, but not sure again not having one on hand.

But good news is I have re-laid out in Illustrator so it can printed in full vector quality. They will look very sharp!

Please give me some insight.

Thanks,

Jamie

END OF QUOTE

I must confess having only very recently bought the Behringer controller i've not had time to install the .syx files into it, so haven't used it to control the Chroma.

I did glance over some of the controls on Matt's design and wondered, like Jamie about the 4 buttons below the display and where they map to encoders for example the pitch button is white and corresponds (i assume) to the single encoder marked "tune" .. with Tune being in Green text (shouldn't it be white too so that the control matches the white button/ or both a different color say yellow?), volume button i assume corresponds to the mod select/depth encoders....

I would ask that please somebody look over Matt's current overlay and suggest any worthwhile amendments..... we might as well make sure that the template is laid out in the most efficient way and i agree perhaps it would make it flow better if both the envelopes mirrored each other on the bottom two rows of encoders....

Im not being lazy, but having only recently got a Chroma and the Behringer controller and with limited knowledge on the full parameters available to the Behringer with CC+, it would be better if someone who is well acquainted could make any amendments....

We can also have the opportunity to make more of the 8x 4 matrix as Justin will be able to fit in more text for different possible button/encoder

So let me know your thoughts and then we can shoot Justin the final design.

Cheers,

Rob.

Jamie Downing · Tue, 24 Jun 2014 15:05:22 -0500

BCR2000 Programmer Overlays

Hello Everyone,

I was recently contacted by the group about creating BCR2000 overlays for the Rhodes Chroma based on the existing PSD file on the site [see Behringer BCR2000: Chromatrol for Behringer B-Control]. I have made adjustments that allow access to all the parameters, to my knowledge anyway. The overlay uses our proven BCR2000 die cut and was rebuilt from the ground up using a vector based program so the graphics and type will be very crisp and clean.

Attached is PNG example, or you can look at online: BCR2000 Programmer Overlay for Rhodes Chroma.

I personally do not own a Chroma so I'm asking for volunteers to reprogram the BCR and test the layout. A few notes. I have added to the parameter names to help clarify what you are editing and more along the lines of standard naming conventions. Rather than just SWEEP for example I have named it LFO SWEEP (since it is really a LFO), and so on. You will also note that clicking on the Filter Cutoff (Tune) encoder knob will now toggle between HPF and LPF. Same for Output Mode.

To make this happen I will need at least 15 buyers, I have yet to determine the actual cost per unit but should be under $40. They are made from 10mil lexan polycarbonate, this is the same or similar material that was used on the Chroma itself so it will be right at home sitting onto your Chroma. This material is extremely tough and has a textured matte finish. If you have seen a Dave Smith synth or modern Moog, this is the same material. They will come pre-cut and ready to install onto your BCR2000.

Please feel free to contact me directly at [email address removed] with any questions or suggestions.

Cheers, Jamie www.synthgraphics.com

Rob Belcher [21030095+] · Wed, 25 Jun 2014 00:10:43 +0100

Re: BCR2000 Programmer Overlays

Oh wow... that looks great Jamie and thanks for mailing the group I thought it would be easier that way. Well I'd be interested in buying a couple for sure, we had at last count close to 30 people interested, so I think getting to 15 shouldn't be a problem.

One question I forgot to ask, do they have some sort of adhesive backing?

Cheers

Jamie Downing · Tue, 24 Jun 2014 18:23:04 -0500

Re: BCR2000 Programmer Overlays

Thanks! Yes, they have a 3M adhesive backing that is permanent. You can still remove it later but you have to pull like crazy.

Philippe [21010227] · Wed, 25 Jun 2014 03:40:17 +0200

Re: BCR2000 Programmer Overlays

Hi Jamie,

It looks really awesome.

Here are my suggestions:

Regarding your modifications and since this overlay is dedicated to the Chroma only I would totally stick to the Chroma's terminology: keep SWEEP and not LFO SWEEP, TUNE and not CUT OFF, WAVEFORM and not VCO WAVEFORM, etc...

It clarifies for you because you are not familiar with the Chroma but for any Chroma user - or at least any Chroma manual reader - it might be confusing actually and certainly less... Chroma-like !

I would also keep the icons for the pink noise and white noise waveforms selection switches instead of words, more intuitive (aren't we in the post-Steve-Jobs era ? ;), after all you didn't write square and saw for the others and you did well.

Note it seems you have omitted the name of the last switch at the very top right: "waveform", it should be put back. Consequently the 3 "VCO waveshape" pots are not necessary where you put them below since they are up there already.

And why repeat 3 times MOD1 SELECT, etc.. at the bottom of the upper part ? 1 time as the original is plenty enough for a Chroma user I'm sure. And I would entirely remove the VCF bracket at the very top of that part since each of those pots can control up to 4 different parameters, not only VCF.

Totally agreed with the envelopes' parameters positions. One question remains: should the last pot be for "OUTPUTS selection" or "FSW MODE" ? Time for a vote ?

Maybe OUTPUTS is more universal to all users since not all of us have the pedals.

Also, you seem to have tried something at he bottom left of the upper part regarding FSW MODE, could you tell us more about what you had in mind ?

Of course these are only suggestions, if other users think differently let's speak about it...

Regards,
Phil

Roel D. [21010092] · Wed, 25 Jun 2014 11:35:22 +0200

Re: BCR2000 Programmer Overlays

Jamie, Phil, others,

Looks great indeed!

As for the terminology, I'm with Phil on the TUNE instead of CUTOFF. But I don't really mind the LFO SWEEP and OSC WAVEFORM, it's a bit clarifying and doesn't seem confusing to me as they are only used in the section names. The big FILTER bracket on top is somewhat weird indeed, as it has different functions. Maybe FILTER / PITCH / CNTRL/VOL? Dunno. Other than that these brackets are great!

I like the look with the waveforms better also.

At this time in this design there is one layer of the upper encoders unused, as I see it? (That's why the WAVEFORM is not in this view, and why there's the 3 WAVEFORM encoders in the main control area, Phil!)

Cheers,
Roel

Philippe [21010227] · Wed, 25 Jun 2014 13:56:07 +0200

Re: BCR2000 Programmer Overlays

Hi Jamie,

I see you have updated many things already thanks ! It's looking more and more like something I would buy :)

Regarding the labels MOD1/2/3 SELECT & DEPTH of the upper part I would take away the coloured background and put them back to white text as they are generic to all 3 (4?) switches; and keep the coloured background or coloured letters (depending on what looks less crowded) only for the first 2 pots. Don't forget the LPF/HPF label !

I still don't think the upper bracket is needed , at least not with this name. If the 2 original layouts had all these things identical in common was certainly for a reason, although I totally understand as a non-user some things felt strange to you and thought it could be a good idea to change them.

Also, you reminded Rob in an earlier email that there were 8x4 clicking encoders. So far only 1 is used (LPF/HPF). That's 31 remaining ! I have to admit I always thought I should implement on mine a PROGRAM# UP & PROGRAM# DOWN click. So if others are interested too I would suggest for example the 2 last upper right pots to do that:

• pot7: PROGRAM# DOWN
• pot8: PROGRAM# UP

Nice when you want to stroll through a whole program bank...

@Roel

Problem with the 3 WAVEFORM encoders in bottom part is you loose 3 parameters. In the current overlay you lose DETUNE, FSW MODE & SWEEP WAVESHAPE pots unless I missed something (the fact the SWEEP WAVESHAPEs are all already present above via direct switch access is not redundant but complementary, again from my point of view, to the pot below).

@Rob

I agree ARP could have made different terminology choices however they are here now and noone can change this, reason why I think it makes more sense to keep them as they were chosen originally. And that way the upgraded BCR will even look like an original optional tool designed by the original ARP team itself and I think will look much more legitimate and desirable (and yes less confusing, from my point of view at least of course, why would a pot with a name control a parameter with another name ?). Would you rename the "Emphasis" pot on a Minimoog controller by "Resonance" and "Contour" by "Envelope" because it is more conventional ? Anyone who spends time with a Minimoog will know what is what within the first hour of use. Same here.

Regards,
Phil

David Clarke [21030085++] · Wed, 25 Jun 2014 08:52:01 -0300

Re: BCR2000 Programmer Overlays

All - a couple thoughts for group consideration:

1) One of the benefits of the BCR2000 over some of the other knob solutions are the LED rings around the knobs, so you can actually 'see' what the setting is before changing it.

While it is nice to have the sweep waveshape availalble on the push buttons at the top - and the osc. waveform on the buttons at the lower right, I'm not aware of how to program the BCR2000 so that it will actually use the LEDs on those buttons to actually 'show' what the current setting is.

If someone knows how to program that - then that'd be great - but if not, it means that if those settings only appear on the buttons - you'll tend to loose the ability know what the current setting for those. e.g., you can certainly press the button to change the setting - but won't be able to see what the setting was.

I'm not suggesting it is a better layout - but that was the reasoning behind the duplication of those two settings on dedicated knobs in the offering here: BCR2000 Set Up

2) A couple typos in the .png image sent to the list:

a) At the top, the orange text reads:

• MOD 1 SELECT
• MOD 2 DEPTH
• MOD 2 SELECT
• MOD 2 DEPTH
• ....

(note the duplication of the MOD2 DEPTH).

b) The orange text at the top includes "MOD 3 DEPTH", but there isn't actually a MOD 3 depth for the "Volume" control.

3) I agree with others that there likely isn't a need to duplicate the Mod 1 select/Mod 1 depth choices for each colour at the top. Instead, since the last 6 knobs will always be used for Mod select/depth choices (for cutoff/pitch/volume, etc.) - a single legend would be fine. [Where a parameter may not be used - it will be evidenced by the BCR's encoder rings being dark]

4) Each knob is currently listed with their names like: ENV 2 AMPL TOUCH, ENV 2 ATTACK, ENV 2 DECAY, etc. The orange brackets over the knob groupings ends up being a bit redunant since the name is simply duplicated (e.g., the bracket over all the items already identified as ENV 2 simply says "Env 2"). If there was a desire to go back and match the Chroma panel, then the specific portion under each name could be removed in preference for the bracket over the top. (e.g., instead of ENV 2 AMPL TOUCH - just AMPL TOUCH). Another approach would be to leave the names on the knobs, and remove it from the bracket (perhaps leaving the orange bracket as a method to visually group the knobs).

Rob Belcher [21030095+] · Wed, 25 Jun 2014 13:31:47 +0100

Re: BCR2000 Programmer Overlays

I *really* dont agree about the removing the colored blocks beneath the Mod 1-3 select / depth.... i think as currently is it makes it the routing very logical, but i think the blocks look better than having the text written 3 times in different colors (that was on the original design)

Im all for as making it as intuitive as possible.... no point copying everything verbatim from the original Chroma "design" if its not very intuitive.....

The LP/HP filter mode is labelled on the front panel, it is to the right of the C Tune know, with a little finger push icon.

Excellent idea about having program up - program down using push button functionality of pots 7 and 8.

One other thing, which i think would be useful the top right push button thats not currently used (above cntrl/vol) could be used to select what 16 channel mode the Chroma is in and would correspond nicely with the 0-15 numbered buttons underneath the first top row of encoders....

That way you could reference the chart and click the button 7 for "Ring Modulator" and 13 "no-cross mod" etc.etc..

I think what we have perhaps with the addition of my suggestion and jamies suggestion of push pots 7-8 to go up/down presets is about as good as we could possibly achieve without cluttering up the front panel with more text for different modes.

Clearly the Chroma parameter chart will still need to be looked over when using the BCR2000... but it massively helps editing at least.

Jamie, can we start sending paypal payments for this, if you send a message with your paypal details you can start getting orders in....

Im really keen to start cooking with the Chroma and the BCR2000!

Cheers

Philippe [21010227] · Wed, 25 Jun 2014 15:29:02 +0200

Re: BCR2000 Programmer Overlays

+1 with everything said by David.

When in doubt, the choice that goes towards matching the Chroma panel is the best in my opinion. Also, it would feel maybe more logical to have ENV1 pots above ENV2 pots. What do others think about this ?

Phil

Philippe [21010227] · Wed, 25 Jun 2014 16:09:28 +0200

Re: BCR2000 Programmer Overlays

I *really* dont agree about the removing the colored blocks beneath the Mod 1-3 select / depth.... i think as currently is it makes it the routing very logical, but i think the blocks look better than having the text written 3 times in different colors (that was on the original design) [...]

As we can realise by now "intuitive" is a relative notion. You think there is no point to copy verbatim, I think it makes a lot of sense, so we will have to agree to disagree on this.

I couldn't read the LP/HP label as it is too small to read on my screen, thanks. Then what is written under the label C TUNE ? And why C TUNE and not TUNE ? So you mean you have the Cutoff tune in one pot and the Pitch tune in another ? For me it was making total sense before when all Tunes were on 1 pot, now it looks confusing.

Now, to try and avoid endless confrontation of everyone's sense of what is "intuitive" or not maybe Jamie could tell us what is the expensive part of the manufacturing process, is it the manufacturing itself or the design of the layout, or something else ?

If it is the manufacturing process alone - for example - then maybe we could have our own individual layout customized. I mean at least I am ready to apply my desired changes myself and send you the modified PSD file if you prefer to.

Or we could make 2 layouts if this is easier for Jamie, 1 following Rob's intuition and 1 following mine and people would pick whichever they want ? Thanks to let me know Jamie...

(actually I'm even convinced that if you manufacture 15 at least of each you will sell them all, some people really don't care about the subtleties we are discussing here as long as there is a name to each pot and button...)

Phil

Jamie Downing · Wed, 25 Jun 2014 10:56:18 -0500

Re: BCR2000 Programmer Overlays

Hey Gang,

Yes I have updated a few things per your requests. I will try to hit everything, but sorry if I miss something, a lot to take in here.

1. I can't really do different versions or one offs, it's too cost prohibitive, the manufacturing at this level of quality is not cheap so several versions is not really an option. But I think we can come up with a design that makes everyone happy.
2. I will remove the top filter bracket bars and rename everything exactly how it is in the manuals. I think in the early days everyone had their own terms, I looked at my old MS-20, Polysix and Poly-61, even they have not so standard names as we see today (EG, MG, etc). I added in the pink and white waveforms, tried to clean it up a bit and moved the labels to the top of the button to make it very clear which is which for the non Steve Jobs generation.
3. All the Wave Shape parameters are present. I'm using this chart and it only shows 4 parameters under Wave Shape. The first being waveform select buttons on the lower right, and the last three as encoders - width, mod select, and mod depth. As for Detune, that's under Control on the top along with FSW mode (now a clickable encoder to toggle through the modes) and Sweep Waveform is selected using the top buttons (it's not part of the OSC).
4. The top buttons are not part of the 4 banks sadly, only the encoders are, so I can't add the blank bank as Patch routing modes. Great idea though, but a limitation of the BCR itself. But there is encoder for that next to the Wave Shape.
5. I added the 4th bank to now control Master Volume and Program Select.
6. I flip flopped the filter Tune and Res to match the Chroma order, actually this worked out better anyway so now the Tunes and Detune are on the same row.

Attached is the latest version slightly larger so you can see things better.

Thanks guys!
Jamie

Jamie Downing · Wed, 25 Jun 2014 11:29:51 -0500

Re: BCR2000 Programmer Overlays

Private email from Jamie to Rob Belcher [21030095+], quoted in his message to the list:

Hey Rob, thanks for helping to get everyone on the same page.

I'm little confused on the VCO pitch? Please clarify, there is no pitch parameter under Wave Shape, but I assume this is in the Pitch group? Is so they are all under encoder #2 now

We can program the BCR so they can click 8 to change prorgams under any bank, but will only go up (not down), if you select the volume/prgm bank then you just use the encoder to go up/down programs, same with volume up/down. Hope that makes sense.

I could move ENV 2 under ENV 1 but then that would screw up the Glide grouping or would need split the CTRL Patch and KYBD even further away from each other, trying to keep thing grouped best as possible. Is ENV 1 for Filter and/or Sweep, and Env 2 for VCA?

Jamie

David Hobson [21030506] · Wed, 25 Jun 2014 13:14:46 -0400

Re: BCR2000 Programmer Overlays

I am pretty much in agreement with Phil on a suggested layout. I believe the overlays should be as true to Chroma "vernacular" and Chroma look and feel as possible. Redundancy should be avoided obviously. I am sure that whatever is settled upon will do the job, and would like to have more updates (images) as the design is finalized.

Also, I seem to be using a old template for the BCR; where is the link to download the latest template for the Chroma? Sometimes I have a hard time locating things.

David

Philippe [21010227] · Wed, 25 Jun 2014 19:52:39 +0200

Re: BCR2000 Programmer Overlays

On Wed, Jun 25, 2014 at 5:56 PM, Jamie Downing wrote:

Hey Gang,

Yes I have updated a few things per your requests. I will try to hit everything, but sorry if I miss something, a lot to take in here.

Thanks for all your efforts.

1. I can't really do different versions or one offs, it's too cost prohibitive, the manufacturing at this level of quality is not cheap so several versions is not really an option. But I think we can come up with a design that makes everyone happy.

OK, let's try to find something consensual then. Although I do believe following the instrument's logic and terminology is what makes more sense, even if names are unusual.

2. I will remove the top filter bracket bars and rename everything exactly how it is in the manuals. I think in the early days everyone had their own terms, I looked at my old MS-20, Polysix and Poly-61, even they have not so standard names as we see today (EG, MG, etc). I added in the pink and white waveforms, tried to clean it up a bit and moved the labels to the top of the button to make it very clear which is which for the non Steve Jobs generation.

Good news. I think you should then also remove the blue line that goes from the CUTOFF button to the upper pot 8.

3. All the Wave Shape parameters are present. I'm using this chart http://www.rhodeschroma.com/content/parameterchart/parameterchart2.1.pdf and it only shows 4 parameters under Wave Shape. The first being waveform select buttons on the lower right, and the last three as encoders - width, mod select, and mod depth. As for Detune, that's under Control on the top along with FSW mode (now a clickable encoder to toggle through the modes) and Sweep Waveform is selected using the top buttons (it's not part of the OSC).

FSW MODE toggle is a good idea per se BUT I still feel putting the waveshape controls among the lower pots is not working. For many reasons:

1. 1. there are 4 parameters controlled by MOD1, 2 or 3 (PITCH, WAVESHAPE, CUTOFF, VOLUME). They are present with the same layout in the upper part but one ! Why change 1 among those 4 ? If you look again at the parameterchart they are all together for a reason: the internal logic of the instrument as designed by ARP engineers.
2. 2. as David explained in his last email, having the WAVESHAPE assigned to a pot allows to see which shape is currently in use thanks to the pot's LED. We lose that info in your current layout.
3. 3. Because FSW Mode is on a toggle you also lose the visual information of which is currently applied.
4. 4. Same thing for Outputs.

and maybe others I forgot. So you see, you break the logic of the instrument's synthesis architecture AND lose at least 3 infos. Now I'm maybe starting to understand that your choice originates from the lack of space to add a 4th colour rectangle under the 3 already there. Maybe all 4 colours should have the same height (meaning the blue height would shrink to the other's shorter height and sticking all 4 together would offer a multi-coloured background for the TEXT. Does that help you ?)

4. The top buttons are not part of the 4 banks sadly, only the encoders are, so I can't add the blank bank as Patch routing modes. Great idea though, but a limitation of the BCR itself. But there is encoder for that next to the Wave Shape.

OK.

5. I added the 4th bank to now control Master Volume and Program Select.

Master volume is a good idea. Regarding Program Select I imagined clicking PROGRAM DOWN and PROGRAM UP would be a less delicate operation than 50 positions on 1 pot. If it's possible to change it that'd be great, but certainly less important than the WAVESHAPE section on upper part of the layout ;)

6. I flip flopped the filter Tune and Res to match the Chroma order, actually this worked out better anyway so now the Tunes and Detune are on the same row.

Thanks !

Attached is the latest version slightly larger so you can see things better.

Thanks guys!
Jamie

Thanks to you ! we're getting there...

Philippe [21010227] · Wed, 25 Jun 2014 19:56:18 +0200

Re: BCR2000 Programmer Overlays

Surely i think its much better to just have one design. [...]

Hi Rob,

No problem, your initiative is deeply appreciated.

I agree with keeping the colour matrix. Maybe the suggestion I just sent to Jamie can help in that regard ? The ARP logo would be a nice addition ! :)

Phil

Philippe [21010227] · Wed, 25 Jun 2014 20:01:42 +0200

Re: BCR2000 Programmer Overlays

On Wed, Jun 25, 2014 at 6:29 PM, Jamie Downing wrote:

I could move ENV 2 under ENV 1 but then that would screw up the Glide grouping or would need split the CTRL Patch and KYBD even further away from each other, trying to keep thing grouped best as possible. Is ENV 1 for Filter and/or Sweep, and Env 2 for VCA?

ENV1 & ENV2 can stay as they are then if it helps general organisation. Let's see an updated layout and we will see if there is anything we could think of...

Phil

Jamie Downing · Wed, 25 Jun 2014 13:06:26 -0500

Re: BCR2000 Programmer Overlays

Attached is Version 3

Jamie

Philippe [21010227] · Wed, 25 Jun 2014 23:12:11 +0200

Re: BCR2000 Programmer Overlays

Thanks. Please let me know when you had a chance to go through my replies to your 6 points.

Phil

Jamie Downing · Wed, 25 Jun 2014 18:40:50 -0500

Re: BCR2000 Programmer Overlays

FSW MODE toggle is a good idea per se BUT I still feel putting the waveshape controls among the lower pots is not working. For many reasons: 1. there are 4 parameters controlled by MOD1, 2 or 3 (PITCH, WAVESHAPE, CUTOFF, VOLUME). They are present with the same layout in the upper part but one ! Why change 1 among those 4 ? If you look again at the parameterchart they are all together for a reason: the internal logic of the instrument as designed by ARP engineers.

Looking at the block diagram, Pitch and Wave Shape make up the OSC (in conventional terms). This is where the old arrangement makes even less sense since Pitch is it's own pot bank and wave shape another pot bank (there are 11 total parameters to make up the entire OSC and only 8 available pot encoders per bank)

To program the entire OSC (Pitch + Wave Shape) simply click on the green Pitch encoder pot bank and you now have them all grouped in the same area. And you see it flows exactly how Arp intended and in order. Whats missing on the old layout is the ability to modulate the waveform, thats completely omitted, you would only be able the modulate the pitch (1,2,3)

As a avid programmer this provides a better workflow. Also note the pot #1 could still assigned to RES even in the Pitch bank, allowing you to adjust the resonance WHILE editing the entire OSC, very handy in programming terms, this would be impossible if the wave shape was in the top row of encoders. Follow me?

See example 1 attached.

2. as David explained in his last email, having the WAVESHAPE assigned to a pot allows to see which shape is currently in use thanks to the pot's LED. We lose that info in your current layout.

I'm not following you here, the wave shape's waveform are selected using the toggles on the lower right bottom, if the toggle LED is lit then that is the waveform you are using. Same as with the SWEEP waveforms.

3. Because FSW Mode is on a toggle you also lose the visual information of which is currently applied.

Well, this is where something has to give. Is programming the sound the main goal of the programmer or being able to change the foot switch? This could be easily access the conventional way directly on the Chroma itself.

Please see Example 2: You will see the two most important sound parameters are on the lower level, since this effects how the OSC is routed it's only natural it be next to the Wave Shape pots.

For Patch routing LED display, simply set the BCR to a range of 0-15 and the pot will only go to 15 and display one more LED dot for each setting. So for example if you wanted Filter FM routing LED 12 would be lit, the 12th showing it's setting 12.

4. Same thing for Outputs. and maybe others I forgot. So you see, you break the logic of the instrument's synthesis architecture AND lose at least 3 infos.

Output is on a pot encoder, so that LED information will still be present. Please remember I'm working with the physical limits of the BCR itself and not intentionally breaking Arp's design arch. I don't feel selecting which output you are sending audio to outweighs the overall intent of the programmer. It is present and again is more of a global parameter that could also be accessed on the Chroma itself. I personally would remove this all together and make it a click toggle in favor of keeping Pot #1 always be filter res no matter what bank you are using.

Hope this all makes sense. Hopefully the included example will help everyone visualize the layout.

Jamie

Jamie Downing · Wed, 25 Jun 2014 19:23:51 -0500

Re: BCR2000 Programmer Overlays

After I sent the last reply the light build went off, I can move Control to its own pot encoder bank so the FSW and OUTPUT can again have there own pot encoders and no clicking the pot encoder. This also allows you to edit the filter res no matter what pot encoder bank you are in.

Keep in mind the top the bottom pot encoders do the exact same thing, so the top group can display the LED the same way the bottom do.

See attached REV 4.

Jamie

Jamie Downing · Wed, 25 Jun 2014 19:39:27 -0500

Re: BCR2000 Programmer Overlays

One more tweak, moved the detune in line with Control on the top row to keep the flow the same as intended, and the HP/LP icon is now larger.

David Clarke [21030085++] · Wed, 25 Jun 2014 22:00:51 -0300

Re: BCR2000 Programmer Overlays

... having the WAVESHAPE assigned to a pot allows to see which shape is currently in use thanks to the pot's LED. We lose that info in your current layout...

... I'm not following you here, the wave shape's waveform are selected using the toggles on the lower right bottom, if the toggle LED is lit then that is the waveform you are using. Same as with the SWEEP waveforms...

Jamie - not advocating one way or the but, but just to clarify this discussion point - it is perhaps a subtle difference between the use as a 'programmer' and an 'editor.'

There is no question that pressing the buttons will cause a control change to be sent - and after pressing the button, the LED on the button will illuminate to indicate what parameter choice is currently active.

That said - the Chroma with CC+ allows patch parameter 'talkback' to the BCR2000 - so if you change the patch on the Chroma, the encoder rings of the BCR2000 will automatically update to display the values as they appear in the currently selected patch on the Chroma. So - if you're looking to 'edit' a patch vs. create one from scratch, then this is a very handy feature since you'll already know what the 'current' setting of a parameter is before you've attempted to change it.

Unless there's a way to program the buttons differently, this 'talkback' feature falls down with the buttons since going to a new patch will result in all the button LEDs showing as 'off' - giving no feedback in terms of how the osc or sweep waveshapes are set in the current patch. If those features are duplicated on a knob, then you do get the feedback of the parameter value in the encoder ring.

(Of course, if there's a way to program the BCR2000 so that it will update the button LED status based on received MIDI CC messages from the respective controller source - then this concern goes away).

David Clarke

Jamie Downing · Wed, 25 Jun 2014 20:58:12 -0500

Re: BCR2000 Programmer Overlays

Thanks David,

The input has been very welcomed, thank you all. Now I'm following you. Not sure if the buttons will light up after receiving a talk back buffer send. The Kiwi upgrades I work with will do this same thing, same with the Dave Smith products.

But in the big picture we are only talking about 4 settings for the OSC waveform and 16 for the Sweep waveform. I would think having a toggle switch and direct visual reference while programming would far out weight counting lighted led dots on a pot encoder. Plus, you should be able to hear that the waveforms of each that are in use for the current program. Meaning, I don't think I would always remember LED 5 on an encoder pot equals one particular waveforms if you follow me.

Thanks,
Jamie

Jamie Downing · Wed, 25 Jun 2014 22:24:19 -0500

BCR2000 Programmer Overlays - Pricing

Hey Everyone,

I have pricing available.

$45.00 or $80 for two.

• Shipping to US is 2-3 day service for $6 USPS
• Overseas 6-10 days $25.00 or $13 for parcel post

NOTE: I cannot guarantee how long parcel post will take, for example while I was in New Zealand working on the Kiwi-106 project it took almost two months for my family to receive a letter back in the states.

I wish remind everyone these are expensive to produce in such small quantities but I am able to get better deal since I lump them in with my other products to save everyone some money. Example, to create just one would cost $175.00. But I know you will be extremely happy with this small investment into your Chroma by having a professional quality and proper BCR programmer overlay.

If you would like to pre-order you can PayPal to [email address removed] but I do not require anyone to do this. I need to rework my website checkout since most are buying full keyboard overlays, otherwise it would charge you too much for shipping.

We are still not 100% done with the layout but I feel we are 95% there and hopefully we can get it finalized by Monday the 30th and start shipping by July 10-15th.

Thank you all for asking me to join the Chroma cause, I am honored. And after looking at it in more in depth I think it's on my short list of synths I would like to own in the near future for sure! Very cool machine! I love your dedication to a classic.

Cheers,
Jamie

Jamie Downing · Thu, 26 Jun 2014 10:48:43 -0500

Re: BCR2000 Programmer Overlays

Attached is revision 6. I think this will work for everyone's needs. We have the enough empty encoders so I added the Sweep Waveform and OSC Waveform to the Pot #2 & 3, see JPG so you can still get visual LED display. BUT we can still keep the toggle buttons. Note: When I programmed the buttons and then the pot encoder to the same CC # on the BCR for testing, they update each other as you change values. I have yet to see if the toggle buttons will update like the pots when you switch programs on a synth that can talk back. I can test this with my Kiwi-106 and Mopho, but not 100% positive they are same since they both use NRPN and/or CC commands. If someone would like the test this as well that would be great.

I also added the Arp logo as requested.

I'm on a 3-day vacation this weekend but will available Monday evening. Please let this latest revision soak it, and visualize yourself using it. As a synth panel designer I think you will find this layout works well and stays as true as possible to how the Arp team intended.

Cheers,
Jamie

Philippe [21010227] · Thu, 26 Jun 2014 17:51:11 +0200

Re: BCR2000 Programmer Overlays

Hi Jamie, answers below :

On Thu, Jun 26, 2014 at 1:40 AM, Jamie Downing wrote:

FSW MODE toggle is a good idea per se BUT I still feel putting the waveshape controls among the lower pots is not working. For many reasons: 1. there are 4 parameters controlled by MOD1, 2 or 3 (PITCH, WAVESHAPE, CUTOFF, VOLUME). They are present with the same layout in the upper part but one ! Why change 1 among those 4 ? If you look again at the parameterchart they are all together for a reason: the internal logic of the instrument as designed by ARP engineers.

Looking at the block diagram, Pitch and Wave Shape make up the OSC (in conventional terms). This is where the old arrangement makes even less sense since Pitch is it's own pot bank and wave shape another pot bank (there are 11 total parameters to make up the entire OSC and only 8 available pot encoders per bank)

To program the entire OSC (Pitch + Wave Shape) simply click on the green Pitch encoder pot bank and you now have them all grouped in the same area. And you see it flows exactly how Arp intended and in order. Whats missing on the old layout is the ability to modulate the waveform, thats completely omitted, you would only be able the modulate the pitch (1,2,3)

Not sure what you mean "missing the ability to modulate the waveform, that's completely omitted" you mean the width of the waveshape ? It was assigned to upper pot#2. You do have a point here regarding workflow, this could be a plus, however - as you know - you then loose that waveshape pot and therefore - as David explained again - the readability of the waveshape chosen (unless, again, the 4 lower buttons LEDs could be updated which doesn't seem to be possible so far)

As a avid programmer this provides a better workflow. Also note the pot #1 could still assigned to RES even in the Pitch bank, allowing you to adjust the resonance WHILE editing the entire OSC, very handy in programming terms, this would be impossible if the wave shape was in the top row of encoders. Follow me?

See example 1 attached.

So yes I think I follow you but it's a win here, lose there and the former layout still felt more logic and therefore intuitive in practice to me. As you say below: this is where something has to give, and I think if 2 confirmed users such as David and Matt organised it that way it certainly because it makes sense, trust them + me ! :) The Control bank is a good idea. It could be added in sequence to the waveshape bank. As you understood by now this is the major change I would ask for, I can be more flexible on the rest :)

2. as David explained in his last email, having the WAVESHAPE assigned to a pot allows to see which shape is currently in use thanks to the pot's LED. We lose that info in your current layout.

I'm not following you here, the wave shape's waveform are selected using the toggles on the lower right bottom, if the toggle LED is lit then that is the waveform you are using. Same as with the SWEEP waveforms.

I understand you follow us now that David re-explained right ?

3. Because FSW Mode is on a toggle you also lose the visual information of which is currently applied.

Well, this is where something has to give. Is programming the sound the main goal of the programmer or being able to change the foot switch? This could be easily access the conventional way directly on the Chroma itself.

Please see Example 2: You will see the two most important sound parameters are on the lower level, since this effects how the OSC is routed it's only natural it be next to the Wave Shape pots. For Patch routing LED display, simply set the BCR to a range of 0-15 and the pot will only go to 15 and display one more LED dot for each setting. So for example if you wanted Filter FM routing LED 12 would be lit, the 12th showing it's setting 12.

4. Same thing for Outputs. and maybe others I forgot. So you see, you break the logic of the instrument's synthesis architecture AND lose at least 3 infos.

Output is on a pot encoder, so that LED information will still be present. Please remember I'm working with the physical limits of the BCR itself and not intentionally breaking Arp's design arch. I don't feel selecting which output you are sending audio to outweighs the overall intent of the programmer. It is present and again is more of a global parameter that could also be accessed on the Chroma itself. I personally would remove this all together and make it a click toggle in favor of keeping Pot #1 always be filter res no matter what bank you are using.

No worries, I'm know for sure you are not intentionally breaking ARP's design, I'm just explaining what i feel is generated by that change. And I totally agree that Output or FSW Mode selection is secondary. However keeping RES pot on all banks is definitely not so important for me.

Philippe [21010227] · Thu, 26 Jun 2014 17:53:29 +0200

Re: BCR2000 Programmer Overlays

Hi Jamie,

I just sent you a reply to yesterday's email. Of course they are comments to version 5 not this new one, I'll get back to you as soon as I read your email in detail.

Cheers,
Phil

Lawrence Eldridge [21010100] · Thu, 26 Jun 2014 17:23:26 +0100

Re: BCR2000 Programmer Overlays

Hi Jamie,

Really liking the latest revision (revision 6) - especially the mod section which looks logical to me. Don't worry about answering this until Monday if you're off for the weekend now but I've got one question about the Mod toggle buttons and the connecting lines that run from the button to the MOD labels (MOD 1 SELECT, MOD 1 DEPTH, etc. etc.). Now I don't own a BCR2000 so if I'm wrong on this then someone please tell me, but I noticed that you've only got the CUTOFF line running upwards to the knobs at the very top, but shouldn't the same happen for PITCH and VOLUME? Its a minor thing but if CUTOFF, PITCH, and VOLUME are all tied to those knobs at the top I've kinda want to have the representative line heading up there too.

Lawrence Eldridge

Jamie Downing · Thu, 26 Jun 2014 11:46:03 -0500

Re: BCR2000 Programmer Overlays

Hi Lawrence,

Yes you are correct, I can add those lines to show they go the top encoders. Good idea.

Thanks,
Jamie

Jamie Downing · Thu, 26 Jun 2014 11:54:05 -0500

Re: BCR2000 Programmer Overlays

Like this?

Maybe this will help others as well.

Lawrence Eldridge [21010100] · Thu, 26 Jun 2014 17:58:28 +0100

Re: BCR2000 Programmer Overlays

Perfect!

Matt Thomas [21010021] · Thu, 26 Jun 2014 18:24:18 +0100

Re: BCR2000 Programmer Overlays

I’ve stayed out of the revision discussions as I’m sure the community will thrash out a good version – one thing I will say though: once the template is finalised it would make a lot of sense for a testing period where someone actually sets up a BCR preset that reflects the projected layout. What makes sense visually may not in-use, or their may even be problems implementing the intended layout in the BCR editor. Even a few days spent trying it out could make all the difference.

On a footnote - I’m going to rather lazily rule myself out of this job on the grounds that I haven’t used the BCR editor since the day I finished the original Chomatrol template some years ago & don’t recall a single thing about the process. Hopefully there are others in the group who’ve wrestled with it more recently.

Jamie Downing · Thu, 26 Jun 2014 14:32:37 -0500

Re: BCR2000 Programmer Overlays

If someone can give me the CC info I can program the BCR to the new layout on Monday evening and then send the SysEx file to whomever wants to test it?

Thanks,
Jamie

David Clarke [21030085++] · Thu, 26 Jun 2014 17:15:04 -0300

Re: BCR2000 Programmer Overlays

... If someone can give me the CC info ...

The CC cross reference is in the second table here: The Chroma CPU Plus (CC+): User's Guide - MIDI Controllers Map (e.g., the table with the "MIDI CC#" column headings)

If easier, you might just want to modify/edit the data in BCR2000_RhodesChroma.txt

David Clarke

Philippe [21010227] · Fri, 27 Jun 2014 00:04:15 +0200

Re: BCR2000 Programmer Overlays

Hi Jamie,

Thanks for this new layout. Definitely some improvements. The ARP logo is a nice touch !

Major suggestion:

WAVE SHAPE bank back where it was, per all the reasons extensively detailed in previous emails. The "exploded" WAVESHAPE bank still gives me the feeling the layout is somewhat scattered when I look at it. Again, I don't think we should try to make it look like any other conventional synth controller but rather like: the Chroma controller.

I understand you didn't find it "natural" or "intuitive" as it was initially since you were coming from other synths practice but I think we can agree that if David and Matt felt comfortable with that layout plus nobody complained about it it's because it does make sense from the Chroma perspective.

You added many improvements already and they are really appreciated. You are asking for feedback, here you have mine. Of course in the end you will do what you decide to do.

If there is any graphic issues created by that we can find solutions I'm sure.

Minor suggestions:

1. 1. If these pots remain I would rather name the SWEEP WAVEFORM pot as SWEEP WAVESHAPE as on the parameterchart.
2. 2. and rename the new WAVEFORM bracket above the 4 buttons WAVE SHAPE as on the parameterchart.
3. 3. Totally agree with Lawrence's comment. Thanks for the change.

Phil

David Hobson [21030506] · Fri, 27 Jun 2014 16:27:23 -0400

Re: BCR2000 Programmer Overlays

Hello Jamie,

I am in agreement with Phil a on his latest suggestions. I believe this project should remain true to accepted Chroma terminology. So far it is looking very nice, and with a few more adjustments it could be great.

I also believe it would be useful to provide a printout of the draft that corresponds with the new BCR template so that those of us who use the BCR can give it a trail run.

You have to keep in mind that there are technicians who do not contribute to the list who may be interested in this overlay as well.

Thanks for all of your efforts,

David.

David Hobson [21030506] · Fri, 27 Jun 2014 16:37:10 -0400

Re: BCR2000 Programmer Overlays

If someone can give me the CC info I can program the BCR to the new layout on Monday evening and then send the SysEx file to whomever wants to test it?

Hello Jamie,

I definitely would like to test the SysEx file. You have a volunteer!

I will email you so you can add me.

Thanks,

David.

Trying to get #0501 running

Eric Frampton [21030501] · Tue, 24 Jun 2014 14:39:23 -0400

Hi All -

TL;DR: I’m having trouble with (I think) the I/O board. No response from leaf switch boards or voice boards. Just re-burned the Keyboard processor EPROM thinking that might help the leaf switch problem, and now the upper row of membrane buttons, the numeric display, and half the alphanumeric display is dead. New PSU installed, voltages are good. Not sure where to begin troubleshooting.

The long version:

As I mentioned in an earlier email, I’m the recently new owner of Chroma #21030501. I’d originally posted with the notion of getting boards made to replace an acid-damaged voice board. Doug Terrebonne [21030114] and William Santana [21030244] came to the rescue for me on that one.

There is acid damage on the right hand leaf switch board, but it only seems to have wiped out one trace (which I was able to patch). There was also acid damage on the voice motherboard, and I was able to clean up or replace everything that was visually messed up, but that’s as far as I could take that at the moment.

Meanwhile, my CC+ board came in from David Clarke [21030085++] and I installed it without incident.

I had previously installed the SPSU and calibrated the main trim on the I/O board for 0.000V. All the voltages are spot-on.

Upon powering the unit up, I could verify that the CC+ was working - at least, it would receive MIDI data and make a dot on the numeric display, and make the MIDI activity light on the little I/O box flash. However, there was no response from the keybed (no flickering of the display, nor flashing of the MIDI activity light), and no voices will tune. There’s no output on either the main out or individual outs, after switching between all 4 of them.

There were crystals growing on the keyboard scanner EPROM, so, thinking that EPROM might have failed and be causing the keyboard not to respond, I removed it and burned a fresh one. Tried a couple of different PROMS, but I get the same result:

Now, when I boot the unit, in addition to the voices and keyboard being dead, the entire upper row of membrane buttons is dead, the numeric display is dead, and the left half of the alpha display is superimposed on the right half. I.e., instead of seeing this:

01234567

I see this:

8983 (first four spots blank, those characters superimposed on the last 4)

or, instead of (say):

P03 1.0

I see this:

P03.0 (with the segments of the 1 brighter underneath the 3)

If I trigger the unit via MIDI, the MIDI activity light on the I/O box still flashes, but the decimal point on the numeric display doesn’t flash anymore.

For testing of this latest ailment, I have the keyboard connected to the I/O board, but not the voice motherboard (it doesn’t seem to matter whether the motherboard is connected or not at this point, so I’m leaving it isolated).

Z15 (74LS374) on the I/O board is running pretty warm compared to the rest of the board. I had a spare one to swap in, but it didn’t make any difference.

Any ideas where to begin?

Thanks,
Eric

Paul DeRocco [21030230] · Tue, 24 Jun 2014 12:18:47 -0700

From: Eric Frampton

Now, when I boot the unit, in addition to the voices and keyboard being dead, the entire upper row of membrane buttons is dead, the numeric display is dead, and the left half of the alpha display is superimposed on the right half. I.e., instead of seeing this:

01234567

I see this:

8983 (first four spots blank, those characters superimposed on the last 4)

The problem would be either in line B2 on its way to Z12-12, or in the corresponding output from Z12-10 to Z13-13. If it's stuck high, then rows 0..3 in both the display and switch matrix will be redirected to rows 4..7. If you see Z12-12 going solidly to ground some of the time, just like the other inputs, then replace Z12. If you don't see it moving, then you'll have to trace back to the flex strip connectors from the CPU board to see where the break is.

Eric Frampton [21030501] · Thu, 26 Jun 2014 00:20:23 -0400

Sure enough, Z12-12 looks fine, and Z12-10 is stuck high. I’ve got a new chip on order (you’d think in a metro area of 10M+ people there’d be more than one electronics shop. Alas, no). Details as they emerge...

Thanks, Paul!

e

Eric Frampton [21030501] · Fri, 27 Jun 2014 17:28:49 -0400

While I’m waiting a replacement LS175 to arrive for the control panel, I’ve started poking around the key switch boards. Despite some direct battery acid damage, for the most part they seem to be OK, except that the computer doesn’t recognize anything being played.

Tracing all the way back up through the CPU, I’m seeing data on all the lines that are (I think) supposed to have data, and the ones that are supposed to be high are pinned high. There a couple of things that look weird to me, though: on the right board, Z1-6 (LS145) is stuck at 3V. Also, I know that Z1-12 is supposed to stay high, but I’m only seeing 4V there - is that right?

Other thoughts, ideas?

e

William Santana [21030244] · Fri, 27 Jun 2014 14:49:04 -0700

Digital ICs stop function at about 4.7 volts. If you are not getting a good 5 volts on the power pin or there is something holding a line from reaching it's full 5 volt high state, then it will either not function or it will not trigger the component down stream.

David Clarke [21030085++] · Fri, 27 Jun 2014 22:10:40 -0300

... I’ve started poking around the key switch boards. Despite some direct battery acid damage, for the most part they seem to be OK, except that the computer doesn’t recognize anything being played...

Eric - just a quick check - in an earlier note it was mentioned that:

... there was no response from the keybed (no flickering of the display, nor flashing of the MIDI activity light), and no voices will tune. There’s no output on either the main out or individual outs, after switching between all 4 of them. ...and no voices will tune

It is the case that if the voice fail auto-tune, then they'll be removed from any voice-assignment. That means if all voice fail auto-tune, that the Chroma wouldn't attempt to make any sound with the cards. You could attempt to force them to play anyway (even if they'd otherwise fail tuning) with [Set Split][31] (You may have already done this - but I just wanted to make sure as otherwise it is correct that no keyboard behaviour would seem apparent).

The MIDI activity light is only intended to show receipt of external MIDI data - and so it is not expected to light up for outgoing MIDI.

Also, as there are diffenet things that could squelch the audio output (volume pedal, broken wire, etc.) perhaps the best way to try to detect keyboard activity by the CPU will be to:

• put in a couple of voice boards
• issue set-split 31, to have them be used (even if they failed auto-tune).
• set up a scratch patch (set split 39) [so as to rule out odd behaviour of a 'note gate' pedal setting]
• see if you see anything in voice-watch mode [set split 37]

... on the right board, Z1-6 (LS145) is stuck at 3V.

If you're looking a 'scope vs. a meter - then 3V wouldn't be expected (nor would it be expected to be static).

Paul DeRocco [21030230] · Sat, 28 Jun 2014 09:40:16 -0700

From: Eric Frampton

Tracing all the way back up through the CPU, I'm seeing data on all the lines that are (I think) supposed to have data, and the ones that are supposed to be high are pinned high. There a couple of things that look weird to me, though: on the right board, Z1-6 (LS145) is stuck at 3V. Also, I know that Z1-12 is supposed to stay high, but I'm only seeing 4V there - is that right?

Are you looking with a scope, or measuring with a meter?

Assuming you've got a scope, Z1-12 isn't supposed to stay high. If the keyboard scanner is running, you should see square(ish) waves of different rates on all KA lines. Z1-12 on one board should be the inverse of Z1-12 on the other board. And guess what: the KA lines come from another 74LS175 on the I/O Board.

As to Z1-6, this should look like any of the other Z1 outputs. If it's stuck, then there could be a board short, or the chip itself could be bad.

Eric Frampton [21030501] · Mon, 30 Jun 2014 14:27:28 -0400

On Jun 27, 2014, at 9:10 PM, David Clarke wrote:

Eric - just a quick check - in an earlier note it was mentioned that:

... there was no response from the keybed (no flickering of the display, nor flashing of the MIDI activity light), and no voices will tune. There’s no output on either the main out or individual outs, after switching between all 4 of them. ...and no voices will tune

It is the case that if the voice fail auto-tune, then they'll be removed from any voice-assignment. That means if all voice fail auto-tune, that the Chroma wouldn't attempt to make any sound with the cards. You could attempt to force them to play anyway (even if they'd otherwise fail tuning) with [Set Split][31] (You may have already done this - but I just wanted to make sure as otherwise it is correct that no keyboard behaviour would seem apparent).

I’ve been using Set-Split 31 for all of this, yessir.

The MIDI activity light is only intended to show receipt of external MIDI data - and so it is not expected to light up for outgoing MIDI.

Got it. I was confused.

Also, as there are diffenet things that could squelch the audio output (volume pedal, broken wire, etc.) perhaps the best way to try to detect keyboard activity by the CPU will be to:

• put in a couple of voice boards
• issue set-split 31, to have them be used (even if they failed auto-tune).
• set up a scratch patch (set split 39) [so as to rule out odd behaviour of a 'note gate' pedal setting]
• see if you see anything in voice-watch mode [set split 37]

If I trigger from MIDI, I can see all the voices trying to fire in voice-watch. But if I play any keys locally, there’s nothing. (I’ve double-checked that Local is On).

I still don’t have audio from the voice cards - just digital hash. But I want to get the keyboard working before I tackle that, as there’s acid damage on that motherboard too. One problem at a time...

... on the right board, Z1-6 (LS145) is stuck at 3V.

If you're looking a 'scope vs. a meter - then 3V wouldn't be expected (nor would it be expected to be static).

I’m looking at a scope, and the line is stuck at 3V. All the other even output lines are a solid 5V, and the odd lines hover around .25V (with a waveform that seems to be exactly 1uS)

The 4 input lines to Z1 aren’t doing much - Z1-12 is roughly 4V high, 13, 14, 15 are all showing that same (roughly) .25V 1K scanning waveform as the odd-numbered outputs. No square waves or hint of actual data being sent to them.

Z1 on the left-hand board is the same, except that line 12 is low, and pin 6 there isn’t stuck at 3V.

Paul DeRocco [21030230] · Mon, 30 Jun 2014 11:38:50 -0700

From: Eric Frampton

I'm looking at a scope, and the line is stuck at 3V. All the other even output lines are a solid 5V, and the odd lines hover around .25V (with a waveform that seems to be exactly 1uS)

The 4 input lines to Z1 aren't doing much - Z1-12 is roughly 4V high, 13, 14, 15 are all showing that same (roughly) .25V 1K scanning waveform as the odd-numbered outputs. No square waves or hint of actual data being sent to them.

Z1 on the left-hand board is the same, except that line 12 is low, and pin 6 there isn't stuck at 3V.

Do you have any evidence that the 8039 keyboard scanner CPU is running? It's possible that its EPROM has faded, and it is crashed. If you have an EPROM eraser and programmer, you could try reprogramming it. The code is available on the site.

Eric Frampton [21030501] · Mon, 30 Jun 2014 14:47:42 -0400

On Jun 28, 2014, at 12:40 PM, Paul D. DeRocco wrote:

From: Eric Frampton

Tracing all the way back up through the CPU, I'm seeing data on all the lines that are (I think) supposed to have data, and the ones that are supposed to be high are pinned high. There a couple of things that look weird to me, though: on the right board, Z1-6 (LS145) is stuck at 3V. Also, I know that Z1-12 is supposed to stay high, but I'm only seeing 4V there - is that right?

Are you looking with a scope, or measuring with a meter?

Looking with a scope.

Assuming you've got a scope, Z1-12 isn't supposed to stay high. If the keyboard scanner is running, you should see square(ish) waves of different rates on all KA lines. Z1-12 on one board should be the inverse of Z1-12 on the other board. And guess what: the KA lines come from another 74LS175 on the I/O Board.

I tried swapping out that LS175 at Z35, but am seeing the same thing with the new one - square-ish waves going into the 4 inputs, but solid 4.5V showing up on pins 2 and 7, and .25V sort of ping or ringing at 1KHz on pins 10, 14, and 15. Nothing resembling square waves there.

As to Z1-6, this should look like any of the other Z1 outputs. If it's stuck, then there could be a board short, or the chip itself could be bad.

gotcha.

e

Paul DeRocco [21030230] · Mon, 30 Jun 2014 14:29:21 -0700

From: Eric Frampton

I tried swapping out that LS175 at Z35, but am seeing the same thing with the new one - square-ish waves going into the 4 inputs, but solid 4.5V showing up on pins 2 and 7, and .25V sort of ping or ringing at 1KHz on pins 10, 14, and 15. Nothing resembling square waves there.

Well, if you trigger on the rising edge of Z35-9 with one probe, and look at the various D lines, you should be able to verify that they all have 0 at that instant half of the time and 1 the other half of the time. If that's true, then you should see those sampled signals appear at the outputs.

If you don't see short active-low pulses on Z35-9, then see my other message about the CPU perhaps being crashed.

Another possible issue: even if the keyboard scanning CPU is still running, if there's a problem in the interrupt logic between it and the main CPU, it could freeze up on the first key press. Make sure you look at the signals without touching any keys after powering up.

Ser No: 21030620 @ ebay

Michael Zacherl [21030253] · Wed, 25 Jun 2014 15:26:23 +0200

[eBay item #171366914835]

;-) m.

Starting bid was €8,000.00, and the auction ended July 4 without a sale. From the description: "Excellent Condition with Midi Interface (KMX) Incl. all Pedals, Flight Case, Original manuals! Original Rhodes Pressure Keys option built in + Original cooling fan built in! The unit is fully working (all cards are OK), Power supply is original, only the capacitor was changed one Year ago!" See 21030620.

TouchOSC iPad

Buddy Casino [21010137] · Sat, 28 Jun 2014 09:54:34 +0200

Hi everyone,

I've just got the CC+ put into my Chroma. Beautiful!

Now, I would like to use the Chroma iPad Editor. Does anybody use that thing, (is it fun to work with) and if so, How do I get that program into my iPad and running?

The TouchOSC I got installed already.

What else do I need?

Is there somewhere a description how to do it, and where to get it. ?

Thanks in advance, Buddy

David Clarke [21030085++] · Sat, 28 Jun 2014 21:56:27 -0300

The instructions are outlined on Matrix's page: New Rhodes Chroma TouchOSC Templates Complete.

These generally expect o use a Mac in the loop too.

If you are just looking to use the iPad alone, then there's this discussion: TouchOSC iPad Template Modifications by Leon van der Sangen.

A quick set of summary instructions for that:

1. Install TouchOSC on the iPad from the Apple App Store
2. Get some sort of MIDI interface hooked up to the iPad (the Line 6 MIDI Mobilizer II seems to do the trick, as does the ESI MIDIMATE 2 - and I'm sure there are others too).
3. Download and install the TouchOSC editor on your computer (be that a PC, Mac, etc.) via the 'Download' section of the page here: TouchOSCO.
4. Download the Chroma touchosc template and place it with your TouchOSC editor installation on your computer. The template is available here: TouchOSC iPad Template Modifications by Leon van der Sangen.
5. To actually get the template on the iPad, it seems that the easiest way is to transfer it there from the editor (although you may also just be able to drag and drop it there with iTunes file transfer too).

Assuming you're using the editor, then on the computer, with the TouchOSC editor open, click on the 'Sync' button.

On the iPad, open TouchOSC. Go into the "Layout" selection. Select "Add". It should look for and find the 'host' associated with your TouchOSC editor installation. When you select the host, it should sync/download anything new. You should now see the Chroma layout in the Layout menu.

In terms of the CC+, you'll want to make a few configuration changes - to ensure that the controllers line up. The same general instructions used for the BCR2000 apply - namely the 'Configuring the Chroma' steps from Behringer BCR2000: BCR2000 Set Up

To recap, those are:

• [Set Split 36]
• Select [P6] - Ensure set to “On”
• Select [P18] - Select “CUSt”
• Select [P20] - Move “Parameter Control” slider
• Select [P24] - Select “Prog”
• [Set Split 36]

Depending on how you'd like it to operate, you might also want to have:

[Set Split 36][P30] (Auto-Send MIDI CC) set to "On" vs. the default of "Off"

If you run into difficulties, let the folks on the Chroma list know, as I expect that someone with an iPad (and/or someone already up and running) will be able to assist.

David Clarke

Buddy Casino [21010137] · Sat, 28 Jun 2014 21:53:59 +0200

OSC iPad Editor

Hi,

does anybody work with the TouchOSC iPad Template and can tell me where I could get it and how to install it?

Thanks, Buddy

Rhodes Chroma #21010100

Lawrence Eldridge [21010100] · Mon, 30 Jun 2014 09:30:14 +0100

By chance I saw on the Web Reviews page an entry for Amazona.de [Blue Box: Rhodes Chroma] and realised that I took those photos for Bluesynths. Entry is here: 21010100.

Originally this unit was owned by Glen and I can now confirm that this is the machine I bought in 2005 from Music Control (managed to get the price down to £1250). In fact when I opened it up I could see where the old PSU had blown from Glen's past experience. Paul mentioned that it had no MIDI converter, but I can confirm that it actually had a Kenton MIDI retrofit, as well as the foot pedals. However the retrofit was limited so I purchased the CC+ and installed it. Unfortunately, soon after this the voice cards started to cascade fail with at least 1 card failing each time, so I sent it back to the engineer at Synth Service Repair (previously Music Control) in 2008. Whilst in his workshop it has had the new SPSU kit installed (to stabilise the cascade fail issues), removal of the old retrofit, the CC+ card firmware has been updated, and the avil case re-foamed. I'm due to have it returned in a few weeks time and all problems have been fixed (fingers crossed). I intend to use the BCR2000 with Jamie's graphical overlay if all goes well.

All the best,
Lawrence Eldridge