If this video was interesting to you, check out the workshop on composing in Python that I'm teaching at Stanford's Center for Computer Research in Music and Acoustics: ccrma.stanford.edu/workshops/comp-with-python
This was one of the 1st Python projects I did. But I tried coding the whole piece not just the section that shifts. It's a lot more complicated as that. The 2nd piano part has to shift exactly a 1/16th note in a specified number of bars which are picked at random from a range. Plus instruments fade in and out and then there are 3 sections with different material. All in all it turned out a big project that I did not complete yet...
Yes, you're right --- very good point! Coding the true score (rather than just the idea of the score) is more challenging and would require some structures for encoding the different sections, the periods of non-acceleration, etc. This would be a really instructive challenge for a later video, although I'm not sure it would be a Python music "short". :-)
Have you thought about coding Arvo Part's "Cantus in Memory of Benjamin Britten"? It's something I thought about doing but then I came across a dissertation where the author already did it, along with some other algorithmic pieces.
I hadn't considered it, but I'll add it to the list of possible videos! I think it's really instructive to try and reconstruct pieces that are already written.
I followed your method and got following error. any idea what could have gone wrong? the music plays with no issue, but I still get this error, and it does not create any pdf file or export to XML. Traceback (most recent call last): The Piano Phase.py", line 26, in performance.to_score(QuantiazationScheme.from_time_signature("3/4", 16)).show() NameError: name 'QuantiazationScheme' is not defined
If this video was interesting to you, check out the workshop on composing in Python that I'm teaching at Stanford's Center for Computer Research in Music and Acoustics: ccrma.stanford.edu/workshops/comp-with-python
This was one of the 1st Python projects I did. But I tried coding the whole piece not just the section that shifts. It's a lot more complicated as that. The 2nd piano part has to shift exactly a 1/16th note in a specified number of bars which are picked at random from a range. Plus instruments fade in and out and then there are 3 sections with different material. All in all it turned out a big project that I did not complete yet...
Yes, you're right --- very good point! Coding the true score (rather than just the idea of the score) is more challenging and would require some structures for encoding the different sections, the periods of non-acceleration, etc. This would be a really instructive challenge for a later video, although I'm not sure it would be a Python music "short". :-)
@@marcevanstein Yes Its definitely not a short!
relatively simple in code but I imagine very tricky to actually play it and track the time shift!
Have you thought about coding Arvo Part's "Cantus in Memory of Benjamin Britten"? It's something I thought about doing but then I came across a dissertation where the author already did it, along with some other algorithmic pieces.
I hadn't considered it, but I'll add it to the list of possible videos! I think it's really instructive to try and reconstruct pieces that are already written.
does this support microtones?
I followed your method and got following error. any idea what could have gone wrong? the music plays with no issue, but I still get this error, and it does not create any pdf file or export to XML.
Traceback (most recent call last):
The Piano Phase.py", line 26, in
performance.to_score(QuantiazationScheme.from_time_signature("3/4", 16)).show()
NameError: name 'QuantiazationScheme' is not defined
You misspelled QuantizationScheme. Did you type it in by hand?