Loomer Architect: A modular MIDI toolkit

[colin@loomer]

what is the total number of patches that will be included in the next release

In terms of patches, I'm aiming for around a hundred, giving a good mix of generative and processing functionality. It's an ongoing process, so hard to say which are "finished" as I'm forever tweaking them, but around 80 - 90% of the way on that front, I'd guess. There are also about 200(ish) macros, again covering generative, processing, and utility functions, and a handful of new "low-level" modules, mainly some UI components and a few utility modules that fill in some gaps/fix some issues with the previous event model. Generally, I'm avoiding adding new monolithic modules if at all possible, prefering customisable macros where I can. All the new modulation stuff - being able to right-click any object and choose "Add LFO", or "Add Envelope" for example - is all macro-based, and as such can be opened and edited.

(But I'd also say that creating macros and the like is generally quick and easy for me: it's the internal code changes to support the library that have taken so long, adding things like multi-threaded graph support, the ability to have more than one graph, to intersperse third-party plug-ins between graphs so you can process the output of other MIDI plug-ins, adding proper style support for UI components. All these little details that seem short work on paper often end being anything but!)

---

Will there be a VST 3 version? TouchDesigner has recently introduced support for VSTs, but only VST 3... Architect inside of TouchDesigner would be an absolute dream.

EDIT: It loads up fine in TouchDesigner from inside of VST 3 plugins that can host other plugins, like DDMF Metaplugin, KushView Element, NI Komplete Kontrol, etc... will need to do more testing to see how it behaves but it looks promising!

There is only one reason I didn't ship VST3 day 1, and that is because I was unsure the future of VST3 MIDI. I didn't want to back myself into a corner, adding some functionality that I'd struggle to keep supporting if VST3 every got "proper" MIDI support. Well, I think the landscape will not be changing any time soon, so I will add the VST3 to the next release, with the caveats thats you're not going to get much in the way of MIDI out from it.

Out of interest, I see that you got it working with a wrapper: could I ask which operating system you're using? Thanks!

[gentleclockdivider]

Still waiting for beta invitations

[colin@loomer]

Still waiting for beta invitations

Don't worry, I've not forgotten, and you'll be amongst the first when it's good to go.

[disc0head]

I will add the VST3 to the next release, with the caveats thats you're not going to get much in the way of MIDI out from it.

Out of interest, I see that you got it working with a wrapper: could I ask which operating system you're using? Thanks!

That's great news! I tested it on a 2018 Mac Mini (Intel) running macOS Big Sur 11.6.5.

[mcbpete]

Could you show us a screenshor of how it can also behave like a tracker please ?

I'm afraid the text-based sequencing support had to be bumped for now: it had some conceptual problems that I just wasn't happy with, and I'd rather have it done right than have it just done to list a feature. I know that's likely disappointing for you as you did specifically ask for this, but how about this as a compromise: I'll extend the early-bird discount available to you until the tracker stuff is back in properly, which'll likely be v1.1 or v1.2.

Are you any closer into getting a 'tracker' like module into Loomer Architect ? Probably would end up being my most used module if available.

[colin@loomer]

Yes: I've had numerous requests for that to be put in, and there are, as far as I know, zero technical hiccups to overcome to get it finished. Like always, it's just a case of time and priorities, but some very nice people have asked for it, and you know: that goes a long way to helping me prioritise these things!

[mcbpete]

That's great news - Previously have used reVisiT for 'midi tracking' but it now seems abandoned and is kinda clunky in it's workflow to route to a midi devices. This definitely seems like it'd be my midi-tracker of choice if implemented

[wvshpr]

Is there a way to do paramter morphing of VSTs in LA?

[colin@loomer]

You have write access to the parameters of hosted VSTs, but (currently) not read access. I assume morphing would require you to be able to read parameters too? If so, I don't think that a big deal to add, to be honest, so I'd be happy to put it in.

[drohnee]

You have write access to the parameters of hosted VSTs, but (currently) not read access. I assume morphing would require you to be able to read parameters too? If so, I don't think that a big deal to add, to be honest, so I'd be happy to put it in.

It would be great to have read access to plugin parameters, Colin. Thanks for including this!

[wvshpr]

You have write access to the parameters of hosted VSTs, but (currently) not read access. I assume morphing would require you to be able to read parameters too? If so, I don't think that a big deal to add, to be honest, so I'd be happy to put it in.

Like many former Kore users I lament its discontinuation. I'm looking for replacement that can do snapshots and morphing, ideally to control VSTs in Bitwig or external hardware. Architect seems powerful, but honestly just starting to wrap my head around it.

[Sevantos]

You have write access to the parameters of hosted VSTs, but (currently) not read access. I assume morphing would require you to be able to read parameters too? If so, I don't think that a big deal to add, to be honest, so I'd be happy to put it in.

Like many former Kore users I lament its discontinuation. I'm looking for replacement that can do snapshots and morphing, ideally to control VSTs in Bitwig or external hardware. Architect seems powerful, but honestly just starting to wrap my head around it.

Echoing and also AZZIN already did nice A-chaos patch that would have more use for modulation, than just midi per se.
Similarly ThomasHelzle is working on modulation of parameters from Architect to DAW.
This should be possible since Leapmotion Geco is doing that thru LoopBe1 (one of few soft of this kind that also works in Bitwig).

My point is: Arp that has no sync modulation with midi note on/off messages has very little use for music, that Bitwigers are mostly looking for, and will serve well only those using samplers or using other DAWs (tough ableton with M4l not has to be the case).

Also while I love probability stuff, literally all Architect devices are about probability, which one can do in Bitwig fairly well too, but there is no device that would make some order in first place, that can be than randomize.
Just device that would make sure elementary progression rule:
that chords do not leading into P5 and P8 interval (Parallel fifth/ Covered Octaves)
- specially when both goes in skip or one in wholestep and other in skip or both go in step up
- no worries for leading into P8 when one part goes in skip and other in a half-step (can be chromatic)
- when it is between outer and inner voices

Not to mention that there is no bass figuring in a first place...
Just this would help to do 5 part writing which I guess only few electronic music producers can handle....(I am not one of them)).

[Kalamata Kid]

Hello Colin,

I have 54 VST’s in the Blocklist. There is not enough room to read the complete file location. Would be great if there was an “Open File Location”. I wonder why so many VST’s in the Blocklist.

[Kalamata Kid]

I am on my second attempt to learn to use Architect.

I was hoping the Built-in modules and the VSTi’s and the VSTfx modules would be in the same Graph. Then to record there would be audio and midi tracks, each track with an input node. So you can then connect any audio module (VSTi or VSTfx) that has an audio out node to the input node of an audio track. The same with midi, you can connect any module that has a midi out node with the midi in node of a midi track.

So there would be a module that is composed of audio and midi tracks and later add automation etc.
Each track would have an input node.

True I may be overlooking some issues. The less desired alternative would be to treat Architect as a midifx/VSTi in Bidule or Mux or Bespoke etc.

[colin@loomer]

The next version allow multiple graphs, and these graphs can be ran alongside and inbetween other VST, AU, etc plug-ins. So it is definitely heading in the direction that will do what you need (and being able to separated things into individual graphs makes organisation much simpler, overall.)