[Philippe Ollivier]

Salut Christophe,
Il y a un souci avec WaitEndDurings. J’ouvre un ticket pour regarder cela et corriger aussi vite que possible. J’ai l’impression que ça rejoint un autre problème que j’ai repéré avec les WaitEndDurings, donc, c’est intéressant d’avoir ta macro pour faire des tests.

Dans l’attente, je te propose d’utiliser la macro ci-dessous qui devrait faire l’affaire. Je remplace les WaitEndDurings par des “Sleep $current_loop_duration_ms$” ce qui dans le cas présent équivaut à la même chose, mais simplifie l’arrêt de la macro, car dans Logelloop 5, on ne peut plus arrêter la macro pendant un Wait. Cela évite de stopper, par erreur, une macro en cours d’exécution.

Autrement dit :
Sleep = tu peux arrêter quand tu veux
WaitDuration (et tous les autres Wait…) = tu ne peux pas faire stop

Je mets aussi :
MacroStopIf {$current_loop_duration_ms$ < 500} En début de macro pour éviter qu'elle tourne s'il n'y a pas de boucle ou une boucle trop courte. Tu peux changer la durée minimale pour qu'elle corresponde à tes besoins. Bonne journée, Philippe

[Philippe Ollivier]

Bonjour Christophe,
Merci pour tes retours qui font plaisir.
Effectivement, Logelloop 5 est beaucoup plus performant à plusieurs endroits et ça a été un gros travail pour y arriver.

Note que si tu l’utilises en 96 kHz, tu diminues la latence de moitié, car les paquets de son sont deux fois plus petits.
Tout sera donc plus réactif, y compris les accès MIDI.

Effectivement, beaucoup de changements au niveau des macros.
Il faut maintenant obligatoirement déclarer les variables que l’on utilise, ce qui permet d’éviter bien des soucis par la suite.

Looper va encore s’améliorer et se voir doté de fonctions majeures dans les mois à venir.
J’espère produire une vidéo de démonstration de ses possibilités rapidement.

Bonne journée,
Philippe

[Philippe Ollivier]

Hi Andy,

“But then everything you then say is very interesting in this regard: a plugin that drives volume and pan would indeed be useful…if I could tell it to do “this” over x amount of time in the way that automation curves in a DAW do.”

Yes, the idea is to connect the curve duration to the loop length. So, it will be possible, for example, to tell the curves will have a “x loops length duration”, as it is in the macro world. But this will be possible with graphical settings.

Philippe

[Philippe Ollivier]

Hi Gwenole,
Here is a macro example for this kind of situation.
Philippe

//*************************** macro begin *****************************
// This macro will reproduce the During reach macro function
// It may be useful with settings not implemented
// in the native During reach funtionnality
// ********************************************************************

// Put your personnal settings here
// you need to know your begin value, your target value
// and the during duration
Declare float $dr_begin_value$ = 10000
Declare float $dr_target_value$ = 200
Declare int $dr_during_length_ms$ = 3000

// Only change those declarations if you
// need something particular
Declare int $dr_step_duration_ms$ = 10
Declare float $dr_steps_count$ = {$dr_during_length_ms$ / $dr_step_duration_ms$}
Declare float $dr_step_size$ = {($dr_target_value$ – $dr_begin_value$) / $dr_steps_count$}
Declare float $dr_current_value$ = $dr_begin_value$
Declare float $dr_current_duration_ms$ = 0

DoRepeat
$dr_current_value$ = {$dr_current_value$ + $dr_step_size$}
Sleep $dr_step_duration_ms$
$dr_current_duration_ms$ = {$dr_current_duration_ms$ + $dr_step_duration_ms$}

//Choose the setting here
InsertSendMessage trk1 1 Frequency $dr_current_value$

While {$dr_current_duration_ms$ < $dr_during_length_ms$} //**************************** macro end ******************************

[Philippe Ollivier]

Hi Olivier,

1/ You are right, there is an issue in Logelloop 5, I made a mistake while making the possibility to select a track as a sample source for Granulaterre. I found it last week and it is fixed for the next release, sorry for the inconvenience.

2/ Haha… I think you just won the prize for finding the oldest bug in Logelloop. I forgot to implement the NextLoopDirect listener for the keyboard and this probably happened between 2002 and 2005, while Logelloop still was in alpha. I fixed the issue, it should work perfectly in the next release or beta version. Concerning the NextLoopDirect macro command, it’s a bit weird as it works here, i made some improvement in this, it may fix something on your computer…

