4 ms·

> Utility of CSound on Android? Yes. My CSound experience is vi, and csound in X Windows. There's a tremendous amount of editing (I don't do much MIDI with it)

by bch 11y ago

> Utility of CSound on Android? Yes. My CSound experience is vi, and csound in X Windows. There's a tremendous amount of editing (I don't do much MIDI with it), and batch-oriented work (which you touch on wrt Androids latency). So, the compute-power of an android device would be enough to render a score, but when I think of producing original work, or even editing some pre-existing work on an Android device, I think "pain" and "frustration". > I wonder if Pd is already onboard? Apparently [0][1]. [0] https://en.wikipedia.org/wiki/Pure_Data https://en.wikipedia.org/wiki/Pure_Data [1] https://puredata.info/downloads/pddroidparty https://puredata.info/downloads/pddroidparty

bch 11y ago
OK. Downloaded, playing with it[0]... at first blush it looks like it presents the sort of interface one might have made themselves w/ the fltk toolkit. So I've got 5 buttons, a trackpad (nice!!) and 4 sliders. It's fun, but different from MY typical work flow which is: edit a score, run, and tweak the text of the params, so I have a sense of control and understanding, versus "just knob twiddling"[1]. This Android port might be fun, though, for experimenting with parameters of instruments, or just recreational noise making. [0] Use "Drone IV", by Michael Gogins from the Examples. [1] I'm not knocking knob-twiddling, I'm just saying it's not _my_ style.
- bch 11y ago
  Fun, but even like "desktop" CSound, it seems pretty easy to introduce artifacts when using it in realtime (I think CSound's greatest strength is batch-processing whereby you set-up the environment, and then let the CPU churn on it and emit a .wav, like a compiler producing a binary). I don't know if this is strictly CSound or Android audio (as @fit2rule was worried about), or combination. It's unfortunate, because CSound is awesome; hopefully anybody who's introduced to CSound via this is patient and tolerant enough to stick with it. Not perfect, but still a great achievement. Congratulations again.
  - fit2rule 11y ago
    Thanks for reporting in on your experience - if I had an Android device handy I'd check it out .. maybe later in the week. Got any samples of your session online by chance - it might help to introduce newcomers to this fantastic tool.

by bch 11y ago

bch 11y ago

OK. Downloaded, playing with it[0]... at first blush it looks like it presents the sort of interface one might have made themselves w/ the fltk toolkit. So I've got 5 buttons, a trackpad (nice!!) and 4 sliders. It's fun, but different from MY typical work flow which is: edit a score, run, and tweak the text of the params, so I have a sense of control and understanding, versus "just knob twiddling"[1]. This Android port might be fun, though, for experimenting with parameters of instruments, or just recreational noise making. [0] Use "Drone IV", by Michael Gogins from the Examples. [1] I'm not knocking knob-twiddling, I'm just saying it's not _my_ style.

bch 11y ago
Fun, but even like "desktop" CSound, it seems pretty easy to introduce artifacts when using it in realtime (I think CSound's greatest strength is batch-processing whereby you set-up the environment, and then let the CPU churn on it and emit a .wav, like a compiler producing a binary). I don't know if this is strictly CSound or Android audio (as @fit2rule was worried about), or combination. It's unfortunate, because CSound is awesome; hopefully anybody who's introduced to CSound via this is patient and tolerant enough to stick with it. Not perfect, but still a great achievement. Congratulations again.
- fit2rule 11y ago
  Thanks for reporting in on your experience - if I had an Android device handy I'd check it out .. maybe later in the week. Got any samples of your session online by chance - it might help to introduce newcomers to this fantastic tool.