Timestretching/Pitchshifting

[d.healey]

@johnmike What about using multiple samplers, does that work?

[johnmike]

@d-healey I’m sure that would work…but for what I’m trying to do I’d need 88 samplers lol(a sampler for each loop on each key)…it would probably be way more efficient and less time consuming for me to just make everything a uniform BPM and then put them in one sampler…

[Christoph Hart]

no, the idea is that the tempo_sync mode will sync each sample to the BPM regardless of its source BPM, but this mode isn't working correctly yet. I'm totally undecided how to address the issue of detecting the bar length and getting the right multiplier so if anyone has ideas how to do this, let me know.

[johnmike]

@Christoph-Hart ahh gotcha…yea that would work…but as it stands this is still way ahead of where we were! I’ve been waiting for this!

[Lindon]

@Christoph-Hart said in Timestretching/Pitchshifting:

no, the idea is that the tempo_sync mode will sync each sample to the BPM regardless of its source BPM, but this mode isn't working correctly yet. I'm totally undecided how to address the issue of detecting the bar length and getting the right multiplier so if anyone has ideas how to do this, let me know.

Yep - you could do it like Kontakt(yew did I just say that?) - have a scripted call that lets the programmer/developer tell the process exactly how long in bars/beats each loop is and what tempo it is

[Christoph Hart]

@Lindon Why not just make a new sample property called NumQuarters that will be used to calculate the original BPM of the sample?

This will override the NumQuarters that you can set with the timestretch properties, which will override the default fallback behaviour of guessing how fast it is using the current tempo.

[Lindon]

@Christoph-Hart said in Timestretching/Pitchshifting:

@Lindon Why not just make a new sample property called NumQuarters that will be used to calculate the original BPM of the sample?

This will override the NumQuarters that you can set with the timestretch properties, which will override the default fallback behaviour of guessing how fast it is using the current tempo.

yep that works too...the only (slight) wrinkle is dealing with odd time signatures.. 6/8 for example - but even then all the developer need know is the number of bars and they can * 4 to get NumQuarters

[Christoph Hart]

@Lindon said in Timestretching/Pitchshifting:

6/8

=> 3 Quarters.

[Christoph Hart]

Alright, I've implemented the NumQuarters property. If this is non-zero, it will use the length of the sample with this information to calculate the source BPM, which should let you use different BPM values for every sample.

I've also fixed something in the engine and now it should play multiple voices with the correct time ratio in sync mode.

[d.healey]

@Christoph-Hart Nice!

[modularsamples]

In sampler it seems monophonic samples aren't summed when the stretch modes are enabled, everything comes out the left speaker.

[BWSounds]

@Christoph-Hart said in Timestretching/Pitchshifting:

I'm thinking about adding this to the AudioLooper too (it's pretty obvious that this might be useful there). Is anybody using the tempo synced mode in a real project? It previously changed the pitch to match the tempo but I guess that is so totally useless that I can replace the functionality and enable timestretching by default when the tempo syncing is activated.

is this a thing yet?
For some reason I cant build from the "feature_timestretch" commits...i'll figure out why on my own...
just asking

[Lindon]

@Christoph-Hart said in Timestretching/Pitchshifting:

Alright, I've implemented the NumQuarters property. If this is non-zero, it will use the length of the sample with this information to calculate the source BPM, which should let you use different BPM values for every sample.

I've also fixed something in the engine and now it should play multiple voices with the correct time ratio in sync mode.

Nice, but I still worry about doing this calc for those 13/7 time signatures, and you know there will be some...

[ulrik]

@Lindon said in Timestretching/Pitchshifting:

Nice, but I still worry about doing this calc for those 13/7 time signatures, and you know there will be some...

Hehe...

[johnmike]

for some reason when I have loops in multiple different samplers with tempo sync turned on they won't sync together...seem to work fine when in the same sampler...but if I want to put like a group of kick loops in one sampler and then a group of snares in a different sampler...tempo sync falls apart...something im missing?

[johnmike]

anything here? anybody have any solve for time sync'ing multiple samplers? or do I need to just keep everything in one sampler? which will suck for what I would like to do as far as controlling the volumes/sends for each group of loops that are in a sampler of it's own...unless there is a way to group samples inside of one sampler and control the volumes on those groups?

[d.healey]

@johnmike said in Timestretching/Pitchshifting:

control the volumes on those groups

[johnmike]

@d-healey interesting...will try this

[johnmike]

@d-healey can I assign an interface slider to those round robin groups tho? I also would love to be able to send the groups to effects buses as well tho...individually...and multi-outs was my end goal as well...which is why I had multiple samplers setup for proper routing of volumes, FX, and outs

[d.healey]

@johnmike I've never used it, but I don't see why you could use a slider to control that value.

Groups can't be routed though (at least not yet, it's on my wishlist), so you're not going to be able to send each set of samples to different effects.

I think you're better off nagging Christoph to solve the bug with multiple samplers going out of sync. Perhaps provide a snippet or demo project that demonstrates the problem.