Macros & Beyond

[Pacocreative]

I’d like to get some more info on scripting and macros in LL.
So here’s a bunch of questions off top of my head.
I think I’ve got through the docu sufficiently, but if something is in the manual, I apologize.

1. Code blocks / functions
I ended up using several Matrix plugins that correspond to physical midi controllers, and have most of my workflow in here.
Some functionalities are doubled between instances of Matrix, and to avoid maintenance issues and confusion, I’m thinking about the following:
* have one “Master” matrix hosting most of the features
* be able to call code blocks or functions from another Matrix
* be able to execute blocks of code in a Matrix Macro from another part of that macro.
The code is currently logically broken into CaseBranches, so I’m thinking about triggering CaseBranch “A” from Case Branch “B” if needed?

Essentially I’m thinking in terms of defining ‘functions’ or ‘classes’ in one place and calling them from another place.
What tools do we have at our disposal?

2. Cross-calling macros
What are ways to somehow call macros between each other?

3. Macro language
I’ve gone through the documentation for programming macros, but wonder if there are other things that are perhaps undocumented?
And if so, what language is this based on? Or is it a 100% custom macro language that you developed for LL?

4. Using other coding options
Since I’m kinda starting to see limits on what’s feasible with macros, what other options of more advanced coding do I have for LL?
I slowly start exploring M4L Devices, where I do have all of Max’ arsenal, plus JS,Java or C if needed, but I’m not sure what bottlenecks I’ll hit that are related from predefined LL <-> Max I/O. It seems the SDK is 2021-ish, so probably a lot of newer 6.0 stuff may not be covered?

5. In some other places I asked about general architecture of LL and how it’s related to MAX. Would love to get a top-level understanding.

Thanks!

[Author]

Posts