Friends of Overtone, what are your personal top three things you'd like to see "fixed" in Overtone. Answer in the thread. Think about it first, so you don't get influenced by the previous answers. 🧵👇
What's wrong with at? "local SC server" do you mean the internal or external server?
internal
The plan is to remove the internal one so that should maybe resolve itself
okay, curious what the tradeoffs are in doing that
other things to fix
• config validation or matching conflict casing with SuperCollider. I’ve set some config params and can’t be confident that they actually did anything because of lacking validation and custom spelling. Overall preference would be simple pass through casing matching SC. E.g. s.options.numOutputBusChannels = 8; in sc becomes (config-set! :numOutputBusChannels 2) rather than (config-set! :max-output-bus 2) as it is currently. Also, since config is now persisted, is there a way to reset it?
• fixing at when running the local SC server
• better docs/wiki on the existing synth functions and proxies
I wrote up my thoughts about removing the internal supercollider https://groups.google.com/g/overtone/c/qndjDV5FS9Y
Spend a morning getting MiniBeast running again https://github.com/overtone/mini-beast/pull/42
To try it out
clojure -Sdeps '{:deps {overtone/mini-beast {:git/url "" :git/sha "b315addc1fc1b3125fce778a953500089c908781"}}}' -M -m minibeast.core That version still has some issues, this one should be better
clojure -Sdeps '{:deps {overtone/mini-beast {:git/url "" :git/sha "ea5894e074eb1f42dc1fa9cbb2b31fcc3783f909"}}}' -M -m minibeast.core And now there's also a jar people can run.
nice work!