Korpus Loopers – Extend buffer length

[Pacocreative]

Hey,

Just arrived at a situation laying out a simple beat, where I’d love to load a sample into a buffer, and bee able to extend the buffer arbitrarily.
For example, to have a 500ms kick drum one in a bar or so…

This could work as follows:
1/ via AudioMessages – Double / SetLengthBeats / SetLengthSamples and insert s
2/ via UI – extend a loop to a sync length. For instance – if a sample is 500ms, but a looper is set to sync to 4 beats, it would extend it’s length (by inserting silence) to 4 beats.
3/ via UI Add a beat / Add a bar / Double buttons

Not crazy important, but thought would share as an idea.
I realize it’s always a matter of balance to choose what NOT to include and where to NOT spend time programming 🙂

[Philippe]

And how to explain to users how it works…

But note that you can already do it with 2 or 3 loopers and 1 or 2 macro using PasteAfter.

• This reply was modified 2 weeks, 6 days ago by Philippe.

[Pacocreative]

I re-approach this. I do think it would be actually handy to think about sync options of loaded samples, assuming we want to work in beat-synchronous mode.
Currently, when you load a sample into a modular looper, it loads in total length and theres really not much synchronization:
1/ Even if sync is set (say to 4 beats), the selection of the sample does NOT correspond to that related to tempo, but that of a sample. So we can’t really load a long loop and easily select 4 beats period, to make a simple beat.
2/ If we load a really short sample (as it’s the case with many percussive sounds), there’s no easy way to make this thing last a bar.

given this, I think it would be beneficial to:
1/ Have a restart/sync button that starts the loop on the beginning of the next phrase
2/ Have a button, that would either trim or extend the content of a looper to that which is set in the sync options
3/ Have an option for waveform selection follow the beat length derived from current tempo and sync, not from the loaded sample length

That way we could easily take a one-shot and use it as a groove foundation.

Yes… probably I can work around a lot of that with macros, but I believe many users will find it handy.

[Philippe]

Hi,

Even if sync is set (say to 4 beats), the selection of the sample does NOT correspond to that related to tempo, but that of a sample. So we can’t really load a long loop and easily select 4 beats period, to make a simple beat.

You are right, I forgot something there… Sorry.
So, I fixed it and now if you hit “Copy”, you copy the real selection in the sample, even in synced mode.
Also, the in and out value memorized in the variables are correct.

If we load a really short sample (as it’s the case with many percussive sounds), there’s no easy way to make this thing last a bar.

Yes, I agree, and yes, I’ve also found myself wondering what to do in this kind of situation.
I add a TrimLoopSamples macro message. With it you can reduce or extend the loop length.
You can use it like this :

InsertSendMessage fx2 1 TrimLoopSamples {$Looper_fx1_rank1_current_length$}

Is TrimLoopSamples a good name for this macro message ?

I wait to add a native UI to do this because I want to find a better idea than resizing the modular looper window to add this UI… We will need to think about it later. But with the new macro message it is really easy to trim the loop length with a simple Matrix.

Have a restart/sync button that starts the loop on the beginning of the next phrase

We have the “Start” macro message to restart the loop, but it is immediate in any case.
In the next release, it will wait for the next beat or the next first beat regarding the synchronization settings.

And also, in the next release, when you paste a sample in a looper and the looper is synced to the metronome, the sample will be played from the next beat or bar regarding the synchronization settings.

Philippe

• This reply was modified 1 week, 3 days ago by Philippe.

[Pacocreative]

I think that gives some good options.
Thanks for considering my input.

On the UI side, one note I had was that minimized/extended window state of a looper is not memorized in presets. Not a priority thing for sure.

“TrimLoopSamples” — yeah something along the line of this. Mybe TrimSample? or SnapSample?

[Author]

Posts