Glicol (an acronym for “graph-oriented live coding language”) is a computer music language with both its language and audio engine written in Rust programming language, a modern alternative to C/C++. Given this low-level nature, Glicol can run on many different platforms such as browsers, VST plugins and Bela board. Glicol’s synth-like syntax and powerful audio engine also make it possible to combine high-level synth or sequencer control with low-level sample-accurate audio synthesis, all in real-time.
Get started
🚀 The Web App
The easiest way to try Glicol:
https://glicol.org
There you can find guides, demos, docs, and apps for collaboration.
Features
-
Near-native, garbage-collection-free and memory-safe real-time audio in web browsers
-
Quick reference in consoles with alt-d
-
The web app automatically loads samples; you can also drag and drop local samples in the browser editor
-
Robust error handling: error reported in console, but previous music will continue!
-
Mix JavaScript code to create visuals with Hydra synth made by @ojack
-
What you see is what you get, i.e. declarative programmering for both code writing and executing: no need to select anything, just change the code and update, Glicol engine will use LCS algorithm to handle adding, updating and removing
-
Decentralised collaboration using yjs and a unique be-ready mechanism
🎁 For Audio Dev
🍿 YouTube Channel
Find Glicol demo videos in this playlist.
Philosophy of Glicol
The motivation of Glicol is:
In NIME community, it is known as:
low entry fee and high ceilings
This is Glicol’s philosophy to approach these goals:
Reflected in the implementation:
Graph-oriented
The basic idea of Glicol is to connect different nodes like synth modules.
All you need to know is the audio input/output behaviour of each node.
Two ways for connecting: >> and ~reference:
// amplitude modulation and lazy evaluation example
// chain with ~ is a ref chain and will not be sent to the DAC
o: sin 440 >> mul ~amp
~amp: sin 1.0 >> mul 0.3 >> add 0.5
It also applies to sequencer and sampler:
// sequencer pattern
// first divide one bar with space
// then further divide each part based on midi number and rest(_)
o: speed 2.0 >> seq 60 _~a _ 48__67
>> sp \blip
// quantity alters probability
~a: choose 60 60 0 0 72 72
As mentioned above, you can try these examples on:
https://glicol.org
If you want, you can even hear how a seq node work:
o: speed 2.0 >> seq 60 _72 _ 48__67 >> mul 0.5
This is actually analogous to how hardware module pass signals.
It is very easy to remember and to get started.
When Glicol is used in education, we can let students see and hear each node, even including ‘envelope’.
Just leave the introduction of data types, Object or Function later when we mix JavaScript with Glicol.
Zero-installation
For the audio engine, instead of mapping it to existing audio lib like SuperCollider, I decide to do it the hard way:
-
write the parser in Rust
-
write the audio engine in Rust that works seamlessly with the AST processing
-
port it to browsers using WebAssembly, AudioWorklet and SharedArrayBuffer
The main reason is to explore performant audio in browsers for easy access and live coding collaboration.
The reward is that we now have an Rust audio lib called glicol_synth:
It can run on Web, Desktop, DAW, Bela board, etc.
And one more thing.
To write everything from low-level also opens the door for meta node.
Now I can explain to students, the hello world tone can also be written in this way:
o: meta `
output.pad(128, 0.0);
for i in 0..128 {
output[i] = sin(2*PI()*phase) ;
phase += 440.0 / sr;
};
while phase > 1.0 { phase -= 1.0 };
output
`
Roadmap
Note that Glicol is still highly experimental, so it can be risky for live performances.
The API may also change before version 1.0.0.
Please let me know in issues or discussions:
- your thoughts on the experience of glicol
- new feature suggestion
- bug report, especially the code that causes a
panic in browser console
- missing and confusion in guides and reference on the website
评论