u-he

zircon · Post by **zircon** » Mon Aug 10, 2009 5:23 pm

I noticed something today with the plain "init" patch, one osc, voice drifting/analog smoothing off, NO other features, no envelope (or rather, no attack, no decay, max sustain, no release.) If I play, say, F#5, release, and then play something like G3, the saw wave VERY audibly seems lowpassed first and then has rising cutoff to max over the course of about 500ms. It's extremely easy to hear. Not sure how else to describe it, but it's really just... bad. What's the deal here?

Urs · Post by **Urs** » Mon Aug 10, 2009 9:51 pm

zircon wrote:I noticed something today with the plain "init" patch, one osc, voice drifting/analog smoothing off, NO other features, no envelope (or rather, no attack, no decay, max sustain, no release.) If I play, say, F#5, release, and then play something like G3, the saw wave VERY audibly seems lowpassed first and then has rising cutoff to max over the course of about 500ms. It's extremely easy to hear. Not sure how else to describe it, but it's really just... bad. What's the deal here?

Hmmm... can't quite follow...

Will have to check that out... does setting Osc Resolution to a higher value make it better?

zircon · Post by **zircon** » Mon Aug 10, 2009 10:13 pm

Increasing osc res fixes it, but it's still bugging me that it exists on the default setting. Just load a saw, play F#4, then stop, then play F#3. Watch with a spectrometer or visual EQ or something. You'll distinctly see the frequencies be quite lowpassed at first and then within 500ms they'll expand to the normal spectrum of a saw.

Urs · Post by **Urs** » Tue Aug 11, 2009 8:18 am

It's definately fixed in latest betas, and probably even long before that... Actually, 500ms would be a bit much though. The default setting for Osc Resolution should be so that it hardly takes any time, and only great intervals should have an just so audile effect.

Later,

Urs

u-he

KVR Audio

2.3 saw bug?