Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Message

Re: [emax] Emax II and the ESi-32

2002-03-06 by wm

i have 3 emaxII's a 8meg turbo keyboard, a 3 meg rack and a 2 meg rack...
does any one knowif there is a way to swap the guts .. so ican make one of
the racks the turbo unit ??  i do'nt like having to carry the keyboar around
any more.

perhaps some one might be interested in  buying the keyboard ?? or all of
the above ??
                 \\\\|////
                     ("@ @")
  __o00o___(_)___o00o__


----- Original Message -----
From: John Silveria
To: emax@yahoogroups.com
Sent: Monday, March 04, 2002 11:47 AM
Subject: [emax] Emax II and the ESi-32


I do use both an Emax II (4Mb) and ESi-32 (32Mb) and I can tell you it's
just not the
same. The ESi-32 does not sound remotely as nice as the Emax II does, plus
it does not
have an internal hard drive option which means taking it live requires me to
take my
removable media drive which I don't like to do and lastly it doesn't have
the three sub
outs the Emax II has either unless you get the turbo board.

Sure the ESi-32 is better for editing and sampling and it has far more
filters and
supports SMDI transfers, but the reason why so many people are still using
Emax II's
(including NIN, DM, Orbital, and a slew of others) is because it sounds so
similar to the
original Emax and sounds far better for drums and analogue samples.


**********************************************************
     AIM/AOL: Emax JS **John Silveria II** ICQ: 60199476

Emax and Emax II User's Group - http://www.silveriafamily.com
Emax and Emax II Mailing List - emax@yahoogroups.com
**********************************************************


Emax and Emax II User's Group

http://www.silveriafamily.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




[Non-text portions of this message have been removed]

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.