3/
Undo and Erase have a dedicated wait function named WaitEndEraseOrUndo, I think if you use it in place of the first sleep, everything is OK.

//****** Begin of the macro *****
UndoRecord
WaitEndEraseOrUndo
NextLoop
Sleep 30
UndoRecord
// ************ End of the macro *************

Why don’t you use

//****** Begin of the macro *****
EraseAllLoops
// ************ End of the macro *************

Or

//****** Begin of the macro *****
EraseAllLoops
WaitEndEraseOrUndo
LoopADirect
// ************ End of the macro *************

Please use one message for one topic, this will make easier the search on the forum.
Thanks,
Best regards,
Philippe

[Philippe Ollivier]

Hi Olivier,
Yes, this is possible since Logelloop 5.0.20.

Below is an example of macro which set the level of each track to a random value between -50 and -20.
We use $track_id$ to set the track number and the syntax is trk[$track_id$].
Of course you can use any declared variable name…
Note that it is also possible to use this with fx, in and out.
Philippe

//************************* Macro begin **********************************************
Declare int $track_id$ = 1
Declare Once float $min_vol$ = -50
Declare Once float $max_vol$ = -20
Declare float $value$ = 0.

DoRepeat
$value$ = {randomScaleInt($min_vol$,$max_vol$)}
During 4500 Reach $value$ TrackVolume trk[$track_id$]
Sleep 50

Set $track_id$ = { ($track_id$==10) ? 1 : ($track_id$ + 1) }
While true
//************************* Macro end **********************************************

[Philippe Ollivier]

Salut Heikki,
Il faut bien que tu commences par retirer la copie d’écran de manière à garder l’interface Logelloop sur l’ordi et avoir la vidéo sur le vidéoprojecteur.
Dans ce cas, tu gardes l’accès à l’interface de Logelloop et bien sûr, tu peux aussi tout commander, y compris la vidéo, à l’aide de macros.
Tu peux donc utiliser la vidéo pour commander Logelloop…

Attention, il faut une carte vidéo assez puissante sur l’ordi.
Philippe

[Philippe Ollivier]

Hi Andy,
There are plenty of possible answers and I make a first post, but it’s possible that I make some other messages later…
I am afraid that using an external DAW is probably the more complicated solution, but yes, you will have a timeline…
The question is : is a timeline useful during a looping session and/or an improvised session?

First of all, I think of a particular function, nobody’s aware of…
Before a multiplication, you can click on the Normal button under the Multiply Button (on Commands window) and when the multiplication occurs, the first loop is not duplicated. OK, that’s a bit rude, but one possible solution! -)

>> “being able to draw in volume shapes on the Editor would actually take Logelloop to a whole new level. Is such a thing even possible in the future?”

Drawing a volume shapes on the editor, is not really in the Logelloop paradigm, I think. Or, at least, you should be able to store the draw and use it later with a loop of a different length. But, to be honest, we have the idea of a native plug to draw a form that you can drive the volume, speed, pan, etc. of the track where it is inserted. For now it is just on the to-do list, don’t expect to see it soon.

>> “Or is there another way of automating volume on a loop after it is recorded?”

The current simplest way of automatizing the Volume may be the LFO, you can connect a LFO to one or more tracks, with a very slow setting, you may even change the phase of one LFO, or delay it… and the faders will move very slowing changing the volume, pan, etc. of the current track. This a solution to edit the volume for slow changes.

If you want to edit inside the bar of the loop, you may use the Slicer…

Of course, you can connect the volume of the first track to a MIDI pedal and move it manually.

>> “Is this where Macros come in?”

Macros are in Logelloop to make everything personal. In this case, of course, you may use a macro.
The advantage of a macro is the fact that a duration is relative to the loop length and this is possible with variables.
For example, your loop length is expressed with the $current_loop_duration_ms$ variable.
So, you may decide to change the volume of the track in relation to the current Loop length.

For example, this macro will change the volume level in relation to the position of the playing head (assuming the speed is set to 1) :

//********************************** Begin of the macro *********************************
Declare int $high_level$ = -10
Declare int $low_level$ = -45

WaitBeginLoop
TrackVolume trk1 = $high_level$

DoRepeat
//Wait a bar
WaitDuration {$current_loop_duration_ms$/ 4}

