Discussion about the Korg PolySix synthesizer group photo

Yahoo Groups archive

Discussion about the Korg PolySix synthesizer

Index last updated: 2026-04-14 00:08 UTC

Message

Re: [PolySix] VCF cutoff quirkiness

2004-07-20 by dizz@elitemofo.com

OK-that makes things a bit more clear. I didn't think it would be the filters
because I can reproduce all of the original presets (a wide range of sounds and
very cheesy I might add). It's just when I tweak the cutoff, it seems to cut
out at spots, mainly toward the lower freqs. It acts just like a dirty pot on a
guitar etc. I think I'll try to clean it out if possible. The KLM 370 looks
easy to remove. I haven't actually had the cover off yet, but do you know if
the pots can be cleaned out? Or are they sealed?  The Psix is an awesome
compliment to my Moog and MS2K etc,,, I think I have a pretty good one judging
from some of the horror stories regarding battery damage. Thanks a bunch for
all the help!!

dizz

Quoting "Chromatest J. Pantsmaker" <chromatest@graffiti.net>:

> No no...  basically, they are saying that the filter probably isn't bad.
> There are 6 discrete filters, one for each voice.  If when you play 6 notes
> in a row (middle C pressed 6 times for example) they all sound the same (bad)
> there are two options.  One option is that ALL 6 filter chips are bad, or
> it's not the filters.  Since it would be pretty strange that all 6 filter
> chips would be bad, you probably don't need to worry about them.
>
> Either the bad sound is coming from some sort of weird setting that is
> telling the voices to make the sound, or there is something wrong after the 6
> voices are combined together.
>
> Now if you only had one note of the 6 pressed that sounded bad, then it must
> be something on that voice, whether the VCO or VCF or related circuitry...
>
>
>
>
> PolySix "Digiest" Page: http://www.acc.umu.se/~amber/Poly6
> Yahoo! Groups Links
>
>
>
>
>
>

Attachments

Move to quarantaine

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