Dynamic playback/stretch control of a current Korpus looper

[Philippe]

Hi Patrick,
Thank you so much for sharing !
All this work is very inspiring for me !

But, one thing is that you can put more than only one Looper in a group, so every looper in the same group will be affected by this kind of controlers.
In your case, that’s probably not a limitation, but this culd be a bit tricky if we would like to implement this natively in Logelloop…

Anyway, as, for the second day you are at the top in macro programming, I suggest you to load “Matrix” and “Matrix Arranger” in the data plugins.
They aren’t interesting in the current case, but may be useful in some other situations.
Best,
Philippe

[Pacocreative]

Hey, thanks for your kind words.
I am using it with 4 loopers concurrently, and using my FCB1010 to the control each of the loopers independently, so a common footswitch layout acts on whatever looper is selected via Korpus, including two pedals that control playback speed and scrubbing in freeze mode. It’s interesting to see how it would extend for multiple loopers in a group, I guess I’ll need to do some testing and debugging.

Thanks for the hint on Matrix, I’ll learn it eagerly.
Currently, I’m looking more into Granulaterre, where I have some ideas.
I’ll start a separate thread for clarity.

[Pacocreative]

Here’s a bit of limitations I arrived at while scripting usage of Korpus.

1/ Missing overdub mix control (reported earlier)
2/ Expanded vs contracted view not stored in a preset -> this would be handy
3/ No Korpus autofade lengths available as variables -> this would be handy
4/ Limited information about groupings (details below)

Assume this situation:
Looper 1 – Group 1
Looper 2 – Group 1
Looper 3 – Group 1
Looper 4 – Group 1
Looper 5 – Group 2
Looper 6 – Group 3

Korpus currently reports the following variables:

End (number of groups)
Counter

This is sufficient to navigate across looper groups and accessing Korpus actions via macros.
But when scripting individual loopers settings and cycling through them, I arrived at the following problem:
Using $Korpus_data1_rank1_Counter_state$ only returns current group, but does not let you access information about how many loopers sit inside a group, and how many in total.

A primitive way of doing what I wanted was:

$Korpus_data1_rank1_Counter_state$ == 1    —> Acess fx1 1
$Korpus_data1_rank1_Counter_state$ == 2    —> Acess fx2 1

etc…

This works until you have several loopers in a group.

I think it would be great to have some more information in Korpus state variables about:
1/ How many groups there are (we got it)
2/ How many loopers are there in total, with their addresses and grouping info
3/ How many loopers (and which ones) are in a current group

I don’t have a specific solution in mind here, just sharing a usage case where it would be beneficial to have a bit more info available.
Theoretically I can hard-code specific cases in my macro, but it makes macros less universal and sharable.

Food for thoughts.

[Author]

Posts