193
edits
Changes
Jump to navigation
Jump to search
mLine 28:
Line 28: + + + + + + + + + + +
Notes on Oram: some differences and new features (view source)
Revision as of 03:43, 24 April 2024
, 24 April→Chains
==The Zynthian UI Workflow==
==The Zynthian UI Workflow==
==Chains==
==Chains==
===An update on chains (and mixbus) for Oram===
A chain may have audio and/or MIDI input. It may have any quantity of MIDI processors, a synth / generator processor and any quantity of audio processors, in that order, e.g. MIDI Input → MIDI Chord processor → Pianoteq → Bollie Delay. (The processors may be in any mix of parallel and series and there is no forced limit to the quantity of processors in the chain except there can only be a maximum of one synth processor.)
If the end of this chain has an audio output, e.g. it is a synth or audio chain then it feeds into a mixer input. The mixer has a channel strip that implements the phase, mono, mute, solo, fader, M/S encoding, etc. The output of this channel strip is by default routed internally (this is called normalisation) to the main mix bus. This is defined by the chain’s audio output configuration, i.e. if “Main Mixbus” is selected then this internal routing is enabled. (See below for an exception.)
Each channel strip has an (stereo) audio output which by default is not routed. This can be routed to other chains and direct physical audio outputs using the chain audio output menu. It is possible to add post-fader effects to a chain. This routes the chains direct output to the post fader effect which is then routed to the targets enabled in the chain’s audio outputs. By default this results in the channel strip’s output being routed to the post-fader effects and the output of those post fader effects being routed to the main mixbus input. The internal normalisation is then disabled.
The main mixbus can also have pre and post fader effects. If it has prefader effects then any chains routed to the main bus will use their direct outputs to feed the main mixbus pre fader effects.
It is a bit complex in implementation and can lead to some unexpected results but it is quite flexible whilst keeping the technical implementation as low-cost as we can. (Lower CPU usage.)
==Navigation==
==Navigation==