As you might know (e. g. hearing the notes the player on the left-hand side plays), I make music. I mainly use ChucK for this purpose, which is a quite simple but functional and well-designed programming language. However, there has been a big limitation in efficiency: I actually had to write down every single note and volume change, filter frequency sweep by my own hands as nasty old numbers in Java-like code. I hope that time has finally ended.
Today I succeeded to connect a very simple Java UI to ChucK via OSC messages (thanks to this post). Now I plan to write my own UI's ("instruments") in Java, generate OSC events with them and record them using the accurate timing built into ChucK. Then I'll use Ruby to generate ChucK code again from the events I recorded. So there goes feedback, too. I'll feel like a real pro... and it all cost nothing, only a little coding experience...
Subscribe to:
Post Comments (Atom)
TODO:
ReplyDelete- block incoming OSC messages in Java (to re-record tracks) - a checkbox for each track
- calculate latency (/latency messages, send+receive to calculate time)