Main repitch algo is lossy, could be better

[simbio-sounds]

A repitch algorithm should work like a 'tape' (pitch and speed combined), and should be the easiest to have as the highest quality.... however, at the moment, its showing quite a big loss of quality when pitching down more than 12 semitones, and especially seems to be missing low end data

Would be great to experiment or do some research on different repitch / tape style warping, maybe comparing quality with inbuilt DAW behaviour or other.... you could look into the algos that MIXXX (open source) software uses and suggest some of these to claude?

I am really invested in helping you improve this as it will make my bitwig experience so much better!

[tucktuckg00se]

Intersect’s current repitch mode uses straightforward variable speed resampling with basic linear interpolation, so pitch and playback speed stay linked like tape/vinyl. That approach is common in samplers because it has very low overhead, but it can sound rougher than higher quality interpolation on larger pitch shifts.

There’s definitely room to improve that. I’d like to look into offering higher quality repitch options later on, probably cubic interpolation and/or sinc interpolation options, so users can choose between low CPU cost and better sound quality.

[simbio-sounds]

cool, yes maybe it is the interpolation differences. It seems bitwig use cubic interpolation in their repitch mode in the sampler and it sounds really good :)