Spencer Russell

This seems like a good idea and should help boost test coverage. It does change behavior a little though, as `_jl_generating_output()` will get called at macro expansion time rather than...

Gotcha. Do you have a preference between blocking/asynchronous `play`? One thing that I've found handy is to add a `wait` implementation so that you can easily simulate blocking behavior from...

I'm working on a new set of abstractions that I'm hoping will make audio easier to incorporate into other packages in a uniform way without pulling in all the AudioIO...

nope, haven't figured out a good solution yet

I added this to my header. I'm not sure if it depends on some other things I've customized, but maybe it'll set you on the right track: ```latex \AtEveryCitekey{% \clearfield{volume}%...

OK, it's passing all the tests. I've done a little refactoring (I moved the socket stuff into `sclang.js` from `sclang-io.js`, and made sure the connection is cleaned up on `quit`....

Thanks for taking the time to look at this, and sorry the PR co-mingled too many different things. A bit after working on this PR I switched back to using...

More (possibly) useful debugging: ``` echo 'SuperColliderJS.interpret(1234, "SCDoc.documents", nil, false)' | sclang > sclang_output ``` Dumps everything supercollider generates to a file. That file is about 250KB, so if there's...

OK. I think I know what's going on. [This gist](https://gist.github.com/ssfrr/8115445c9fb40f36b2f9027a3cb7e640) shows the output from the above node script, with each `stdout` callback displayed as: ``` ------STDOUT------- content ------------------- ``` at...

I think we could get away with just a SC->JS socket and continue to provide input via `STDIN`. We control what goes in over `STDIN` so that should be fine....