Overview

The bus modules allows us to send signals from one BUS module to another BUS module somewhere else in the patch. there are 16 buses, each of which can contain 8 signals.

Documentation

• Wiki - https://github.com/TheTechnobear/SSP/wiki/BUS
• Forum - https://forum.percussa.com/t/bus-module

Parameters

Name	Desc
Dest	DestinationBus (1-16) for the inputs
Src	Source Bus (1-16) for the outputs

Inputs

Name	Desc
In1-8	Input to bus

Outputs

Name	Desc
1-8	Output to bus

Usage

there are 4 (main?) use cases for using BUS

a) patch design #1 - bigger patches we can only patch between objects on the same network page, so we can us a BUS to send audio/cv from a module on page 1 to page 16

b) patch design #2 - organisation we might want to group the functionality of a patch 'logically’ e.g, put a number of modules together in a page (block of 8) ( e.g. page 1) for an oscillator voice. and then put our FX/ master output on page 15/16.

theres a few benefits to this, partly patch readability, but also allowing you too quick/easily rearrange things. (it’d be awesome if one day, we could copy pages within a patch, or between patches!)

c) patch design #3 - mixing so if we design using (b) , we might have a couple of different voices (say page #1 and page #2) which go to a common fx change (page #16) via a BUS (e.g. bus #1) , and they are mixing into the same bus #1

but we could now easily change this so that page 2 uses a different fx change. just create the new fx change on page #15, with a new bus, src’d from bus #2, and switch the voice on page #2 to use bus#2

d) overcome limitations for linking objects. a single module connected to two objects, will connect to same inputs on each. e.g. if you connect STE to two ENV (eg. G1/G2) , you cannot say which ENV you wish to connect to G1 to and with G2 too. (this one, you'll understand when you hit the issue ;) )

tips

TheTechnobear posted a detailed description of how and when to use BUS, you can find it here

more info on Using the BUS module