Timestretching/Pitchshifting

[d.healey]

@BWSounds Yeah I tried numbers first as well :)

[Lumi283]

@d-healey I tried, but it's not working... I tried with Tonality = 0.01, it changes the pitch but impossible to define which one.

[d.healey]

@Lumi283 I just looked at the docs and I don't think the tonality parameter does what you want - https://docs.hise.audio/hise-modules/sound-generators/list/streamingsampler.html#timestretching

Looks like you can just use any standard pitch modulator as long as timestretching is enabled for the sampler

If the timestretching is enabled, any pitch modulation (using the modulation or root note detune) will not change the pitch using resampling but with the pitch transposition of the timestretch algorithm which retains the duration of the sample.

[d.healey]

@Christoph-Hart Did you say there was a way to get a stretch ratio below 50%?

Oh never mind, I can just set it in the function and it works.

[Casmat]

@d-healey Can't get timestretch working properly on my end, I have three samplers and setting 2x timevariant timestretch to all three causes a lot of audio issues and clips, keeping only one sampler activated works better, but theres still audio issues, doesnt seem to be really cpu since my task manager cpu chart shows some resources left... the video shows the issues:

timestretchissue.mp4

In the vid, the first part is showing the timestretch enabled on all three samplers with half and double speed stretches. Then I turn off the first two samplers so that only one is on half speed stretching and it still makes some audio issues. Any ideas?

[d.healey]

@Casmat I can't assess what's going on behind the scenes in that video. Make a test project, add 3 samples, load some samples, play around with the settings in the sampler module UI. See what result you get. If it works without issue then the problem is caused by something else in your main project.

Are you using IPP?

[Casmat]

@d-healey yup, test project does the same, ipp is enabled and just recompiled today..

[d.healey]

@Casmat Send me the test project (with some of the samples you're using if possible)

[Casmat]

@d-healey https://we.tl/t-bDHJ1vv0Jg Try pressing down chords of 3/4/5

[Christoph Hart]

@Casmat you can‘t play 10 voices of timestretched sounds. One voice is about 10-15% depending on your system.

[d.healey]

I'm not noticing an issue

https://filedn.eu/larUQgXOwVjQdvpPaD96lHH/2023-08-28 12-09-59.mkv

[Casmat]

@Christoph-Hart @d-healey so i guess its time to get a new computer:grinning_face_with_sweat:

[d.healey]

@Christoph-Hart Do you think there is anything that can be done to improve the CPU usage, especially when in low latency mode? At the moment I think the applications for the time stretching in virtual instruments are quite limited because of these two factors.

[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