tl;dr: We'll be moving to a Sequencer-based playback implementation soon, which will make it a bit more complicated to implement custom behavior like scheduled functions.
But more importantly, I have plans to move Alda in a direction where the process that's doing the playback isn't necessarily going to be a Clojure program, which will make executing scheduled Clojure functions impossible.
Also important to note: I don't think scheduled functions are currently of any use. Originally the use case was to print things at various points in the score, which was more of a novelty than anything (although I did consider building a score debugging function on top of them; I think this is still doable without scheduled functions, however), and then even that stopped working when we switched to a client/server architecture. So all in all, I don't think anyone is currently using scheduled functions for anything useful, and it ought be safe to remove them. (Please let me know if that's not the case!)
See discussion here.
tl;dr: We'll be moving to a Sequencer-based playback implementation soon, which will make it a bit more complicated to implement custom behavior like scheduled functions.
But more importantly, I have plans to move Alda in a direction where the process that's doing the playback isn't necessarily going to be a Clojure program, which will make executing scheduled Clojure functions impossible.
Also important to note: I don't think scheduled functions are currently of any use. Originally the use case was to print things at various points in the score, which was more of a novelty than anything (although I did consider building a score debugging function on top of them; I think this is still doable without scheduled functions, however), and then even that stopped working when we switched to a client/server architecture. So all in all, I don't think anyone is currently using scheduled functions for anything useful, and it ought be safe to remove them. (Please let me know if that's not the case!)