[Pacocreative]

Thanks for looking into it.
Yes, it’s internal SSD, different volume.
Take your time.
My life does not depend on it.
yet.

[Pacocreative]

Great hints. Still considering this vs Novation Launch Control x2 + Novation LaunchPad.

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

[Pacocreative]

Sure. I don’t think it’s a problem of my specific macros.
Here’s a template where I only added labels.
They show up, but the code breaks – i.e. when button is pressed or dial moved, the action stops working.
If labels are removed, they work fine (see dial 1&2 vs 3)

The code is one of your templates:

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 1
	MessageMain { "Dial " + (currentCaseValueString()) + " value is : " + currentCaseOptionValueFloat(0)}
	TrackVolume trk1 = {scale(currentCaseOptionValueFloat(0), 0, 127, -76, 0)}
	BreakCaseBranch

CaseBranch 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 4
	MessageMain { "Dial " + (currentCaseValueString()) + " value is : " + currentCaseOptionValueFloat(0)}
	BreakCaseBranch

CaseBranch 9_toggleOn
	// Your code here
	MessageMain { "Dial " + (currentCaseValueString()) + " value is : " + currentCaseOptionValueFloat(0)}
	Message "The button number 9 is On"
	BreakCaseBranch

CaseBranch 9_toggleOff
	// Your code here
	Message "The button number " + (currentCaseValueString()) + " is Off"
	BreakCaseBranch

CaseBranch 10_toggleOn
	// Your code here
	Message "The button number " + (currentCaseValueString()) + " is On"
	BreakCaseBranch

CaseBranch 10_toggleOff
	// Your code here
	Message "The button number " + (currentCaseValueString()) + " is Off"
	BreakCaseBranch

CaseBranch 11_toggleOn
	// Your code here
	Message "The button number " + (currentCaseValueString()) + " is On"
	BreakCaseBranch

CaseBranch 11_toggleOff
	// Your code here
	Message "The button number " + (currentCaseValueString()) + " is Off"
	BreakCaseBranch

CaseBranch 9
	// Your code here
	Message "The button number 9 was pushed"
	BreakCaseBranch

CaseBranch 9_up
	// Your code here
	Message "The button number 9 was released"
	BreakCaseBranch

CaseBranch 10
	// Your code here
	Message "The button number 10 was pushed"
	BreakCaseBranch

CaseBranch 11
	// Your code here
	Message "The button number 11 was pushed"
	BreakCaseBranch

CaseBranch 12
	// Your code here
	Message "The button number 12 was pushed"
	BreakCaseBranch

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

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

CaseBranch 32
	// Your code here
	Message "The button number 32 was pushed"
	BreakCaseBranch

EndCaseBranches
// Put here some code that will be interpreted after each CaseBranch

[Pacocreative]

Since we’re in LL6.1 now and I’m exploring the same subject…
What conditions need to happen so that VST plugin presets were displayed in LL preset window (and thus saved with LL preset)?

I checked a bunch of plugins, some VSY, some VST, and most of them did not show presets in LL plugin window (like Portal, Density), some others like Effectrix did.

[Pacocreative]

Any ideas on why the text labels fail for me?

[Pacocreative]

Thanks Philippe,

It seems that 128/Very fast works quite fine.
Upon further testing, I’m seeing that using LL with Loopback 2 generally makes LL choke, even not in priority mode, so I’ll avoid that.

[Pacocreative]

Write rights for the entire folder and all subfolders with projects are RW for admin and RW for users (“staff”)
LL does not have issues writing, as it successfully create project structure and own files.

“CopyToFile” works fine in the main looper, as I reported.
“Write Audio File” under yellow arrow is exactly the one crashing for me. Every time.

[Pacocreative]

I arrived at really lots of clicking and dropoffs in audio performance, which was generally making it unusable for performance.
So I started a thorough investigation, and here are my findings.
TLDR – not your fault. It’s a particular configuration that made it misbehave.

The symptoms:
– CPU load is NOT exceeding 25-30% (or 20% in LL)
– Noticeably laggy UI
– severe amount of clicking heard in audio outputs
– clicking on speed change in loopers
– clicking while scrubbing through the loopers in freeze mode
– clicking while manipulating MIDI-mapped parameters, which were not even supposed to affect the sound

