marak / jsonloops Goto Github PK

get gotta be able to fix the play.js file for nodejs to NOT use childprocesses and afplay, thats crazy talk.

we need something like openAL to let us easily play wav files with < 1ms latency

We need to have an easy way to attach meta-data to a track or a beat.

Some examples would be:

track.volume
track.pan
beat.velocity

I'm not sure the best way to add this meta-data. I don't want to complicate the current schema for a JSONloop, but we will need to add something.

Just wondering if you're releasing this software, and if you are, what license are you going to use. I think it would be interesting to extract the server and client components as a generic, real-time client-server synced-event framework (buzzword bingo!) that goes beyond your basic pubsub model.

Installation and configuration is going to be a pita for anyone who wants to start hacking. They'll need to build node as 32bit (and install irrKlang? not sure if its fully vendored )

We should figure out if there is a way to force irrKlang to work without rebuilding node, or attempt to switch to sfml bindings or something.

The point is, we need an easy way to install a JSONloops servers so people can try the project out.

Branch @ https://github.com/catshirt/JSONloops/tree/osc

Deps @ https://github.com/catshirt/node-osc

Add the ability for the browser to download all audio samples in current loop from the server.

Add the ability for the browser to upload new audio assets to the server.

The client should use the highest available file api (HTML5 drag and drop) and degrade gracefully to a flash uploader.

Using http://www.schillmania.com/projects/soundmanager2/ and pending the completion of: https://github.com/Marak/JSONloops/issues#issue/7 we should add the ability to enable audio playback in the browser.

should be pretty easy, just create another version of play.js and have it wrap:

http://www.schillmania.com/projects/soundmanager2/

and then swap the play libs based on the env

To keep this simple, we should create a server-side command that will spawn a child process that takes the current loop and streams it to disk as a wav or mp3 file.

The only thing I'm not sure of is how we will actually create this mix programmatically. I think this is going to depend on the server-side audio library we decide on.

JSONloops should be able to load samples dynamically from Soundcloud based on searches from the browser UI.

Users should be able to assemble custom kits based on searched sounds, then use those kits in JSONloops without having to access SoundCloud servers again ( i.e. JSONloops should stream any acquired media assets from soundcloud into its local directories )

Create a JSON schema to express how JSONloops are constructed. With this schema we can use existing validator tools to check if a loop is constructed properly and throw friendly error messages if not.

http://json-schema.org/