nicross/syngen

A spatial sound and synthesis toolkit for game development.

Hi there 👋

I'm a web developer and accessibility advocate with a degree in computer music. I make games at the intersection of my passions. Primarily I leverage real-time synthesis and procedural generation to craft interactive audio experiences. To achieve this I created syngen, a spatial sound and synthesis toolkit.

syngen's Issues

Add utilities for loading audio files into buffers

I've typically used this library for synthesizing pure sounds, but it could be useful for folks to have utilities that simplify loading audio assets into AudioBuffers (which could then be leveraged by syngen.audio.synth.createBuffer). In the next minor release I'd like to add a syngen.audio.load method (or namespace of methods) that asynchronously loads assets. It might return a Promise that resolves with an AudioBuffer filled with data.

Considering HTTP/2, I'm not concerned with providing an audio sprite interface. A better workflow might be defining any sprites when loading an asset, which returns a hash of AudioBuffer instances that result from splitting its data at certain points.

Let me know if you have any thoughts.

Finalize v2.0.0 release

There is a v2.0.0 branch currently in alpha. It has a simplified API and contains quite a few new useful utilities. Examples include:

• syngen.sound replaces syngen.prop and syngen.props with a simpler interface
• syngen.ephemera helps manage memory of objects like noise generators
• Several namespace changes, like syngen.utility becoming syngen.fn and syngen.tool
• Likewise, everything under syngen.audio has been moved down under the syngen global
• syngen.tool.generatorNd and syngen.tool.streamerNd which generate and stream objects in chunks
• Geometric shapes like syngen.tool.plane, syngen.tool.cone, and syngen.tool.sphere

I've been using it for Periphery Synthetic EP, most recently Fishyphus, and plan to use it for new projects moving forward. Therefore, I consider it stable enough to use in production.

However, I haven't found the time to finish documenting the new features. Once complete, it will then become the main branch and only supported release.

Unfortunately there's no ETA for manifesting this intention. The projects keep me very busy!