For example:
– the audio source is a modular looper
– I’m using external controller to manipulate aux sends on other channels
– while I move my knob, the audio degrades

I tested:
– Acousmonium vs stereo
– Various I/O configs
– Using the same interface for In and Out
– Using different interfaces for In and Out
– Using and not using Software Routing (Rogue Amoeba Loopback 2)
– High-priority mode for LL

My go-to configuration was:
LL in high-priority mode ⇀ Loopback 2 ⇀ Main output + monitoring output on two different devices

Apparently, the only configuration producing heavy issues is:
LL in high-priority mode + Loopback as output for software routing

What seems safe is:
LL (no priority) ⇀ Loopback
LL (priority) ⇀ various hardware outputs

Hope this is helpful to anybody falling into the same issues.

Still interested in Phillipe’s / Chris’ recommendations on how to prevent dropoffs in general and assure stage-performance reliability.
I’m still hearing occasional clicks.

[Pacocreative]

From the crash reporter, I’m getting the following.
Copied only the beginning, full file here:
https://www.dropbox.com/scl/fi/d6dvbpupxa2p103g50d6s/Crash.txt?rlkey=o7gqn1k0max9kbv17liqzs9l9&dl=0

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Logelloop 6 [70867]
Path:                  /Applications/Audio/*/Logelloop 6.app/Contents/MacOS/Logelloop 6
Identifier:            com.logelloop.logelloop6
Version:               6.1.21 (6.1.21.2526065)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2024-12-26 11:35:08.8219 +0100
OS Version:            macOS 13.6.4 (22G513)
Report Version:        12
Anonymous UUID:        852B539F-953F-9928-5AF4-2B1A87406498

Sleep/Wake UUID:       A1ECC548-ADF6-49C0-BC04-8138D18D5A93

Time Awake Since Boot: 770000 seconds
Time Since Wake:       1550 seconds

System Integrity Protection: enabled

Crashed Thread:        58  Java: Simple Buffer disk writter consumer

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   Logelloop 6 [70867]

VM Region Info: 0 is not in any region.  Bytes before following region: 4379467776
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      105096000-107b1a000    [ 42.5M] r-x/r-x SM=COW  ...S/Logelloop 6

Application Specific Information:
abort() called

[Pacocreative]

Thanks,

For swing and microtime, I imagine that it may be difficult to introduce early time, but delayed by x ticks or swing as percentage should be fine.
For the grid randomization, let’s see how far I can go by macros, especially that I plan on adding Euclidean Rhythms fill. If macros prove to be a bottleneck to do so, perhaps I’ll leave this idea to you.

[Pacocreative]

1/ I have no crash report. Any suggestions on how to create it?
2/ The same happens with previous LL – v6.0
3/ I initially tested with 4 loopers.
4/ I started a new project, one looper on insert, crashes right away.
5/ It’s an internal SSD.
6/ Paths:

$current_project$		                string	RecTest
$current_project_impulses_path$		        string	/Volumes/Data/Music/LL Projects/RecTest/Impulses/
$current_project_medias_path$		        string	/Volumes/Data/Music/LL Projects/RecTest/Medias/
$current_project_output_recorder_path$		string	/Volumes/Data/Music/LL Projects/RecTest/Output Recordings/
$current_project_path$		                string	/Volumes/Data/Music/LL Projects/RecTest/
$current_project_saved_loops_path$		string	/Volumes/Data/Music/LL Projects/RecTest/Saved Loops/

Btw, I have no problems writing using “copy to files” from an old track looper.

[Pacocreative]

That’s very helpful. Thank you, Chris.
I guess there are no methods for things like array.push() array.sort() etc…?
Is there a way to define functions in macros?

[Pacocreative]

Super helpful, that worked. Many thanks!

[Pacocreative]

You’re a legend.

[Pacocreative]

Re #4 – Saving learned midi mappings in Matrix, I found in one of examples:

	It is possible to set the midi mappings by list
	arguments are itemID midiInputType midiNote midiChannel
	SendData midiMappingByList 3 cc 16 11 6 cc 2 11 8 cc 3 11
	SendData midiMappingByList 11 cc 16 11 12 cc 2 11 13 cc 3 11

So I’m set.

[Author]

Posts