Re: [microsound] Max/MSP sound quality

[t4nk3 <tanke@xxxxxxxxxxxx>]

>> I believe that the origin of most of the "bad sound" complaints is in the
>> patch programming, specifically a lack of understanding of
>> aliasing.  MSP is lean and assumes nothing; therefore if you don't have a
> solid
>> understanding of basic DSP theory it's easy to introduce contaminating
> noise due to
>> frequency foldback. for instance, pitching a sample up in MSP can
>> result in aliasing.  (professional samplers use quartic interpolation to
>> minimize the unwanted frequencies.)  using a phasor~ to generate a
> sawtooth
>> wave results in aliasing, as does using a phasor~ -> >~ 0.5 to generate a
> square wave.
>> ...


i found this thread also really interesting a sent it to peter castine, with
whom we´re going to organize a max/msp course here in berlin soon...
i wanted to know what he thought about it and thought i´d share that with u
people....

quote:   "I would only add that Max/MSP's bare-bones approach is not just a
matter of limited development resources; it's a matter of philosophy and
approach. Max is meant to be a collection of simple, encapsulated
modules, each of which does what it says it does. To someone who
understands Max, the notion of a module that would do extra processing
behind your back to fulfill someone else's idea of what "sounds good"
would be utter anathema.

Max objects do what they say they do. No more, no less."


all the best
mark