
GETTING STARTED:


01
Congratulations!
Thank you for your interest in the DC-500 product range. We've written this short setup guide to help you get your module working exactly the way you want it. Read on for a quick overview of how to set up the world's first fully reprogrammable 500-Series module!
02
Meet Daisy & DIYRE:
The DC-500 is a novel implementation of Electrosmith's Daisy Seed chipset. Head to daisy.audio to learn all about the Seed & its accepted programming languages.
DC-500 variants including and upwards of the Mk4.0 feature DIYRE-compatible colour module support. Head to DIYRE to learn more, and to (optionally) choose some analogue plugins for your DC-500 output!

Credit: Electrosmith & DIYRE.

03
Test your DC:
Each DC-500 is shipped pre-loaded with an Electrosmith Seed3 DSP host, and pre-programmed with Daisy Bootloader to allow for easy DSP flashes to the module. For users to experience DC-500 sound right out the box, every module is shipped with a sample gain stage patch that uses both knobs as simple volume controls. Rack up your module & give the knobs a spin!
Don't hear anything? If running DC without Colour modules installed, make sure your DC-500 is in clean mode by checking the switch located in the middle of the module's side cutout window is set to 'bypass'.
04
The fun part:
Ready to flash your own custom DSP? To do this, we need to put your Seed3 into bootloader mode -- this puts Daisy into a state ready to receive new DSP code.
With the DC-500 module unpowered, connect to the Seed3 via any USB-C data cable & hit the Seed's 'BOOT' button within 2 seconds of plugging-in (that's the leftmost button when viewing the device from its 500-Series edge connectors at the back). Didn't hit the button in time? While holding 'RESET', hit 'BOOT' again, immediately releasing both buttons afterwards.
Never connect USB to Daisy while the module is powered. Any trouble? Head to flash.daisy.audio for more bootloader support, or to update/re-install.
Once you've got your Seed3 in bootloader mode, flash DSP of your choice in a suitable language (we strongly recommend Plug Data), or visit the Cult Sound library of Plug Data patches for inspiration.
To write code for your Daisy, you'll need a way to tell the chip which variables in your DSP are connected to the DC-500's external control knobs. Be advised these controls are connected to Daisy's ADC5 & ADC6 pins by default, but can be changed via the screw terminals on the DC-500 circuit board. To tell Daisy how to map your code to the external knobs, you'll need a .json config file -- an 'instruction manual' for how Daisy maps your code to its knobs. Read more, and watch the Plug Data patching tutorial below!




Use this .json file for mapping your DC-500 knobs to DSP parameters of your choosing, or find custom .json file guidance here. For beginners, we recommend using Plug Data for coding. Use the Heavy Compiler to flash patches by setting Plug Data to 'compiled mode', & follow the compile dialogue from there. For more a comprehensive guide, head here. When watching the guide, be aware your DC's Daisy already has the bootloader (discussed at 04:30) installed. Unplug USB-C when you're done, rack-up, and enjoy!
If using Plug Data with the Heavy Compiler, we recommend starting flash settings at 96kHz, with a block size of 96, & patch size set to 'big'. Adjust these variables as needed for your specific needs.

Controls:

Be advised that the control knobs on the DC-500 are linear. This means that by default, your DSP will read them as scaling directly between 0 & 1 as the knob is turned up.
If your control knobs don't seem to be working properly, please test them using the sample gain stage patch in the Cult Sound library. If your module runs this patch successfully, your control issue is likely down to software/coding-based user error. If the control issue persists, please inspect the screw terminals connecting your DC-500 control knobs wires to the PCB. These wires can come loose after modification, so be sure to give them a proper tighten if customising your device!
We strongly recommend audio-rate signal smoothing implementations in your DSP for parameter control signals. Visit the Cult Sound library for inspiration.


USAGE NOTES :


01
Signal Metering:
Some DC models (like the Mk4.0) use passive signal meters. In these cases, the stereo signal LEDs behave more like 'sweet-spot' indicators, showing you that you're making the most of your DC-500's substantial unity gain headroom. In response to customer feedback, newer models' signal meters (like the Mk4.1 and up) are more responsive to signals at lower levels.
02
Gain Staging Colour Modules:
All currently-available DC modules (Mk4.0 and up) feature switchable Colour Module support at their stereo outputs. This stage's placement varies a little between DC models, but is always post-Daisy, and always has a maximum internal headroom of approximately +17dBu.
This means users are able to drive any inserted Colour Modules appropriately hard if needed, but more often -- especially when used on stems & full mixes -- means the sweet spot for DC-500 input level (when in Colour mode) is closer to the range of +8dBu to +16dBu.
This typically results in more subtle 'mastering-style' colouration from DIYRE-compatible modules, and allows for substantial signal crest factor headroom while still ensuring appropriate signal-to-noise ratios for DC's onboard Daisy AD/DA converters.
To get the very best from the DC-500 as a hardware insert, we recommend a setup using converters calibrating 0dBFS at +24dBu.



