Timestretching/Pitchshifting

[Christoph Hart]

@d-healey no it‘s a pretty complex algorithm. For me it‘s about as performant as the complex pro algorithm in Ableton.

You might add a HQ button that toggles the low latency that people can use when exporting to bring down the spikes a bit.

[d.healey]

@Christoph-Hart That's a good idea! How is the CPU compared to rubberband? I can't remember what you said before.

[Christoph Hart]

@d-healey way better (2x as good)

[Casmat]

@Christoph-Hart @d-healey just tried it on a 2013 Mac Pro (2.7ghz 12 core intel Xeon E5, with 32 gb ram) and the glitches still occur, could this be a compatibility issue or something?

Thanks!

[d.healey]

@Casmat You're probably just maxing out the CPU, what does the CPU meter in HISE show?

[Casmat]

@d-healey where can I find this? I thought I had found it somewhere (like the CPU/RAM/VOICES info text on some hise vsts) but I can’t find it anymore

[d.healey]

@Casmat Click the little keyboard icon in the top right

[Casmat]

@d-healey ok, just ran it through and a single sampler in timevariant mode with ratio at 100% gives 40% cpu per voice. A single note with all three samplers wit the same settings goes above 100%. And with timestretch disabled altogether on all three samplers, it sits at a happy 10% with multiple notes pressed. Something’s up…

[johnmike]

@Christoph-Hart hope your vacay was good! Any thoughts on this? still having this issue...and in the compiled plugin it's not locking to the BPM either...it locks in HISE but not n the compiled plugin in logic...

@johnmike said in Timestretching/Pitchshifting:

@d-healey back again...this time I am having the bpm issue you mentioned...but seems as tho as long as im between 85-134BPM everything plays fine...until I go 135 and above or 85 and below it falls apart...see vid

https://www.dropbox.com/scl/fi/qu51spzbuqiu0bpcr58lg/BPM-weird.mov?rlkey=ptx1ef3gm8xlm2v4jl3miu8z3&dl=0

[johnmike]

@Christoph-Hart @d-healey any updates or workarounds for this?