Re: [Pythonsound-devel] pmask and athenaCL

[christopher a. <ar...@fl...>]

thanks for your permission, and im glad you got a chance to check out the
software. please feel free to send along comments, suggestions, or bug
reports. also, please download a new version of athenaCL (or use cvs
update): i fixed a mean bug yesterday. all versions have been updated, and
there is a new chapter to the documentation covering textures.

i too look forward to working on interopeability between the two packages
as well. i dont quite understand OMDE yet, but i will certainly
investigate it in the future.

athenaCL needs python 2.1 or better. works fine in 2.2.

i grabbed pmask version 0.12 off of your site. perhaps it looked odd
because i left out some files: output.py, pitch.py, povray.py,
precision.py, scales, and score.py. this may be a mistake, but my original
plan was not to included the complete pmask package, as i only need
Generator subclasses. These objects will be wrapped in an object in
athenaCL and integrated into athenaCL's argument checking and texture
system. i cant use pmask score, scale, or pitch data-structures (yet?) as
athenaCL already has different implentations of these features tied
closely to the pitch model and the UI.

however, for the sake of giving users all the tools possible, and if you
prefer, i could just as well include the entire pmask package. my
intuition is that most users would rather have a separate copy of pmask
for pmask work, even if one is included within the athenaCL directory.
what do you think?

my goal is to have pmask Generators available from within athenaCL by
version 1.1. the next release, 1.0.14, will include pmask files, though
they are not yet tied to anything in athenaCL. i likely will not get to
version 1.1 until early may.

____________________
   christopher ariza
http://flexatone.com



On Sun, 3 Mar 2002, Maurizio Umberto Puxeddu wrote:

> On Wed, 27 Feb 2002, christopher ariza wrote:
>
> >
> > hi Maurizio. i talked to you sometime ago about my python/csound project
> > called athenaCL. i have been hacking away, and now (after basically
> > redesigning most of the code) i am at the point where i can easily begin
> > to add many parameter operators for use within my software. cmask/pmask
> > provides exactly the kind of library of operators i will need, and i would
> > like to ask permission to include a number of pmask files (within a pmask
> > directory) with athenaCL. since we both use the GPL, i cant imagine that
> > this will bei a problem. i will of course provide the proper
> > acknowledgements and any other information you think necessary. i am also
> > contacting Hans Mikelson for permission to use chaos.py, and Andre
> > Bartetzki for cmask in general.
>
> Of course no problems by my side.
>
> > my goal with athenaCL is to create an agorithmic composition environment
> > that is based on a user friendly, interactive command line interface;
> > rather than writting code that you run to make scores (like cmask/pmask),
> > athenaCL is an application that lets you browse your settings, checks
> > errors, and perform global edits. in this way i think pmask and athenaCL
> > each fill a particular niche.
>
> I'm happy to hear that. I experimented a bit with AthenaCL. Obviously we
> got different views about UI but AthenaCL is very interesting. I hope this
> operation will also
> enable accessing AthenaCL features from OMDE/pmask. I'm open to
> suggestions to improve the interopeability of the two software and to fix
> the bugs you'll find outin OMDE/pmask.
>
> > the files i would like to include are these:
> > accumulator.py
> > bpf.py
> > chaos.py
> > generator.py
> > list.py
> > mask.py
> > oscillator.py
> > quantizer.py
> > range.py
> > rng.py
> > segment.py
>
> What version of Python is AthenaCL based on?
>
> What version of OMDE/pmask are you using?
>
> It seems to me that you are referring to an old version. This may be a
> problem.
>
> Regards,
>
> Maurizio Umberto Puxeddu.
>
>