Yahoo Groups archive

Emu XL-7 & MP-7 User's Group

Index last updated: 2026-04-29 00:09 UTC

Message

Re: Early Rizer Filter Problem

2004-08-24 by steve_the_composer

Thanks for the reminder.  I remember the discussion here and your 
previous advice about Q.  In fact, before I ran into the problem 
myself I suggested to the other user adjusting the filter 
parameters.  In my case, the offending preset [P2500: pad:Richness] 
had Q=0 on both layers.

With EarlyRizer, it almost seems like the filter starts rising 
before the sample is completely out of the gate!! :-)

I ended up tweaking VEnv Attack1 Rate on both layers.  This let me 
have the least change on each layer (from 0 to 2 on one layer; from 
0 to 7 or 8 on the other layer).  Since its a pad, the miniscule 
attack change is hardly noticeable.

As for high Q's, I have an ART X-15 controller with 2 pedals.  99 
44/100% of the time, I have them controlling cutoff and resonance.  
Noodling with my midi sax, I play the cuttoff pedal, esp. with delay 
or pan delay effects.  But I almost always have Q backed off from 
max.  Its definitely too intense, but nice to know its there if I 
need it.  Occasionally, I momentarily push the Q to the floor.

--Steve


--- In xl7@yahoogroups.com, Aaron Eppolito <synthesis77@y...> wrote:
> Congratulations, you found the culprit of the problem (i.e the 
filter)
> much quicker than people have in the past.  We had a relatively 
long
> discussion on preset pops that took quite a while to track down in 
the
> past.
> 
> An alternate solution (which may or may not change the sound less) 
is
> to turn down Q ever so slightly.  Same deal.  The filter has a lot 
of
> resonance that when combined with certain sounds, clips the 
filter.  As
> a side note, you'll notice that most filters have their max Q set 
at 80
> instead of 100.  At your own risk, you can turn them up... =)
> 
> -Aaron

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.