1.1.2+ WaveTable read affected by +1.0 & -1.0 values

Nu Audio Science · 27 Jul 2009

infuzion wrote: 3) Learn to enjoy the "unique" sound. !

Gets my vote hahahahahahahah

NAS

rl · 27 Jul 2009

Not a bug - it's a feature: http://en.wikipedia.org/wiki/Gibbs_phenomenon

infuzion · 27 Jul 2009

rl wrote: Not a bug - it's a feature: http://en.wikipedia.org/wiki/Gibbs_phenomenon

My understanding of SynthMaker is that you're supposed to drag & drop to slap to together a synth. I think SM is meant so that you don't need a university degree in science to be able to program with SM. I'm sure that over half of SM users don't know Gibbs is before today, & maybe 90%. (Well, not directly, but I'm sure you get my direction).

In order for SM to be user friendly, the Wave Table Read primitive doesn't necessarily need to be fixed, but at least: A: The Wave Draw module needs to be adjusted, I would say using *0.82353. B: This "Gibbs Phenomenon" needs to be well documented, both in PDF & WiKi.

AngularMomentum · 27 Jul 2009

If you had SE before SM you know about this. 🙂

The SE oscillators have a setting to cancel this effect. In my experience it also cancels a lot of brightness to the oscillators, so I never used the option.

infuzion · 27 Jul 2009

I skipped SE & went straight to SM 😇 The colored connectors & this form attracted me to SM over SE, which seemed to have scattered support.

That dulled sound sounds like 2048 vs 256 Wavetables. The said issues were with 2048 WTs BTW.

Nu Audio Science · 28 Jul 2009

infuzion wrote: I skipped SE & went straight to SM 😇 The colored connectors & this form attracted me to SM over SE, which seemed to have scattered support .

Oh how times can switch things around uh

NAS

Panoply · 20 Sept 2009

Has it always been like this?

I'd swear that I've made 'perfect' square waves in the WT before, using the wavedraw, or just plain arrays, and they've been fine. Currently, I can't get anything even approaching squarish to play back sensibly at all, no matter what I do to multiple it by something to take it away from 1 ... its just not having it. In effect, the more square-like the issue becomes, the more HP'd the signal becomes. And its a major issue long before the wave is a square!

example shown ... my multiplications take it to 0.25 in here, before it gets near the WT, and the effect is no more or less strong ... or am I doing it wrong?

Any help with this problem appreciated. I'm using 1.1.3 release.

I use the wavedraw coz its stock and displays the issue in a familiar manner

Try making a module where you fade the array before the wave read between square and saw ... and hear the sound gradually fail more and more. I swear it wasn't like this! What happened?

infuzion · 21 Sept 2009

I'm reporting a bug with a square of values of only +1.0 & -1.0, while you have a WT of +/-0.25.

Panoply · 21 Sept 2009

I thought the issue might be related - and I also thought I might have misunderstood your multiply by 0.82353 stage or be applying it at the wrong place.

I'll open a new thread then.

infuzion · 22 Sept 2009

They could be related, but they seem like different issues. Mine seems to be "intersample peaks" &/or the Gibbs Phenomenon as RL posted above. My issues also has simple workarounds, & may be more of a document & shipped-module error rather than an SM core issue.