Timestretching/Pitchshifting
-
@Lumi283 tonality is between 0 and 1.
-
@Christoph-Hart
Okay, I understand, and what values correspond to semitones? -
@Christoph-Hart any luck with time stretching across multiple samplers? or is it something im doing wrong?
-
@johnmike I‘m on vacation at the moment so I can‘t check stuff with actual audio but I‘ll take a look when I get back.
-
@Lumi283 Try dividing 1 by 12 (if it's linear, I haven't tested it).
-
@Christoph-Hart said in Timestretching/Pitchshifting:
@johnmike I‘m on vacation at the moment
What, do you also take time off sometimes, how will we manage?
-
@Christoph-Hart definitely enjoy your vacay! I can wait lol...was just wondering...sorry to bother! thanks for all you do!
-
@johnmike I just tested and it seems to work fine (I notice that if I set the tempo too high it loops back to a slower tempo which is weird, but that could be a Linux thing).
Here's a video I made
https://e.pcloud.link/publink/show?code=XZlUk2ZWBrmKoz56wb9iQHR1DbWaFkrDBYkHere's the audio file I'm using in the video
https://e.pcloud.link/publink/show?code=XZtUk2ZePJ9aI3hKympkKub2n0EU8IESwA7I left numQuarters at 0
-
@d-healey seems like you are using the same loop in both samplers correct? I was looking on my phone so everything was small…are the on the same key as well? What about on different keys with different loops that are different lengths/different BPMs? That’s my situation
-
@johnmike I didn't try that. I'll give it a go now
-
@johnmike Still appears to work
https://e.pcloud.link/publink/show?code=XZgGk2ZlqVQ1o3uA67uRu2vgfRjCjoGlBCk
Here's the second file: https://e.pcloud.link/publink/show?code=XZxGk2ZLwkpbCMFaJmA0LLPL0NOQF8KSH1y
In the video the file on the left (sampler 1) is 120BPM, the one on the right is 100BPM. Also note that the BPM values I set in the settings panel are out by 10BPM (this is a bug on Linux, so 90BPM in the settings panel is actually 100BPM).
I mapped the samples to different keys in different samples. NumQuarters still set to 0.
At 100BPM the sample on the right plays back at normal speed and the one on the left is slowed. When I set the tempo to 120BPM the one on the left plays at normal speed and the one on the right is sped up.
-
@d-healey interesting…maybe it’s a Mac bug…I will try again once I get home this evening to see…maybe I need a fresh session…maybe some code or something in my session is messing with it(I don’t see how but maybe…)i did replicate an older session to copy over some code I wanted to use in this project…I’ll start from scratch and see what I come up with
-
@d-healey soooo upon opening a fresh session with the loops everything is indeed syncing perfect across multiple samplers...but everything falls apart when I open up the old session with the same loops...so that means something maybe in my coding is messing with the tempo sync possibly...im gonna work on systematically deleting things until I figure out the culprit...thanks for testing for me!
-
@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
-
The processorID is not working for the timestretching modes..
-
@BWSounds Could you explain in more detail?
-
@d-healey
isn't this suppose to control the modes? -
@BWSounds Ah now I understand. I confirm it doesn't work here either.
-
@d-healey
is it possible code this function? -
This would be the scripting for it
const var Sampler1 = Synth.getSampler("Sampler1"); inline function onKnob1Control(component, value) { Sampler1.setAttribute(Sampler1.Timestretching, value); }; Content.getComponent("Knob1").setControlCallback(onKnob1Control);But it returns an error that implies the attribute hasn't been setup in the HISE source. I'll take a look and see if it's a simple fix I can do.
