This page contains documentation on the functions included in the CiderFrontAPI.
Additional resources in the plugins such as images and other files can be accessed with methods like
./plugins/:packageName/:filethis resolves to
:packageNamerefers to the
nameproperty in package.json for the plugin.
Note: CiderAudio requires Advanced Audio Functionality to be enabled in the app settings.
Cider features a custom audio stack, available in the renderer.
CiderAudio.context- Primary AudioContext
CiderAudio.source- Audio Source
CiderAudio contains the following nodes:
CiderAudio.audioNodes.gainNode- Main gain node
CiderAudio.audioNodes.spatialNode- Used by audio spatialization
CiderAudio.audioNodes.audioBands- Used by EQ
CiderAudio.audioNodes.vibrantbassNode- Used to deliver vibrant bass functionality
CiderAudio.audioNodes.llpw- Used by Cider Adrenaline Processor (CAP)
CiderAudio.audioNodes.analogWarmth- Used by Analog Warmth
CiderAudio initializes with
CiderAudio.hierarchical_loading()Inside the loading process, all audioNodes are cleared and re-initialized and chained based on what the user has enabled. The designed hierarchy for loading audio functions is as follows:
h1 item- AudioBand (final output)
h2 item 1- AudioBands vibrantbass_h2_1() (vibrant bass node)
h2 item 2- llpw_h2_2() (CiderAudio.audioNodes.llpw)
h2 item 3- analogWarmth_h2_3() (CiderAudio.audioNodes.analogWarmth)
- Spatial Node is always the last node in the chain