Yes, I can share the .csd file used to make this piece, it is attached. Usually, even if I write a piece in another language, as I did with this piece, I try to get the piece to save a self-contained .csd file to archive and document the piece, that is what I have attached.
The actual piece is a Python program that uses the CsoundAC algorithmic composition library to generate the score. The piece includes a graphical user interface for fine-tuning the sounds and setting the right balance of levels and effects. The user interface is defined using Glade for Python Gtk. The piece was written, edited, and run from the SciTE text editor using customizations of the editor that I wrote. The way this system works is documented here: https://github.com/gogins/csound-extended/tree/develop/playpen.
The Csound orchestra is embedded in the Python code and uses my modular system of Csound patching, documented here: https://github.com/gogins/csound-extended/blob/develop/silencio/patches/modular_csound.pdf.
I have independent Csound include files for many instruments and effects like these, here: https://github.com/gogins/csound-extended/tree/develop/silencio/patches.
I make all the source code for all my compositions publicly available here: https://github.com/gogins/michael.gogins.studio.
The main Python file for this piece is here: https://github.com/gogins/michael.gogins.studio/blob/master/music/sounds_with_internals/Drone-3-1.py.
CsoundAC and the SciTE extensions are in my csound-extended repository, including the source code for the MVerb reverb opcode plugin used in this piece, here: https://github.com/gogins/csound-extended/tree/develop.
Thanks for your interest,
Drone-3.py.csd (40 KB)