Understanding the structure

Before you jump into creating content, it's also a good idea to get a clearer idea about the terms we'll be using in the software, and what they are about. We have tried to give a succint explanation here.

Swar Performer Objects

Swar Performer implements several types of objects. Understanding how these objects work and interact with each other is important for using the software effectively.

Tracks

Tracks are available in three different types:

MIDI / Instrument — The main track type, used to load virtual instruments such as SwarPlug and play them through MIDI events.
Audio — An audio track allows you to handle live audio input from microphones or other audio sources.
Aux — An aux track can be used to create redirections in the audio signal flow.

Swar Performer allows you to create and configure all three track types, including settings such as gain, panning, and audio effects.

Devices

Devices are responsible for producing the MIDI events that are sent to tracks.

Swar Performer allows you to create one or more devices. These devices are virtual by default, but they can also be connected to your physical MIDI hardware so you can play directly from your own keyboard or controller.

Mappings

Mappings define how specific key ranges on devices are linked to tracks.

The mapping system is highly flexible. For example:

Different key ranges on a single device can target different tracks
Multiple devices can target the same track

This makes it possible to create advanced performance setups adapted to your workflow.

Scenes

Mappings are specific to scenes. Changing scenes therefore changes the way your keyboard(s) interact with tracks.

Scenes can be changed:

By clicking on a scene directly
By assigning and triggering a specific key or button from your keyboard

This provides full flexibility to switch instruments and performance configurations dynamically while performing.

Sessions

Sessions are the documents that are created, loaded, and saved in Swar Performer.

A session contains the complete configuration of all objects described above, including tracks, devices, mappings, and scenes.

In practice, different sessions can be used for different performances or setups when larger configuration changes are required beyond what scenes alone can provide.

Welcome