First let me say that I will, after this message, take this topic off-list UNLESS other linart subscribers let me know they want the topic to stay here. I don't want to bore writers and visual artists with issues that might be only relevant to the small world of mad scientists making music with Python. But if some of you like it, I'll be happy to continue to bore you so.
On Sun, Sep 30, 2001 at 03:54:59PM +0200, Maurizio Umberto Puxeddu wrote: > Could I ask if we could agree on the internal rapresentation of > musical events in Python and few other standards? I agree that we should try to agree, once we work out what exactly we are trying to agree on. :) I'm very pleased to hear from you about this, and in fact once I'd worked out a few more basic issues I was planning on writing to you about how pysco and pmask might work together. But with my glacial pace of development, it's a good thing you started the discussion before I got around to it. > My OMDE/pmask has similar aims and it's in a simmetric development stage > compared to pysco: it's weak where, as I understand, pysco is strong > and vice versa. I've only just started looking at pmask, but I think that's a fair assessment, with the qualification that pmask seems to be already much more mature than pysco. I think we're approaching this from opposite and complementary ends. I've just run and looked at all the examples in pmask 0.12, and while I don't yet understand all the details or implications, it seems that pmask is good for easily generating large groups of notes from a few relatively simple statements. Pysco on the other hand has nothing to say about individual notes or scales or rhythms, and gives you no high-level tools with which to create them. The only part of the object-oriented version that's working now is the high-level organization of sections in time relative to each other, because that's the part that I've always found most lacking when I try to do computer music. So if we can find a nice way they can work together, that would be great! It also seems to me that pmask is pretty closely tied to csound. Is this incorrect? I want a framework for gluing together different sound-generating tools; midi softsynths, csound, ecasound, saol, TAON, who knows what else. > You know, just to do not end with two quite nice tools for personal use > only. I'm starting to think that the bazaar thing is no that real. > Not a good sensation. No, no, no! I want to work together on this. I'm just slow and wanted to develop my ideas a bit further before showing anything to you. But maybe it's better to have this discussion before we diverge too far. > At the moment there are software of this kind around: > > 1) Pysco > 2) PyScP What's this? I searched for this name on google and got only something that provides an ftp-like interface over SSH, nothing to do with music. I'm replying to your other message privately. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com
