5 ms·
Have been trying to get into live coding, mostly with Supercollider but Sonic-Pi looks nice as well (certainly less verbose). On the composition side of things
by bodge5000 4y ago
Have been trying to get into live coding, mostly with Supercollider but Sonic-Pi looks nice as well (certainly less verbose). On the composition side of things it seems to be fantastic, I've used a lot of Renoise and this way of doing things just feels like a more direct way of what I was trying to do there, really nice.
The big drawback for me so far has been sound design. Actually building your own synths can be difficult to even get the basics down, working with samples is predictably a bit of a pain (to the point where I intended to just use synths for everything, drums included), and it doesn't look like many of these tools provide an easy way to reuse synths you've made before in different files.
I know that a lot of the time you can plug these tools into a traditional DAW, which obviously fixes the sound design issue, but this is the kind of thing I'd only really want to use standalone. Maybe its just a part of the learning curve, and eventually sound design gets more intuative.
- lpil 4y agoI think it's not really intended for synth design and complex sound design, it's more akin to an instrument than a DAW. If you read the source code for Sonic Pi you'll see that most the synths are implemented in SuperCollider language or Clojure using the Overtone library, not Ruby/Sonic Pi.
- otikik 4y agoDidn’t Renoise have some sort of Lua interface? In theory it should allow doing what this is doing, and more.
- bodge5000 4y agoIt does, but it ends up working a little bit like using a regular live-coding language with a DAW in that your switching between the two tools. Plus, from what I can remember in Renoise its largely about populating the tracker interface itself rather than values, which makes the whole live portion of it a bit more challenging