[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.

[Philippe]

Hi

1/ Overdub Mix level exposed for macro

In the next release you will find OverdubMixLevel in the list

2/ Track pitch exposed for macro

In the next release you will ind TrackPitches that can be use like this

SFXSendMessage 1 TrackPitches 6 pitch 12

Where 6 is the track id, and 12 is the desired pitch value
To set the begin or end pitch faoir each track you will be able to put :

SFXSendMessage 1 TrackPitches 8 pitchout 2
SFXSendMessage 1 TrackPitches 3 pitchin -7

Or even :

SFXSendMessage 1 TrackPitches 6 pitch 12 8 pitchout 2 3 pitchin -7
You can put as many setting after the word TrackPitches in the same list.

3/ RandomGrid to accept probability parameter (0. = none, 1. = 100%)

(I think you already asked for this somewhere else. Please don’t double questions, messages and feature request. The more informations I will receive, the less time I will have to read, answer and code 😃)

Changing this would need to re-write a lot of code and taking the risk to break user presets.
A new tool should be available soon to meet this demand.

4/ Ability to lock rows, columns or cells from randomization

Same answer

5/ Ability to provide programs by rows in a simple list/array format

In the next release, you will find a new GridSet macro message to Granulaterre.
you will be able to use it like this :

SFXSendMessage 3 GridSet $x_grid$ $y_grid$ {randomBool(0.5) ? 1 : 0}

where the first value is the x position 1 (is left bottom), the second is the y position (is left bottom) and the third one is 1 to activate or 0.
You will even be able to use it like this :

SFXSendMessage 2 GridSet 2 8 1 4 5 1 5 6 1 9 5 1 10 6 1 10 7 1

6/ Better input routing — Is there a way to direct signal to GT coming from Inputs window AUX sends? Or other FX tracks? That would allow to pre-fx and have consistent routing with Korpus loopers.

1 – put a looper in fx1 insert 1
2 – put an audio send in fx1 insert 2
3 – set the audio send to the channel 1
4 – set an audio receive in one input of Logelloop
5 – set the audio receive to the channel 1
6 – you will now receive the looper output in Granulaterre

[Philippe]

Hi,
Yes, good catch !
I forgot the former message to normalize when I changed for the AudioMessage menu.
I remove the old one that was not connected anymore.
You should now use :

SFXSendMessage 1 AudioMessages Normalize

This already work in the current version.
Philippe

[Philippe]

Hi,
I have added User Presets in the AU plug-ins loader.
They can be loaded by macro messages.
I think this will be useful for many mac users.
Philippe

[Philippe]

Hi there,
No, there is no tool to capture Midi events in macros.

We have indeed made many improvements since the first versions of the scripting system, and we regularly add new tools in this area. I don’t think we’ll be adding any midi listeners to do what you want in the near future. If you know how to program using Max, you can easily make a data plug-in that listens to the Midi device and feeds a variable that you then use in the macro… If you can’t do it yourself, I will try to make something for you.

Otherwise, if you have a little patience, I’ll try to think of a tool to easily convert incoming Midi streams and direct them to Loopers or Granulaterre. To be continued…

And yes, this tool you are thinking about is a good idea !
Philippe

[Philippe]

Hi,

You are right, and I arrived at the same issues while programming a 150-buttons Matrix (!).
Playing currently with a layout for Novation Launchpad X, and setting up most of my workflows there.

This is great to read !
Programming Matrix was a big work, so I am very happy to see that some users like it.

If you choose to spend a New Year programming Logelloop, I guess you’re a freak… LOL
Happy New Year!

haha, I took a short break to celebrate !
And now again at work…

Happy new Year !

Best,
Philippe

[Philippe]

Hi Paco,
Thank you so much for the perfect explanation.
Yes, you are right, there is a bug if you ask again the same group after it was manually changed.
This is fixed for the next release.
Thanks again.
Philippe

[Philippe]

hi Patrick,
I cannot confirm the first one.
Could you try again please?
Or maybe there is something missing in your steps to reproduce ?
For example this macro work perfectly here :

InsertSendMessage fx1 1 Group 2
InsertSendMessage fx2 1 Group 3

WaitUserAction

InsertSendMessage fx2 1 Group 2
InsertSendMessage fx1 1 Group 3

***

I confirm the ref field issue, and it is fixed for the next one.

Thank you for the report.
Best,
Philippe

[Philippe]

Hi Patrick,
Thank you so much for this great contribution !
While trying it, I see that the midi learn buttons aren’t well set, and it seems that removing the “WaitDuration” line after the “itemamount” fixe the issue.
I am not sure the that the WaitDuration is still needed in my templates either…
I will look at it.
Best !
Philippe

[Philippe]

I don’t know.
I think it’s because you have more buttons on the compact and it is cheaper.
The extender may be a good choice to.

Note that sending meters level and things like this to the Midi controller will not be on the top of our to do list… 😅

In reality, I don’t like Behringer for many reasons, the weight is one of them…
But I needed motorized fader.

Now with the new reachtoModify functionality in Logelloop, you can go without motors…

[Philippe]

Hi,
I had misread the paths which indicate that the project is not on the same volume as Logelloop.
And I had asked the wrong question, it can indeed be an internal SSD while being another volume! -)

So, I can reproduce the crash which happens if the project is not on the same Volume as Logelloop.
We’ll fix this soon and release a new version, but in the meantime, you can work with projects that are on the main volume.
Thanks for reporting the issue.
Philippe

[Philippe]

