---------------------------- Original Message ---------------------------- Subject: Re: [music-dsp] Antialiased OSC From: "Scott Gravenhorst" <[email protected]> Date: Mon, August 6, 2018 8:06 pm To: [email protected] -------------------------------------------------------------------------- > > Nigel Redmon via [email protected] wrote: >> >>Arg, no more lengthy replies while needing to catch a plane. Of >>course, I didnt mean to say Alesis synths (and most others) were >>drop sampleI meant linear interpolation. The point was that stuff >>that seems to be substandard can be fine under musical >>circumstances... > > This is an important point. I see so often developer approaches that start > at the most complex and most computationally burdensome when simpler > approaches work well enough to pass the "good enough" test. I start at the > low end and if I can hear stuff I don't like, then I'll try more "advanced" > techniques and that has served me very well. > well, we might have different definitions about what "complex and computationally burdensome" is.� i don't always measure it out as what's the least MIPS.� sometimes it's a computational burden to toss in a conditional execution instruction.� sometimes is less computational burden to just extend the model to use more resources, like more wavetables just after NoteOn to cover the attack.� i just think that as long as 4K word wavetables can cover 10+ octaves (but there's a lotta redundancy in those wavetables for the high pitches).� the easiest way to do it simply is just do it the same old way, but throw enough wavetable length at it. again, this is a softsynth running on a platform with ca. gig or memory.� the cost is about 16K per wavetable.� maybe an instrument needs 64 wavetables laid out in some array to cover modulation in all of the dimensions.� that's a meg for one instrument. i'll admit it's an aesthetic issue.� even though i do it too, i dislike if() statements in the real-time processing code.� it's just that's how i would extend the range of an instrument rather than grafting this wavetable biz to the "naive" method (that might produce some aliases at a low level).� how do you graft them together clicklessly or glitchlessly?� it just seems to me that doing it the same consistent way makes it the least complex and computationally burdensome. -- r b-j� � � � � � � � � � � � �[email protected] "Imagination is more important than knowledge." � � � �
_______________________________________________ dupswapdrop: music-dsp mailing list [email protected] https://lists.columbia.edu/mailman/listinfo/music-dsp
