Triggers

Triggers are a core feature of Devalang that let you load and execute sound samples with precision. They form the foundation for building reactive or rhythmic elements in your compositions.

You can trigger samples manually, link them to other events, or combine them in groups for more complex behaviors.

Types

Triggers can be categorized based on how they are activated:

• Manual triggers — explicitly called using their name in the script.
• Event triggers — react to time or custom events using on and emit.
• Dynamic triggers (coming soon) — based on external inputs (e.g., sensor data, MIDI).

Loading

To use a sample in Devalang, you first need to load it.

This is done using the @load directive, which imports the sample file and assigns it a name for later use.

This is typically done at the beginning of your script.

For the moment, only WAV files are supported, but support for other formats like MP3 and OGG is planned.

Duration

When you load a sample, Devalang automatically calculates its duration in milliseconds.

You can choose between using the sample full duration (auto), or specifying a custom duration in milliseconds.

You can also use beat units like 1/4, 1/8, etc., which will be converted to milliseconds based on the current tempo.

Bank Triggers

You can use the bank triggers by chaining bank and trigger keywords together.

This allows you to load and trigger samples from a specific bank (optionally aliased).

Effects

When triggering a sample, you can configure its behavior using a set of parameters:

Events

You can listen to time-based or custom events using on, and emit your own events with emit.

• Periodic events: on beat: ..., on bar: ...
• Custom events: on custom: ... with emit custom { key: value }

Examples

Here’s how to declare and trigger samples in Devalang: