ChromaTalk Archives: August 2008
- German to English Translators? (6 messages)
- Chroma on Craigslist Toronto (2)
- low velocity chroma (19)
- CC+ 5th batch (12)
- BCR-2000 map (3)
- Chroma/Expander picture (2)
- Chroma voice bd on eBay
- panel question (2)
- Chroma on german Ebay (6)
- chroma user - Koto
- Power supply surge suppressor sub. (2)
- Roy Paynter / UK Chroma service (2)
German to English Translators?
Chris Ryan [21030691] · Sat, 2 Aug 2008 10:34:34 -0700
I've received permission from Synthesizer Magazin to publish on the site the Chroma article Jesper pointed out back in April. I'll publish it in its original German (which I'm getting close to finishing via OCR and careful transcription), but would also like to make an English version available. Is there anyone on the list who would be able and willing to help me out on this? The article is six pages long but there are a fair number of large images, so it's probably three or four pages of text.
Christian Kleine [21030210] · Sat, 02 Aug 2008 19:50:46 +0200
Hi Chris,
I can help, if you have a scan or something like this.
Jesper Ödemark [21010135] · Sat, 02 Aug 2008 20:04:22 +0200
Come on germans... don't force a poor swede with only three years of german in school to take on the assignment! ;)
Erik Vellinga [21010286] · Sun, 3 Aug 2008 12:41:15 +0200
I can do it.
Chris Ryan [21030691] · Sun, 3 Aug 2008 09:34:00 -0700
Thanks everyone. Christian is going to take a shot at this.
Erik Vellinga [21010286] · Sun, 3 Aug 2008 21:36:28 +0200
Christian, good luck. If you need help or if you want to split it in two just let me know.
The English and original German versions of the article were added to the site in September 2008.
Chroma on Craigslist Toronto
Chris Ryan [21030691] · Thu, 7 Aug 2008 20:49:20 -0700
[URL removed; posting ID 786566638]
From the description: "This synthesizer is not working, but complete with many extra parts and accessories, including heavy duty case, owner and service manuals, patch data cassette tape. Was functional, but needs a new power supply replacement. Will sell off for $600 cash, no trades please."
I tried contacting the seller but got a bounce from craiglist; not sure why.
Jesper Ödemark [21010135] · Fri, 08 Aug 2008 11:18:54 +0200
600 bucks - that's a neat bargain for someone if they only get through on the address!
low velocity chroma
Anders Elo [21010104] · Sat, 9 Aug 2008 20:12:49 +0200
Hello chroma list! I have perhaps discovered a problem with the velocity sensor/setting/ curve on my chroma. It seems that I can only reach a maximum velocity value of 100 (instead of 127). Using an external keyboard to play the chroma works fine but thats a terrible workaround.
What could be the issue here ?
Lars Johansson [21030632] · Sat, 9 Aug 2008 23:29:16 +0200
Looks like a firmware problem. Much like the DX-7 originally.
Ken Ypparila [21030229] · Sat, 9 Aug 2008 14:50:47 -0700
Are you talking about a MIDI conversion? I don't ever remember that being an issue back when I was testing the MIDI converter design years ago. Also there would have been many complaints over the years about that if it had ever happened with anyone else out there. The only issue I remember was when they rewrote the velocity curves for the the first firmware update on the Chroma which made it difficult to achieve low velocity.
Jack Colburne [21030142+] · Sun, 10 Aug 2008 00:10:32 -0400
Ken , i remember that rewrite well... completely trashed my patches and the machine never felt "right" after that. I could never get the same feel again.
Weren't you were working for Fender at the time?... I think i remember you working on the Sunn Midi controlled mixers or lighting systems or something around that time.
David Clarke [21030085++] · Sat, 09 Aug 2008 22:43:44 -0400
... I have perhaps discovered a problem with the velocity sensor/setting/ curve on my chroma. It seems that I can only reach a maximum velocity value of 100 (instead of 127).
Anders - so we can make suggestions about what you might be seeing, would it be possible for you to describe how you're making your observations?
For instance - are you monitoring the MIDI output from the Chroma while striking the keys of the Chroma itself? If so, which MIDI interface is being used? Is this S/N 21010104 from the registry, with the Kenton MIDI kit?
If it is the Kenton kit, then perhaps the it has a limit. That kit doesn't integrate tightly with the internal data of Chroma.
Can you generate lower velocities OK, or does the interface generate all notes at the same (fixed) velocity of 100?
Ken Ypparila [21030229] · Sun, 10 Aug 2008 00:00:13 -0700
Ken , i remember that rewrite well... completely trashed my patches and the machine never felt "right" after that. I could never get the same feel again.
Weren't you were working for Fender at the time?... I think i remember you working on the Sunn Midi controlled mixers or lighting systems or something around that time.
Yes, I got Paul D. to give me the location of the velocity table so that I could try to adjust it back to where it was. I was able to get it close but he had to shorten the table to make room for something so it wasn't possible to get it back exactly. There was an eprom set labeled "B" that Fender gave out that had my updated table.
Anders Elo [21010104] · Sun, 10 Aug 2008 09:18:20 +0200
Hi David and all.
This is concerning the Chroma with S/N 21010104 but nowdays it has both the CC+ and the SPSU installed (registry needs an update). I'm monitoring the velocity output in Logic studio while striking the keys... Hmmmmm The chroma is connected to a Midiman midisportx4 and the prophet08 that I used as controller is connected to a Motu 828mkII fw.
Yes, I can generate lower velocity too.
Anders Elo [21010104] · Sun, 10 Aug 2008 19:47:27 +0200
I would expect that with a very fast strike you should be able to reach the 120 or 124 value from the Chroma.
Yes, I was able to hit it up to 112 but it is impossible to get this high by playing normally.
Is it possible to tweak the sensor sensitivity somehow?
David Clarke [21030085++] · Sun, 10 Aug 2008 12:01:29 -0400
This is concerning the Chroma with S/N 210210104 but nowdays it has both the CC+ ... Yes, I can generate lower velocity too.
Anders - based on the Chroma Computer Interface Manual, the Chroma only has 5 bits of velocity data. That means it stores its velocity data as a number from 0 to 31.
MIDI will allow velocity to go from 0 to 127.
Because of this difference in how numbers are stored, whichever MIDI interface is used, a velocity conversion from Chroma -> MIDI and MIDI -> Chroma is required.
The table below is used for the CC+ in the Chroma -> MIDI direction.
From this table we can see that if a maximum Chroma velocity of '31' happens, then the corresponding MIDI value will have a maximum value of 124. (i.e., it is expected that we wouldn't get 127).
That having been said, 124 is still quite a bit higher than the 100 that you are seeing.
I would expect that with a very fast strike you should be able to reach the 120 or 124 value from the Chroma.
| Chroma Velocity | MIDI Velocity |
|---|---|
| 0 | 1 |
| 1 | 4 |
| 2 | 8 |
| 3 | 12 |
| 4 | 16 |
| 5 | 20 |
| 6 | 24 |
| 7 | 28 |
| 8 | 32 |
| 9 | 36 |
| 10 | 40 |
| 11 | 44 |
| 12 | 48 |
| 13 | 52 |
| 14 | 56 |
| 15 | 60 |
| 16 | 64 |
| 17 | 68 |
| 18 | 72 |
| 19 | 76 |
| 20 | 80 |
| 21 | 84 |
| 22 | 88 |
| 23 | 92 |
| 24 | 96 |
| 25 | 100 |
| 26 | 104 |
| 27 | 108 |
| 28 | 112 |
| 29 | 116 |
| 30 | 120 |
| 31 | 124 |
Luca Sasdelli [21010226] · Mon, 11 Aug 2008 13:13:45 +0200
Hi Anders,
the time-to-fly "sensor" is indeed a switching time measurement between rest and hit contacts; perhaps it could be varied by changing the scan timing, or (easier, I guess) by applying different conversion tables, that can fit that specific instrument.
This is an interesting issue for an upcoming CC+ firmware release :-)
BTW: did you increase the capacitor for the sustain pedal problem? Did it fix the issue?
Anders Elo [21010104] · Mon, 11 Aug 2008 14:09:44 +0200
Hello Luca,
On Aug 11, 2008, at 13:13 , Luca Sasdelli wrote:
Hi Anders,
the time-to-fly "sensor" is indeed a switching time measurement between rest and hit contacts; perhaps it could be varied by changing the scan timing, or (easier, I guess) by applying different conversion tables, that can fit that specific instrument.
This is an interesting issue for an upcoming CC+ firmware release :-)
Yes, having different velocity curve options and/or being able to tweak the sensitivity in the CC+ would be a very nice feature.
Another 'must have' feature is better support for stereo modes. Alternating left-right, alternating random, and unison stereo on the same midi channel. That would be fantastic to have. It's not really useful the way it works today I think, when you have to assign a specific midi channel to each output.
BTW: did you increase the capacitor for the sustain pedal problem? Did it fix the issue?
Nope, not been able to do that yet, but I promise to get back to you as soon as it's done.
Anders Elo [21010104] · Fri, 15 Aug 2008 22:21:51 +0200
I also remember that update and the resulting bad 'feel'. If I recall correctly, I put the original 8039 back into my Chroma and it's been that way since. This implies that the curve table is there on the IO board and not in the main CPU EPROM, no?
Yes that's the way I've understood it too but but as Luca and others pointed out it is a 5 bit value ranging from 0-31 translated by the CPU and sent out by midi. The CC+ should easily be able to transform this with its own velocity table and perhaps even include a factor to tweak the sensitivity.
Anders Elo [21010104] · Fri, 15 Aug 2008 23:15:54 +0200
Reading the service manual IO-section: "Whenever information is to be transmitted to the main computer, the 8039 supplies the time measurement on port 2 bits 6-0 (pins 21-24, 35-37). Bit 7 (pin 38) will be high for a release and low for an attack."
It looks like the 8039 on the I/O board is sending the timing measurement as a 7-bit value to the main CPU. So then it's more likely that the 'updated' 8039 just transformed the timing measurement before passing it further to mother. The 5 bit velocity curve table seems to be located in main CPU which means the CPU has to shift 2 bits to the bucket and later translate this back to 7 bit midi velocity data, ouch!
// anders - a bit confused now
Jimmy Moyer [21030184] · Fri, 15 Aug 2008 15:18:49 -0400
I also remember that update and the resulting bad 'feel'. If I recall correctly, I put the original 8039 back into my Chroma and it's been that way since. This implies that the curve table is there on the IO board and not in the main CPU EPROM, no?
Does anyone know what other improvements I'm missing out on by sticking with the original?
Is there possibly a newer drop-in for the 8039 that would allow more programming space, to for example, increase the limited number of velocity steps we have now?
David Clarke [21030085++] · Fri, 15 Aug 2008 19:46:00 -0400
It looks like the 8039 on the I/O board is sending the timing measurement ...to the main CPU.
That's correct.
Changing the 8039 code can affect the overall velocity though.
When the main firmware changed from Rev 12 to Rev 14 it seems there was also a change to the code in the Keyboard Scanning Code (i.e., the 8039's code).
The change in the 8039's code affects how fast the 8039 watches the keyboard.
The Rev 2 8039 checks the keyboard 'faster' than the current Rev 3 8039 code (approx 2% faster). (xref: Keyboard Velocity Curves).
To answer Jimmy Moyer's question - if it was only the 8039 code that was reverted back, then there is nothing else being 'missed' - there will just be a change in timing.
If anyone is interested, the difference between the Rev 2 and Rev 3 8039 code can be seen in the commented scan2.asm and scan3.asm files [see EPROM Code: Disassembled Chroma (Main Firmware) Source].
Looking at this, we see that the Rev 2 code scans slower than the Rev 3 code.
What this will means is, if you have the Rev 2 8039 code installed - they you can actually hit the keys slower than with the Rev 3 code, to get the same velocity value from the keyboard.
A mini 'straw poll':
Talking only about the Chroma itself (and not about how it responds to sends MIDI):
- How many people don't like the velocity response?
- Of those that don't like it - do you think there would be one, static mapping which everyone could agree on?
In terms of MIDI:
- Of those who don't like the mapping - do you feel that it is better to have the Chroma implement alternate/settable maps vs. using MIDI re-mapping capabilities which already exist in most sequencers/hosts?
Anders Elo [21010104] · Sat, 16 Aug 2008 22:12:03 +0200
Thanks David for making this clear.
The Rev 2 8039 checks the keyboard 'faster' than the current Rev 3 8039 code (approx 2% faster). (xref: Keyboard Velocity Curves).
Ok, so how does the velocity table look in the CC+?
If anyone is interested, the difference between the Rev 2 and Rev 3 8039 code can be seen in the commented scan2.asm and scan3.asm files here:
Well done, this is better than the manual. :)
Looking at this, we see that the Rev 2 code scans slower than the Rev 3 code.
Assuming now that I have the slower rev 3 code, to resolve my 'low velocity' problem, I should get an Eprom programmer and revert back to Rev 2.
- How many people don't like the velocity response?
I don't. :o)
- Of those that don't like it - do you think there would be one, static mapping which everyone could agree on?
No; I think there should be like 3-4 curves to match different playing styles.
In terms of MIDI:
- Of those who don't like the mapping - do you feel that it is better to have the Chroma implement alternate/settable maps vs. using MIDI re-mapping capabilities which already exist in most sequencers/hosts?
Yes, definitely, the chroma has a very good keyboard, I think it would be best to take full advantage of that. The chroma_velocity-to-midi_translation table should also make use of full 7bit resolution (not up-scaled 5bit).
David Clarke [21030085++] · Sat, 16 Aug 2008 21:06:00 -0400
Ok, so how does the velocity table look in the CC+?
As most users had expressed a preference for Rev 12, the CC+ uses the Rev 12 velocity table.
Assuming now that I have the slower rev 3 code, to resolve my 'low velocity' problem, I should get an Eprom programmer and revert back to Rev 2.
Note: While the current graph on the site indicates only a 2% difference in scanning speeds between the 'rev 2' and 'rev 3' keyboard scanning code - the difference is quite a bit more distinct, as noted here: Keyscan code disassembly/corrections/scan rate
I will work with Chris Ryan to update the data on the graph page to reflect this.
Chroma Velocity Curves has been revised.
Trying Rev 2 keyboard scanning code would likely be the quickest method to see if you get a more desirable Chroma response.
Anders Elo [21010104] · Sun, 17 Aug 2008 09:47:52 +0200
On Aug 17, 2008, at 03:06 , David Clarke wrote:
As most users had expressed a preference for Rev 12, the CC+ uses the Rev 12 velocity table.
This would mean that all Chromas having Rev 3 keyscan code and the CC + (or rev 12 cpu) should experience my problem. Are there any others out there?
Note: While the current graph on the site indicates only a 2% difference in scanning speeds between the 'rev 2' and 'rev 3' keyboard scanning code - the difference is quite a bit more distinct, as noted here:
A guesstimate based on my own tests is that the overall effect on the sensitivity is around 20% slower.
Trying Rev 2 keyboard scanning code would likely be the quickest method to see if you get a more desirable Chroma response.
With your conclusion that rev 3 is faster i.e more sensitive but reports a 'slower' timing due to different implementation, then the best solution would be that the CC+ had at least rev12 and rev14 tables implemented.
Even better if the CC+ had the velocity tables implemented differently by being 7bit-->7bit instead of 7bit-->5bit and then just make the 5bit DAC conversion on the fly.
Jimmy Moyer [21030184] · Mon, 18 Aug 2008 17:23:28 -0400
Playing the Chroma itself, somehow the 'feel' (with the original KB scanner) is fine for me.
If I try to, for example play a sampled piano via MIDI, the limited velocity steps can be quite obvious, forte notes that inconsistently jump out. It would be great if there was a way to get more resolution.
Right now, I keep another keyboard around just for cases when this is a problem. (OK, and sometimes the choice of 64 keys is a limit, but an 88 key Chroma seems like a unlikely upgrade!)
CC+ 5th batch
Sandro Sfregola [21010294] · Wed, 13 Aug 2008 09:50:37 +0100
We have once again placed enough people on the CC+ 'wait list' to justify another build of boards.
We propose to accept orders for this fifth build up until Saturday, September 14th (midnight, Eastern Time).
To ensure a timely order of parts for those who have requested CC+ boards, we would like to receive payment by Saturday, September 21st.
Within September 7th we will be individually getting back in touch with the people on the wait list to see if you're still interested - and if so, to confirm your order. [David will be contacting the people from North America and Sandro will be contacting the people from the EU.]
If you're not currently on the wait list - but would like to have a board from the 5th build - please be sure to get in touch before September 14th.
If you believe you're on the wait list but have not received an e-mail from either Sandro or David within September 7th - be sure to let them know.
Once again, thank you for your continued interest and participation.
Jesper Ödemark [21010135] · Wed, 13 Aug 2008 11:22:42 +0200
so, to confirm your order. [David will be contacting the people from North America and Sandro will be contacting the people from the EU.]
And those from other regions? (sorry, couldn't help it :) )
Once again, thank you for your continued interest and participation.
They sure should be interested - it's an amazing upgrade!
Sandro Sfregola [21010294] · Wed, 13 Aug 2008 11:01:56 +0100
Thank you Jesper (hi):
Europe, Africa, Middle East please contact Sandro; North, central and south America, Australia, China, Japan please contact David.
Sandro
(We do not ship to Mars because of the lack of insurance and tracking problems).
Leonardo Ascarrunz [no serial number]runz [[no serial number]runz">no serial number] · Wed, 13 Aug 2008 09:32:26 -0600
What makes the upgrade so amazing? from what i understand the CC+ board is a modern version of the chroma computer board with new code inserted to enable native midi support. Am i missing something? Are there new features like syncable lfo's or new modulation options?
Luca Sasdelli [21010226] · Wed, 13 Aug 2008 18:15:02 +0200
Hi Leo,
the CC+ is IMHO a must-have one; there is a (long!) feature list at CPU Plus (CC+).
Jesper Ödemark [21010135] · Wed, 13 Aug 2008 19:52:04 +0200
What makes the upgrade so amazing? from what i understand the CC+ board is a modern version of the chroma computer board with new code inserted to enable native midi support. Am i missing something? Are there new features like syncable lfo's or new modulation options?
Better midi is cool, 200 memory positions is a nice feature. Lower power consumption is not bad, instant scratch patch and similar features are very useful... But to me the best of the best is the acceptance of midi control change messages for every parameter there is. In my case this means that by adding a knob box I can tweak everything like I want to, and in realtime too. No more button pushing!
I e - Get One! :)
Richard Willoughby [21030348] · Wed, 13 Aug 2008 11:08:42 -0700
The lower power consumption is very noticable on my Chroma.......before CC+ was installed, you could fry an egg on its chasis after 5 minutes......I feel much more comfortable leaving it on for longer periods now......runs way-aaaaaaay cooler !! So much so that it will make its first appearance in my live setup on Saturday night.....The Midi is very tight and the 200 memory locations are a blessing as well. I've temporarily given up on involving the BCR-2000 for now due to frustration, so I'm still knobless. Anyone have a map available for download ???......that thing has me stumped.....
See BCR 2000 map below.
Werner Schöenenberger [21010114] · Wed, 13 Aug 2008 20:34:44 +0200
- more sound banks,
- expandable
- reliable
My Chroma did not have MIDI. But even then I would have bought the CC+. One of the best third party upgrades for synths I ever saw.
Michael Salmon [21030155] · Wed, 13 Aug 2008 15:47:33 -0700
CC+ 5th batch (note)
everyone should get one, cc+ is amazing. so amazing. i want to kiss the inventors
Jesper Ödemark [21010135] · Wed, 13 Aug 2008 19:43:24 +0200
(We do not ship to Mars because of the lack of insurance and tracking problems).
Last I heard they weren't too keen on the entire midi idea anyway. I don't think ARP and Rhodes were as much Pro-Mars as Roland was! ;)
Richard Willoughby [21030348] · Wed, 13 Aug 2008 15:59:58 -0700
Re: CC+ 5th batch (note)
...now lets not get carried away......we should wait for some more add-ons and mega-future-features/CC+ upgrades first before kisses.....maybe hugs will suffice for now
;)
Michael Salmon [21030155] · Wed, 13 Aug 2008 16:49:54 -0700
Re: CC+ 5th batch (note)
polyhug
BCR-2000 map
Andrew Dalebrook [21010180] · Thu, 14 Aug 2008 09:39:38 +1200
I've temporarily given up on involving the BCR-2000 for now due to frustration, so I'm still knobless. Anyone have a map available for download ???......that thing has me stumped.....
Richard:
Check out this post [from the thread "MIDI Controllers," April 2007].
It is a BCR-2000 map for the KMX interface, not the CC+, but may have some relevance. Feel free to email me if you need some more help.
Richard Willoughby [21030348] · Wed, 13 Aug 2008 15:56:53 -0700
oh....thank you very much!
Ken Ypparila [21030229] · Wed, 13 Aug 2008 20:05:46 -0700
The KMX/Syntech MIDI interface didn't offer a MIDI continuous controller number for every Chroma parameter because at the time (MIDI was brand new, we're talking '84-'85) the spec forbade the use of certain controller numbers. It didn't offer enough numbers for the number of Chroma parameters. I had to choose what I thought were the least used parameters to leave off. Later on, everyone started using the forbidden control numbers anyway plus the MMA offered ways to expand the number of controllers as well. I developed the firmware on an older, long gone system so the source code couldn't be updated without a lot of bother so that's why it is the way it is.
Chroma/Expander picture
Mark Smith [2103-PT-002] · Wed, 13 Aug 2008 20:03:48 -0700
Hi - Here's a shot of my setup with the Expander.
Jesper Ödemark [21010135] · Thu, 14 Aug 2008 08:10:44 +0200
Thermometer and patch programming chart - nice "add-ons"! :D
It looks amazing with the Halloween siblings like that.
Chroma voice bd on eBay
Mark Smith [2103-PT-002] · Tue, 19 Aug 2008 04:13:36 -0700
Hi -
Here's another Chroma Voice bd for sale. This one needs tech work but it will power up with an ERR. [Item #260276512283]
panel question
Werner Schöenenberger [21010114] · Sat, 23 Aug 2008 09:07:44 +0200
Hi all,
a quick question concerning revision of a chroma panel. A friend of mine has received a chroma which obviously was stored somehow in a wet environment. One effect is that the sensor contacts do not work proper anymore. Is there a recommendation how to fix the contact issue in the control panel? Thank you very much in advance.
John Leimseider [21030434++] · Sat, 23 Aug 2008 08:52:11 -0600
We have right and left Chroma and Expander membrane assemblies available... I'll be out of the office until Sept 9. After that, please feel free to Email me for details...
Chroma on german Ebay
Jesper Ödemark [21010135] · Mon, 25 Aug 2008 14:15:01 +0200
Syntech interface, pedals, manuals etc.
[Item Z110282885708]
Only collection in person, but looks nice and the case looks re-foamed. Very modest price this far (121 euros) but rising...
(I haven't asked for the serial.)
Picture from the auction:
Claes von Heijne[16330008] · Mon, 25 Aug 2008 13:59:34 +0000
What is that single pedal to the right, it looks just right in style? There was no such pedal in the original shipment when you bought a new Chroma, but a volumepedal and a sequence step pedal together with the double pedal.
Chris Ryan [21030691] · Sat, 30 Aug 2008 09:24:46 -0700
What is that single pedal to the right, it looks just right in style? There was no such pedal in the original shipment when you bought a new Chroma, but a volumepedal and a sequence step pedal together with the double pedal.
That is unusual; I haven't seen it before.
The owner let me know that this is Chroma 21010195.
Michael Zacherl [21030253] · Sun, 31 Aug 2008 10:12:58 +0200
always in trackig mode, hm? ;-)
Michael. (long time no see ... errm ... read ...)
David Clarke [21030085++] · Sun, 31 Aug 2008 11:33:57 -0400
The extra pedal is very interesting as it really does look to be the exact same style/manufacture as the dual-pedal assembly - but half as wide and only for one pedal.
The ARP 16-voice piano reported came with a dual pedal assembly with two brass pedals. Anyone know if perhaps the 4-voice came with a single pedal assembly?
Jack Colburne [21030142+] · Sun, 31 Aug 2008 11:59:26 -0400
Had been thinking the same thing, found this pic on line...
Yup, it's an ARP pedal.
Go to next message in thread, September 2008
chroma user - Koto
Jesper Ödemark [21010135] · Mon, 25 Aug 2008 13:31:07 +0200
Hi List!
I bought a bunch of cheesy 80's syntpop records incl. "the best of italo disco vol. 8" and on the gatefold are images of some of the bands on the records. And what is the guy in Koto posing with do you think?
I found a lousy image on discogs.com. Here; http://www.discogs.com/image/R-153784-1201814428.jpeg
Here is the relevant picture:
No doubt it's a Chroma when you have the real picture in front of you. Time to spin more Koto I think! :D
I have no confirmation of which tracks it was used on, but this compilation includes; "Jabdah"
Power supply surge suppressor sub.
Steve Jones · Fri, 29 Aug 2008 13:39:56 +1000
Hi there, I am a new member, I am a service tech who used to be a warranty tech. for the Chroma and Polaris. Just a heads up on a component that may work in place of the obsolete L60V6 surge suppressor. I have found another device which is a bi-directional surge suppressor, it is not in a T03 case but has about the same power handling, ie: 1500W, and costs less than a dollar. The part is a Transorb 1N6267A, they come in several Voltages, the one that you would need is 6.8V. This should do fine I think to replace the crowbar suppressor that usually fails in these machines. Should be available pretty much anywhere.
Steve Jones · Fri, 29 Aug 2008 16:35:30 +1000
Oops sorry for the typo, the voltage should be 7.8V, not 6.8V.
Go to next message in thread, September 2008
Roy Paynter / UK Chroma service
Matt Thomas [21010021] · Sun, 31 Aug 2008 19:01:03 +0100
Hi,
I'm trying to contact Roy Paynter to get my voice boards serviced - I've tried Paul Hackett Evans' email as given on the Chroma site but it's discontinued, so I can't get Roy's phone number. Does anyone have Paul's current email address or Roy's number?
Failing that does anyone have contact details for any good UK based Chroma tech?
Paul Hackett-Evans [21010094] · Sun, 31 Aug 2008 23:20:57 +0100
Hi Matt,
I'm sorry - my email address changed when I switched internet providers some time ago - I must have forgotten to ask Chris to change the "Tech centres" web page that lists my details. I apologise!!!
My address now is [see Service: Roy Paynter]
Is your address [removed]?
Please confirm that and I'll send you an email with Roy's contact details.