Yahoo Groups archive

Korg DW8000, Mono/Poly, MS-20...

Index last updated: 2026-04-28 22:44 UTC

Message

Re: Greetings

2002-04-02 by fredbart26753

--- In DW8000@y..., 

Hi Louis,
Thanks for the welcome and the fast reply. I was thinking the same 
thing about the DW8000's aftertouch. The other korg I use is one of 
thosh ix300 Workstations so I am used to the velocity and aftertouch.
The ix is good for 'real' instrument sounds but I like the DW sound 
for synth sounds (especially when they use a lot of that resonant 
filter :o)    I have seen some dw8000s on ebay and am even 
considering trying to get one with the angel city turbo upgrade. For 
my purposes it would be mainly so that the keyboard can be split 
into different sounds. I wonder how well those things work?
  Well GTG for now,
Frank



Louis Zirkel III <lzirkel@c...> wrote:
> On Tue, Apr 02, 2002 at 04:27:39AM -0000, fredbart26753 wrote:
> 
> > Looks like a new board.  Hope to see it grow. I currently have 2 
> > korg boards in my line-up. One is a DW6000 which I suppose 
qualifies 
> > for this group.I've had it since the late 80's and had retired 
it 
> > when the internal battery went out, but recently I missed it and 
so 
> > replaced the battery and it is up and running. I am now 
considering 
> > a DW8000 but not sure yet. Just wanted to say hi to all and I'll 
> > check back to see how this group comes along.
> > :o)  frank
> 
> Welcome to the group.  I've got both a DW6000 and a DW8000 and 
while they
> sound similar, in my opinion, the DW8000 is so much more 
expressive because
> of it's aftertouch.  I've wanted one for years and finally bought 
one last
> year and have been extrememly pleased with it.  I don't do much 
more than 
> noodle with any of my music equipment, but the DW8000 is my 
favorite
> keyboard by far.
> 
> -- 
> Louis Zirkel III (lzirkel@c...)
> Century Development Solutions

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.