Edit: with a bit pure data flavor mixed in... super nice!
That said, guessing a bunch of those are meant to be concise examples.
For what its worth my quick take on a lot of the text-based sound coding environments [1] is that they provide a relatively quick way to approach creating audio programmatically differently compared to a more traditional spatial / grid-based daw.
One nice thing about Cracked is that you can treat it as an audio input in Ableton, Logic, etc. and so you could use it to generate a sound to sample / process further in a daw arrangement. I had stumbled across it originally from the author's Wikipedia page which mentions that he uses it to create longer albums / pieces https://en.wikipedia.org/wiki/Bill_Orcutt
Interview with him about it https://www.thewire.co.uk/news/41540/bill-orcutt-releases-op...
[1] https://tidalcycles.org/ https://sonic-pi.net/ https://chuck.stanford.edu/ https://supercollider.github.io/
Desktop wrapper: https://github.com/billorcutt/Cracked
Cat examples: https://idroppedmyphonethescreencracked.tumblr.com/
I'm thinking of time stretch effects like mine https://github.com/bungee-audio-stretch/bungee
love the demo https://bungee.parabolaresearch.com/change-audio-speed-pitch
have you thought about wrapping it as an audio unit or vst via juce/clap/iplug so its usable in a daw?
https://juce.com/ https://cleveraudio.org/developers-getting-started/ https://github.com/iPlug2/iPlug2
it's ported from Rust
const whatever = ...
I would rather refer to them by these names than by strings. It's both faster and safer to do so.
