Documentation » The Processing Cycle

Introduction

Thanks to Robin Gareus' advice and help, Zrythm uses a processing algorithm that depends on an acyclic graph of ports. This algorithm splits processing jobs into threads and processes each node until the terminal nodes are reached and there are no more "trigger nodes". The algorithm is explained in detail below.

The Graph

The Processing Graph is an acyclic graph of nodes, which are explained below. The graph is re-created every time there is a change in Port connections. When the graph gets (re)created, it goes through the project and finds all nodes that should be added to it and adds them, then creates NUM_CPU_CORES - 1 threads for processing trigger nodes.

Ports

Track's (Channel's) and Plugin's are made up of Port's. These ports can be connected with each other, as long as they are the same PortType ( with a few exceptions) and of opposite PortFlow.

When these ports are connected, during processing, the signals from the source port are summed into the destination port. What this means in practice depends on the PortType. For audio, the signal is simply added to the existing one. For event/MIDI ports, the MidiEvent's from the source port are appended to the events of the destination port.

Nodes

Trigger Nodes