In a nutshell, you'd get exponentially higher CPU load without any audible improvement at higher sampling rates. The thing with PM is that the algorithm is built around measurement data that's based on actual people listening to actual audio - so the data set doesn't and can't *exist* for frequency content above around 22khz. Yeah, I know, that's inconvenient, and yes, that's planned. Surely you must have higher sample rates planned for a future update!?!Hey, Why isn't it supporting up to 96KHz? You know it's terribly inconvenient only supporting lower sample rates since I only work in 88.2 & 96Khz. Man I haven't seen a spec like that in 10 years. What the hell Denis?!?! Damn!! Pitchman only supports 44.1 & 48Khz!?!?! Is there perhaps a demo that exhibits how PM can help in such a case? these two uses are of great interest to me as I tend to use quite a lot of feedback with delays. Feed synth pads through it that take up too much space, quantize them to their actual pitches, cranking up PURIFY to make them sound more 'organ-esque', thus loosing most of their noisiness and diffuse character. Feed wall-of-sound DI guitars through it before re-amping, that can give nice textures. Wherever you'd use resonators, filter banks, vocoders, pitch shifters etc, give PM a try. By putting PM on the return after the delay, he can force the echoes into whatever harmony is currently playing. Delay with feedback is great to smooth out transitions between song sections, but obviously, the repeats will be in the 'old' pitch of the, say, last chord of the verse.and depending on the chords of the next section may clash in pitch.

One user reported using PM to make feedback delays not clash with chord changes.

Zynaptiq pitchmap audioz