3 ms·
Seconding everything you say here It takes a while to get it but it is very powerful. Docs could be a bit better (they're not bad) but in the end it is Ruby co
by raverbashing 7y ago
Seconding everything you say here
It takes a while to get it but it is very powerful. Docs could be a bit better (they're not bad) but in the end it is Ruby code. I would also be happier if I had a CLI because the IDE editor has (minor) issues but it also helps a lot with its integration with the rest of the system
But those are minor issues in a great project.
Yes it uses supercollider (too bad that API is much more complicated than Sonic-Pi)
- abetusk 7y agoI haven't used it but apparently there's a `sonic-pi-cli` project that has a command line interface to Sonic Pi [1]. It's unclear to me whether the Sonic Pi IDE has to be running to use it, though. I agree the documentation could be better but, in it's favor, there's a built in tutorial/examples along with built in documentation in the IDE that gets you most of the way there. I find it hard to track down what some of the options do on effects and other functions but these are minor complaints of mine. [1] https://github.com/Widdershin/sonic-pi-cli https://github.com/Widdershin/sonic-pi-cli
- lpil 7y agoIf I might be so cheeky I would suggest my Rust alternative, it is much faster and has a greater feature set -> https://github.com/lpil/sonic-pi-tool/ https://github.com/lpil/sonic-pi-tool/
- lpil 7y agoI created a command line interface for Sonic Pi which can be found here -> https://github.com/lpil/sonic-pi-tool/ https://github.com/lpil/sonic-pi-tool/ Due to some security related changes in Sonic Pi it does not work with the latest version, but hopefully Sam and I can resolve this in future.