Hello Ward, new owner of a Polypulse here. It took me some time to notice its specs and philosophy on the “groovebox” market and I am now very eager to dive into it. I used to make tracks on supercollider – I quit it (at least for the time being) because I found that setting up the audio environnement (buses etc) was quite tedious, but I’ve always been nostalgic of the freedom in composition it provides. I’ve been dreaming of a sort of “supercollider in a box” since then, and the Polypulse is the nearest thing I believe.
The cue system, in particular, makes a lot of sense to me. The way it is implemented corresponds to the way I think of my songs, much better than anything pattern based, following a more classic approach. Besides, the coding/algorithmic aspect of it is very interesting.
I have questions about the programming language we can use in the cue steps, especially about the if/else statements. In the online manual, the only example you give of a condition is “chance()”. And it seems there in only random and chance you can choose from when looking for something to evaluate in the conditionnal statement.
Also, you don’t give an example of a practical use one could make of a while loop. And indeed, I don’t see any in the current state of the language. What could it be ?
So I am curious to know if you consider this aspect of the PP is done, or if you plan to expand the possibilities of the programming language, with new functions, things you can evaluate, etc.
Side note: when you press “no” on the cue step edit screen, you erase a character. But since there is no way to input a single character, you’re a bit stuck if that was a mistake ! Maybe “no” shouldn’t erase a character, to avoid accidentaly having to rewrite your code?
Thanks a lot, I have a question about saving, but I’ll post it elsewhere.
Léon
