Rhodes Chroma Polaris group photo

Yahoo Groups archive

Rhodes Chroma Polaris

Archive for chromapolaris.

Index last updated: 2026-03-30 01:08 UTC

Thread

Reprogramming the Polaris -- wish list

Reprogramming the Polaris -- wish list

2011-04-03 by rob_ocelot

I've noticed recently that a lot of the older CPU-controlled synths are getting upgrades in both software and hardware. Off the top of my head I can name the Roland Jupiter 4/Promars, Jupiter 6, JX-3p/MKS-30, JX-10/MKS-70, Sequential Pro-One, Korg DSS-1, and Polysix.

Would the Polaris benefit from a similar tune up? How easy/difficult would it be to disassemble the 80186 code using a standard Intel disassembler? Is there any documented Polaris code anywhere?

Debugging would be a hassle unless we could write a suitable Polaris emulator (ha!) or perhaps use a hardware EPROM emulator like the Southern Cross.

I'll just note for the record that I *love* the Polaris however it does have some characteristic functional quirks. Would removing or changing these things make it less of a Polaris?

As for what enhancements I'd like to see (both software and hardware) here's my list. Feel free to chime in:

*Slider 'snap' mode toggle:

Moving a slider after changing a patch causes the slider value to 'snap' to the value of the physical slider position which can be somewhat jarring in a live concert situation. One way around this would be to hold the slider value at the current patch value until the physical slider position sweeps though the value in the current patch. I can see merits in both approaches and would like to preserve of the original Polaris functionality if possible.

*Different glide/portamento modes:

Currently the only way to activate glide is via footswitch. It would be nice in some situations to activate it and keep it activated by a membrane panel button combination.

*Expander mode:

This would require a rewrite of how the Polaris allocates voices. Essentially you would hook another Polaris up via MIDI (or Chroma interface) and select expander mode which would grant 12 voice polyphony by selectively sending certain notes to the other Polaris and suppressing others that would normally be sent via MIDI OUT. May be of limited usefulness given that the Polaris already has a damn good voice stealing routine that is very good at hiding the 6 voice polyphony.

*Reverse pitch bend toggle:

Current pitch bend lever behavior is the opposite of what most synth makers have adopted (towards player = pitch down, away from player = pitch up). Reversing this may require hardware modification which makes retaining original functionality more complicated.

*Oscillator Mix:

The Polaris has both oscillators at 100% volume with no way to adjust their levels. Definitely a hardware mod.

*Full Resonance Sweep:

Currently the Polaris has 8 levels of filter resonance provided by a CEM3372. The 3372 however is capable of the entire spectrum of resonance values. Why this method was chosen is unclear but I suspect it might have to do with what is actually pleasing to the ear. As a comparison the Akai AX-60 uses a CEM3394 with the full resonance spectrum -- sweeping through the resonance is very aliased, harsh, and produces a lot of unpredictable (and some would say not pleasing) sounds (this might be an apples vs oranges comparison). Changing this
would require some pretty extensive hardware modification.

*Auxiliary Display:

