edit 23rd December 2016 : λ is not yet available for download, and no date yet…(It is still in a development stage where I’d have to release new binaries every day in order to deliver bug fixes and I have no streamlined solution for doing that…)
Since early 2015 I’ve been working every now and then on an application, now named λ, that was originally intended to be a modular GUI front-end for the Composer’s Desktop Project (CDP) command line programs. During the past few months I’ve started developing it more actively and it is becoming something larger. In addition to running the CDP programs, it now also hosts VST2/VST3/AU plugins and has some built-in processings too, among them a multilane sound sequencer/mixer. (I don’t want to call it “multitrack” because I don’t want to get stuck with some traditional notions about a DAW application…)
It resembles a modular patching environment like Max/MSP in that it has processing “nodes” or “objects” that can be connected together into a “patch” or a “graph”. However what makes λ a bit different is that each node always has some defined duration of audio or other data available and the nodes downstream can always randomly access all that data. So things like reverse playback or granular processing that “scans” the source audio in any direction/speed are possible no matter what the upstream nodes are doing. (For example the output of a reverb plugin can be reversed and so on.)
Why the weird name that is just the Greek lower case letter λ? Well, why not? 😉 However, if people don’t want to type that character, I am willing to tolerate them using “Lambda” or “lambda” instead. And if the name really becomes some kind of a problem, I may reconsider changing it.
Here are some YouTube videos demonstrating a bit what it can do :
At the moment λ is heavily based on offline processing the nodes into files on disk. However more responsive pseudo realtime processing can be added to some of the node types in the future. It will still however be mostly geared towards composers/sound designers who don’t necessarily need full realtime response, MIDI inputs, audio recording with monitoring etc. λ is not going to become a traditional DAW or even a traditional modular patching environment. There are plenty of those around already, so I don’t need to make one that tries to replicate ProTools, Reaper, Cubase, Max/MSP, Bidule and so on.
And then the question…Is HourGlass dead? It is. 😦 But wait… Not really. It will live on inside λ as a processing node. Currently the HourGlass node is not as comprehensive as the old Qt based application, but it will (re)develop as time goes on.