Yahoo Groups archive

Emax

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

Thread

EIII, ESi-32 destructive editting

EIII, ESi-32 destructive editting

2004-02-08 by tbiggz

Hi, I have an emulator III rack with O.S. 2.42.  I use it a lot with 
an Sp1200; dumping sampled signals to the EIII for processing and 
back to the SP for playback. 

I have a pretty good selection of destructive editing tools on the 
EIII (especially for a 93 OS!).  I have a huge 256 tap lowpass/hipass 
phaselinear filter, all other IIR filter forms, compression, digital 
eq, etc...

My question is why Emu removed some of these filters from the EIIIx 
and ESI models.  They seem to keep the EQ and compression-- but 
that's pretty much all that remains.. any reason for this?  Or do 
they have these features in some OS update that doesn't get mentioned 
in the manuals?

Anyone know about this?

RE: [emax] EIII, ESi-32 destructive editting

2004-02-08 by Rob Keeble

Hi,
Some EIII cool (but processor intensive) features were removed to make way
for better new features on the EIIIX/ESI's, this was probably becuase the
EIII had a co-processor and the EIIIX did not - although there is space to
fit one. The ESI range is just an EIIIX with smaller surface mount
components.

Regards
rob
www.emulatorarchive.com
Show quoted textHide quoted text
  -----Original Message-----
  From: tbiggz [mailto:infarmah@...]
  Sent: 08 February 2004 18:49
  To: emax@yahoogroups.com
  Subject: [emax] EIII, ESi-32 destructive editting


  Hi, I have an emulator III rack with O.S. 2.42.  I use it a lot with
  an Sp1200; dumping sampled signals to the EIII for processing and
  back to the SP for playback.

  I have a pretty good selection of destructive editing tools on the
  EIII (especially for a 93 OS!).  I have a huge 256 tap lowpass/hipass
  phaselinear filter, all other IIR filter forms, compression, digital
  eq, etc...

  My question is why Emu removed some of these filters from the EIIIx
  and ESI models.  They seem to keep the EQ and compression-- but
  that's pretty much all that remains.. any reason for this?  Or do
  they have these features in some OS update that doesn't get mentioned
  in the manuals?

  Anyone know about this?



  Emax and Emax II User's Group Website

  http://www.silveriafamily.com



----------------------------------------------------------------------------
--
  Yahoo! Groups Links

    a.. To visit your group on the web, go to:
    http://groups.yahoo.com/group/emax/

    b.. To unsubscribe from this group, send an email to:
    emax-unsubscribe@yahoogroups.com

    c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



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

Re: [emax] EIII, ESi-32 destructive editting

2004-02-08 by Garth Hjelte

At 06:48 PM 2/8/04 +0000, you wrote:
>Hi, I have an emulator III rack with O.S. 2.42.  I use it a lot with
>an Sp1200; dumping sampled signals to the EIII for processing and
>back to the SP for playback.
>
>I have a pretty good selection of destructive editing tools on the
>EIII (especially for a 93 OS!).  I have a huge 256 tap lowpass/hipass
>phaselinear filter, all other IIR filter forms, compression, digital
>eq, etc...
>
>My question is why Emu removed some of these filters from the EIIIx
>and ESI models.  They seem to keep the EQ and compression-- but
>that's pretty much all that remains.. any reason for this?  Or do
>they have these features in some OS update that doesn't get mentioned
>in the manuals?
>
>Anyone know about this?

They switched to digital filters starting with the EIIIx, different deal, 
different things. The plain EIII is highly coveted for those reasons, the 
analog filter is really cool.

Note that the new Emulator X - the Emux =) - has a buttload of filters.

Garth Hjelte
Sampler User

Re: EIII, ESi-32 destructive editting

2004-02-09 by tbiggz

The EIIIx digital filters were, to my understanding, implemented in a 
separate chip--i.e. the burden of 32 channel realtime IIR filtering 
was not put all on the main processor but rather moved to a separate 
digital chip instead of separate CEM filters. 

The tools i'm talking about seem to have nothing to do with the 
realtime filtering datapath.  They are likely microprocessor 
algorithms run on the main controller; I think this is why nothing 
else can be done while the processing takes place.

Perhaps the co-processor matter is the decisive one.  What that 
really means i'm not sure.  What was a co-processor in terms of 1988 
technology?  Was this a separate DSP-type chip or some extra built in 
PAL logic to do transposing?  And why could it be removed (i.e. 
faster next-gen main processor?).. It seems the algorithms were just 
not deemed useful enough to be ported to later models.. oh well too 
bad.  I'm really pretty glad I bought my EIII rack though.




--- In emax@yahoogroups.com, Garth Hjelte <garth@c...> wrote:
> At 06:48 PM 2/8/04 +0000, you wrote:
> >Hi, I have an emulator III rack with O.S. 2.42.  I use it a lot 
with
> >an Sp1200; dumping sampled signals to the EIII for processing and
> >back to the SP for playback.
> >
> >I have a pretty good selection of destructive editing tools on the
> >EIII (especially for a 93 OS!).  I have a huge 256 tap 
lowpass/hipass
> >phaselinear filter, all other IIR filter forms, compression, 
digital
> >eq, etc...
> >
> >My question is why Emu removed some of these filters from the EIIIx
> >and ESI models.  They seem to keep the EQ and compression-- but
> >that's pretty much all that remains.. any reason for this?  Or do
> >they have these features in some OS update that doesn't get 
mentioned
> >in the manuals?
> >
> >Anyone know about this?
> 
> They switched to digital filters starting with the EIIIx, different 
deal, 
> different things. The plain EIII is highly coveted for those 
reasons, the 
> analog filter is really cool.
> 
> Note that the new Emulator X - the Emux =) - has a buttload of 
filters.
Show quoted textHide quoted text
> 
> Garth Hjelte
> Sampler User

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.