Re: perl / python, was apspec activity: music for single stack

One thing you can do with pmask is to be able to write score sections that
can loop, Hans Mikelson has a good tutorial that talks about how to use
pmask to make drum grooves:
http://csounds.com/ezine/winter2001/pmask/ , I'd like to check out your
system as well, because since its also written in python, its possible to
use it with pmask. One thing that pmask does is place score events into
python objects, while cmask simply puts them into strings, so with pmask
you can pass events from these event objects into other systems.



On Fri, 23 Apr 2004, iain duncan wrote:

> I took a look at pmask, and it ( along with cmask ) does seem worth
> exploring. However, it is ( fortunately ) quite a different beast than what
> I have been working on. I do think there may be good potential in being able
> to move data back and forth between the two however. It seems to me that
> pmask and cmask are better for essentially "hard algorythmic" writing,
> whereas what I am doing is somewhere between that and score writing. My goal
> is ultimately to have a very powerful yet dense total environment for making
> pattern based music in csound. So I intend people to work directly on the
> event lists, using functions to alter them when needed, but the event list
> being "home base" so to speak. This meant to be an improvement on inspecting
> csound score language directly, and to be an environment that would replace
> say Sonar/Cubase/Logic as one's composing pad. Essentially I want something
> like an extremely souped up version of Sonar/Cakewalks event editor, but
> aimed at making it easy to do complicated programming, if a little
> unattractive for simple programming. One will type into the editor much like
> a spread sheet, but also be able to run functions that offset, scale, copy,
> set, repeat, etc, with far more options than conventional multi-trackers
> allow. All meant to be quick to use as well. I aim to have one able to
> listen, think, and program, with less time spent on the program part in
> order to achieve the desired result. Anyway I will post preliminaries soon!
> 
> Iain
> 
> 
> 
> 
> ----- Original Message -----
> From: "Brian Redfern" <[email protected]>
> To: <[email protected]>
> Sent: Friday, April 23, 2004 2:27 PM
> Subject: Re: [CsndTek] perl / python, was apspec activity: music for single
> stack
> 
> 
> > If you like python, its worth looking at pmask, which does everything that
> > cmask used to, but with python. Its more than a step sequencer, you can
> > use a bunch of different algorithms to generate scores, but you can also
> > just use it for step sequencing. I've just gotten into it, and am still
> > learning how to use it, but its very promising, so when I get some
> > tune-age going, I'll post a link to the list.
> >
> >
> >
> > On Fri, 23 Apr 2004, iain duncan wrote:
> >
> > > > I used perl to automate the process of writing the csound score file.
> > > > Then I used csound in deferred time to render the sound file.
> > >
> > > Care to share more details? I have been working on the same thing with
> > > Python, so I'm quite interested.
> > >
> > > For others interested, I will soon be putting out my very alpha first
> set of
> > > tools for text based step sequencing using a modified gvim and python
> > > scripts. Basically it's like a tracker/event list approach with 1 line
> per
> > > sixteenth note ( though that can change ) and one instrument per
> sequence
> > > file. This then gets processed into a big score. I'm still hashing out
> some
> > > details though, but it works. Generated a functional score from
> multi-track
> > > step lists yesterday.
> > >
> > > I've come to the realize that the score language is beautiful in it's
> > > elegant simplicity but not so fun to edit directly. On the other hand,
> it's
> > > a dead easy to format to automate.
> > >
> > > Iain
> > >
> > > >
> > > > Have a nice weekend!
> > > > - --
> > > > gerald wenzel
> > > > music: http://apspec.com
> > > > linux & code: http://geraldwenzel.com
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -----BEGIN PGP SIGNATURE-----
> > > > Version: GnuPG v1.2.1 (GNU/Linux)
> > > > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> > > >
> > > > iD8DBQFAiSVAIpVgmwHkjoURAuBcAJ43xc1DEg4vyDzRSgvIJmKxYkPV5gCfZ6/K
> > > > fXs6fE6NEedZkdruCJKSiyg=
> > > > =eF9k
> > > > -----END PGP SIGNATURE-----
> > > > _______________________________________________
> > > > csoundtekno mailing list
> > > > [email protected]
> > > >
> > > > Subscribe, unsubscribe, change mailing list options:
> > > > http://plot.bek.no/mailman/listinfo/csoundtekno
> > >
> > > _______________________________________________
> > > csoundtekno mailing list
> > > [email protected]
> > >
> > > Subscribe, unsubscribe, change mailing list options:
> > > http://plot.bek.no/mailman/listinfo/csoundtekno
> > >
> >
> > _______________________________________________
> > csoundtekno mailing list
> > [email protected]
> >
> > Subscribe, unsubscribe, change mailing list options:
> > http://plot.bek.no/mailman/listinfo/csoundtekno
> 
> _______________________________________________
> csoundtekno mailing list
> [email protected]
> 
> Subscribe, unsubscribe, change mailing list options:
> http://plot.bek.no/mailman/listinfo/csoundtekno
> 

_______________________________________________
csoundtekno mailing list
[email protected]

Subscribe, unsubscribe, change mailing list options:
http://plot.bek.no/mailman/listinfo/csoundtekno