[Philippe]

Hi,
Thank you for the crash report.
We will look at it carefully but at the first look, I do not see something clear but we know which part of the code is crashing.

Could you please make some other tests ?

—> are the writing rights on the “saved loop” folder and the project folder correctly set in order that Logelloop can write in the folder ?
—> what happens if you use “WriteAudioFile” in the yellow arrow in one Looper ?
—> can you write loops using CopyToFile with the main looper ?

Thanks,
Philippe

[Philippe]

Hi Paco,

* swing & microtime

This is an old feature request !
I tried many ways of implementing it, and I’ve never been convinced by the result.
You are interested in the possibility to set the trigger earlier or later for each step?
For example, -0.5 to +0.5 ?
I will try again…

– chords/harmony to track transpose ratios

have you had a look to the microtonality settings?
You can set them by macro.

– grid population ⇀ randomize density

Yes, you can do it by macro !

* grid population ⇀ lock rows & columns from randomization

Unfortunately, to do so, I will need to re-program the randomization from scratch.
But, Yes, I like the idea.
I put it on the list !

Philippe

[Philippe]

Hi,
Tested with 4 loopers. No crash here.
Can send the crash report please?
Also, what is the value of $current_project_saved_loops_path$ ?
Is it on the internal HD or SSD ?
How many loopers?
Can you try with a new project?
Thanks,
Philippe

[Philippe]

Hi,
“Macro ctrls for SFX…” is now deprecated.
You should use the regular macro messages instead.

And :

InsertController sfx 2 18 = MasterVolume {scale(currentCaseOptionValueFloat(0), 0, 127, 0, 1.25)}

is not a right use of “InsertController” which was only intended to be used with LFX inserts and not SFXs.

So, I think what you are looking for is :
SFXSendMessage 2 MasterLevel {scale(currentCaseOptionValueFloat(0), 0, 127, -76, 0)}

You can take it by selecting the MasterLevel line in the “Macro messages for Granular…” part of the help window and click cmd + c.

I hope I understand well what you want to do and this message will help…
Best,
Philippe

[Philippe]

Hi,
You are right, I totally forgot it.
I had Macro, OSC and Midi control for the OverdubFeedbackLevel in the next release.
Thanks for the report.
Philippe

[Philippe]

Hi Daniel,
As you know we made many fixes around the link issues for this version.

At a moment I wrote this in the fixes :

Fixed the link synchronisation”. Does this mean that you have found a fix to the Ableton Link issue?

But in fact, the issue is not fixed, so I think I should remove this in the release note.
I am so sorry… I promise that we will have a fix in a not so long time as it is something important.
Best regards,
Philippe

