Finally uploaded [soundtouch~] binaries, source code and help patch:

http://www.katjaas.nl/pitchshift/soundtouch~.html

Katja

The external works like a charm, I just want to say "thanks".
SuperHighQuality.

The C++/C compilation issues you found probably deserve a link to your pages in the tutorial section.

Alberto

Very nice one Katja, how nice that you can pull off such amazing things for all off us to play with. Quickly throw in a simple feedback in the helpfile and amazing soundscapes are instantly there. I guess i'll be using this in the future in my setup.

nice, thanks

Hello,
Has anyone here tried to use Frequency Modulation with [soundtouch~]? I have attempted it here with , but it doesn't sound much like FM and there is a lot of crackling. Is it possible, or perhaps with a future version?

Edit: The crackling and and a large delay are present even in slower, non-modulatory tempos. The delay seems to accumulate and the "soundtouched" sound becomes farther and farther behind the original.

http://www.pdpatchrepo.info/hurleur/transpositiontest.pd

Hello,
Has anyone here tried to use Frequency Modulation with [soundtouch~]? I have attempted it here with , but it doesn't sound much like FM and there is a lot of crackling. Is it possible, or perhaps with a future version?

Edit: The crackling and and a large delay are present even in slower, non-modulatory tempos. The delay seems to accumulate and the "soundtouched" sound becomes farther and farther behind the original.

http://www.pdpatchrepo.info/hurleur/transpositiontest.pd

Hello diemildefreude,

If you change pitch with [soundtouch~] there is no smooth transition indeed. The Soundtouch library was never specifically made for realtime sound processing, and at compile time I had to choose between two options (two bads actually). This is from the readme that's included with [soundtouch~]:

"The SoundTouch C++ library offers a preprocessor definition to prevent clicks when changing pitch factor. It is called PREVENT_CLICK_AT_RATE_CROSSOVER and lives in file STTypes.h. If [soundtouch~] is compiled with #define PREVENT_CLICK_AT_RATE_CROSSOVER 1, clicks are gone, but the latency will double. For binary distributions of [soundtouch~] I have opted for the clicks rather than the increased latency. The SoundTouch API does not offer a way to avoid them both.

tests, builds and bug reports:

Notice that clicks and cracks during pitch-factor changes are inherent to the way soundtouch~ binaries were built for this distribution, and a compile-time option exists to trade these artifacts for a longer latency time (see section 'how to build'). Please do not send me bug reports about this, but instead recompile the class according to your preference."

To make a smooth [soundtouch~] with low latency, the library code should be substantially rewritten, if possible at all. That is still over my head, but who knows I may be able to do it in the future (or someone else...). Anyway, thanks for reminding me of it.

Katja

Ah, thank you for the reply. I suppose I should have read the readme...

Please be sure to let us know if/when you release a new version!

Hi anybody know how to compile the object in order to remove those click even if increasing the latency. i tried to take off the // from the .h file but nohing happened...