//Move the fader down during half a bar
During {$current_loop_duration_ms$/ 8} Reach $low_level$ TrackVolume trk1
WaitEndDurings
//Wait half a bar
WaitDuration {$current_loop_duration_ms$/ 8}
//Wait a bar
WaitDuration {$current_loop_duration_ms$/ 4}
//Move the fader up during half a bar
During {$current_loop_duration_ms$/ 8} Reach $high_level$ TrackVolume trk1
//Wait half a bar to complete the loop…
WaitDuration {$current_loop_duration_ms$/ 8}
WaitEndDurings
Sleep 10
WaitBeginLoop
While true
//********************************** End of the macro *********************************

There are plenty of such possibilities with macros.

Something I also like very much is to use random calculations to set the volume :

//********************************** Begin of the macro *********************************
WaitBeginLoop
DoRepeat
//Wait a bar
WaitDuration {$current_loop_duration_ms$/ 4}

//Move the fader to a random level during half a bar
During {$current_loop_duration_ms$/ 8} Reach {randomScaleInt(-76, 0)} TrackVolume trk1
WaitEndDurings
//Wait half a bar
WaitDuration {$current_loop_duration_ms$/ 8}
//Wait a bar
WaitDuration {$current_loop_duration_ms$/ 4}
//Move the fader to a random level during half a bar
During {$current_loop_duration_ms$/ 8} Reach {randomScaleInt(-76, 0)} TrackVolume trk1
//Wait half a bar to complete the loop…
WaitDuration {$current_loop_duration_ms$/ 8}
WaitEndDurings
Sleep 10
WaitBeginLoop
While true
//********************************** End of the macro *********************************

>> “Further: I notice there is Loops A B and C! How do people use these two extra loop systems in their workflow?”

I do not often use A B C, so if someone else could say something about this way of construction loops, I will also be glad to read! -)

>> “Is this the way to create meta-structure?”

Yes! note that’s also possible to copy between loops with the Copy function. It is also possible to use CopyAfter to aggregate loops.

>> “And then there are Presets! and morphing from one to another..again, is this a way to build higher structures?”

Yes, you can use presets and you can recall your presets with the preset arranger or with a macro…
best regards,
Philippe

[Philippe Ollivier]

Hi Andy, this is strange, that’s ok on my computer with the current Logelloop version. Which plugs are they? if that’s related to Native Instruments plugs : https://www.logelloop.com/2019/06/21/limitations/
best regards,
Philippe

[Philippe Ollivier]

Hi Ploughman,
Looking at the code and thinking of a better way to manage the monitor part, I remember that the monitoring is a very old routing system in Logelloop (made for Logelloop 1!). And I think that, as now we have a bunch of aux channels, the good option to monitor the inputs is to use an aux channel in pre. That’s the way we do it on every mixer or DAW.

So I don’t think I will change the way Monitor is working and it can even be deprecated and disappear at a time (Logelloop 6 or 7).
I highly encourage all Logelloop users to go with aux channels to monitor inputs.

Thanks for your comprehension.
Philippe

[Philippe Ollivier]

Hi Andy,
Many thanks for this contribution. In fact, we did this kind of comparison earlier during the Logelloop 5 development but not recently with the release version. Logelloop 5 takes fewer CPU in many cases and this is visible on both activity monitors…

Thant would be interesting to try your project/settings on different computers to compare the results, but for sure, in any case, performances are better with Logelloop 5.

Philippe

[Philippe Ollivier]

Hi Ploughman,
Also note that it is possible to check AS (auto start) in the preferences panel on this macro slot, so that, at each project load, Logelloop will be set to your basic settings.
Cheers,
Philippe

[Philippe Ollivier]

Cette situation est bizarre, il faudrait plutôt comprendre pourquoi d’un coup le menu ne propose plus les presets qui existent pourtant bien puisqu’ils s’affichent à nouveau lorsque tu en crées un nouveau…

[Philippe Ollivier]

Salut Christophe,
Tu as vérifié qu’il est bien chargé avant de demander l’effacement?
Par défaut, le presser de clicher se charge en début de boucle, donc, il faut qu’une boucle soit enregistrée pour que ça se charge.
Philippe

[Philippe Ollivier]

Hi Ploughman,
That’s a very good question! -)
In fact, those two buttons where clickable in Logelloop 1 but I changed the way they work to save some CPU consumption. OK , that’s a very law gain of CPU, but more than ten years ago that was important. I looked at the code and I can say that I can change it, but not before the Logelloop 5 release.

The workaround is to open two inputs needed by the same audio hardware input, one for the monitoring and the other for the Looper routing.
Then, Mute and unMute will do the trick.

Hope that’s not impossible for you to do it.
Philippe

[Author]

Posts