[Csnd] patterns in python
Date | 2012-08-08 11:22 |
From | peiman khosravi |
Subject | [Csnd] patterns in python |
Dear all, has anyone come across this? https://github.com/danstowell/isobar/tree/ It seems that it doesn't allow embedding patterns inside one-another http://www.mcld.co.uk/blog/blog.php?339 And it lacks many random generators but it seems relatively simple to develop it further. Are there any other python pattern libraries available? Best, Peiman |
Date | 2012-08-08 12:21 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] patterns in python |
Yes, good. and in case you don't know it, perhaps you can use AthenaCL for some things too http://www.flexatone.org/article/athenaCLMain Oeyvind 2012/8/8 peiman khosravi |
Date | 2012-08-08 12:36 |
From | peiman khosravi |
Subject | Re: [Csnd] patterns in python |
Thanks Oeyvind. I have never tried AthenaCL but I will now that you mention it. I guess I should be able to call if from within blue. Will post any further findings. Best, Peiman On 8 August 2012 12:21, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Yes, good. |
Date | 2012-08-08 12:39 |
From | peiman khosravi |
Subject | Re: [Csnd] patterns in python |
Looking through the manual of AthenaCL I get the idea that it's very note orientated ('paths' defining pitch classes and so on). I don't feel to uncomfortable with this. What is it like in your experience? Thanks Peiman On 8 August 2012 12:36, peiman khosravi <peimankhosravi@gmail.com> wrote: Thanks Oeyvind. I have never tried AthenaCL but I will now that you mention it. I guess I should be able to call if from within blue. Will post any further findings. |
Date | 2012-08-08 12:51 |
From | peiman khosravi |
Subject | Re: [Csnd] patterns in python |
For example: "A TextureInstance consists of many configurable slots, or attributes. These attributes allow the user to customize each Texture. Attributes include such properties as timbre (instrument and parametric timbre specifications), rhythm (duration and tempo), frequency materials (Path, transposition, and octave position), and mixing (amplitude and panning). Other attributes may control particular features of the Texture, like the number of voices, position of chords, or formal properties." How can a serious computer programme in the 21st century start with such simplistic assumptions as the separation between pitch and 'timbre'? My interest in the generative approach comes solely from my desire to have more control over the micro-level detail of sound rather than note-level structures, and on this level such separations don't exist. The perspectives are so different that I am sure one will encounter endless limitations when trying to adapt note-based algorithms to generate micro-events. It's fine for one of projects but if it's going to be one's compositional environment, I'm afraid it will become limiting and inhibit imagination. Currently, other than Cmask there aren't any easy-to-access csound-related libraries specifically created with this philosophy. I think we need something like this. That may be a task for me follow in a few months (developing a python library). P On 8 August 2012 12:39, peiman khosravi <peimankhosravi@gmail.com> wrote: Looking through the manual of AthenaCL I get the idea that it's very note orientated ('paths' defining pitch classes and so on). I don't feel to uncomfortable with this. What is it like in your experience? |
Date | 2012-08-08 12:59 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] patterns in python |
I haven't been able to dive deeply into AthenaCL, but I've noted the same things as you. I thought perhaps the "data member" atttributes could be used more flexibly, disregarding the original intention that they be notes in a melody, but you may very well be correct in assuming that it will lead to inconvenience and limitations later on. best Oeyvind 2012/8/8 peiman khosravi |