463 karma · joined February 3, 2014
Would the DifferentialEquations.jl work in the Julia community qualify? As I understand it for the pure Julia solvers you can run them through autodiff to differentiate with respect to the parameters. Chris Rackauckas has talked a lot about how cool it is that he can take his solvers that were not written to be AD-aware and use somebody else’s AD package that’s not specialized for diff eqs, and combined you get differentialable diff eqs.
3ms to complete codegen is orders of magnitude faster than I expected. Does that include everything necessary from making the change through actually synthesizing samples?
Can you give a little more detail in how this compares architecturally with something like PD? I imagine a tradeoff of generating LLVM MIR and compiling it is that you can get better performance, but don't get the interactive experience of hearing changes immediately as you tweak the object graph.
Does the DSP graph operate on blocks or sample-by-sample?
That said, a huge part of an artist's work is contextualizing their work and building a story around it, so in some ways if these guys were able to successfully convince people that it was worth $435k then good on them. I just don't expect that to last. When video equipment was inaccessible to most, simple video art was innovative and new. Now that the tools are easy to get and use the work needs to be more sophisticated.
[1]: http://bela.io
Ignoring the role of racism and sexism to try to put all the blame on socio-economic background is a gross oversimplification. The NYtimes had a really nice infographic [1] showing the racial disparities in class mobility. tl;dr - white folks who are born rich tend to stay rich more often than black folks, and those who are born poor are more likely to move upwards.
[1]: https://www.nytimes.com/interactive/2018/03/19/upshot/race-c...
I'm not sure if there's a fair way to quantify drama in a community, but it hasn't been a big issue for me relative to all the positive interactions I've had with other julians.
Then because putting all those dots can be unwieldy, there's the `@.` macro which puts a dot on all your function calls.
The main thing I didn't get a feel for was how this works as your document gets longer, or you're working on multiple documents. If you're writing a book does the whole thing end up being in the same text area and you just scroll around? Is there a save/load?
This is different from supercollider (and I think sound), which have an explicit control rate.
[1]: https://developers.google.com/gmail/markup/reference/flight-...
I think most people want meaningful (purposeful?) lives. Some find that almost exclusively through their work, some through their nonprofessional activities, some through their families. Most are probably a mixture. I think people often find happiness through figuring out what's important to them and organizing their life around that.
I also tried to flip the keras switch to run on top of theano instead but it had issues that I didn't have time to fix, so I just stuck with the original lasagne/theano stack.
Broadly low-level audio APIs are divided into 2 categories:
1. Callback-based - every time the underlying system has a new block of audio available and/or needs to be supplied with a new block, it calls your callback, which reads input data, does whatever processing you want, and writes output data
2. Stream-based - Inputs and Outputs are represented by streams. You can read from the input stream to record and write to the output stream to play back.
Both types of API can be used for low-latency audio, but you generally introduce a buffer of latency when you need to convert between them.
Portaudio lets applications choose which API they want to use.
It could be interesting to do multi-user individual-perspective shutter-based 3D, but you'd need to run at a really high framerate and you'd probably have brightness issues as each eye would only be receiving light for some smaller fraction of time.
http://web.media.mit.edu/~gordonw/CompressiveLightFieldProje...
Similar concept optically (as far as I can tell, it's not really my field) but solves some of the practical implementation issues (particularly the one-projector-per-pixel problem).
I can also whole-heartedly recommend the Saleae logic analyzer, it's saved me literally hundreds of hours over the past few years, and keeps getting better.