Forums > Gen

Same pitchshift algorithm sound different in GEN and MSP !?!

January 13, 2014 | 3:40 pm

Hi,

In this little attached patch i have the exact same pitchshift algorithm in gen and in msp… but it sound different! (Better, more fluid in gen)

Can you tell me why or point my mistake?
Thanks!

(I’m benchmarking different monophonic pitchshift algorithms in this topic: http://cycling74.com/forums/topic/monophonic-pitchshift-engines-benchmark-psola-in-gen/ )

…And I would love to add some kind of formant control in this gen algorithm… if, by chance, anyone have some directions to do that… :-)


January 14, 2014 | 3:38 am

Apparently it’s a behaviour of tapout that cannot delay less than the vector size… man… hmm, It would be nice if there would be a warning in the max window when one try to do so…

So when i replace tapin/tapout by delay~, now the sound is the same! (apparently)

Also, then i don’t understand why people are using tapin/tapout instead of delay~ to make some overlap-add pitch shift algorithms, which make the delay go down to 0 all the time, and thus sound bad…


January 14, 2014 | 3:40 am

( here was a topic about this strange tap out thing: http://cycling74.com/forums/topic/tapintapout-vs-delay-am-i-imagining-this/ )


January 14, 2014 | 5:08 am

tapin~/tapout~ introduce one vector size of delay to permit feedback: you can loop back tapout~ to tapin~, assuming you put some gain control in order to destroy your ears ;-) so the minimum of delay that you can have is one vector.

delay~ on the other hand let you have any delay you want, allowing the feedback to be within the object (so you can’t add other effects before in the feedback loop, it’s just gain control).

Gen works at the sample level and let you have 1 sample delay, which explain the sound difference that you may have with small delays.


Viewing 4 posts - 1 through 4 (of 4 total)