Hi,
I don’t want to say that the problem is in your macro, but I need to see how you connect things to make it work. And by giving me the whole macro from the beginning, you’re saving us time, because I don’t have to ask you a lot of questions… -)

In this case, I see that you’ve changed the name displayed in the dial or button, but you haven’t changed the name of the corresponding CaseBranch. This may not be clear in the provided templates, in which case I’ll have to add some documentation in them, but the method is that the button or dial transmits its name to the macro, which first looks if this name corresponds to a CaseBranch, and them the action of that CaseBranch is made.

Intuitively, you probably thought we’d base it on the number of the button or dial, but at some point it seemed better to me to base it on the name. That way, when you edit your macro, you easily know which UI the CaseBranch corresponds to. I think it makes sense.

I don’t think the errors displayed in the console are that serious.
I will have to check, and fix the issue if it is needed or hide the errors if they’re not necessary.

Below, the simplified macro with the corrections.
I hope I’ve answered correctly and I haven’t missed the issue you reported.
Philippe

Declare Local Once boolean $firstTime$ = true
Declare Local int $itemID$ = 1
Declare Local int $itemSize$ = 56
Declare Local int $verticalPosition$ = 1

If { $firstTime$ }
	$firstTime$ = false
	//SendData midiMapping clearAll
	SendData itemamount 32

	WaitDuration 300

	DoRepeat
		SendData itemtype $itemID$ dial
		SendData item dial $itemID$ name $itemID$
		$itemID$ = {$itemID$ + 1}
		WaitDuration 10
	While {$itemID$ < 9}

	SendData mainWindow setsize 463 {30 + ($itemSize$ * 4)}

	SendData item button 0 fontface regular
	//SendData button 0 fontsize 40
	SendData item button 0 bgcolor 0. 0. 0. 1.;
	SendData item button 0 bgoncolor 0.773 0.145 0.196 1.;
	SendData item button 0 bordercolor 0.2 0.2 0.2 1.;
	SendData item button 0 borderoncolor 0.2 0.2 0.2 1.;
	SendData item button 0 textcolor 0.827 0.827 0.824 1.
	SendData item button 0 textoncolor 0.827 0.827 0.824 1.;

	//Labels, for some reason they don't work
	SendData item 1 name "Vol 1"
	SendData item 2 name "Vol 2"

	SendData item 30 name "Button 30"
	SendData item 31 name "Button 31"
	SendData item 32 name "Button 32"

	SendData item dial defaultSettings
	SendData basicdisposition
	SendData MacroInitialized
	MacroStop
EndIf

// Which Case is it ?
Message { "Button or Dial number " + currentCaseValueString() + " : " + currentCaseOptionValueFloat(0)}

CaseBranch "Vol 1"
	MessageMain { "Dial " + (currentCaseValueString()) + " value is : " + currentCaseOptionValueFloat(0)}
	TrackVolume trk1 = {scale(currentCaseOptionValueFloat(0), 0, 127, -76, 0)}
	BreakCaseBranch

CaseBranch "Vol 2"
	MessageMain { "Dial " + (currentCaseValueString()) + " value is : " + currentCaseOptionValueFloat(0)}
	TrackVolume trk2 = {scale(currentCaseOptionValueFloat(0), 0, 127, -76, 0)}

	BreakCaseBranch

CaseBranch 3
	MessageMain { "Dial " + (currentCaseValueString()) + " value is : " + currentCaseOptionValueFloat(0)}
	TrackVolume trk3 = {scale(currentCaseOptionValueFloat(0), 0, 127, -76, 0)}
	BreakCaseBranch

CaseBranch "Button 30"
	// Your code here
	MessageMain "The button number 30 was pushed"
	BreakCaseBranch

CaseBranch "Button 31"
	// Your code here
	MessageMain "The button number 31 was pushed"
	BreakCaseBranch

CaseBranch "Button 32"
	// Your code here
	MessageMain "The button number 32 was pushed"
	BreakCaseBranch
EndCaseBranches

[Philippe]

Can you please send me your whole macro code ?

[Philippe]

Hello,
Please be more clear when reporting a problem or asking a question.

I’ve noticed in the current version that plug-ins’s settings are stored correctly, but that when the plug-in is loaded via a Logelloop preset, the settings are not applied – a second preset must be loaded for the settings to be applied. This probably happens because the plug-in hasn’t finished loading when the settings are applied. Is that the issue you experiment ?

I’ll find out where the problem lies and fix it as soon as possible.

As for the display of the plug-in’s own presets in its window, I don’t bother with them and I don’t try to memorize them.
What I do memorize are the plug-in settings, whenever possible, which is not the case for Native Instruments plug-ins and perhaps some others.

I don’t know where I can find Portal or Density.

[Philippe]

Hi,
There is a ratio between being more in realtime and having better performances.
When I use Logelloop for precise Live Looping and when it needs to be very realtime, I set :

I/O vector size to 256 or less.
Internal precessing to “Very fast” or “Very very fast”

And I don’t use the CPU-hungry modules.

But when I use Logelloop in a more sound design way (Granulars, Granulaterre, many Looper in Time Stretch or ETS, pitches). I set it for performances :

I/O vectore size to 512 or more (depending on my sound card).
Internal precessing to “Fast” or “Economy”

Also, it is very important to set the modules to Off when you don’t use them.

Does this change something in your situation ?

Also, remember that your computer and your processor need to be fast if you want to make many sound design at the same time.
Philippe

[Author]

Posts