EP-133 K.O. II Tips 5: Time Stretching (stretch to 3, 8, or 16 bars; troubleshoot chopping & more)

[@This1That0]

Thanks for the explainer. Ive been time stretching a lot lately and I’ve mostly stuck with bars. Ill check out bpm as i didnt realize the chopping kept the original bar stretch! Thats a great find.

[@yellow.eyez.]

Great video , thanks

[@pongtrometer]

Freakin’ amazing overview, thanks so much . Excellent stuff 👾

[@namedoesntmatter7681]

Hey man great video and some nice tipps! I was wondering if anybody knew how to truncate or crop a sample or is there some kind of workaround? This would make editing, stretching and chopping samples much easier I think.

[@windowbed]

Thanks for watching! I don't think there's a way to do that. You can adjust the start/end points for a pad, but you can't save it as the new start/end of the original sound.

[@namedoesntmatter7681]

@@windowbed Yea I tried a few things like copying and so on but nothing worked. I hope this will be added with an update. Would help saving space and I think it would make the combination of trimming, timestretching and chopping much easier or clearer. As far as I understand the chopping here is basically cloning the pad with new trim settings for the sound. And with that the timestretch settings are copied set for the lenght of the full sample. That means I have to redo the stretching but for each chop. Additionally if my chops are not all the same size the timestretching is basically not working anymore. Does that make sense or am I thinking in a wrong direction here? I think after trimming and timestretching a crop/truncate into a new sample would make that much easier.

[@windowbed]

I agree it would help save space and time if we could truncate samples. Not sure if that's gonna happen, so in the meantime you might want to use BPM mode to time-stretch your samples before you chop them. It's less precise in some ways, but the benefit is that you can chop your sample and each pad will play back at the rate it was stretched before, instead of stretching to a whole bar or something else.

[@LuminalAbnormality]

Good info man. I was looking for a time stretching deep dive a few days ago. You can't even do this on the op-1(that I know of) so this is definitely helpful.

[@windowbed]

Thanks! Yeah, I don't think you can do time stretching like this on the OP-1 at all. Pretty neat feature.

[@ChemistryLemur]

Very good tips and explanation, subbed!

[@windowbed]

Thank you!

[@jakewastaken]

So you could theoretically sample in something that was deliberately sped up before sampling and then stretch it out 8 bars in a loop while bringing it back to the original speed if you got it just right? Or at least close to it?

[@windowbed]

Yep! It'll degrade in quality quite a bit but you can see Ricky Tinez doing this in his first video (I think) with the KO II--he samples something in pitched a few octaves up then lowers the pitch on the KO II.

[@eurorail]

So I like your channel and I like what you do but this video is absurd. Why don’t you just say that this algorithm that they use for time stretching is not ready for prime time and drop it. It is not useful. All it shows is that in fact Some of the features are toy like.

[@windowbed]

Thanks for the comment! I'm curious about why you think the time stretching isn't ready yet. Using sound edit + time fader, you can stretch a sample from 1/8 bar to 40 bars and nearly any duration between, which is all I could ask for. As far as showing weird behaviors in the device, my interest is in explaining things that confused me to help others. I don't work for TE so I'm not showcasing it or anything; just teaching people who already have one.

[@baer_of_sidechain]

Great deep dives, love your op z explainers too

[@jakewastaken]

It is useful to understand the particular quirks of any tool, and it’s often fun to explore what’s possible and what isn’t. Not every video on KZbin is a product review or a rant. Some are just deep dives and exploration, and a lot of us really value that. The Altair 8080 wasn’t “ready for prime time” and “wasn’t useful” to most people when it dropped. It seemed like mainframes were the only useful way to have a computer. What ended up happening, however, is that people tinkered and came to understand its quirks and limitations. This allowed them to exploit those quirks and find useful ways to explore new possibilities. We owe almost everything to those pioneers, so we should encourage this kind of spirit. You wouldn’t have a PC or a smartphone without it.

[@baer_of_sidechain]

The purpose of this video is to show how a combination of settings can be used to push the stretching algo in KO2 to its limits. Which is great value, given there's no shortage of rant videos on how KO2 is missing [insert your favorite feature] and is not [insert your beloved sampler]. Besides, what might sound as an absurd limitation to you could be the most embraced quality to someone else.