Had long discussions with my brother (the family musician) on how to encode chords. At some point I even used the actual UTF characters for sharp and bemol and was a total nightmare to write :D
My effort is mostly abandoned (I switched to teach my kids to actually play!). Courage!
The editor is pretty barebones at the moment
A couple of things I noted:
- I couldn't work out how to run two chunks in sequence - I'm presuming the language doesn't support it yet, since none of the examples do it either?
- It would be nice if the "play" keyword accepted the "loop" syntax too (or something similar)
- On the web editor, despite the song reaching the finish, you have to press stop before you can press play again. It's a little thing, but I spent an embarrassingly long amount of time thinking it was just a firefox bug, copying my song to clipboard, refreshing the page and pasting it back in!
That said, have enjoyed playing with it. Any future plans?
Running two chunks in sequence is currently not supported, but I've been considering a separate block (or a customization of a run of a chunk) that could allow that behavior.
Adding looping functionality to play would also be a nice addition.
Future plans wise, in the short term I'm looking to address some bugs and proposed features. But generally want to get the interpreter to a stable state
In terms of extending, is there an easy interface for generating custom waveforms? Or alternatively, if I generate sine oscillator raw data just using javascript math functions, can I mix the resulting waveform into a Handel chuck that's already running?
My first though was that this would make a great basis for Visual Coding! Great Work ;)
I'm looking for something that helps my get back into chip-tunes composing. I used to be an ImpulseTracker junkie in the past.
start
chunk lefthand
play C3, Eb3, G3 for 2b
rest for 2b
endchunk
chunk righthand
play C3 for 1b
play Gb3 for 1b
play Eb3 for 1b
play Db3 for 1b
endchunk
run lefthand with loop for 100
run righthand with loop for 100
finish
Your question does bring up an interesting idea, which would be to have a 'play somechunk' command that is blocking. But that does not exist at the moment
1. Readability:
Ex.
start
play E3, Ab3 for 1b
rest 5b
play E3, Ab3 for 1b
finish
It is somewhat intuitive to read the above without experience with the language (or with programming in general).
2. Procedures: You can create chunks (procedures), which are reusable. For example you can create a chunk which takes 3 chord playables as parameters and run that chunk with any arguments. And also stack those runs on top of each other (because all run chunks play at the same time).
One notable aspect of Handel is the behavior of its procedures, which are called chunks. Each chunk is conceptually a song track and all run chunks (from procedure calls) play at the same time. A run of a chunk can be customized by passing in arguments (ex. chords to use). The bpm, instrument, and loop amount of a run of a chunk can also be optionally set to further customize that run.
Open to questions and feedback!