03
Latency:
Depending on the DSP users run inside their DC-500s, their modules will carry a variable amount of roundtrip latency. While this can be corrected for in most modern DAWs when using DC as a hardware insert, users ought to be advised that altering their block size & sampling rates can also dramatically affect latency. We found DC's latency can usually be minimised to undetectable levels for many patches with lower-to-medium CPU demands, and tops-out around 300ms in the most extremely demanding patches.

Mk4.0 FIGURES:

01
Frequency-Response, & Distortion:
A great deal of care has been put into ensuring users get true audio transparency when using their DC-500s. This means that your DC will only affect your audio in exactly the way you tell it to, only when you want it to. When running a clean passthrough feeding Daisy's input directly to its output, users will hear virtually no audible imprint from the DC hardware itself.
997Hz, 20-20,000Hz
Daisy at 96kHz, 96 block
At +12dBu:
THD: 0.0005%
THD + N: 0.0034%
At +4dBu:
THD: 0.0012%
THD + N: 0.0083%
THD% / INPUT LEVEL:

FREQUENCY RESPONSE AT +24dBu:


02
Noise Floor(s):
To understand the DC-500's noise floor, we need to talk about Daisy's 'callback noise'. Unfortunately, isolated Daisy Seeds frequently introduce audible artefacts into their signal path. This 'callback noise' is a function of Daisy's internal sample rate / internal block size. Think of block size as the number of 'chunks' Daisy's onboard CPU processes audio in. Larger block sizes mean Daisy has more time to work through complex DSP, and smaller block sizes mean Daisy must process audio with more agility.
Because Daisy's callback noise fundamental frequency occurs at the chip's sample rate / block size, a Seed running at 96kHz & a block size of 96 will often produce a 1kHz harmonic in the audio path, with 2nd 3rd, 4th, etc.. harmonics stretching up the audible frequency band.
Until now, the best way to tackle this has been to reduce Daisy's block size, thereby moving the callback frequency higher up the audible spectrum (a block size of 4 puts the callback fundamental out of the audible range at 24kHz when running Daisy at 96kHz). Unfortunately, lower block sizes mean Daisy's CPU must work significantly harder all the time, making the chip a less powerful option for heavy DSP & demanding sonic processing.
A substantial amount of the DC-500's circuitry goes toward filtering out this noise. As of the Mk4.0, Cult Sound is proud to announce that the module's aggressive attenuation of unwanted artefacts places Daisy's callback noise & harmonics below the noise floor.
While users may very occasionally hear Daisy 'waking up' after sitting idle for a long time, or hear other digital noise if Daisy's CPU is overworked & begins to under-run calculations (this means your patch needs optimisation!), users can be fully confident that any callback noise in their module only moves the noise floor by ±0.3dB, making it effectively inaudible in all use cases. Review the graphs below for more detail.
NOISE FLOOR AT 96kHz, 96 BLOCK SIZE:
.png)
Note the DC-500's -80.7dBu A-weighted noise floor, and how the Daisy's 1kHz callback tone (and harmonics) sit below -105dBu.
NOISE FLOOR AT 96kHz, 256 BLOCK SIZE:
.png)
Note the how the Daisy's 375Hz callback fundament here is attenuated, and how the resultant higher-order callback harmonics sit below -105dBu. Also note -- as above -- the DC-500's -80.7dBu A-weighted noise floor.
NOISE FLOOR AT 96kHz, 2 BLOCK SIZE:
.png)
Note the how the Daisy's callback fundament is absent at low block sizes, sitting out of the audible frequency range. Also note how the absence of audible callback in the DC-500's A-weighted noise floor only lowers it by 0.2dBu. This means users can confidently run high-block-size, DSP-heavy processing inside their modules with only a 0.2dB reduction in usable dynamic range, leaving well over 100dB of dynamics.

CONTEXT:
All measurements are averages, taken from at least 16 readings per variable.
Multiple DC-500 Mk4.0 modules tested to produce the above figures.
All dBu figures carry variation of ±0.5. All figures produced in DC-500 Mk 4.0's with Colour Modules bypassed.
All figures produced using clean passthrough patches in Seed3 chips running at 24-bit 96kHz sample rate conversion.
All distortion, noise, & frequency figures are corrected for, and/or eclipse interface & converter interference.
500-Series rack & PSU noise may result in distorted figures. As such it is well possible the DC-500 Mk4.0's figures may be better than measured here. Conversely, DC modules may measure worse in differing user contexts.
Power consumption varies dramatically depending on Daisy host material & Colour Module usage. As such we cannot provide current draw specs for the module, but advise using a 500-Series rack capable of supplying 200mA per slot.
CONTACT SUPPORT :
Please don't hesitate to fill out the form below for any questions or concerns relating to our Cult Sound hardware products. Someone will be in touch with you shortly to discuss your enquiry. If you are worried your Cult Sound product is damaged or may become damaged, we strongly advise you avoid dismantling or modifying your device until you have either received a response from our technician, or consulted a practicing audio hardware professional.