Kind of a pie-in-the-sky idea but I thought I'd throw it out there. What I envision is an external LCD display with an onboard microcontroller that plugs into the Chroma interface. This would display currently edited parameter names and their values or things like MIDI channel selection that are currently displayed as LED flashes on the membrane panel. Likely not a feasable idea due
to power supply requirements (I don't think the Chroma interface would provide the needed power).

*Aftertouch Control:

Another pie-in-the-sky project. The Polaris MIDI spec responds to both key and channel pressure (channel aftertouch) and routes this information to pedal parameters. It would be an interesting experiment to replace the Polaris keybed with an aftertouch capable one. The easiest way to do this would be to keep the controller keyboard electronics intact and sacrifice the Polaris MIDI IN. If my
reading of the MIDI documentation is correct the Polaris is theoretically capable of receiving polyphonic aftertouch though I'm unsure if the sound engine is capable of dealing with the high volume of data poly aftertouch generates.

Re: [chromapolaris] Reprogramming the Polaris -- wish list

2011-04-03 by David Clarke

Some thoughts...

> How easy/difficult would it be to disassemble the
> 80186 code using a standard Intel disassembler?

It should be no harder or easier than any other disassembly project.
You would take the binary images from the PROMS, combine to make a
consolidated image and then run through a disassembler.

You would need to identify things such as the reset vector location, and
start adding symbols for jumps, etc. - until you can get to a version of
the code which you can otherwise identify what parts of it do.

I've always had a irrational dislike of x86 assembler, so I've never
really had too much interest in this myself.

> Is there any documented Polaris code anywhere?

Not insofar as I know.

> *Slider 'snap' mode toggle:

Depending on the end goal, it may be easier to implement this with an
external knob/controller interface. The external device can query the
Polaris to find out the current setting of the knob and will then only
edit from that point onwards (e.g., you can use a rotary encoder vs. a
slider where its position has signficance).

That having been said - if you had a fully disassembled image - and
assuming there's space left in the PROMs, the "don't start to change
until you're at the old value" idea doesn't seem like it would be too
difficult to achieve.

> *Expander mode:

I'd expect this to be the toughest to achieve (well).

> *Reverse pitch bend toggle:

Lever 1 and Lever 2 (as well as the Pedal) are read by the CPU as an
analog voltage (e.g., it comes into the CPU via an ADC). That means, in
software, you could choose to handle the data however you wanted. You
could reverse the sense of the data - or, you could even choose to
assign those levers (or the pedal) to modulate different elements of the
patch.

> *Oscillator Mix:
>
> The Polaris has both oscillators at 100% volume
> with no way to adjust their levels. Definitely a hardware
> mod.

Unless there was a desire to make this only a HW setting (e.g., a knob
to adjust mix), this would likely be both a HW and SW mod. The HW mod
would be to allow one of the signals to be attenuated (vs. the other) -
the SW mod to allow some way to control this and to make it a 'storable'
patch parameter.

> *Full Resonance Sweep:
>
> Currently the Polaris has 8 levels of filter resonance provided by a
> CEM3372. ... Why this method was chosen is unclear but I suspect
> it might have to do with what is actually pleasing to the ear...

Like the Rhodes Chroma, the resonance is set via 3 weighted resistors.
The processor can individually control whether these are on or off. The
3 inputs lead to 3 bits of control - or 8 discrete resonance steps. The
top-most setting is intended to allow self-oscillation.

To allow fully discrete control would require HW modifications and well
as SW modifications - which would effectively use a DAC to drive the
resonance on the chip vs. the three discrete SW bits.

> *Auxiliary Display:
> What I envision is an external LCD display with an
> onboard microcontroller that plugs into the Chroma interface.
> This would display currently edited parameter names...

This actually wouldn't be difficult to do. All that you would need is a
small controller (perhaps a Microchip PIC), a few resistors and a
low-power LCD. I suspect the Chroma Port would have sufficent 'extra'
power for this. The 'effort' on this one would be writing the PIC code,
so that the text which is shown will be what you want to see for the
parameters.

We built something similar to the Rhodes Chroma
(http://www.rhodeschroma.com/?id=cpuplusalphadisplay); however, prior to
bringing the code into the Chroma's CPU board similar code was running
externally (via the Chroma Port) in a knob box:

http://www.rhodeschroma.com/content/chromaknob/chromaknob5.jpg

A later incarnation of that box used a PIC and a four-line LCD display.

The Parallax Model 27979 display was a good compromise for price and
power consumption (and ease of interfacing).

David C.

Re: Reprogramming the Polaris -- wish list

2011-04-04 by Jesse

(sent yesterday from wrong address)
 
Interesting idea... I'd join in and take one of the coding efforts if someone gets it to the point where we can view the existing code in an acceptable language... C seems possible but it would likely need refactoring to be readable.  I don't know much about how to disassemble, etc. but I can code, especially given a body of working code.

--
http://amoebafunk.com
http://metameme.org
http://apogaea.com

Re: [chromapolaris] Re: Reprogramming the Polaris -- wish list

2011-04-05 by Thomas Rizzi

Does anyone know what language the Chroma operation system is written in?
Do we have to look at a specific assembly language?

I am VERY interested in this project.
Thanks
Thomas Rizzi
RizziTech



From: Jesse <jesse@...>
To: chromapolaris@yahoogroups.com
Sent: Mon, April 4, 2011 8:04:34 AM
Subject: [chromapolaris] Re: Reprogramming the Polaris -- wish list

 

(sent yesterday from wrong address)
 
Interesting idea... I'd join in and take one of the coding efforts if someone gets it to the point where we can view the existing code in an acceptable language... C seems possible but it would likely need refactoring to be readable.  I don't know much about how to disassemble, etc. but I can code, especially given a body of working code.

--
http://amoebafunk.com
http://metameme.org
http://apogaea.com

RE: [chromapolaris] Re: Reprogramming the Polaris -- wish list

2011-04-05 by Paul D. DeRocco

> From: Thomas Rizzi
>
> Does anyone know what language the Chroma operation system is
> written in?
> Do we have to look at a specific assembly language?
> I am VERY interested in this project.

It was written using the Intel ASM86 assembler, along with the companion
linker and locator, running on an Intel development system. No other
assembler is source compatible with it; Microsoft's MASM and Borland's TASM
are substantially different, especially in the area of macros.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@...

Re: [chromapolaris] Re: Reprogramming the Polaris -- wish list

2011-04-05 by Jesse

This is sounding less and less feasible...  Does anyone have a clue on the effort involved in doing something like this?  I've googled a little, but am having difficulty understanding all that would be involved.
 
 
On Mon, Apr 4, 2011 at 11:33 PM, Paul D. DeRocco <pderocco@...> wrote:
 

> From: Thomas Rizzi
>
> Does anyone know what language the Chroma operation system is
> written in?
> Do we have to look at a specific assembly language?
> I am VERY interested in this project.

It was written using the Intel ASM86 assembler, along with the companion
linker and locator, running on an Intel development system. No other
assembler is source compatible with it; Microsoft's MASM and Borland's TASM
are substantially different, especially in the area of macros.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@...




--
http://amoebafunk.com
http://metameme.org
http://apogaea.com

RE: [chromapolaris] Re: Reprogramming the Polaris -- wish list

2011-04-05 by Paul D. DeRocco

> From: Jesse
>
> This is sounding less and less feasible... Does anyone have
> a clue on the effort involved in doing something like this?
> I've googled a little, but am having difficulty understanding
> all that would be involved.

What it would take is permission from Fender to release the source code,
which I believe I've got somewhere (since I wrote it), plus some work on
translating it into a form that can be processed by some other assembler.
Since I don't know anybody at Fender any more, I have no idea how to go
about the first part.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@...