Scott Cotton

is creating Golang Audio Support
Select a membership level
per month
GopherGain to amplify our productivity. 
per month
CleanSound tier get accounts associated with the projects for public debates (issue tracking, etc)
Limited (50 of 50 remaining)
per month
DizzyDsp contributors are doing some serious math.




per month

About Scott Cotton

I'm working, happily, day and night on releasing some pretty cool audio/music signal processing apps.  I've done a great deal of work making audio work well in the Go programming language.  Many people have expressed an interest in doing audio processing work in Go, and yet it seems most of them abandoned the idea after starting because of the poor level of audio support in Go.  Googlers and other gopher team members have written proposals related to audio, and there are a myriad of interesting one-off projects which serve as proof of concept but which aren't reliably maintained or reliable.

Go is an excellent general purpose programming language and has the potential to become a solid platform for software based audio processing.

As part of my commercial app development, I'm working on,  building a lively set of open source projects to best address infrastructure needs for audio processing with Go, (to be announced soon on github under  These projects will address the needs for 

- reliable audio i/o for mac, linux, and hopefully with some open source windows without external 3rd party C dependencies, except os-host supplied support (eg ALSA).  Low latency is an important goal, as is integration with OS needs like audio sessions, and looking a bit further down the road, mobile platforms.
- simple, reliable, and efficient audio processing utilities and interfaces.  Think Web Audio or Apple Audio Units "done right" -- less framework, more library, more composability and clarity.
- core spectral processing/filtering tools.

These projects are well underway, so check back soon.  They also address functionality particularly well suited to an open-source development model, with ample interest to fuel use-driven reliability and functionality, and positioned as most depended-upon components of higher level apps which might make more sense in a commercial or dual-licensed model.

Funds will go towards: code hosting, project management, and development time.  Open source contributers will be invited to collaboratively share the budget if they, like me now, need the funds to finance their work.    

$0 of $100 per month
Code hosting with a dedicated domain will be set up with roadmap and initial code.
1 of 3

Recent posts by Scott Cotton