[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

[Philippe]

Hi Patrick,
So, yesterday morning, you wrote :

I guess it’s doable via macros, but I’m a newbie. Could you suggest a way?

And yesterday evening you posted four perfect macros…
Yes, I think these macros will be useful for many users.

Thank you for the great work !
Best,
Philippe

[Philippe]

Mind explaining what “currentCaseOptionValueFloat(0)” refers to in this context?

This is used in Matrix and Matrix arranger that are data plug-ins that use macro.

And is there a way of achieving something like this:
$Looper_fx[$someindex$]_rank1_HTSFreeze_state$

Not currently, but yes, that would be great and it is on the to do list !

I’m currently using an ugly way:
IfThen { $k_index$ == 1 } Do Set $c_freeze$ = $Looper_fx1_rank1_HTSFreeze_state$
IfThen { $k_index$ == 2 } Do Set $c_freeze$ = $Looper_fx2_rank1_HTSFreeze_state$
IfThen { $k_index$ == 3 } Do Set $c_freeze$ = $Looper_fx3_rank1_HTSFreeze_state$
IfThen { $k_index$ == 4 } Do Set $c_freeze$ = $Looper_fx4_rank1_HTSFreeze_state$

Not so ugly as the index solution isn’t crurrently working ! 😊

What language are we using for these macros in general? I’d prefer to save you from questions I can find answers to.

This a native language, but many things are the same as they would be in Java…

[Philippe]

1/

If you put :

DoOnce
Declare int $k_index$ = $Korpus_data1_rank1_Counter_state$
InsertSendMessage fx[$k_index$] 1 HTSSpeed {scale($midiv_cc1$, 0, 127, 100, 1)}
EndDoOnce

it is the same as you put

Declare int $k_index$ = $Korpus_data1_rank1_Counter_state$
InsertSendMessage fx[$k_index$] 1 HTSSpeed {scale($midiv_cc1$, 0, 127, 100, 1)}

DoOnce is not useful.

2/
You should not trig the macro with your expression pedal, because you will trig to many time the macro and that will create some issues in Logelloop.
Please use a macro loop or something else instead.
3/
I made a mistake, when writing :

DoRepeat
InsertSendMessage fx[$Korpus_data1_rank1_Counter_state$] 1 SpeedFloat {scale($midiv_cc1$, 0, 127, -20, 20)}
Sleep 50
While true

I wanted to write :

DoRepeat
InsertSendMessage fx[$Korpus_data1_rank1_Counter_state$] 1 SpeedFloat {scale(currentCaseOptionValueFloat(0), 0, 127, -20, 20)}
Sleep 50
While true

Sorry

[Philippe]

I think the best approach should be something else.
I will think to it.

For the midi issue, I wonder if this is the looper itsel taht is sending some midi value to the midi device and they come back to Logelloop… I don’t know.

[Philippe]

Hi,
There are plenty of things in your messages.
I can’t answer everything now.

1/
the cc command is to trig the macro.
And yes you should go with a variable to get the cc value. As you’ve done.

To scale the variable, you should use :
InsertSendMessage fx1 1 { scale($midiv_cc1$,0,127,0,1) }
for example

You will find those expression in the “references guide” (button at the bottom of the macro editor.

2/ You should load Korpus in the data plug-ins page in place of in a track as we made before.
I know there are no tutorials yet about this…
But Korpus is more a data plug-in, a new thing in Logelloop 6.

3/ In the macro variable viewer page, you can filter “Korpus” and see the variable $Korpus_data1_rank1_Counter_state$ that reports the current Korpus group.
You can use this variable in you macro.

And in the macro you should put :
InsertSendMessage fx[$Korpus_data1_rank1_Counter_state$] 1 SpeedFloat {scale(currentCaseOptionValueFloat(0), 0, 127, -20, 20)}

assuming Korpus is in data 1 rank 1…

4/ you may organize a loop in your macro, like this :

DoRepeat
InsertSendMessage fx[$Korpus_data1_rank1_Counter_state$] 1 SpeedFloat {scale(currentCaseOptionValueFloat(0), 0, 127, -20, 20)}
Sleep 50
While true

Then, as soon as the macro is running, the speed will be updated every 50 ms.

Please, note that I didn’t test those macro, so maybe there are some typos…

This topic is interesting, I will answer more later, and perhaps I will make a tutos.
Best,
Philippe

[Philippe]

Hi Patrick,
Every Logelloop commands that have an action on long push needs to receive the note off equivalent.
This is the only way for Logelloop to now that you pushed the button for more than 300 ms…

So, you need to configure your Midi footboard to send a cc 0 when you release the button.
I think that is possible on every footboard.
On the FCB1010, I advise preferring Midi notes…
Tell me if this advice resolve your problem.

Sorry for not being clear enough in the soft. I will try to add information somewhere.
Best regard,
Philippe

[Philippe]

Salut Matthieu,
Merci d’être content !

Lorsque tu lances Node dans Max, ça utilise des ressources qui se trouvent dans le package “Node for Max”.
Tu trouveras ce package à l’endroit suivant dans l’application Max : Max/Contents/Ressources/C74/packages.

Là, tu copies le dossier “Node for Max” et tu le mets dans l’application Logelloop en suivant ce chemin :
Logelloop 6/Contents/Ressources/C74/packages.

Tu relances l’application Logelloop et à partir de ce moment-là, tu pourras faire fonctionner les node.js dans Logelloop 6.
On pourrait ajouter le package par défaut mais je trouve que c’est un peu lourd, ça ajouterait plus de 200 Mo à l’application…
Bonne journée,
Philippe

[Philippe]

Hi Daniel,
We will soon be releasing Logelloop 6.1
We’ve tried to make some improvements to synchronisation with Ableton.
It turns out that everything is not yet perfectly stable, but it’s not easy to fix for several reasons.
As soon as Logelloop 6.1 is released, we’ll be working on this again.
I’m really sorry I can’t do better at the moment.
Philippe

[Author]

Posts