All right, I'll give you the full rundown and you tell me if there's anything novel or interesting. I've looked at wikipedia and the closest I've come to recognizing my idea is in the "mathematical models" section of the wikipedia article on algorithmic composition.
Basically, the concept behind this program is to use only mathematical formulas to write musical compositions. The only knowledge the composer is required to know is arithmetic (including the modulo operation), trigonometric and logarithmic functions, rounding functions, the absolute functions, and some indicative operators that return 1 if the relation is true (the equality, inequality, greater-than and lesser-than relations) and 0 if not, as well as how the different variables increment after evaluation. The composer doesn't need to know how to program.
A note in that context has 4 numbers associated with it, the pitch, duration, temporal offset from the beginning of the piece, and velocity. If you take all the notes in a composition and assign them an order, you get a sequence. A sequence can be calculated by a function. The simplest variable on which to sample that function is the number of notes written before the current note, which we'll call "c", for note counter. Another variable would be the time taken up by all the notes previously written, which we'll call "t", for time (as counted in MIDI ticks) elapsed. There's also a "data[expression][expression]:parameter-name" that provides the value of any parameter of any note that's been previously written in the context of that piece. But let's not talk about "data:", because then things get real complicated real fast. There's also a "D" constant, for the Duration of the piece.
Now we get to the potentially novel part: These musical parameter functions can be piecewise! Well, sort of piecewise. The composer can use several subfunctions to define the sequence that they want to use, but instead of defining the subdomain for each subfunction as a range, instead, the length of each subdomain (aka segment) is calculated by a function, and the subfunction calculated over that segment is also calculated (aka selected) by a function. These two "control functions" are named the length selector and formula selector, respectively. This also means that each subfunction has a number associated with it, assigned implicitly by it's appearance order. Now, this segmentation allows for new variables to be used, such as the "s" variable, representing the quantity of segments previously completed, and the "L" constant (at least it's a constant segment-wise) and "l" variable, which represent the Length of the current segment and the length remaining in the current segment, being measured in notes or ticks, at the composer's choosing. Additionally, there are the variables counting the number of times the subfunction has completed a segment (named "n") and the number of notes the subfunction specifically has written ("x"). These four last variables cannot be used by the control functions, because they are either calculated by them or don't know their values.
A final variable is merely a uniformly-distributed random variable, named "r", which takes a decimal value in the range [0,1[. Additionally, every "r" in a formula is evaluated independently, and has a different value.
I realize that this is a very strange way of writing music, but the idea was to provide a conceptual framework for the mathematical modelisation of individual musical pieces, which would have potentially profound consequences for music theory. In addition, we could then have a mathematical language for discussing the structure of a piece, or a specific melody, or anything that music theorists could think of.