From andersvi at extern.uio.no Tue Mar 1 02:15:41 2005 From: andersvi at extern.uio.no (Anders Vinjar) Date: Tue, 01 Mar 2005 11:15:41 +0100 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <4223BFA4.8080605@gmail.com> (Chris Dawson's message of "Mon, 28 Feb 2005 17:04:36 -0800") References: <4223BFA4.8080605@gmail.com> Message-ID: NOTAM has been running PlanetCCRMA with various kernels (redhat-8/9, FC-1/2/3) as main linux-environment since the start of the dist, and seem to continue to be doing so for the moment. Most things seem to work well for most people. I know they consider Agnula/Demudi at times, but no conversion yet. Although also installed as part of the PlanetCCRMA-dist, they use local builds of Snd/CM/CLM/CMN, at times also various PD-libs for various reasons: local hacks, fixes, odditities & development work. CM from CVS seems to be functioning great. >>> "C" == Chris Dawson writes: C> This is not directly related to CM, so if people wish to C> answer offline, that is definitely acceptable. I am about to C> install a new distro on my desktop, and would like advice C> about which audio-optimized distribution people are using. I C> suspect CCRMA is what most will recommend since it is C> developed IIRC by the same people who do CM, but does anyone C> feel happy using Agnula, for example, or audioslack? I C> personally try to stay away from RedHat, and though Fedora is C> better, I would definitely prefer a debian based distro. I'll C> prepare myself for the flames... C> C> Thanks, Chris C> C> -- linux hacker From fbar at footils.org Tue Mar 1 02:41:38 2005 From: fbar at footils.org (Frank Barknecht) Date: Tue, 1 Mar 2005 11:41:38 +0100 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <4223FFDE.1030403@cesmail.net> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> Message-ID: <20050301104138.GE13343@fliwatut.scifi> Hallo, M. Edward (Ed) Borasky hat gesagt: // M. Edward (Ed) Borasky wrote: > I tried AgNuLa briefly when it first came out. They used to have two > flavors, DeMuDi (Debian-based) and ReMuDi (Red Hat based) but they may > have dropped the Red Hat flavor. ReMuDi is dead. If you want a rpm-based audio distribution, the way to go is the Planet. > In any event, I'm not sure they have packages for any of the CCRMA > tools (like CM); you'd need to get ".deb" packages from somewhere or > build them from source. There is no CM package in Debian/Demudi yet, but there is interest to incorporate it. As Debian has a full assortment of LISPs and Schemes, installing CM from CVS/source is no big problem, if you follow the instrucitons on the CM site. However of course a .deb would be nicer. Any help would be highly welcome over on the AGNULA lists. > What I have seen of AgNuLa (the Debian flavor) is quite impressive. I > don't particularly like either Gnome or fluxbox, but KDE is too > heavyweight for some of the real-time work, and even if you don't load > Gnome, a lot of it gets installed anyway, because a number of packages > depend on big chunks of it. You can load anything in the Debian > repositories on a DeMuDi system. If I had a dedicated audio system, it > would be my distro of choice for that system. I agree here: Installation of Demudi is very easy, as it uses the new Debian installer and has some audio related tweaks (including seeminly minor things like disabling the usbmidi/usbaudio drivers in favour of the ALSA drivers, something several distributions still fail at.) As it's Debian based, you have a HUGE pool of other software to install almost without pain using Debian testing, soon stable. This includes installing different desktop environments or window managers etc. Ciao -- Frank Barknecht _ ______footils.org__ _ __latest track: fqdn _ http://footils.org/cms/show/38 From znmeb at cesmail.net Tue Mar 1 07:32:53 2005 From: znmeb at cesmail.net (M. Edward (Ed) Borasky) Date: Tue, 01 Mar 2005 07:32:53 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <20050301104138.GE13343@fliwatut.scifi> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> Message-ID: <42248B25.90403@cesmail.net> Frank Barknecht wrote: >There is no CM package in Debian/Demudi yet, but there is interest to >incorporate it. As Debian has a full assortment of LISPs and Schemes, >installing CM from CVS/source is no big problem, if you follow the >instrucitons on the CM site. However of course a .deb would be nicer. >Any help would be highly welcome over on the AGNULA lists. > > Gentoo already has packaged "cm", but they took the coward's way out and just used the Scheme version under Guile. At my instigation, they are re-packaging it to use their version of the Debian "common-lisp-controller". A Debian source package should be easy once the CLC work is done. I've also requested "clm" and "cmn" and a combined "cm/clm/cmn" package. I'd take a shot at the packaging myself if I knew anything about how to use the "common-lisp-controller". Is there documentation on it somewhere? Besides, can't you install from an RPM on Debian (and Gentoo)? Does there need to be a ".deb" for a package to make it into AgNuLa? From rm at fabula.de Tue Mar 1 07:41:58 2005 From: rm at fabula.de (rm at fabula.de) Date: Tue, 1 Mar 2005 16:41:58 +0100 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <42248B25.90403@cesmail.net> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> Message-ID: <20050301154158.GB30603@seid-online.de> On Tue, Mar 01, 2005 at 07:32:53AM -0800, M. Edward (Ed) Borasky wrote: > Frank Barknecht wrote: > > >There is no CM package in Debian/Demudi yet, but there is interest to > >incorporate it. As Debian has a full assortment of LISPs and Schemes, > >installing CM from CVS/source is no big problem, if you follow the > >instrucitons on the CM site. However of course a .deb would be nicer. > >Any help would be highly welcome over on the AGNULA lists. > > > > > Gentoo already has packaged "cm", but they took the coward's way out and > just used the Scheme version under Guile. At my instigation, they are > re-packaging it to use their version of the Debian > "common-lisp-controller". A Debian source package should be easy once > the CLC work is done. I've also requested "clm" and "cmn" and a combined > "cm/clm/cmn" package. I'd take a shot at the packaging myself if I knew > anything about how to use the "common-lisp-controller". Is there > documentation on it somewhere? I'd rather go for ASDF-installable versions of cm/clm/cmn. That's all that's needed to cooperate with CLC. > Besides, can't you install from an RPM on Debian (and Gentoo)? Does > there need to be a ".deb" for a package to make it into AgNuLa? Ugly hack only. Building the debs is actually rather trivial - it's the dependency checking that is rather hard if you want it to be usefull. hth Ralf Mattes > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From znmeb at cesmail.net Tue Mar 1 20:21:22 2005 From: znmeb at cesmail.net (M. Edward (Ed) Borasky) Date: Tue, 01 Mar 2005 20:21:22 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <20050301154158.GB30603@seid-online.de> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> Message-ID: <42253F42.3050603@cesmail.net> rm at fabula.de wrote: >I'd rather go for ASDF-installable versions of cm/clm/cmn. That's all that's >needed to cooperate with CLC. > > I think that's the approach the Gentoo packager is taking, but without documentation, I have know way of knowing what he is doing or why. :) Since I've got the attention of CM/CLM/CMN users, what are the tradeoffs between having them individually packaged and packaged as a bundle as described in the documentation? I do plan to use both CM and CLM, but probably not CMN. So if I get them packaged separately, it will be a minor inconvenience, and if I get them packaged as a bundle, there might be a memory hit at run time I don't need. >Ugly hack only. Building the debs is actually rather trivial - it's the >dependency checking that is rather hard if you want it to be usefull. > > Yeah ... especially when you have the option of Guile, Clisp, CMUCL or SBCL as you do with CM 2.5.0. From taube at uiuc.edu Wed Mar 2 04:35:49 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 2 Mar 2005 06:35:49 -0600 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <42253F42.3050603@cesmail.net> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> Message-ID: <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> >> Ugly hack only. Building the debs is actually rather trivial - it's >> the >> dependency checking that is rather hard if you want it to be usefull. there are no dependencies. since the last release of cm you can build all the systems separately then load what you want at run time. for example, depending on what im doing these days i start cm and then load in either clm2 or clm3. if midishare is properly installed it is automatically loaded. loading these systems at runtime is fast, flexible and lets you stay current -- saving images doesnt make much sense anymore unless your goal is to keep a snapshot "stable" (whatever that means with software like this!) all three -- clm, cmn and cm -- check at runtime to see if their fasls are out of data, and if so, they get compiled so installation and running is identical. so for cm installation is: tar -zxf cm.tar.gz and running is: cm/bin/cm.sh asdf installs can just load src/cm.lisp or if they need more control, load src/make.lisp and call make-cm with the appropriate arguments. On Mar 1, 2005, at 10:21 PM, M. Edward (Ed) Borasky wrote: > rm at fabula.de wrote: > >> I'd rather go for ASDF-installable versions of cm/clm/cmn. That's all >> that's >> needed to cooperate with CLC. > I think that's the approach the Gentoo packager is taking, but without > documentation, I have know way of knowing what he is doing or why. :) > Since I've got the attention of CM/CLM/CMN users, what are the > tradeoffs between having them individually packaged and packaged as a > bundle as described in the documentation? I do plan to use both CM and > CLM, but probably not CMN. So if I get them packaged separately, it > will be a minor inconvenience, and if I get them packaged as a bundle, > there might be a memory hit at run time I don't need. > >> Ugly hack only. Building the debs is actually rather trivial - it's >> the >> dependency checking that is rather hard if you want it to be usefull. >> > Yeah ... especially when you have the option of Guile, Clisp, CMUCL or > SBCL as you do with CM 2.5.0. > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From rm at fabula.de Wed Mar 2 05:31:39 2005 From: rm at fabula.de (rm at fabula.de) Date: Wed, 2 Mar 2005 14:31:39 +0100 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> Message-ID: <20050302133139.GA3361@seid-online.de> On Wed, Mar 02, 2005 at 06:35:49AM -0600, Rick Taube wrote: > >>Ugly hack only. Building the debs is actually rather trivial - it's > >>the > >>dependency checking that is rather hard if you want it to be usefull. > > there are no dependencies. since the last release of cm you can build > all the systems separately then load what you want at run time. for > example, depending on what im doing these days i start cm and then load > in either clm2 or clm3. if midishare is properly installed it is > automatically loaded. Oh, i wasn't talking about interdependencies inbetween cm/cmn/clm. A "proper" Debian packet would have to set dependencies on "a lisp implementation capable of running cm/clm..." or Guile. > loading these systems at runtime is fast, flexible and lets you stay > current -- saving images doesnt make much sense anymore unless your > goal is to keep a snapshot "stable" (whatever that means with software > like this!) all three -- clm, cmn and cm -- check at runtime to see if > their fasls are out of data, and if so, they get compiled so > installation and running is identical. so for cm installation is: > tar -zxf cm.tar.gz > and running is: > cm/bin/cm.sh > > asdf installs can just load src/cm.lisp or if they need more control, > load src/make.lisp and call make-cm with the appropriate arguments. Yes, of course. I'm just woundering whether it might be worth the effort to migrate all of that to ASDF. After all, ASDF does itself already track lsip/fasl dependencies etc. (and it's posssible to express other dependencies as well. Imagine that parts of a fiktious CM-GUI would depend on Lambda-GTK ...). Cheers Ralf Mattes From marco at trevisani.net Wed Mar 2 06:34:22 2005 From: marco at trevisani.net (marco trevisani) Date: Wed, 2 Mar 2005 10:34:22 -0400 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <20050302133139.GA3361@seid-online.de> References: <4223BFA4.8080605@gmail.com> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <20050302133139.GA3361@seid-online.de> Message-ID: <200503021034.22619.marco@trevisani.net> HI all, as for .deb packaging: an year ago i started to package the trinity...:-) , i acutally did it just for clm and then could not find enough free time to finish the job for the others two. It should not be difficult. Of course the best way for Debian would be to offer clm, cm and cmn either as single packages and as well as a meta package that installs the three of them, and since csound is now available for Debian it would be great to make that as part of the package to (i think simply as "suggested" or "depends"). I use clm-3 for my Debian set up deb-packaged by me, and i'm more than glad to pass all the scripts to anybody who is interested in complete the job and has time (contact me privately if you are interested). My Debian files for clm are updated to clm-3. Last time i have updated clm-3 in my machine was on november 2004. It is "old", just because i was wrting a composition so usually, to be safe, while working i stick with the last working fine (for me) version. As for distribution...Even if i worked (and actually cofounded) DeMuDi, i always staied with a clean Debian ,where eventually DeMuDi should fall as part of the debian-multimedia, and i think this is happening...i'm not following closely this right now. I'm running a clean Debian unstable with 2.6.10, and i get all i need for music and it runs smooth, stable (even if "unstable"). Somewhere i read that DeMuDi is going to test 2.6.10, which i think is a good move. Just to give an idea of the audio software i use, a part for the trinity and SND: ardour, jack, pd/gem/pdp, audacity, csound, cecilia, wavesurfer - as far i remember. Lately i jumped into the animation field and software under debian i use with success are: blender,yafray, gimp, cinepaint, povray (in the non free section in debian,,though it is more recent and working fine the newest version on their site povray.org, next version 4.0 is suppose to be free-software), cinelerra (non packaged in Debian and available in deb package from an unofficial site). Now i trow a little rock in the lake to see the reactions...:-)) I havent used cm from the middle of 90s, i like it, but i should go back and study it again, and free time is now distributed in little drops...though i have a ..."dream" ... It would be amazing if it would be possible to integrate an animation tool such as povray scripts into cm so to be able to right audio/animation algorhythmic compositions.....i found, by seraching the web, that someone, years ago wrote some lisp code for povray. I think it would be amazing... Ok i have also the second stage of the dream...It would be greater to integrate scripts like dvdauthor and encoders, ffmpeg, transcode, so to compose audio and animation and then have them eoncoded and recorded on a dvd... ok ok, it was just a dream...:-) ciao, marco -- ************************************************************************ marco trevisani http://marco.trevisani.net marco at trevisani.net Neither MS-Word nor MS-PowerPoint attachments please (use rtf) Please DO NOT store my e-mail in your OUTLOOK express addressbook "Malditas sean las guerras y los canallas que las hacen" J.Anguita ************************************************************************ From marco at trevisani.net Wed Mar 2 07:41:47 2005 From: marco at trevisani.net (marco trevisani) Date: Wed, 2 Mar 2005 11:41:47 -0400 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <200503021034.22619.marco@trevisani.net> References: <4223BFA4.8080605@gmail.com> <20050302133139.GA3361@seid-online.de> <200503021034.22619.marco@trevisani.net> Message-ID: <200503021141.48130.marco@trevisani.net> sorry for the second message...i need to make a correction...amongst the english errors that were present in my message there there is one in the below sentence that could make really unreadable the message. to be able to write and not to be able to right... sorry, marco Alle 10:34, mercoled? 02 marzo 2005, marco trevisani ha scritto: | It would be amazing if it would be possible to integrate an animation tool | such as povray scripts into cm so to be able to right audio/animation | algorhythmic compositions.....i found, by seraching the web, that someone, | years ago wrote some lisp code for povray. I think it would be amazing... | Ok i have also the second stage of the dream...It would be greater to | integrate scripts like dvdauthor and encoders, ffmpeg, transcode, so to | compose audio and animation and then have them eoncoded and recorded on a | dvd... | ok ok, it was just a dream...:-) | | ciao, | marco -- ************************************************************************ marco trevisani http://marco.trevisani.net marco at trevisani.net Neither MS-Word nor MS-PowerPoint attachments please (use rtf) Please DO NOT store my e-mail in your OUTLOOK express addressbook "Malditas sean las guerras y los canallas que las hacen" J.Anguita ************************************************************************ From znmeb at cesmail.net Wed Mar 2 08:02:26 2005 From: znmeb at cesmail.net (M. Edward (Ed) Borasky) Date: Wed, 02 Mar 2005 08:02:26 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <200503021034.22619.marco@trevisani.net> References: <4223BFA4.8080605@gmail.com> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <20050302133139.GA3361@seid-online.de> <200503021034.22619.marco@trevisani.net> Message-ID: <4225E392.2030507@cesmail.net> marco trevisani wrote: >Now i trow a little rock in the lake to see the reactions...:-)) >I havent used cm from the middle of 90s, i like it, but i should go back and >study it again, and free time is now distributed in little drops...though i >have a ..."dream" ... >It would be amazing if it would be possible to integrate an animation tool >such as povray scripts into cm so to be able to right audio/animation >algorhythmic compositions.....i found, by seraching the web, that someone, >years ago wrote some lisp code for povray. I think it would be amazing... >Ok i have also the second stage of the dream...It would be greater to >integrate scripts like dvdauthor and encoders, ffmpeg, transcode, so to >compose audio and animation and then have them eoncoded and recorded on a >dvd... >ok ok, it was just a dream...:-) > > Well ... from what I've seen in the list of packages available in Debian (and Gentoo) that work with Common Lisp, putting something like this together doesn't look all that difficult if you are a CM and Common Lisp expert. Of course, you can always execute command-line tools in a Lisp function, right? :) From marco at trevisani.net Wed Mar 2 08:29:26 2005 From: marco at trevisani.net (marco trevisani) Date: Wed, 2 Mar 2005 12:29:26 -0400 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <4225E392.2030507@cesmail.net> References: <4223BFA4.8080605@gmail.com> <200503021034.22619.marco@trevisani.net> <4225E392.2030507@cesmail.net> Message-ID: <200503021229.26282.marco@trevisani.net> Alle 12:02, mercoled? 02 marzo 2005, M. Edward (Ed) Borasky ha scritto: | marco trevisani wrote: | >Now i trow a little rock in the lake to see the reactions...:-)) | >I havent used cm from the middle of 90s, i like it, but i should go back | > and study it again, and free time is now distributed in little | > drops...though i have a ..."dream" ... | >It would be amazing if it would be possible to integrate an animation | > tool such as povray scripts into cm so to be able to right | > audio/animation algorhythmic compositions.....i found, by seraching the | > web, that someone, years ago wrote some lisp code for povray. I think it | > would be amazing... Ok i have also the second stage of the dream...It | > would be greater to integrate scripts like dvdauthor and encoders, | > ffmpeg, transcode, so to compose audio and animation and then have them | > eoncoded and recorded on a dvd... | >ok ok, it was just a dream...:-) | | Well ... from what I've seen in the list of packages available in Debian | (and Gentoo) that work with Common Lisp, putting something like this | together doesn't look all that difficult if you are a CM and Common Lisp | expert. Of course, you can always execute command-line tools in a Lisp | function, right? :) Yes indeed, this is particularly true for the second part, encoders etc. that are very easy to call via command line (dvdauthor reads and generates xml scripts). A different story would be for povray, which integration would be similar, on the conceptual side to csound whitin cm. Infact, a part for the final step, the command line to invoke in order to excecute some scripts, all the calls for the scripts (lights, camera, reflections, objects, textures etc.) should somehow imported into cm in order to write them in lisp, Yes indeed this work would be rather tedious than complicated.... ciao, marco -- ************************************************************************ marco trevisani http://marco.trevisani.net marco at trevisani.net Neither MS-Word nor MS-PowerPoint attachments please (use rtf) Please DO NOT store my e-mail in your OUTLOOK express addressbook "Malditas sean las guerras y los canallas que las hacen" J.Anguita ************************************************************************ From taube at uiuc.edu Wed Mar 2 09:00:47 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 2 Mar 2005 11:00:47 -0600 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <200503021141.48130.marco@trevisani.net> References: <4223BFA4.8080605@gmail.com> <20050302133139.GA3361@seid-online.de> <200503021034.22619.marco@trevisani.net> <200503021141.48130.marco@trevisani.net> Message-ID: > | It would be amazing if it would be possible to integrate an > animation tool > | such as povray scripts into cm so to be able to right > audio/animation > | algorhythmic compositions.....i found, by seraching the web, that > someone, if these scripts simply involve file based processing this sort of thing is really not that difficult to add to the existing framework by suclassing an existing io stream and writing a handful of methods. if it involves "direct connection" its more difficult (lisp ffis) but can still be done. but of course it takes someone doing it.. right now i am aware of seveal such useful projects by people on this list: direct output to alsa midi seqs score file output to supercollider3 plotting output to gnuplot and someone recently inquired about generating enigma files for working with sibelius and finale. it would be a Fine Thing if these things could be added so that everyone might benefit. i am more than happy to help and contribute in whatver way i can but i cant become a guru in the api's and file formats for all these things! From cewing at u.washington.edu Wed Mar 2 09:25:01 2005 From: cewing at u.washington.edu (cristopher pierson ewing) Date: Wed, 2 Mar 2005 09:25:01 -0800 (PST) Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: References: <4223BFA4.8080605@gmail.com> <20050302133139.GA3361@seid-online.de> <200503021034.22619.marco@trevisani.net> <200503021141.48130.marco@trevisani.net> Message-ID: On the subject of output to povray, I've been using some code developed by a friend up here in Seattle to do just that. I've used it to create a layer of animated stuff in a short film I've been doing. The CM part detected onsets of some bell-like sounds and generated a 'score' of povray macro calls that generated the video in synch with the audio. The base code is pretty simple. I can ask him if he'd be willing to throw the stuff up for everyone to use. C ******************************** Cris Ewing CME and Telehealth Web Services University of Washington School of Medicine Work Phone: (206) 685-9116 Home Phone: (206) 365-3413 E-mail: cewing at u.washington.edu ******************************* On Wed, 2 Mar 2005, Rick Taube wrote: > >> | It would be amazing if it would be possible to integrate an animation >> tool >> | such as povray scripts into cm so to be able to right audio/animation >> | algorhythmic compositions.....i found, by seraching the web, that >> someone, > > if these scripts simply involve file based processing this sort of thing is > really not that difficult to add to the existing framework by suclassing an > existing io stream and writing a handful of methods. if it involves "direct > connection" its more difficult (lisp ffis) but can still be done. but of > course it takes someone doing it.. right now i am aware of seveal such > useful projects by people on this list: > direct output to alsa midi seqs > score file output to supercollider3 > plotting output to gnuplot > and someone recently inquired about generating enigma files for working with > sibelius and finale. > it would be a Fine Thing if these things could be added so that everyone > might benefit. i am more than happy to help and contribute in whatver way i > can but i cant become a guru in the api's and file formats for all these > things! > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > From marco at trevisani.net Wed Mar 2 09:45:44 2005 From: marco at trevisani.net (marco trevisani) Date: Wed, 2 Mar 2005 13:45:44 -0400 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: References: <4223BFA4.8080605@gmail.com> Message-ID: <200503021345.44591.marco@trevisani.net> Alle 13:25, mercoled? 02 marzo 2005, cristopher pierson ewing ha scritto: | On the subject of output to povray, I've been using some code developed by | a friend up here in Seattle to do just that. I've used it to create a | layer of animated stuff in a short film I've been doing. The CM part | detected onsets of some bell-like sounds and generated a 'score' of povray | macro calls that generated the video in synch with the audio. The base | code is pretty simple. I can ask him if he'd be willing to throw the | stuff up for everyone to use. that would be very nice. marco | | C | | ******************************** | Cris Ewing | CME and Telehealth Web Services | University of Washington | School of Medicine | Work Phone: (206) 685-9116 | Home Phone: (206) 365-3413 | E-mail: cewing at u.washington.edu | ******************************* | | On Wed, 2 Mar 2005, Rick Taube wrote: | >> | It would be amazing if it would be possible to integrate an | >> | animation | >> | >> tool | >> | >> | such as povray scripts into cm so to be able to right | >> | audio/animation algorhythmic compositions.....i found, by seraching | >> | the web, that | >> | >> someone, | > | > if these scripts simply involve file based processing this sort of | > thing is really not that difficult to add to the existing framework by | > suclassing an existing io stream and writing a handful of methods. if it | > involves "direct connection" its more difficult (lisp ffis) but can | > still be done. but of course it takes someone doing it.. right now i | > am aware of seveal such useful projects by people on this list: | > direct output to alsa midi seqs | > score file output to supercollider3 | > plotting output to gnuplot | > and someone recently inquired about generating enigma files for working | > with sibelius and finale. | > it would be a Fine Thing if these things could be added so that everyone | > might benefit. i am more than happy to help and contribute in whatver | > way i can but i cant become a guru in the api's and file formats for all | > these things! | > | > _______________________________________________ | > Cmdist mailing list | > Cmdist at ccrma.stanford.edu | > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist | | _______________________________________________ | Cmdist mailing list | Cmdist at ccrma.stanford.edu | http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist -- ************************************************************************ marco trevisani http://marco.trevisani.net marco at trevisani.net Neither MS-Word nor MS-PowerPoint attachments please (use rtf) Please DO NOT store my e-mail in your OUTLOOK express addressbook "Malditas sean las guerras y los canallas que las hacen" J.Anguita ************************************************************************ From nando at ccrma.Stanford.EDU Wed Mar 2 11:01:32 2005 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: 02 Mar 2005 11:01:32 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> Message-ID: <1109790092.8642.122.camel@cmn37.stanford.edu> On Wed, 2005-03-02 at 04:35, Rick Taube wrote: > >> Ugly hack only. Building the debs is actually rather trivial - it's > >> the > >> dependency checking that is rather hard if you want it to be usefull. > > there are no dependencies. since the last release of cm you can build > all the systems separately then load what you want at run time. for > example, depending on what im doing these days i start cm and then load > in either clm2 or clm3. if midishare is properly installed it is > automatically loaded. > loading these systems at runtime is fast, flexible and lets you stay > current -- saving images doesnt make much sense anymore unless your > goal is to keep a snapshot "stable" (whatever that means with software > like this!) all three -- clm, cmn and cm -- check at runtime to see if > their fasls are out of data, and if so, they get compiled so > installation and running is identical. That is true for a user that installs in his/her/its home directory (or somewhere else where he has write access) and has complete control of the software. It is not possible to do that on a packaged version of cm/clm/cmn (at least the way I package it), the user of the software is typically not the installer (root) and will not have write access to the packaged binaries. Planet CCRMA has had Common Lisp based packages for cm/clm/cmn since 2001. The packaging approach I have used lately is to load the prebuilt systems at runtime on top of a clean lisp image (this is for cm 2.4.x, clm2/clm3 and cmn). Maybe this could be used as "inspiration" for other packagers. The current package structure is like this (this is after several iterations over the years on how to package the stuff): clm -> source code only, common to all lisps clm-cmucl -> requires "clm" and "cmucl", packages all cmucl binaries clm-sbcl -> requires "clm" and "sbcl", packages all sbcl binaries clm-xxx for other supported versions of lisp same with clm2 prefix for a backwards compatibility package for clm2. same naming and packaging scheme for cmn. So, installing a working clm for a particular lisp in Planet CCRMA is just "apt-get install clm-cmucl". I presume this could be converted into an "emerge clm-cmucl" command :-) The binary packages include a simple subsystem lisp stub that loads what's needed, and a one line bash script installed in /usr/bin that starts that particular flavor, so just typing /usr/bin/clm-cmucl starts the cmucl version of lisp and loads all of clm. Same mechanism for cmn. Cm is sligthly different as it contains hooks to signal loading the other packages (this is still 2.4.x, the latest official release): cm -> source code only cm-cmucl -> requires "cm" and "cmucl", packages all cmucl binaries cm-xxx for other supported lisps cm-clm-cmucl -> requires "clm", includes just one file that signals the cm startup code to load clm before loading cm into the lisp image. cm-clm-xxx for other supported versions of lisp cm-cmn-xxx for cmn and supported versions of lisp So, installing "apt-get install cm-clm-cmucl cm-cmn-cmucl" will install the whole thing and after that typing "/usr/bin/cm-cmucl" will load everything into a fresh copy of lisp (clm, then cmn, then cm). Or, installing "apt-get install cm-clm-cmucl cmn-cmucl" will install everything but will only load clm and cm on startup when typing /usr/bin/cm-cmucl, after that it would be possible to load cmn by saying "(require 'cmn)". Anyway, I'm sure there are better, more clean and lispy ways of doing all this. Still, probably the packaging structure and dependencies are fine. I also have packages for slime so that it is easy to run any of these packages as subprocesses of emacs or xemacs. More details available on request (file structure within a package, details and so on and so forth, many small details had to be hacked for this to work). Or download the relevant source packages from: http://ccrma.stanford.edu/planetccrma/mirror/all/linux/SRPMS/ -- Fernando > so for cm installation is: > tar -zxf cm.tar.gz > and running is: > cm/bin/cm.sh > > asdf installs can just load src/cm.lisp or if they need more control, > load src/make.lisp and call make-cm with the appropriate arguments. > > On Mar 1, 2005, at 10:21 PM, M. Edward (Ed) Borasky wrote: > > > rm at fabula.de wrote: > > > >> I'd rather go for ASDF-installable versions of cm/clm/cmn. That's all > >> that's > >> needed to cooperate with CLC. > > I think that's the approach the Gentoo packager is taking, but without > > documentation, I have know way of knowing what he is doing or why. :) > > Since I've got the attention of CM/CLM/CMN users, what are the > > tradeoffs between having them individually packaged and packaged as a > > bundle as described in the documentation? I do plan to use both CM and > > CLM, but probably not CMN. So if I get them packaged separately, it > > will be a minor inconvenience, and if I get them packaged as a bundle, > > there might be a memory hit at run time I don't need. > > > >> Ugly hack only. Building the debs is actually rather trivial - it's > >> the > >> dependency checking that is rather hard if you want it to be usefull. > >> > > Yeah ... especially when you have the option of Guile, Clisp, CMUCL or > > SBCL as you do with CM 2.5.0. > > From taube at uiuc.edu Wed Mar 2 12:27:37 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 2 Mar 2005 14:27:37 -0600 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <1109790092.8642.122.camel@cmn37.stanford.edu> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <1109790092.8642.122.camel@cmn37.stanford.edu> Message-ID: yes the main point i wanted to make was that loading seperate pacakges at runtime is better than shipping images in installs because then each package can be upgraded on its own as the user wishes but still work together. thats what the planet ccrma packaging does as described. fwiw, if you start cm and it doesnt have write permission for a fasl it thinks it should update it will simply load the source file. I think most lisps now compile everything anyway. >> >> there are no dependencies. since the last release of cm you can build >> all the systems separately then load what you want at run time. for >> example, depending on what im doing these days i start cm and then >> load >> in either clm2 or clm3. if midishare is properly installed it is >> automatically loaded. >> loading these systems at runtime is fast, flexible and lets you stay >> current -- saving images doesnt make much sense anymore unless your >> goal is to keep a snapshot "stable" (whatever that means with software >> like this!) all three -- clm, cmn and cm -- check at runtime to see >> if >> their fasls are out of data, and if so, they get compiled so >> installation and running is identical. > > That is true for a user that installs in his/her/its home directory (or > somewhere else where he has write access) and has complete control of > the software. From nando at ccrma.Stanford.EDU Wed Mar 2 12:45:40 2005 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: 02 Mar 2005 12:45:40 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <1109790092.8642.122.camel@cmn37.stanford.edu> Message-ID: <1109796340.8641.449.camel@cmn37.stanford.edu> On Wed, 2005-03-02 at 12:27, Rick Taube wrote: > yes the main point i wanted to make was that loading seperate pacakges > at runtime is better than shipping images in installs because then each > package can be upgraded on its own as the user wishes but still work > together. Sorry I misunderstood. Yes, of course we agree on that. > thats what the planet ccrma packaging does as described. > fwiw, if you start cm and it doesnt have write permission for a fasl it > thinks it should update it will simply load the source file. > I think most lisps now compile everything anyway. Hmmm, I don't understand what you are trying to say in this last part. -- Fernando > >> there are no dependencies. since the last release of cm you can build > >> all the systems separately then load what you want at run time. for > >> example, depending on what im doing these days i start cm and then > >> load > >> in either clm2 or clm3. if midishare is properly installed it is > >> automatically loaded. > >> loading these systems at runtime is fast, flexible and lets you stay > >> current -- saving images doesnt make much sense anymore unless your > >> goal is to keep a snapshot "stable" (whatever that means with software > >> like this!) all three -- clm, cmn and cm -- check at runtime to see > >> if > >> their fasls are out of data, and if so, they get compiled so > >> installation and running is identical. > > > > That is true for a user that installs in his/her/its home directory (or > > somewhere else where he has write access) and has complete control of > > the software. From rm at fabula.de Wed Mar 2 12:46:06 2005 From: rm at fabula.de (rm at fabula.de) Date: Wed, 2 Mar 2005 21:46:06 +0100 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <1109790092.8642.122.camel@cmn37.stanford.edu> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <1109790092.8642.122.camel@cmn37.stanford.edu> Message-ID: <20050302204606.GC3361@seid-online.de> On Wed, Mar 02, 2005 at 11:01:32AM -0800, Fernando Lopez-Lezcano wrote: > > > That is true for a user that installs in his/her/its home directory (or > somewhere else where he has write access) and has complete control of > the software. > > It is not possible to do that on a packaged version of cm/clm/cmn (at > least the way I package it), the user of the software is typically not > the installer (root) and will not have write access to the packaged > binaries. > > Planet CCRMA has had Common Lisp based packages for cm/clm/cmn since > 2001. The packaging approach I have used lately is to load the prebuilt > systems at runtime on top of a clean lisp image (this is for cm 2.4.x, > clm2/clm3 and cmn). Maybe this could be used as "inspiration" for other > packagers. The current package structure is like this (this is after > several iterations over the years on how to package the stuff): Hmm, the way ASDF is set up on Debian each user has her own spool area for compiled fasls. So the source is installed in a central palce (/usr/share/common-lisp/sources/...) but the compiled fasls go into userspecific cache directories: /var/cache/common-lisp-controller/$USER/$IMPLEMENTATION/$PACKAGE Once there used to be a fasl-cache for the whole system (and the common lisp controller was required to keep that cache up to date but it turned out that that approach was more of a security headache then a performance improvement). A "hypothetical" cm.deb would put all source files (including the ASDF package description) into /usr/share/common-lisp/sources/cm/ and then create a link from the asdf file into //usr/share/common-lisp/systems. After that a simple (asdf:oos 'asdf:load-op :cm) would load Common Music (allways with the most up-to-date fasls - even after an update of the Lisp implementation). > clm -> source code only, common to all lisps > clm-cmucl -> requires "clm" and "cmucl", packages all cmucl binaries > clm-sbcl -> requires "clm" and "sbcl", packages all sbcl binaries > clm-xxx for other supported versions of lisp Distributing binary lisp files is a nightmare - at least for the Open Source Lisps i know .... Cheers RalfD From nando at ccrma.Stanford.EDU Wed Mar 2 14:05:41 2005 From: nando at ccrma.Stanford.EDU (Fernando Lopez-Lezcano) Date: 02 Mar 2005 14:05:41 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <20050302204606.GC3361@seid-online.de> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <1109790092.8642.122.camel@cmn37.stanford.edu> <20050302204606.GC3361@seid-online.de> Message-ID: <1109801141.8641.562.camel@cmn37.stanford.edu> On Wed, 2005-03-02 at 12:46, rm at fabula.de wrote: > On Wed, Mar 02, 2005 at 11:01:32AM -0800, Fernando Lopez-Lezcano wrote: > > > > > > That is true for a user that installs in his/her/its home directory (or > > somewhere else where he has write access) and has complete control of > > the software. > > > > It is not possible to do that on a packaged version of cm/clm/cmn (at > > least the way I package it), the user of the software is typically not > > the installer (root) and will not have write access to the packaged > > binaries. > > > > Planet CCRMA has had Common Lisp based packages for cm/clm/cmn since > > 2001. The packaging approach I have used lately is to load the prebuilt > > systems at runtime on top of a clean lisp image (this is for cm 2.4.x, > > clm2/clm3 and cmn). Maybe this could be used as "inspiration" for other > > packagers. The current package structure is like this (this is after > > several iterations over the years on how to package the stuff): > > Hmm, the way ASDF is set up on Debian each user has her own spool area > for compiled fasls. So the source is installed in a central palce > (/usr/share/common-lisp/sources/...) but the compiled fasls go into > userspecific cache directories: > > /var/cache/common-lisp-controller/$USER/$IMPLEMENTATION/$PACKAGE > > Once there used to be a fasl-cache for the whole system (and the > common lisp controller was required to keep that cache up to date but > it turned out that that approach was more of a security headache then > a performance improvement). > > A "hypothetical" cm.deb would put all source files (including the > ASDF package description) into /usr/share/common-lisp/sources/cm/ > and then create a link from the asdf file into //usr/share/common-lisp/systems. > After that a simple (asdf:oos 'asdf:load-op :cm) would load Common Music > (allways with the most up-to-date fasls - even after an update of the > Lisp implementation). > > > clm -> source code only, common to all lisps > > clm-cmucl -> requires "clm" and "cmucl", packages all cmucl binaries > > clm-sbcl -> requires "clm" and "sbcl", packages all sbcl binaries > > clm-xxx for other supported versions of lisp > > Distributing binary lisp files is a nightmare - at least for the > Open Source Lisps i know .... I see, a completely different way of doing things, different from most other packages (which include binaries). This leads to replicated fasls on all home user directories, but of course, whether it is a waste or not depends on available space, how many users and so on and so forth. I have had no problem (so far) while distributing things this way, but the packages are dependency locked to a particular version of the base lisp, and that may not be possible in your case. I did have problems a while back while trying to distribute images with everything built in. So I guess what I posted is not very useful :-[ -- Fernando From znmeb at cesmail.net Wed Mar 2 19:26:24 2005 From: znmeb at cesmail.net (M. Edward (Ed) Borasky) Date: Wed, 02 Mar 2005 19:26:24 -0800 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <1109790092.8642.122.camel@cmn37.stanford.edu> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <1109790092.8642.122.camel@cmn37.stanford.edu> Message-ID: <422683E0.1090606@cesmail.net> Fernando Lopez-Lezcano wrote: > >So, installing a working clm for a particular lisp in Planet CCRMA is >just "apt-get install clm-cmucl". I presume this could be converted into >an "emerge clm-cmucl" command :-) The binary packages include a simple >subsystem lisp stub that loads what's needed, and a one line bash script >installed in /usr/bin that starts that particular flavor, so just typing >/usr/bin/clm-cmucl starts the cmucl version of lisp and loads all of >clm. Same mechanism for cmn. > > Gentoo is, for the most part, built from source. The "packages", called "ebuilds", are scripts which unpack, configure, make and install for "typical" packages. In the case of a source like CM or CLM, which will run in multiple Lisp environments, Gentoo would define a "USE flag". So, to build with Guile, CMUCL, Clisp and SBCL, one would write USE="guile cmucl clisp sbcl" emerge cm I'm not familiar yet with the internals of Gentoo's Common Lisp Controller, but it was derived from Debian's and takes care of recompiles when one of the underlying Lisp environments changes. >Cm is sligthly different as it contains hooks to signal loading the >other packages (this is still 2.4.x, the latest official release): > >cm -> source code only > > This is all Gentoo has at the moment ... when you install, it unpacks the source and when you run, it calls Guile and runs the Scheme version in it. That's getting fixed at my instigation. :) >[snip] > >Anyway, I'm sure there are better, more clean and lispy ways of doing >all this. Still, probably the packaging structure and dependencies are >fine. > > Ah yes ... if you're constrained to binary RPMs, a lot of hacking is required. The standard "bin/cm.sh -l " works just fine in a normal user account, but it would need to be modified for multi-user systems, as I believe someone has pointed out. Rick, how difficult would it be to have a read-only "cm.sh" in /usr/bin, which compiled code into a *user's* binary, say, "~znmeb/bin"? From taube at uiuc.edu Thu Mar 3 07:13:22 2005 From: taube at uiuc.edu (Rick Taube) Date: Thu, 3 Mar 2005 09:13:22 -0600 Subject: [CM] question on audio distributions, CCRMA or Agnula, others? In-Reply-To: <422683E0.1090606@cesmail.net> References: <4223BFA4.8080605@gmail.com> <4223FFDE.1030403@cesmail.net> <20050301104138.GE13343@fliwatut.scifi> <42248B25.90403@cesmail.net> <20050301154158.GB30603@seid-online.de> <42253F42.3050603@cesmail.net> <5410a917de5166ea4fd42c1e6661926c@uiuc.edu> <1109790092.8642.122.camel@cmn37.stanford.edu> <422683E0.1090606@cesmail.net> Message-ID: > .Rick, how difficult would it be to have a read-only "cm.sh" in > /usr/bin, which compiled code into a *user's* binary, say, > "~znmeb/bin"? #!/bin/sh lispcmd --eval (progn (load "/path/to/cm/src/make.lisp") (make-cm :bin-directory "~/whatever") (cm)) but i dont see the sense of everyone having their own fasl tree since the sources are the identical. in fact i dont really see the utility of storing cm's fasls outside of its tree at all but thats probably why i would make a bad sys admin. but running lisp programs isnt like running c programs where you install a single exe file under /bin and then remove .o files. to install cm i would unpack the tarball and then call cm/bin/cm.sh for every lisp command I had on my system. then isntall a symlink 'ln -s /usr/bin/cm /path/to/cm/bin/cm.sh' so users can simpy type 'cm' just allow cm.sh to save its fasls under its own bin/ directory -- it will automatically maintain differnt fasls subdirectories for each lisp you have on the system. if you do it this way then people can start up in any lisp they want to: cm -l clisp cm -l sbcl -e emacs or whatever If you find it necessary to save the .fasls outside of the tree, then a script something like the one above could do it. From rhomboid at u.washington.edu Fri Mar 4 11:14:29 2005 From: rhomboid at u.washington.edu (Don Craig) Date: Fri, 4 Mar 2005 11:14:29 -0800 Subject: [CM] povray and lisp Message-ID: Hi, all- I gather that there has been chat about extensions for video work. Attached is some code for doing "scores" for POVRay. Strictly speaking, this is not CM; it will work in any common lisp (I'm pretty sure). But you can certainly use it in a CM/CLM enviroment. I'm confidant there are no name/package conflicts. If somebody wants to rework the code to build it into CM, fell free! As part of the attachment there is a stupid povray example that shows the necessary steps that have to be done in povray for this to work. if somebody comes up with a better way, I'd love to see it. any questions, just email me, Don -------------- next part -------------- A non-text attachment was scrubbed... Name: povray_ex.tar Type: application/x-tar Size: 10240 bytes Desc: not available URL: From marco at trevisani.net Fri Mar 4 12:04:37 2005 From: marco at trevisani.net (marco trevisani) Date: Fri, 4 Mar 2005 16:04:37 -0400 Subject: [CM] povray and lisp In-Reply-To: References: Message-ID: <200503041604.38269.marco@trevisani.net> Thank you for sharing the code. BTW, is there asomething wrong with my mailer, because i could not open the tar file? thank you, marco Alle 15:14, venerd? 04 marzo 2005, Don Craig ha scritto: | Hi, all- | | I gather that there has been chat about extensions for video work. | Attached is some code for doing "scores" for POVRay. Strictly speaking, | this is not CM; it will work in any common lisp (I'm pretty sure). But | you can certainly use it in a CM/CLM enviroment. I'm confidant there | are no name/package conflicts. | | If somebody wants to rework the code to build it into CM, fell free! | | As part of the attachment there is a stupid povray example that shows | the necessary steps that have to be done in povray for this to work. if | somebody comes up with a better way, I'd love to see it. | | any questions, just email me, | Don -- ************************************************************************ marco trevisani http://marco.trevisani.net marco at trevisani.net Neither MS-Word nor MS-PowerPoint attachments please (use rtf) Please DO NOT store my e-mail in your OUTLOOK express addressbook "Malditas sean las guerras y los canallas que las hacen" J.Anguita ************************************************************************ From carl.boingie at verizon.net Fri Mar 4 17:40:58 2005 From: carl.boingie at verizon.net (Carl Edwards) Date: Fri, 04 Mar 2005 20:40:58 -0500 Subject: [CM] povray and lisp In-Reply-To: Message-ID: Thank you very much, Don! It looks very interesting. I'm off to the POV site now in search of further documentation! Thanks again, Carl Edwards > > Hi, all- > > I gather that there has been chat about extensions for video work. > Attached is some code for doing "scores" for POVRay. Strictly speaking, > this is not CM; it will work in any common lisp (I'm pretty sure). But > you can certainly use it in a CM/CLM enviroment. I'm confidant there > are no name/package conflicts. > > If somebody wants to rework the code to build it into CM, fell free! > > As part of the attachment there is a stupid povray example that shows > the necessary steps that have to be done in povray for this to work. if > somebody comes up with a better way, I'd love to see it. > > any questions, just email me, > Don > > From bil at ccrma.Stanford.EDU Mon Mar 7 04:18:07 2005 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Mon, 07 Mar 2005 04:18:07 -0800 Subject: [CM] acl 4? Message-ID: <422C467F.90207@ccrma> Is anyone still using ACL 4? From taube at uiuc.edu Tue Mar 8 14:20:07 2005 From: taube at uiuc.edu (Rick Taube) Date: Tue, 8 Mar 2005 16:20:07 -0600 Subject: [CM] copier -> length of periods In-Reply-To: References: Message-ID: > the pattern-period contains 6 elements, i.e.: > (next cp t) > => (b a c b a c) > but what i want, is that the repetition comes in the NEXT period, rev 1.4 of patterns.scm in cvs head now allows you to do this. There was no documentation on copier so i added that as well: http://pinhead.music.uiuc.edu/~hkt/cm/doc/dict/copier-cls.html From taube at uiuc.edu Tue Mar 8 14:36:29 2005 From: taube at uiuc.edu (Rick Taube) Date: Tue, 8 Mar 2005 16:36:29 -0600 Subject: [CM] fm and ring modulation Message-ID: <5ed46eafe0d1644c41dad9852e6a0c5e@uiuc.edu> I forgot to say I also documetned two functions fm-spectrum and rm-spectrum (fm and ring modulation). fm-spectrum has been in the sources but undocumented, rm-spectrum is new. the documentation is here: http://pinhead.music.uiuc.edu/~hkt/cm/doc/dict/fm-spectrum-fn.html http://pinhead.music.uiuc.edu/~hkt/cm/doc/dict/rm-spectrum-fn.html From rbastian at club-internet.fr Fri Mar 11 04:10:12 2005 From: rbastian at club-internet.fr (=?iso-8859-15?q?Ren=E9=20Bastian?=) Date: Fri, 11 Mar 2005 13:10:12 +0100 Subject: [CM] cmn, umlaute, diacritics, accents Message-ID: <05031113101200.00757@rbastian> Hi, Please, is there a way to get diacritics signs in a text with CMN ? (in TeX code, vowels like \^a, \"a, \'a etc) In PostScript it is possible to code these vowels with diacritics into free places of a font. But CMN must "understand" it. Thanks for your answers. -- Ren\'e Bastian From bil at ccrma.Stanford.EDU Mon Mar 14 04:02:54 2005 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Mon, 14 Mar 2005 04:02:54 -0800 Subject: [CM] cmn, umlaute, diacritics, accents In-Reply-To: <05031113101200.00757@rbastian> References: <05031113101200.00757@rbastian> Message-ID: <42357D6E.6060103@ccrma> > Please, is there a way to get diacritics signs in a text with CMN ? If you know where they are in the font, you can embed the font location in the text: (cmn (prolog #'(lambda (score) (make-ISO-encoded-version score "Times-Roman" "ISO-Times-Roman"))) staff treble (c4 q (text "s\\374\\337" (dy 1.5) (dx -.25) (font-name "ISO-Times-Roman") (font-scaler .5) (gray-scale .25)))) which is "s" "u-umlaut" "double-s". My grandfather spelled my last name with a-umlaut -- I should figure out how to do that in a sig line. From k.s.matheussen at notam02.no Tue Mar 15 15:39:31 2005 From: k.s.matheussen at notam02.no (Kjetil Svalastog Matheussen) Date: Wed, 16 Mar 2005 00:39:31 +0100 (CET) Subject: [CM] Running CLM in realtime. Message-ID: This is a small announcement. For the last three/four months I have, with support from Notam (http://www.notam02.no), been working on the files rt-compiler.scm, rt-engine.scm, eval-c.scm and oo.scm in the SND distribution. rt-engine.scm is a realtime engine, a little bit like the supercollider3 program "scsynth". rt-compiler.scm is a compiler that compiles scheme-look-alike blocks of code into machine-code that can be sent to rt-engine. Almost all of CLM is supported. I'm kind-of announcing this now, since its actually working very well now. The performance is awesome, and it seems to be stable, in the sence that it doesn't crash, I think. However, I haven't stabelized the API yet, so things will change, and using the system for making large interactive installation or something might be a bit risky in the current state. However (again), I want people to check this out, if it seems interesting, and give me comments about the API or other things that look horrible. Check out the top of rt-compiler.scm for documentation about the system, and the top of rt-engine.scm for a couple of examples. I have made a realtime-version of Bil's bird.scm called rt-bird.scm which I have put here: (including my latest versions of rt-compiler.scm, rt-engine.scm and eval-c.scm) http://www.notam02.no/arkiv/src/snd/ To run it do the following: 1. Start Jack. 2. Start SND. 3. Cut and paste into SND: (load-from-path "rt-compiler.scm") (load "rt-bird.scm") (-> rt-engine start) (make-birds) You can also add additional birds by calling (make-birds) again and again and again. -- From k.s.matheussen at notam02.no Wed Mar 16 05:09:09 2005 From: k.s.matheussen at notam02.no (Kjetil Svalastog Matheussen) Date: Wed, 16 Mar 2005 14:09:09 +0100 (CET) Subject: [CM] Re: Running CLM in realtime. In-Reply-To: References: Message-ID: On Wed, 16 Mar 2005, Kjetil Svalastog Matheussen wrote: > > This is a small announcement. > Oops, forgot to check my files before posting the announcement. There was a couple of "typos" in yesterdays rt-compiler.scm. I have uploaded a working version to http://www.notam02.no/arkiv/src/snd/ There are also some additional requirements to make this work, which I didn't specify yesterday. Those are: -A very recent version of SND. Probably not more than about 1.5 weeks old. -rt-compiler.scm, rt-engine.scm and eval-c.scm from http://www.notam02.no/arkiv/src/snd -jack and jack-devel -libsndfile and libsndfile-devel (Sorry, I didn't figure out out how to use libsnd.) To make the two gui-examples in the top of rt-engine work you also need: -SND compiled with --use-gtk -gtk2 and gtk2-devel -- From testcase at asu.edu Mon Mar 14 15:45:03 2005 From: testcase at asu.edu (todd ingalls) Date: Mon, 14 Mar 2005 16:45:03 -0700 Subject: [CM] pval in markov In-Reply-To: <422C467F.90207@ccrma> References: <422C467F.90207@ccrma> Message-ID: <740060ce15e0b7e55f1d6f60a11a32bf@asu.edu> Hi. Was wondering if perhaps I am misunderstanding something about pval. The following works - (setf x (new random :of `((50 weight ,(pval (between .1 .2))) (51 weight ,(pval (between .8 1.0)))))) (next x 20) => (51 51 51 51 51 50 50 50 51 51 51 51 51 51 51 51 50 51 51 51) but the following does not in a markov pattern (setf x (new markov :of `((50 -> (51 ,(pval (between .2 1.0))) (50 .1)) (51 -> (50 ,(pval (between .2 1.0))) (51 .1))))) => value # is not of the expected type NUMBER. [Condition of type TYPE-ERROR] Now, the following does work: (setf x (new markov :of `((50 -> (51 ,(funcall (pval-thunk (pval (between .2 1.0))))) (50 .1)) (51 -> (50 ,(funcall (pval-thunk (pval (between .2 1.0))))) (51 .1))))) (next x 20) => (50 51 50 51 50 51 50 51 50 51 51 50 51 51 51 50 51 50 51 50) is there a less verbose way to use pval in a markov pattern? From bil at ccrma.Stanford.EDU Wed Mar 16 07:05:27 2005 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Wed, 16 Mar 2005 07:05:27 -0800 Subject: [CM] Re: Running CLM in realtime. In-Reply-To: References: Message-ID: <42384B37.7040904@ccrma> I finally updated the snd tarball at ccrma-ftp and the cvs files -- sorry about the delay. The newest guile has removed the ability to turn off the garbage collector (I think -- if it's still there, it has changed without any comment). I hope this won't foul things up. From k.s.matheussen at notam02.no Wed Mar 16 07:42:44 2005 From: k.s.matheussen at notam02.no (Kjetil Svalastog Matheussen) Date: Wed, 16 Mar 2005 16:42:44 +0100 (CET) Subject: [CM] Re: Running CLM in realtime. In-Reply-To: <42384B37.7040904@ccrma> References: <42384B37.7040904@ccrma> Message-ID: On Wed, 16 Mar 2005, Bill Schottstaedt wrote: > I finally updated the snd tarball at ccrma-ftp and the > cvs files -- sorry about the delay. > > The newest guile has removed the ability to turn off > the garbage collector (I think -- if it's still there, > it has changed without any comment). I hope this won't > foul things up. > I haven't used that trick, so it wont affect my stuff. But I knwe about it, so I could have been. But now that I know that it has been turned off (hopefully not forever though...), I won't use that trick in the future either, probably. Thanks! -- From taube at uiuc.edu Wed Mar 16 07:47:12 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 16 Mar 2005 09:47:12 -0600 Subject: [CM] pval in markov In-Reply-To: <740060ce15e0b7e55f1d6f60a11a32bf@asu.edu> References: <422C467F.90207@ccrma> <740060ce15e0b7e55f1d6f60a11a32bf@asu.edu> Message-ID: <266bf0c0f6cb53e0a0b20243980ae873@uiuc.edu> > Was wondering if perhaps I am misunderstanding something about pval. assuming that you are trying to get dynamic weights, ie weights that change as the pattern evolves, then no you are not misunderstanding anything -- this is a long standing misfeature of the markov pattern. actually im going over all the pattern stuff (and rewriting/updating the pattern documentation) right now, ill see if i can do something about this while im at it. > Now, the following does work: > > (setf x (new markov :of `((50 -> (51 ,(funcall (pval-thunk (pval > (between .2 1.0))))) (50 .1)) > (51 -> (50 ,(funcall (pval-thunk (pval (between .2 1.0))))) (51 > .1))))) this wont do what you want -- the value of your funcall is a constant, not a pval. if you want a workaround for now, since you are doing 1st order markov you can use the graph pattern instead: (new graph :of `((50 :to ,(new random :of `((51 :weight ,(pval (between .2 1.0))) (50 :weight .1)))) (51 :to ,(new random :of `((50 :weight ,(pval (between .2 1.0))) (51 :weight .1)))))) From bil at ccrma.Stanford.EDU Fri Mar 18 03:18:42 2005 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Fri, 18 Mar 2005 03:18:42 -0800 Subject: [CM] snd 7.11? Message-ID: <423AB912.4050501@ccrma> Snd 7.11 Mike Scholz greatly expanded and improved the Ruby stuff in Snd (not to mention many other general improvements): snd_test.rb replaced by snd-test.rb, new files mix.rb, dsp.rb, pvoc.rb -- an amazing addition to Snd! Kjetil Matheussen implemented real-time support: the new files are oo.scm, rt-compiler.scm, and rt-engine.scm -- another amazing addition! delay and move-locsig bugfixes thanks to Fernando. changed libxm to libxg in gtk case, also xm-version to xg-version added --with-static-xg configure option (same as --with-static-xm) added the -export-dynamic loader switch if using Gnu's ld and dlfcn band limited sawtooth in dsp.scm (Stilson/Smith/Kritov) bes-j0|1|n, bes-y0|1|n, bes-i0, erf|c, lgamma (etc from libm) mus-interpolate env-channel-with-base Ruby side of edit-list->function zoom-focus-style can be a function polyshape generator (polynomial + oscil) mus-chebyshev-first|second-kind (as "kind" arg to partials->polynomial) partials->waveshape no longer normalizes the partials (to parallel partials->polynomial) gc-off and gc-on are no-ops now in Guile -- the underlying support was removed in the CVS Guile in CMN: Anders Vinjar fixed a bug in display-crescendo removed obsolete make-cmn.cl in CLM: Rick fixed a bug in play run* cleaned-up finally ffi cleaned-up (removed various obsolete linkages) removed ACL 4.n support sbcl can now handle multi-instrument files and no longer uses the *.sbcl kludge with much help from: Fernando Lopez-Lezcano, Mike Scholz, Kjetil Matheussen, Rick Taube, Anders Vinjar, Kyle Markley, Steve Bankowitz. checked: Intel C 8.1, gtk 2.6.3|4, Sun Workshop C (via S Bankowitz) (I'm having troubles moving files around, so it's not impossible that the rpm files are messed up -- please let me know of any problems!) From taube at uiuc.edu Fri Mar 18 07:26:48 2005 From: taube at uiuc.edu (Rick Taube) Date: Fri, 18 Mar 2005 09:26:48 -0600 Subject: [CM] pval in markov In-Reply-To: <740060ce15e0b7e55f1d6f60a11a32bf@asu.edu> References: <422C467F.90207@ccrma> <740060ce15e0b7e55f1d6f60a11a32bf@asu.edu> Message-ID: i think i have dynamic weights working with markov patterns now. its in rev. 1.6 of patterns.scm in CVS head. for instructions on installing by cvs see: http://pinhead.music.uiuc.edu/~hkt/cm/doc/install.html#restore_cvs by the way, this sort of dynamic markov is pretty much what i did to create a piece called amazing grace some years ago if you want to hear with it sounds like here is a link to an mp3 of the original performance (karlsruhe 1995 i think). the weights of 3rd order markov were slowly twiddled over time to cause the music to "congeal" into melodic and rhythmic tropes in the folksong http://pinhead.music.uiuc.edu/~hkt/music/amazing-grace/Amazing-Grace- KA.mp3 > the following does not in a markov pattern > > (setf x (new markov :of `((50 -> (51 ,(pval (between .2 1.0))) (50 > .1)) > (51 -> (50 ,(pval (between .2 1.0))) (51 .1))))) From taube at uiuc.edu Fri Mar 18 07:27:13 2005 From: taube at uiuc.edu (Rick Taube) Date: Fri, 18 Mar 2005 09:27:13 -0600 Subject: [CM] pattern updates and fixes Message-ID: Ive completely rewritten cm's pattern documentation and added new (hopefully more useful) examples of usage in the dictionary. the dictionary also contains a new "overview" page that will (hopefully) help newcomers understand how to use them. the new tutorial page is here: http://pinhead.music.uiuc.edu/~hkt/cm/doc/dict/patterns-topic.html and it has links to all the new/updated pattern docs. please let me know of any errors or bugs! ive also fixed a few bugs/misfeatues in patterns.scm and in output to midi files in the last few days (thank you anders!) see the changelog for an explanation From dlphillips at woh.rr.com Mon Mar 21 11:09:24 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Mon, 21 Mar 2005 14:09:24 -0500 Subject: [CM] a cmio question In-Reply-To: References: Message-ID: <423F1BE4.50603@woh.rr.com> Hi Rick: I've been using the GUI for a while now, it's very cool, but I have one frustration I'd like to resolve. Apparently the Header field for the Csound tab is designed to accept only a single entry. Could it be designed to acccept a list like this: (list "f1 0 8192 10 1" "f2 0 8192 10 1 .9 .8 .7 .6 .5 .4 .3 .2 .1" "f3 0 8192 10 .1 .2 .3 .4 .5 .6 .7 .8 .9 1" "f4 0 8192 10 0 1 0 0 .8 0 0 0 .5 0 0 0 0 .1" "f5 0 8192 10 1 0 .9 0 0 .7 0 0 0 .4 0 0 0 0 .01")) Also, there are other score options I'd like to auto-include, such as the t tempo statement. Normally I place them right after the function tables, but again there doesn't seem to be a way to do this with the GUI. I can of course add them after score production, but that breaks the cycle for realtime playback. Any suggestions ? Best, dp From taube at uiuc.edu Mon Mar 21 12:04:03 2005 From: taube at uiuc.edu (Rick Taube) Date: Mon, 21 Mar 2005 14:04:03 -0600 Subject: [CM] a cmio question In-Reply-To: <423F1BE4.50603@woh.rr.com> References: <423F1BE4.50603@woh.rr.com> Message-ID: <0be6dc6258c813c3a8a51c4a1daeed2b@uiuc.edu> Yes. all you have to do is define a lisp variable to hold your header string or list and then use the #.var feature in the header buffer: (setq myheader "big long hairy string") (cmio) and then put #.myheader in the "Header:" field, ie on the csound page do: Header: [ #.myheader ] i think you can specify a list off strings and the .sco file should handle that as well. (setf myheader (list "fi..." "f2..." )) (cmio) #.myheader any field with a WHITE background should let you do the #.var trick. so do you want me to add a tempo field? i can do that too, on the same line i guess. > Hi Rick: > > I've been using the GUI for a while now, it's very cool, but I have > one frustration I'd like to resolve. Apparently the Header field for > the Csound tab is designed to accept only a single entry. Could it be > designed to acccept a list like this: > > (list "f1 0 8192 10 1" "f2 0 8192 10 1 .9 .8 .7 .6 .5 .4 .3 .2 .1" > "f3 0 8192 10 .1 .2 .3 .4 .5 .6 .7 .8 .9 1" "f4 0 8192 10 0 1 0 0 .8 0 > 0 0 .5 0 0 0 0 .1" "f5 0 8192 10 1 0 .9 0 0 .7 0 0 0 .4 0 0 0 0 .01")) > > Also, there are other score options I'd like to auto-include, such as > the t tempo statement. Normally I place them right after the function > tables, but again there doesn't seem to be a way to do this with the > GUI. I can of course add them after score production, but that breaks > the cycle for realtime playback. Any suggestions ? > > Best, > > dp > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Mon Mar 21 12:23:13 2005 From: taube at uiuc.edu (Rick Taube) Date: Mon, 21 Mar 2005 14:23:13 -0600 Subject: [CM] a cmio question In-Reply-To: <423F1BE4.50603@woh.rr.com> References: <423F1BE4.50603@woh.rr.com> Message-ID: <10e040a9476e12c2d157d3416a497d75@uiuc.edu> > there are other score options I'd like to auto-include, such as the t > tempo statement. Normally I place them right after the function > tables, but again there doesn't seem to be a way to do this with the > GUI. I can of ooops i didnt see all of this: if there are fields other then just Tempo send me the complete list, it looks like there are some spare pixels on that page to fit more stuff... also, you can initialize window's pages instead of always typing in the stuff: (cmio :csound '(:header "#.myheader" :score-file "foo.sco")) and so on. see: http://pinhead.music.uiuc.edu/~hkt/cm/doc/dict/cmio-fn.html#csound From dlphillips at woh.rr.com Mon Mar 21 13:20:09 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Mon, 21 Mar 2005 16:20:09 -0500 Subject: [CM] a cmio question In-Reply-To: <0be6dc6258c813c3a8a51c4a1daeed2b@uiuc.edu> References: <423F1BE4.50603@woh.rr.com> <0be6dc6258c813c3a8a51c4a1daeed2b@uiuc.edu> Message-ID: <423F3A89.4080908@woh.rr.com> Rick Taube wrote: > Yes. all you have to do is define a lisp variable to hold your header > string or list and then > use the #.var feature in the header buffer: > > (setq myheader "big long hairy string") > (cmio) > and then put #.myheader in the "Header:" field, ie on the csound page > do: > > Header: [ #.myheader ] > > i think you can specify a list off strings and the .sco file should > handle that as well. > > (setf myheader (list "fi..." "f2..." )) > (cmio) > #.myheader > > any field with a WHITE background should let you do the #.var trick. Too cool. Works perfectly, and I can revise it on the fly. Neat, thanks for the clue. :) > so do you want me to add a tempo field? i can do that too, on the same > line i guess. I started thinking about this and decided that I want to think about it a little more. I'm not sure adding anything is necessary, now that I know the #.var feature, and I'm not sure how you could incorporate the Csound score notion of sections, section repeats, and section tempo control into the cmio GUI without clutter. Gotta think about it... Thanks for the help ! Best, dp From taube at uiuc.edu Mon Mar 21 14:15:45 2005 From: taube at uiuc.edu (Rick Taube) Date: Mon, 21 Mar 2005 16:15:45 -0600 Subject: [CM] a cmio question In-Reply-To: <423F3A89.4080908@woh.rr.com> References: <423F1BE4.50603@woh.rr.com> <0be6dc6258c813c3a8a51c4a1daeed2b@uiuc.edu> <423F3A89.4080908@woh.rr.com> Message-ID: > I'm not sure how you could incorporate the Csound score notion of > sections, section repeats, and section tempo control into the cmio GUI > without clutter. Gotta think about it... its been a long time since i looked at the csound scorefile stuff, but i think for things like sections you might do better to define an 's' object (similar to the existing 'i' and 'f' objects...). that way you could simply output them into the scorefile from your process just like i and f statements. --rick From dlphillips at woh.rr.com Mon Mar 21 17:51:43 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Mon, 21 Mar 2005 20:51:43 -0500 Subject: [CM] a cmio question In-Reply-To: References: <423F1BE4.50603@woh.rr.com> <0be6dc6258c813c3a8a51c4a1daeed2b@uiuc.edu> <423F3A89.4080908@woh.rr.com> Message-ID: <423F7A2F.1070101@woh.rr.com> Rick Taube wrote: >> I'm not sure how you could incorporate the Csound score notion of >> sections, section repeats, and section tempo control into the cmio >> GUI without clutter. Gotta think about it... > > > its been a long time since i looked at the csound scorefile stuff, but > i think for things like sections you might do better to define an 's' > object (similar to the existing 'i' and 'f' objects...). that way you > could simply output them into the scorefile from your process just > like i and f statements. Thanks, Rick, I'll try that, it sounds like the right solution. I'll let you know how it works. Best, dp From taube at uiuc.edu Wed Mar 23 14:15:16 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 23 Mar 2005 16:15:16 -0600 Subject: [CM] cm 2.6.0 download available Message-ID: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> Common Music 2.6.0 is now available for download from Sourceforge: http://sourceforge.net/projects/commonmusic/ I won't go into any details since this has been an ongoing saga, see doc/changelog.text for the complete listing of new features. Many many thanks to Anders Vinjar and Dave Phillips for testing. Tested in: OS LISP VERSION SYSTEMS TESTED ---------------------------------------------------- x86 sbcl 0.8.17 midi,clm3,cmn,gtk2 x86 cmucl 19a midi,clm3,cmn,gtk2 osx guile 1.6.7 midi osx openmcl cvs midi,clm3,cmn,midishare,gtk2 osx clisp 2.32 midi osx sbcl 0.8.17 midi cygwin clisp 2.33.1 midi winxp clisp 2.33.1 midi From taube at uiuc.edu Wed Mar 23 14:20:25 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 23 Mar 2005 16:20:25 -0600 Subject: [CM] Drag and drop CM.app for OSX available Message-ID: I've bundled CLM-3, CMN, CM 2.6.0 together as a drag-and-drop OS X application. The bundle includes all GTK libs so if you have X11 installed you should be able to open a graphics window without installing anything else. The dmg file is also at sourceforge: http://prdownloads.sourceforge.net/commonmusic/cm_2.6.0-app-osx.dmg.gz? download see the enclosed readme for more information. From taube at uiuc.edu Wed Mar 23 14:45:16 2005 From: taube at uiuc.edu (Rick Taube) Date: Wed, 23 Mar 2005 16:45:16 -0600 Subject: [CM] ASDF installation for CM now working Message-ID: <61e56a251288f342f5bbec0812ee0dff@uiuc.edu> Its now possible to download, install, compile and load CM using ASDF and ASDF-INSTALL. See: http://www.cliki.net/asdf http://www.cliki.net/asdf-install Thank you Greg Pfeil! Its pretty cool. This little snippet downloaded and built cm on my wireless network at home (openmcl) ------------------------------------------------------------------------ (require 'asdf) (push "/Lisp/ccl/tools/asdf-install/" asdf:*central-registry*) (asdf:operate 'asdf:load-op 'asdf-install) (setq asdf-install:*verify-gpg-signatures* nil) (asdf-install:install 'cm) ------------------------------------------------------------------------ Here is a trace if you don't believe me: ? Install where? 0) System-wide install: System in /usr/local/asdf-install/site-systems/ Files in /usr/local/asdf-install/site/ 1) Personal installation: System in /Users/hkt/.asdf-install-dir/systems/ Files in /Users/hkt/.asdf-install-dir/site/ 2) Abort installation. --> 1 ;;; ASDF-INSTALL: Downloading 970724 bytes from http://commonmusic.sourceforge.net/cm_2.6.0.tar.gz to CM.asdf-install-tmp ... ;;; ASDF-INSTALL: Installing CM.asdf-install-tmp in /Users/hkt/.asdf-install-dir/site/, /Users/hkt/.asdf-install-dir/systems/ cm-2.6.0/ cm-2.6.0/bin/ cm-2.6.0/bin/.cvskeep cm-2.6.0/bin/cm.sh cm-2.6.0/cm.asd cm-2.6.0/doc/ cm-2.6.0/doc/changelog.text cm-2.6.0/doc/cm.html cm-2.6.0/doc/css/ cm-2.6.0/doc/css/cm.css cm-2.6.0/doc/dict/ cm-2.6.0/doc/dict/accumulation-cls.html cm-2.6.0/doc/dict/amplitude-fn.html cm-2.6.0/doc/dict/append-object-fn.html cm-2.6.0/doc/dict/axis-cls.html cm-2.6.0/doc/dict/axis-fn.html cm-2.6.0/doc/dict/beat-var.html cm-2.6.0/doc/dict/between-fn.html cm-2.6.0/doc/dict/cd-fn.html cm-2.6.0/doc/dict/cents-gtscaler-fn.html cm-2.6.0/doc/dict/chord-cls.html cm-2.6.0/doc/dict/chromatic-scale-var.html cm-2.6.0/doc/dict/clm-audio-stream-cls.html cm-2.6.0/doc/dict/clm-stream-cls.html cm-2.6.0/doc/dict/cm-sh.html cm-2.6.0/doc/dict/cm-version-fn.html cm-2.6.0/doc/dict/cmio-fn.html cm-2.6.0/doc/dict/cmio-topic.html cm-2.6.0/doc/dict/cmio1.png cm-2.6.0/doc/dict/cmio10.png cm-2.6.0/doc/dict/cmio11.png cm-2.6.0/doc/dict/cmio12.png cm-2.6.0/doc/dict/cmio13.png cm-2.6.0/doc/dict/cmio14.png cm-2.6.0/doc/dict/cmio2.png cm-2.6.0/doc/dict/cmio3.png cm-2.6.0/doc/dict/cmio5.png cm-2.6.0/doc/dict/cmio6.png cm-2.6.0/doc/dict/cmio7.png cm-2.6.0/doc/dict/cmio8.png cm-2.6.0/doc/dict/cmio9.png cm-2.6.0/doc/dict/cmn-cls.html cm-2.6.0/doc/dict/cmn-stream-cls.html cm-2.6.0/doc/dict/copier-cls.html cm-2.6.0/doc/dict/copy-object-fn.html cm-2.6.0/doc/dict/cycle-cls.html cm-2.6.0/doc/dict/date-and-time-fn.html cm-2.6.0/doc/dict/decimals-fn.html cm-2.6.0/doc/dict/decode-interval-fn.html cm-2.6.0/doc/dict/defaxis-mac.html cm-2.6.0/doc/dict/defobject-mac.html cm-2.6.0/doc/dict/doeach-mac.html cm-2.6.0/doc/dict/drunk-fn.html cm-2.6.0/doc/dict/eodqmk-fn.html cm-2.6.0/doc/dict/eopqmk-fn.html cm-2.6.0/doc/dict/events-fn.html cm-2.6.0/doc/dict/expl-fn.html cm-2.6.0/doc/dict/explseg-fn.html cm-2.6.0/doc/dict/explsegs-fn.html cm-2.6.0/doc/dict/f-cls.html cm-2.6.0/doc/dict/false-var.html cm-2.6.0/doc/dict/find-object-fn.html cm-2.6.0/doc/dict/fit-fn.html cm-2.6.0/doc/dict/fm-spectrum-fn.html cm-2.6.0/doc/dict/funcall-cls.html cm-2.6.0/doc/dict/graph-cls.html cm-2.6.0/doc/dict/heap-cls.html cm-2.6.0/doc/dict/hertz-fn.html cm-2.6.0/doc/dict/histogram-fn.html cm-2.6.0/doc/dict/hshamp-mac.html cm-2.6.0/doc/dict/hshi-mac.html cm-2.6.0/doc/dict/i-cls.html cm-2.6.0/doc/dict/import-events-fn.html cm-2.6.0/doc/dict/index.html cm-2.6.0/doc/dict/input-fn.html cm-2.6.0/doc/dict/insert-object-fn.html cm-2.6.0/doc/dict/interp-fn.html cm-2.6.0/doc/dict/interpl-fn.html cm-2.6.0/doc/dict/interval-fn.html cm-2.6.0/doc/dict/invert-fn.html cm-2.6.0/doc/dict/io-mac.html cm-2.6.0/doc/dict/join-cls.html cm-2.6.0/doc/dict/keynum-fn.html cm-2.6.0/doc/dict/line-cls.html cm-2.6.0/doc/dict/list-named-objects-fn.html cm-2.6.0/doc/dict/list-subobjects-fn.html cm-2.6.0/doc/dict/log-axis-cls.html cm-2.6.0/doc/dict/lookup-fn.html cm-2.6.0/doc/dict/loudest-var.html cm-2.6.0/doc/dict/make-cm-fn.html cm-2.6.0/doc/dict/map-pattern-data-fn.html cm-2.6.0/doc/dict/map-subcontainers-fn.html cm-2.6.0/doc/dict/map-subobjects-fn.html cm-2.6.0/doc/dict/markov-analyze-fn.html cm-2.6.0/doc/dict/markov-cls.html cm-2.6.0/doc/dict/midi-channel-map-var.html cm-2.6.0/doc/dict/midi-channel-pressure-cls.html cm-2.6.0/doc/dict/midi-cls.html cm-2.6.0/doc/dict/midi-connections-var.html cm-2.6.0/doc/dict/midi-control-change-cls.html cm-2.6.0/doc/dict/midi-eot-cls.html cm-2.6.0/doc/dict/midi-file-stream-cls.html cm-2.6.0/doc/dict/midi-key-pressure-cls.html cm-2.6.0/doc/dict/midi-key-signature-cls.html cm-2.6.0/doc/dict/midi-note-off-cls.html cm-2.6.0/doc/dict/midi-note-on-cls.html cm-2.6.0/doc/dict/midi-pitch-bend-cls.html cm-2.6.0/doc/dict/midi-program-change-cls.html cm-2.6.0/doc/dict/midi-sequence-number-cls.html cm-2.6.0/doc/dict/midi-sequencer-event-cls.html cm-2.6.0/doc/dict/midi-smpte-offset-cls.html cm-2.6.0/doc/dict/midi-stream-cls.html cm-2.6.0/doc/dict/midi-system-event-cls.html cm-2.6.0/doc/dict/midi-tempo-change-cls.html cm-2.6.0/doc/dict/midi-text-event-cls.html cm-2.6.0/doc/dict/midi-time-signature-cls.html cm-2.6.0/doc/dict/midi-topic.html cm-2.6.0/doc/dict/midishare-stream-cls.html cm-2.6.0/doc/dict/mode-cls.html cm-2.6.0/doc/dict/new-mac.html cm-2.6.0/doc/dict/next-fn.html cm-2.6.0/doc/dict/note-accidental-fn.html cm-2.6.0/doc/dict/note-fn.html cm-2.6.0/doc/dict/note-name-fn.html cm-2.6.0/doc/dict/now-fn.html cm-2.6.0/doc/dict/object-gtcmn-fn.html cm-2.6.0/doc/dict/object-name-fn.html cm-2.6.0/doc/dict/object-parameters-fn.html cm-2.6.0/doc/dict/object-time-fn.html cm-2.6.0/doc/dict/octave-number-fn.html cm-2.6.0/doc/dict/odds-fn.html cm-2.6.0/doc/dict/output-fn.html cm-2.6.0/doc/dict/palindrome-cls.html cm-2.6.0/doc/dict/pattern-state-fn.html cm-2.6.0/doc/dict/pattern-value-fn.html cm-2.6.0/doc/dict/patternqmk-fn.html cm-2.6.0/doc/dict/patterns-topic.html cm-2.6.0/doc/dict/pick-fn.html cm-2.6.0/doc/dict/pickl-fn.html cm-2.6.0/doc/dict/pitch-class-fn.html cm-2.6.0/doc/dict/play-fn.html cm-2.6.0/doc/dict/player-cont-fn.html cm-2.6.0/doc/dict/player-load-midifile-fn.html cm-2.6.0/doc/dict/player-mute-fn.html cm-2.6.0/doc/dict/player-pause-fn.html cm-2.6.0/doc/dict/player-save-midifile-fn.html cm-2.6.0/doc/dict/player-set-tempo-fn.html cm-2.6.0/doc/dict/player-solo-fn.html cm-2.6.0/doc/dict/player-start-fn.html cm-2.6.0/doc/dict/player-stop-fn.html cm-2.6.0/doc/dict/player-stream-cls.html cm-2.6.0/doc/dict/player-unmute-fn.html cm-2.6.0/doc/dict/player-unsolo-fn.html cm-2.6.0/doc/dict/plotter-add-layer-fn.html cm-2.6.0/doc/dict/plotter-close-fn.html cm-2.6.0/doc/dict/plotter-data-fn.html cm-2.6.0/doc/dict/plotter-fn.html cm-2.6.0/doc/dict/plotter-front-styling-fn.html cm-2.6.0/doc/dict/plotter-property-fn.html cm-2.6.0/doc/dict/plotter-redraw-fn.html cm-2.6.0/doc/dict/plotter-scroll-fn.html cm-2.6.0/doc/dict/plotter-topic.html cm-2.6.0/doc/dict/plotter-zoom-fn.html cm-2.6.0/doc/dict/plotter1.png cm-2.6.0/doc/dict/plotter2.png cm-2.6.0/doc/dict/plotter3.png cm-2.6.0/doc/dict/plotter4.png cm-2.6.0/doc/dict/plotter5.png cm-2.6.0/doc/dict/point-cls.html cm-2.6.0/doc/dict/power-var.html cm-2.6.0/doc/dict/prime-form-fn.html cm-2.6.0/doc/dict/process-mac.html cm-2.6.0/doc/dict/pval-cls.html cm-2.6.0/doc/dict/pval-mac.html cm-2.6.0/doc/dict/pwd-fn.html cm-2.6.0/doc/dict/quantize-fn.html cm-2.6.0/doc/dict/ran-fn.html cm-2.6.0/doc/dict/random-cls.html cm-2.6.0/doc/dict/range-cls.html cm-2.6.0/doc/dict/ransegs-fn.html cm-2.6.0/doc/dict/remove-object-fn.html cm-2.6.0/doc/dict/remove-subobjects-fn.html cm-2.6.0/doc/dict/rescale-envelope-fn.html cm-2.6.0/doc/dict/rescale-fn.html cm-2.6.0/doc/dict/rewrite-cls.html cm-2.6.0/doc/dict/rewrite-generation-fn.html cm-2.6.0/doc/dict/rhythm-fn.html cm-2.6.0/doc/dict/rm-spectrum-fn.html cm-2.6.0/doc/dict/rotation-cls.html cm-2.6.0/doc/dict/save-object-fn.html cm-2.6.0/doc/dict/scale-max-fn.html cm-2.6.0/doc/dict/scale-min-fn.html cm-2.6.0/doc/dict/scale-mod-fn.html cm-2.6.0/doc/dict/scale-order-fn.html cm-2.6.0/doc/dict/scale-var.html cm-2.6.0/doc/dict/scaleeql-fn.html cm-2.6.0/doc/dict/scalegt-fn.html cm-2.6.0/doc/dict/scalegteql-fn.html cm-2.6.0/doc/dict/scalelt-fn.html cm-2.6.0/doc/dict/scalelteql-fn.html cm-2.6.0/doc/dict/scaler-gtcents-fn.html cm-2.6.0/doc/dict/sco-stream-cls.html cm-2.6.0/doc/dict/seq-cls.html cm-2.6.0/doc/dict/set-clm-output-hook-fn.html cm-2.6.0/doc/dict/set-midi-output-hook-fn.html cm-2.6.0/doc/dict/set-sco-output-hook-fn.html cm-2.6.0/doc/dict/shell-fn.html cm-2.6.0/doc/dict/shuffle-fn.html cm-2.6.0/doc/dict/softest-var.html cm-2.6.0/doc/dict/sprout-fn.html cm-2.6.0/doc/dict/stop-fn.html cm-2.6.0/doc/dict/subcontainers-fn.html cm-2.6.0/doc/dict/subobjects-fn.html cm-2.6.0/doc/dict/syntax.html cm-2.6.0/doc/dict/tempo-var.html cm-2.6.0/doc/dict/tendency-fn.html cm-2.6.0/doc/dict/terms.html cm-2.6.0/doc/dict/transpose-fn.html cm-2.6.0/doc/dict/transposer-cls.html cm-2.6.0/doc/dict/true-var.html cm-2.6.0/doc/dict/tuning-cls.html cm-2.6.0/doc/dict/vary-fn.html cm-2.6.0/doc/dict/wait-fn.html cm-2.6.0/doc/dict/wait-until-fn.html cm-2.6.0/doc/emacs.html cm-2.6.0/doc/img/ cm-2.6.0/doc/img/cmlogobb.png cm-2.6.0/doc/img/cmlogobw.png cm-2.6.0/doc/img/cmlogosw.png cm-2.6.0/doc/install.html cm-2.6.0/etc/ cm-2.6.0/etc/cminit.lisp cm-2.6.0/etc/contrib/ cm-2.6.0/etc/contrib/lock.cm cm-2.6.0/etc/examples/ cm-2.6.0/etc/examples/cring.cm cm-2.6.0/etc/examples/fm.ins cm-2.6.0/etc/examples/foster.cm cm-2.6.0/etc/examples/intro.cm cm-2.6.0/etc/examples/ligeti.cm cm-2.6.0/etc/examples/plotter.cm cm-2.6.0/etc/examples/reich.cm cm-2.6.0/etc/examples/rt.cm cm-2.6.0/etc/examples/scales.cm cm-2.6.0/etc/test.cm cm-2.6.0/etc/xemacs/ cm-2.6.0/etc/xemacs/cm.el cm-2.6.0/etc/xemacs/custom.el cm-2.6.0/etc/xemacs/init.el cm-2.6.0/etc/xemacs/listener.el cm-2.6.0/readme.text cm-2.6.0/src/ cm-2.6.0/src/.cvsignore cm-2.6.0/src/acl.lisp cm-2.6.0/src/clisp.lisp cm-2.6.0/src/clm-stubs.lisp cm-2.6.0/src/clm.lisp cm-2.6.0/src/clm.scm cm-2.6.0/src/clm2.lisp cm-2.6.0/src/clm2.scm cm-2.6.0/src/clos.lisp cm-2.6.0/src/cm.lisp cm-2.6.0/src/cm.scm cm-2.6.0/src/cmn-stubs.lisp cm-2.6.0/src/cmn.lisp cm-2.6.0/src/cmn.scm cm-2.6.0/src/cmu.lisp cm-2.6.0/src/data.lisp cm-2.6.0/src/data.scm cm-2.6.0/src/goops.scm cm-2.6.0/src/gui/ cm-2.6.0/src/gui/drawing.lisp cm-2.6.0/src/gui/editing.lisp cm-2.6.0/src/gui/eventio.lisp cm-2.6.0/src/gui/gtkffi-cmusbcl.lisp cm-2.6.0/src/gui/gtkffi-openmcl.lisp cm-2.6.0/src/gui/plotter.lisp cm-2.6.0/src/gui/support.lisp cm-2.6.0/src/gui/widgets.lisp cm-2.6.0/src/guile.scm cm-2.6.0/src/io.lisp cm-2.6.0/src/io.scm cm-2.6.0/src/iter.lisp cm-2.6.0/src/level1.lisp cm-2.6.0/src/level1.scm cm-2.6.0/src/loop.lisp cm-2.6.0/src/loop.scm cm-2.6.0/src/make.lisp cm-2.6.0/src/mcl.lisp cm-2.6.0/src/midi1.lisp cm-2.6.0/src/midi1.scm cm-2.6.0/src/midi2.lisp cm-2.6.0/src/midi2.scm cm-2.6.0/src/midi3.lisp cm-2.6.0/src/midi3.scm cm-2.6.0/src/midishare/ cm-2.6.0/src/midishare/.cvsignore cm-2.6.0/src/midishare/MidiShare-Interface.lisp cm-2.6.0/src/midishare/midishare-stubs.lisp cm-2.6.0/src/midishare/midishare.lisp cm-2.6.0/src/midishare/midishare.scm cm-2.6.0/src/midishare/Player-Interface.lisp cm-2.6.0/src/midishare/player.lisp cm-2.6.0/src/midishare/player.scm cm-2.6.0/src/mop.lisp cm-2.6.0/src/mop.scm cm-2.6.0/src/objects.lisp cm-2.6.0/src/objects.scm cm-2.6.0/src/openmcl.lisp cm-2.6.0/src/patterns.lisp cm-2.6.0/src/patterns.scm cm-2.6.0/src/pkg.lisp cm-2.6.0/src/sbcl.lisp cm-2.6.0/src/scales.lisp cm-2.6.0/src/scales.scm cm-2.6.0/src/scheduler.lisp cm-2.6.0/src/scheduler.scm cm-2.6.0/src/scheme.lisp cm-2.6.0/src/sco.lisp cm-2.6.0/src/sco.scm cm-2.6.0/src/spectral.lisp cm-2.6.0/src/spectral.scm cm-2.6.0/src/stocl.lisp cm-2.6.0/src/utils.lisp cm-2.6.0/src/utils.scm #P"/Users/hkt/.asdf-install-dir/site/cm-2.6.0/" #P"/Users/hkt/.asdf-install-dir/site/cm-2.6.0/" ;;; ASDF-INSTALL: Loading system "cm" via ASDF. ; loading system definition from /Users/hkt/.asdf-install-dir/systems/cm.asd ; into # ; registering # as cm ;Compiler warnings : ; Undefined function COMMON-LISP-USER::CM, in (PERFORM :AFTER (LOAD-OP (EQL #))) inside an anonymous lambda form. ; Installation directory: "/Users/hkt/.asdf-install-dir/site/cm-2.6.0/" ; Compiling "src/gui/gtkffi-openmcl.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/gtkffi-openmcl.dfsl" ; Compiling "src/midishare/MidiShare-Interface.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/MidiShare-Interface.dfsl" ; Compiling "src/midishare/Player-Interface.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/Player-Interface.dfsl" ; Compiling "src/clm-stubs.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/clm-stubs.dfsl" ; Compiling "src/cmn-stubs.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/cmn-stubs.dfsl" ; Compiling "src/pkg.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/pkg.dfsl" ; Compiling "src/openmcl.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/openmcl.dfsl" ; Compiling "src/clos.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/clos.dfsl" ; Compiling "src/iter.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/iter.dfsl" ; Compiling "src/level1.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/level1.dfsl" ; Compiling "src/scheme.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/scheme.dfsl" ; Compiling "src/utils.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/utils.dfsl" ; Compiling "src/mop.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/mop.dfsl" ; Compiling "src/objects.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/objects.dfsl" ; Compiling "src/data.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/data.dfsl" ; Compiling "src/scales.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/scales.dfsl" ; Compiling "src/spectral.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/spectral.dfsl" ; Compiling "src/patterns.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/patterns.dfsl" ; Compiling "src/io.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/io.dfsl" ; Compiling "src/scheduler.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/scheduler.dfsl" ; Compiling "src/sco.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/sco.dfsl" ; Compiling "src/clm.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/clm.dfsl" ; Compiling "src/clm2.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/clm2.dfsl" ; Compiling "src/midi1.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/midi1.dfsl" ; Compiling "src/midi2.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/midi2.dfsl" ; Compiling "src/midi3.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/midi3.dfsl" ; Compiling "src/midishare/midishare.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/midishare.dfsl" ; Compiling "src/midishare/player.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/player.dfsl" ; Compiling "src/cmn.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/cmn.dfsl" ; Compiling "src/gui/plotter.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/plotter.dfsl" ; Compiling "src/gui/support.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/support.dfsl" ; Compiling "src/gui/widgets.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/widgets.dfsl" ; Compiling "src/gui/editing.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/editing.dfsl" ; Compiling "src/gui/drawing.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/drawing.dfsl" ; Compiling "src/gui/eventio.lisp" ; Loading "bin/openmcl_0.14.2-050216_darwin-powerpc/eventio.dfsl" ; Garbage collecting. /\\\ ---\\\--------- ----\\\-------- ----/\\\------- Common Music 2.6.0 ---/--\\\------ --/----\\\----- / \\\/ NIL ? From znmeb at cesmail.net Wed Mar 23 20:47:05 2005 From: znmeb at cesmail.net (M. Edward (Ed) Borasky) Date: Wed, 23 Mar 2005 20:47:05 -0800 Subject: [CM] cm 2.6.0 download available In-Reply-To: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> Message-ID: <42424649.9070306@cesmail.net> Rick Taube wrote: > Common Music 2.6.0 is now available for download from Sourceforge: > > http://sourceforge.net/projects/commonmusic/ > > I won't go into any details since this has been an ongoing saga, > see doc/changelog.text for the complete listing of new features. > Many many thanks to Anders Vinjar and Dave Phillips for testing. > > Tested in: > > OS LISP VERSION SYSTEMS TESTED > ---------------------------------------------------- > x86 sbcl 0.8.17 midi,clm3,cmn,gtk2 > x86 cmucl 19a midi,clm3,cmn,gtk2 > osx guile 1.6.7 midi > osx openmcl cvs midi,clm3,cmn,midishare,gtk2 > osx clisp 2.32 midi > osx sbcl 0.8.17 midi > cygwin clisp 2.33.1 midi > winxp clisp 2.33.1 midi > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > I just verified that it works on Gentoo Linux with sbcl 0.8.20!! I've notified the Gentoo Lisp and sound people about the release (and the ASDF features). I'm testing with cmucl 19a now. Now that the ASDF work is done, it shouldn't be much longer before the 2.6.0 release is in the Gentoo repository. So ... does anyone want to package this for Debian? The Agnula folks would be eternally grateful (and some of them lurk on this list :). From dlphillips at woh.rr.com Thu Mar 24 03:02:04 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Thu, 24 Mar 2005 06:02:04 -0500 Subject: [CM] cm 2.6.0 download available In-Reply-To: <42424649.9070306@cesmail.net> References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> Message-ID: <42429E2C.1080501@woh.rr.com> Greetings: I was going to add that MidiShare works under x86/cmucl, but I'm having some serious problems with it, at least when I try using it with the cmio GUI. I'll post a real report on the trouble later, but I thought I should verify first whether anyone else has worked with MidiShare with an x86 Lisp. Anyone ? If so, how did you make it work ? Best, dp M. Edward (Ed) Borasky wrote: > Rick Taube wrote: > >> Common Music 2.6.0 is now available for download from Sourceforge: >> >> http://sourceforge.net/projects/commonmusic/ >> >> I won't go into any details since this has been an ongoing saga, >> see doc/changelog.text for the complete listing of new features. >> Many many thanks to Anders Vinjar and Dave Phillips for testing. >> >> Tested in: >> >> OS LISP VERSION SYSTEMS TESTED >> ---------------------------------------------------- >> x86 sbcl 0.8.17 midi,clm3,cmn,gtk2 >> x86 cmucl 19a midi,clm3,cmn,gtk2 >> osx guile 1.6.7 midi >> osx openmcl cvs midi,clm3,cmn,midishare,gtk2 >> osx clisp 2.32 midi >> osx sbcl 0.8.17 midi >> cygwin clisp 2.33.1 midi >> winxp clisp 2.33.1 midi >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist >> > I just verified that it works on Gentoo Linux with sbcl 0.8.20!! I've > notified the Gentoo Lisp and sound people about the release (and the > ASDF features). I'm testing with cmucl 19a now. Now that the ASDF work > is done, it shouldn't be much longer before the 2.6.0 release is in > the Gentoo repository. So ... does anyone want to package this for > Debian? The Agnula folks would be eternally grateful (and some of them > lurk on this list :). > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > From taube at uiuc.edu Thu Mar 24 04:20:37 2005 From: taube at uiuc.edu (Rick Taube) Date: Thu, 24 Mar 2005 06:20:37 -0600 Subject: [CM] linux and midishare In-Reply-To: <42429E2C.1080501@woh.rr.com> References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> Message-ID: I just tried Midishare with the cmio window using the CM.app for OSX and its working. I think anders also had problems getting it to work on linux. I would first try to get Midishare working just in the repl and once thats reliable adding the window hopefully wont be a problem Another alternative for direct-to-midi on linux might be to use Nando's ALSA midi streams, but Im not sure what the status of this is --t i think he got something working for his class. On Mar 24, 2005, at 5:02 AM, Dave Phillips wrote: > Greetings: > > I was going to add that MidiShare works under x86/cmucl, but I'm > having some serious problems with it, at least when I try using it > with the cmio GUI. I'll post a real report on the trouble later, but I > thought I should verify first whether anyone else has worked with > MidiShare with an x86 Lisp. Anyone ? If so, how did you make it work ? > > Best, > > dp From dlphillips at woh.rr.com Thu Mar 24 06:02:39 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Thu, 24 Mar 2005 09:02:39 -0500 Subject: [CM] linux and midishare In-Reply-To: References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> Message-ID: <4242C87F.1080708@woh.rr.com> Hi Rick: Okay, here's what's happening: Apparently the Open/Close buttons on the Midishare tab aren't working. If I run (midi-open) and (midi-close) from the CM prompt I see a Common Music entry come and go in the msConnect window. Performing the same actions with the buttons does nothing. Any suggestions ? Best, dp Rick Taube wrote: > I just tried Midishare with the cmio window using the CM.app for OSX > and its working. I think anders also had problems getting it to work > on linux. I would first try to get Midishare working just in the repl > and once thats reliable adding the window hopefully wont be a problem > Another alternative for direct-to-midi on linux might be to use > Nando's ALSA midi streams, but Im not sure what the status of this is > --t i think he got something working for his class. > > On Mar 24, 2005, at 5:02 AM, Dave Phillips wrote: > >> Greetings: >> >> I was going to add that MidiShare works under x86/cmucl, but I'm >> having some serious problems with it, at least when I try using it >> with the cmio GUI. I'll post a real report on the trouble later, but >> I thought I should verify first whether anyone else has worked with >> MidiShare with an x86 Lisp. Anyone ? If so, how did you make it work ? >> >> Best, >> >> dp > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > From dlphillips at woh.rr.com Thu Mar 24 06:15:01 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Thu, 24 Mar 2005 09:15:01 -0500 Subject: [CM] linux and midishare In-Reply-To: References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> Message-ID: <4242CB65.7040105@woh.rr.com> Hi Rick: Btw, if I run (midi-open?) and it returns NIL, a subsequent call to (midi-open) will freeze the interpreter. If (midi-open?) returns with a port there's no problem. Best, dp From dlphillips at woh.rr.com Thu Mar 24 06:29:22 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Thu, 24 Mar 2005 09:29:22 -0500 Subject: [CM] linux and midishare In-Reply-To: References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> Message-ID: <4242CEC2.8000308@woh.rr.com> Hi Rick: I'm running this code from Example 4 in the MIDI topic dictionary page: (define (rankeys reps rhy dur lb ub) (process repeat reps output (ms:new typeNote :dur dur :pitch (between lb ub)) wait rhy)) So far, so good. I run this code: (output (ms:new typeNote :pitch 80 :dur 1000)) Still good, except I hear no sound. In my msConnect window I've connected CM to an instance of fluidsynth loaded with a GM soundfont. If I run this code: (sprout (rankeys 30 200 250 60 90) 2000) I get this error at the Lisp prompt: Error in KERNEL::UNBOUND-SYMBOL-ERROR-HANDLER: the variable RUN-PROC is unbound. [Condition of type UNBOUND-VARIABLE] Restarts: 0: [ABORT] Return to Top-Level. Debug (type H for help) (RT-SPROUT # 2000) Source: (MIDITASK RUN-PROC (+ (MIDIGETTIME) (OR AHEAD 0)) *MP* ID ...) 0] 0 * Best, dp From dlphillips at woh.rr.com Thu Mar 24 06:56:04 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Thu, 24 Mar 2005 09:56:04 -0500 Subject: [CM] linux and midishare In-Reply-To: <4242CEC2.8000308@woh.rr.com> References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> <4242CEC2.8000308@woh.rr.com> Message-ID: <4242D504.7000307@woh.rr.com> Sorry, I don't know how that URL junk got in there. Dave Phillips wrote: > Hi Rick: > > I'm running this code from Example 4 in the MIDI topic dictionary page: > > (define (rankeys reps rhy dur lb ub) > (process repeat reps > output (ms:new typeNote :dur dur > :pitch (between > lb ub)) > wait rhy)) > > > So far, so good. I run this code: > > (output (ms:new typeNote :pitch 80 :dur 1000)) > > Still good, except I hear no sound. In my msConnect window I've > connected CM to an instance of fluidsynth loaded with a GM soundfont. > > If I run this code: > > (sprout (rankeys 30 200 > 250 60 90) 2000) > > > I get this error at the Lisp prompt: > > Error in KERNEL::UNBOUND-SYMBOL-ERROR-HANDLER: the variable RUN-PROC > is unbound. > [Condition of type UNBOUND-VARIABLE] > > Restarts: > 0: [ABORT] Return to Top-Level. > Debug (type H for help) > > (RT-SPROUT # {580C1729}> 2000) > Source: (MIDITASK RUN-PROC (+ (MIDIGETTIME) (OR AHEAD 0)) *MP* ID ...) > 0] 0 > * > > Best, > > dp > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > From taube at uiuc.edu Thu Mar 24 07:25:56 2005 From: taube at uiuc.edu (Rick Taube) Date: Thu, 24 Mar 2005 09:25:56 -0600 Subject: [CM] linux and midishare In-Reply-To: <4242D504.7000307@woh.rr.com> References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> <4242CEC2.8000308@woh.rr.com> <4242D504.7000307@woh.rr.com> Message-ID: <1bb55b26333164486f3ba6e1197ec84e@uiuc.edu> On Mar 24, 2005, at 8:56 AM, Dave Phillips wrote: >> If I run this code: >> >> (sprout (rankeys 30 200 250 60 90) 2000) > I get this error at the Lisp prompt: Yes, sprouting processes "interactivly" (ie scheduling them in "real time") via Midishare wont work on Linux because -- at the time I added this code -- callbacks were not supported in CMUCL (see the top of midi-topic.html where is says it only works in osx/openmcl.) However, now that callbacks are part of CMUCL (and soon in SBCL) it might very well be possible to get this working on linux now. Unfortunately, i dont know what sort of timeframe you are hoping for -- i also have to start a new piece so I dont know how much time im going to have for new features over the next few months. From nature at timeprints.com Fri Mar 25 04:40:13 2005 From: nature at timeprints.com (Zoran Spasojevic) Date: Fri, 25 Mar 2005 07:40:13 -0500 Subject: [CM] snd digital input Message-ID: <424406AD.2040202@timeprints.com> I have an m-audio audiophile 2496 sound card with 96kHz sampling rate. I would like to use file/record option with the digital output directly from the sound card. I started using snd recently and I would appreciate any help in setting up snd to do that. Perhaps this is done already and if so how can I check that this is the case. Thanks in advance, Zoran From mr.macos at earthlink.net Fri Mar 25 04:35:53 2005 From: mr.macos at earthlink.net (Zoran Spasojevic) Date: Fri, 25 Mar 2005 07:35:53 -0500 Subject: [CM] snd digital input Message-ID: <424405A9.2000101@earthlink.net> I have an m-audio audiophile 2496 sound card with 96kHz sampling rate. I would like to use file/record option with the digital output directly from the sound card. I started using snd recently and I would appreciate any help in setting up snd to do that. Perhaps this is done already and if so how can I check that this is the case. Thanks in advance, Zoran From dlphillips at woh.rr.com Sat Mar 26 07:03:49 2005 From: dlphillips at woh.rr.com (dlphillips at woh.rr.com) Date: Sat, 26 Mar 2005 10:03:49 -0500 Subject: [CM] CM + MidiShare + Linux Message-ID: <97a9db97d48c.97d48c97a9db@columbus.rr.com> Greetings: I'm having some luck with MidiShare with Common Music under Linux and CMUCL 19. Here's what I can reliably make happen: * (midi-open) * (output (ms:new typeNote :port 1 :pitch (between 50 80) :dur (pick 1000 2000 3000))) * (midi-close) The output note will sound on a MidiShare-connected instance of fluidsynth. Apparently this will work only if fluidsynth is launched *after* CM has been opened with a MidiShare port (i.e., as shown above). If I try (midi-open) again after (midi-close) then Lisp will lose its mind and requires an explicit kill -9. Often (quit) will also cause Lisp to lose its mind and I have to explicitly kill Lisp too. The cmio GUI also works if I enter the output statement above in the Events entry box. However, this code will not work (no sound): (define (ms-test ) (process repeat 100 output (ms:new typeNote :port 1 :pitch (between 50 80) :dur (pick 1000 2000 3000)) wait .015)) Am I missing something ? Best, dp From taube at uiuc.edu Sat Mar 26 11:59:19 2005 From: taube at uiuc.edu (Rick Taube) Date: Sat, 26 Mar 2005 13:59:19 -0600 Subject: [CM] CM + MidiShare + Linux In-Reply-To: <97a9db97d48c.97d48c97a9db@columbus.rr.com> References: <97a9db97d48c.97d48c97a9db@columbus.rr.com> Message-ID: I cant debug the problem until I am able to compile Midishare on my debian/demudi box. make currently dies when it tries to compile the kernel., Ive sent a message to the midishare list but so far no answer. -rick On Mar 26, 2005, at 9:03 AM, dlphillips at woh.rr.com wrote: > Greetings: > > I'm having some luck with MidiShare with Common Music under Linux > and CMUCL 19. Here's what I can reliably make happen: > > * (midi-open) > * (output (ms:new typeNote :port 1 :pitch (between 50 80) :dur > (pick 1000 2000 3000))) > * (midi-close) > > The output note will sound on a MidiShare-connected instance of > fluidsynth. Apparently this will work only if fluidsynth is launched > *after* CM has been opened with a MidiShare port (i.e., as shown > above). > > If I try (midi-open) again after (midi-close) then Lisp will lose > its mind and requires an explicit kill -9. > > Often (quit) will also cause Lisp to lose its mind and I have to > explicitly kill Lisp too. > > The cmio GUI also works if I enter the output statement above in the > Events entry box. However, this code will not work (no sound): > > (define (ms-test ) > (process repeat 100 > output (ms:new typeNote :port 1 > :pitch (between 50 80) > :dur (pick 1000 2000 3000)) > wait .015)) > > Am I missing something ? > > Best, > > dp > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From dlphillips at woh.rr.com Sun Mar 27 04:24:24 2005 From: dlphillips at woh.rr.com (dlphillips at woh.rr.com) Date: Sun, 27 Mar 2005 07:24:24 -0500 Subject: [CM] update re: CM/Linux/MidiShare Message-ID: <9ac8219a5f59.9a5f599ac821@columbus.rr.com> Hi Rick: I think I've figured out how and where MidiShare works and doesn't work with CM in Linux. Basically, code written with the high-level MIDI objects will work fine. For example, the following code will work in either the cmio GUI or from the prompt: (define (ms-test1) (process repeat 200 output (new midi :time (now) :duration (pick .1 .2 .3 .2 .1 .1 .2 .3 .2 .1) :amplitude (between 40 60) :keynum (pick 58 60 62 64 65 67 68 70 72 73 75 76 79 80)) wait (pick .1 .2))) (define (ms-test2) (process repeat 200 output (new midi :time (now) :duration (pick .1 .2 .3 .2 .1 .1 .2 .3 .2 .1) ; :duration (pick .25 .25 .50 1.0 .25 .25 .50) :amplitude (between 40 60) :keynum (pick 36 38 41 43 48 50 53 55 60 62 65 67 70 72)) wait (pick .1 .2))) Assuming an opened MS MIDI port, running (events (list (ms-test1) (ms-test2) "midi.port") will then create a realtime MIDI output stream that I can play via a MidiShare-enabled fluidsynth. Incidentally, the GUI replaces whatever file name is in the Execute entry box with "midi.port", which I think is correct behavior, yes ? The situation is not so clear regarding the low-level MIDI objects, i.e. the ms:* family. This code will work fine when run alone: (output (ms:new typeNote :port 1 :pitch (between 50 80) :vel (between 30 50) :dur (pick 100 200 300))) But it fails in this setting: (define (rankeys) (process repeat 100 output (ms:new typeNote :port 1 :pitch (between 50 80) :vel (between 30 50) :dur (pick 100 200 300)) wait (pick 100 200))) ; (events (rankeys) "midi.port") Running (rankeys) in the Events dialog results in the following error: * (events (rankeys) "midi.port") No matching method for the generic function #, when called with arguments (#). [Condition of type PCL::NO-APPLICABLE-METHOD-ERROR] Restarts: 0: [CONTINUE] Retry call to :FUNCTION. 1: [ABORT ] Return to Top-Level. Debug (type H for help) ("DEFMETHOD NO-APPLICABLE-METHOD (T)" # # # (#)) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:pcl/braid.lisp. 0] 1 * Btw, I can open and close the MS MIDI port without errors now (from GUI or prompt), though I'll keep an eye on its behavior. So, my provisional conclusion is that MidiShare works fine with CM's high level MIDI objects but not so well with the low-level ones. There may be advantages to using the MidiShare objects but I've not been testing anything that can't be done with the high level objects. I will keep testing and would appreciate any advice re: looping with the MidiShare objects. Best regards, dp From taube at uiuc.edu Sun Mar 27 07:18:36 2005 From: taube at uiuc.edu (Rick Taube) Date: Sun, 27 Mar 2005 09:18:36 -0600 Subject: [CM] Re: update re: CM/Linux/MidiShare In-Reply-To: <9ac8219a5f59.9a5f599ac821@columbus.rr.com> References: <9ac8219a5f59.9a5f599ac821@columbus.rr.com> Message-ID: <6867e7a384227e056b9c039203027beb@uiuc.edu> Thanks for the testing! The error is definately a bug but Im not sure where or why it is happening. So while Im still waiting for someone from the midishare list to tell me what to do, could you please send me a backtrace of this error (by typing the command BACKTRACE when you are in cmucl's debug loop): > Running (rankeys) in the Events dialog results in the following error: > * (events (rankeys) "midi.port") > No matching method for the generic function > #, when called > with > arguments > (# (ALIEN:STRUCT MIDISHARE::TMIDIEV > Incidentally, the GUI replaces whatever file name is in the Execute > entry box with "midi.port", which I think is correct behavior, yes ? no this is a bug too: Only files should be placed in that buffer to execute. From dlphillips at woh.rr.com Sun Mar 27 12:05:16 2005 From: dlphillips at woh.rr.com (dlphillips at woh.rr.com) Date: Sun, 27 Mar 2005 15:05:16 -0500 Subject: [CM] Re: update re: CM/Linux/MidiShare Message-ID: <9b96a79b5751.9b57519b96a7@columbus.rr.com> Hi Rick: Here's the backtrace: No matching method for the generic function #, when called with arguments (#). [Condition of type PCL::NO-APPLICABLE-METHOD-ERROR] Restarts: 0: [CONTINUE] Retry call to :FUNCTION. 1: [ABORT ] Return to Top-Level. Debug (type H for help) ("DEFMETHOD NO-APPLICABLE-METHOD (T)" # # # (#)) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:pcl/braid.lisp. 0] BACKTRACE 0: ("DEFMETHOD NO-APPLICABLE-METHOD (T)" # # # (#)) 1: (OUTPUT # NIL) 2: (NIL) 3: ((METHOD PROCESS-EVENTS NIL (FUNCTION T T T)) # # # 0 ...) 4: (SCHEDULE-EVENTS # # 0) 5: (EVENTS # "midi.port") 6: (EXTENSIONS:INTERACTIVE-EVAL (EVENTS (RANKEYS) "midi.port")) 7: (LISP::%TOP-LEVEL) 8: ((LABELS LISP::RESTART-LISP EXTENSIONS:SAVE-LISP)) HTH, dp From taube at uiuc.edu Sun Mar 27 16:16:01 2005 From: taube at uiuc.edu (Rick Taube) Date: Sun, 27 Mar 2005 18:16:01 -0600 Subject: [CM] Re: update re: CM/Linux/MidiShare In-Reply-To: <9ac8219a5f59.9a5f599ac821@columbus.rr.com> References: <9ac8219a5f59.9a5f599ac821@columbus.rr.com> Message-ID: Sorry, I should have had a second cup of coffee before responding this morning. The error you got is not a bug. I think the "high" and "low" level is not made clear enough on the Midi topic page. Specifically, ms:new makes "alien" c objects that are not part of Lisp's type system and so they cannot be hooked into the high-level event handling. Put another way, the only thing that can really use midishare allocated things is midishare itself. So you can create them in Lisp and you can also send/receive them directly to/from midishare but nothing else. > But it fails in this setting: > (define (rankeys) > (process repeat 100 > output (ms:new typeNote :port 1 > :pitch (between 50 80) > :vel (between 30 50) > :dur (pick 100 200 300)) > wait (pick 100 200))) > > ; (events (rankeys) "midi.port") From juanig at ccrma.Stanford.EDU Sun Mar 27 20:40:45 2005 From: juanig at ccrma.Stanford.EDU (Juan Reyes) Date: Sun, 27 Mar 2005 20:40:45 -0800 Subject: [CM] snd digital input In-Reply-To: <424405A9.2000101@earthlink.net> References: <424405A9.2000101@earthlink.net> Message-ID: <1111984845.4618.10.camel@coconut> > I have an m-audio audiophile 2496 sound card with 96kHz sampling rate. > I would like to use file/record option with the digital output directly > from the sound card. AFAIK, if you are using Snd on a Linux system with ALSA the "spdif" digital i/o's don't seem to work on a 2496 96KHz and delta cards. On OS-X you should check on the M-Audio delta console application and enable digital i/o's using the professional option (avoid consumer). Good luck, --* Juan From dlphillips at woh.rr.com Mon Mar 28 05:47:36 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Mon, 28 Mar 2005 08:47:36 -0500 Subject: [CM] Re: update re: CM/Linux/MidiShare In-Reply-To: References: <9ac8219a5f59.9a5f599ac821@columbus.rr.com> Message-ID: <42480AF8.2050502@woh.rr.com> Hi Rick: Okay, thanks for the clarification. However, the example below is quoted from the CM dictionary MIDI topic page (Example 4). If I understand correctly, this code will work with a sprout call only under OSX/OpenMCL, yes ? You do make that clear, I think I just didn't want to believe it. ;-) The MidiShare system is great for realtime MIDI output from CM, it works very well with the high-level objects. However, I still have some questions: How do I stop a realtime stream before it's ended ? How is the MS MidiPlayer used, or can it be used at all under Linux ? I'll post a separate message with some example code for anyone wanting to test realtime MIDI output with CM + MidiShare + Linux. Meanwhile I'm pretty happy with CM's realtime MIDI performance. It would be great to be able to start/stop/pause/continue a realtime stream, do you think that's a possibility when using high-level objects ? Btw, Csound is also capable of realtime MIDI output. I coded some CM examples that prepared Csound scores for realtime MIDI out, they worked perfectly from within CM (i.e., the cmio GUI). Considering MidiShare's capabilities, it would be great to see more extensive support for it. Time-code support is one of it's more interesting features, it would be interesting to place CM in a time-sync'd applications environment, but I think at this point I'm dreaming out loud. :) Thanks again for the help! Best, dp Rick Taube wrote: > Sorry, I should have had a second cup of coffee before responding this > morning. The error you got is not a bug. I think the "high" and "low" > level is not made clear enough on the Midi topic page. Specifically, > ms:new makes "alien" c objects that are not part of Lisp's type system > and so they cannot be hooked into the high-level event handling. Put > another way, the only thing that can really use midishare allocated > things is midishare itself. So you can create them in Lisp and you can > also send/receive them directly to/from midishare but nothing else. > > >> But it fails in this setting: >> (define (rankeys) >> (process repeat 100 >> output (ms:new typeNote :port 1 >> :pitch (between 50 80) >> :vel (between 30 50) >> :dur (pick 100 200 300)) >> wait (pick 100 200))) >> >> ; (events (rankeys) "midi.port") > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > From dlphillips at woh.rr.com Mon Mar 28 06:40:34 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Mon, 28 Mar 2005 09:40:34 -0500 Subject: [CM] Using MidiShare with CM and Linux: A brief tutorial Message-ID: <42481762.90302@woh.rr.com> Greetings: I've been experimenting with CM's use of GRAME's MidiShare interface and I thought I'd share my successes with anyone else on the list who might want to explore this aspect of CM a bit further. First, it seems that there are problems building MidiShare on some distros, notably the current AGNULA/Demudi distro but possibly others. I can successfully build and install MidiShare from CVS on a Planet CCRMA RH9 system with GCC 3.2.2. I suspect there may be compiler and kernel incompatibilities that await being addressed by the MidiShare developers. My apologies, I can't directly help anyone having such troubles, but I do suggest that you write to the developers for a patch to update the sources. After building and installing the MidiShare system you'll probably need to manually install the driver module. This command does the trick: modprobe MidiShare If it fails you may have a module installation problem. Review your build and installation steps, and make sure the MidiShare.o module is present in /lib/modules/your-kernel-here/misc (or similar path). If you continue to have problems contact the MidiShare developers. MidiShare includes a number of helpful GUI and command-line components, including a graphic patch bay for connecting MidiShare sources, apps, and targets. Start the msConnect patch bay with this command: msconnect You should see entries only for MidiShare (0) and msconnect (1). Now launch CM in your usual fashion. If the MidiShare module has been correctly installed you should see a check mark by the MidiShare name on the Systems tab in the cmio GUI (btw, the Load button doesn't seem to work for loading MidiShare). However, by itself the presence of the module does nothing. You must open a MidiShare port by either clicking on the port Open button on the MidiShare tab or issue this command at the Lisp prompt: (midi-open) You can close the port by clicking the Close button or by issuing this command: (midi-close) When you open a MidiShare port you should see an instance of "Common Music" appear in the msConnect GUI. If you don't see it you may need to check whether you've correctly installed MidiShare. See the MidiShare documentation for more information regarding its configuration and troubleshooting procedures. You can query CM for an opened port by issuing the (midi-open?) command, but it has caused problems for me with subsequent calls to (midi-open). That bug may be fixed by now. You can also ask CM for the ID of its MidiShare port with this command from the Lisp prompt (without parentheses!) : *mp* It should return the same slot number for Common Music as seen in the msConnect panel. Now start an instance of fluidsynth with the following options: fluidsynth --midi-driver=midishare --audio-driver=alsa -C0 -R0 -g3 /home/dlphilp/soundfonts/8mbgmsfx.sf2 Of course you'll want to substitute your own path and soundfont. The C and R options turn off chorus and reverb, the g option sets the gain (it's too low by default, IMO). The MIDI and audio driver selections should be obvious. The msConnect GUI should now include an entry for fluidsynth. If you have problems with fluidsynth, see the fluidsynth documentation for more information regarding fluidsynth's options and realtime performance controls. Btw, typing 'man fluidsynth' in an xterm or at the console prompt will open the very informative fluidsynth manual page. Return to the msConnect GUI and connect the Common Music entry in the Applications column to the fluidsynth entry in the Destinations column. At this point you're ready to run some MidiShare-capable code. Try the following simple example as a test: (define (ms-test1) (process repeat 200 output (new midi :time (now) :duration (pick .1 .2 .3 .2 .1 .1 .2 .3 .2 .1) :amplitude (between 40 60) :keynum (pick 58 60 62 64 65 67 68 70 72 73 75 76 79 80)) wait (pick .1 .2))) (define (ms-test2) (process repeat 200 output (new midi :time (now) :duration (pick .1 .2 .3 .2 .1 .1 .2 .3 .2 .1) :amplitude (between 40 60) :keynum (pick 36 38 41 43 48 50 53 55 60 62 65 67 70 72)) wait (pick .1 .2))) ;;; (events (list (ms-test1) (ms-test2)) "midi.port") To run this example from the GUI, simply save it as a file (e.g. ms-test.cm) and load it either via the CM Lisp prompt or the cmio interface. If you are not using the GUI just enter the events line at the prompt. For the GUI just put this line in the Events entry dialog: (list (ms-test1) (ms-test2)) For some reason the action will replace the filename in the Execute entry box (i.e. "ms-test.cm") with "midi.port". This is a bug, but it's a helpful one: if it doesn't appear then you'll know that there's something wrong with your code or system setup. If all the parts are correctly in place you should hear the process begin immediately. Please note that this process applies *only* to the CM's high-level MIDI objects. The low-level objects are not currently usable in such processes under Linux, although you can test the examples from the MIDI topic page by entering them at the prompt. Note that some examples will not work as expected, but in fact the low-level objects are not particularly necessary if you have no need for MidiShare's more specialized services. Improvements I'd like to see include a start/stop/pause/continue control for realtime playback and some further explication regarding the MidiShare MIDI file player (as seen in the cmio MidiShare tab). In other respects this system appears to be working well under Linux and is a valuable addition to CM's output targets. Feel free to notify me of any corrections to this brief tutorial. I also welcome any other examples that show off CM's MidiShare support. Rick: Btw, did CM at one time support Cmix as an output target ? If so, is there any chance that it could be revived for RTCmix someday ? Best, dp From znmeb at cesmail.net Mon Mar 28 07:43:27 2005 From: znmeb at cesmail.net (M. Edward (Ed) Borasky) Date: Mon, 28 Mar 2005 07:43:27 -0800 Subject: [CM] Using MidiShare with CM and Linux: A brief tutorial In-Reply-To: <42481762.90302@woh.rr.com> References: <42481762.90302@woh.rr.com> Message-ID: <4248261F.9040400@cesmail.net> Dave Phillips wrote: [snip] Two questions: 1. Has anyone successfully built MidiShare with Gentoo Linux? I tried once and couldn't tell whether it was working or not. It's not something I need to have, so I haven't really spent much time with it. 2. What is the licensing status of MidiShare? Can it legally be packaged and distributed with Planet CCRMA, Debian, DeMuDi or Gentoo? The last time I looked, you were free to download it and use it, but not to distribute it. If it *can* be re-distributed, I can probably get it packaged for Gentoo. You Debian and Fedora folk are on your own, though :). From dlphillips at woh.rr.com Mon Mar 28 09:03:01 2005 From: dlphillips at woh.rr.com (Dave Phillips) Date: Mon, 28 Mar 2005 12:03:01 -0500 Subject: [CM] a little more MidiShare coolness In-Reply-To: References: <011d1153b0202d6f73f2c2ec412603f4@uiuc.edu> <42424649.9070306@cesmail.net> <42429E2C.1080501@woh.rr.com> Message-ID: <424838C5.4090402@woh.rr.com> Greetings: I just discovered the msAlsaSeq bridge. It appears as a MidiShare client in the msConnect patch bay and as an ALSA sequencer client in any ALSA sequencer-compliant MIDI patch bay (e.g. in QJackCtl). Very cool, I can now connect CM's realtime MIDI stream to any of my softsynths, including VSTi plugins (yes, VST/VSTi plugins can be run under Linux). Many thanks to Dr. Albert Graef for msAlsaSeq ! Best, dp From michael at klingbeil.com Tue Mar 29 22:04:24 2005 From: michael at klingbeil.com (Michael Klingbeil) Date: Wed, 30 Mar 2005 01:04:24 -0500 Subject: [CM] clm-3 help Message-ID: I'm looking for some help with an instrument that won't compile. It seems to work fine under clm-2. With clm-3 I get a .c file but the compilation fails with errors about undeclared variables. This is on MacOS X and OpenMCL. I tried without success using clm-3 16-Mar-05 (in Rick's CM.app) and also with clm-3 23-Mar-05. I tried adding in some declare statements but that didn't seem to help. I wonder if there is an issue with the run macro compiler. I got some similar errors with another instrument (undeclared variables) but I was able to fix the problem by getting rid of a let statement in the run macro. Are let blocks a bad idea within run? I am including the compiler errors and the instrument definition. Any advice is appreciated. Regards, Michael ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Compiling #4P"proj:ins;noisetone.ins.newest".; Writing "/Users/mkling/Desktop/mand/ins/clm_noisetone.c" ; Compiling "/Users/mkling/Desktop/mand/ins/clm_noisetone.c" /Users/mkling/Desktop/mand/ins/clm_noisetone.c: In function `clm_noisetone14': /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: `G1060' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: (Each undeclared identifier is reported only once /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: for each function it appears in.) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:155: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:156: error: `G1060_r' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:156: error: `DEGREE_ENV_r' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:164: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:165: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:166: error: `DISTANCE_ENV_r' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c: In function `clm_noisetone14': /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: `G1060' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: (Each undeclared identifier is reported only once /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: for each function it appears in.) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:154: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:155: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:156: error: `G1060_r' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:156: error: `DEGREE_ENV_r' undeclared (first use in this function) /Users/mkling/Desktop/mand/ins/clm_noisetone.c:164: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:165: error: array subscript is not an integer /Users/mkling/Desktop/mand/ins/clm_noisetone.c:166: error: `DISTANCE_ENV_r' undeclared (first use in this function) ; Loading #4P"proj:ins;noisetone.dfsl.newest".; Compiling "/Users/mkling/Desktop/mand/ins/clm_noisetone.c" > Error in process listener(4): Error opening shared library >"/Users/mkling/Desktop/mand/ins/clm_noisetone.dylib": dyld: >/Applications/CM.app/Contents/MacOS/dppccl can't open library: >/Users/mkling/Desktop/mand/ins/clm_noisetone.dylib (No such file or >directory, errno = 2) > > While executing: OPEN-SHARED-LIBRARY > Type :POP to abort. Type :? for other options. 1 > :q ? ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;; ;;;; file: noisetone.ins ;;;; (definstrument noisetone (start dur amp ampfunc ;; amplitude envelope (must be envelope) freqfunc bwfunc ;; frequency and bandwidth (can envelopes or scalar) &key (bwbase 0.0) (ampbase 10) ;; base for amplitude envelope (mix 1.0) ;; control mix between noisy sinusoid = 1.0 ---> 0.0 = pure sinusoid (degree 45.0) (distance 1.0) (reverb 0.1) ;; how much signal to send to reverberator ) (let* ((beg (floor (* start *srate*))) (end (+ beg (floor (* dur *srate*)))) (ampenv (if ampbase (make-env :envelope ampfunc :duration dur :scaler amp :base ampbase) (make-env :envelope ampfunc :duration dur :scaler amp))) (noise (make-rand-interp (if (numberp bwfunc) (+ bwfunc bwbase) bwbase))) (bwenv (if (listp bwfunc) (make-env :envelope bwfunc :duration dur :scaler (hz->radians 1.0)) nil)) (freqenv (if (listp freqfunc) (make-env :envelope freqfunc :duration dur :scaler (hz->radians 1.0)) nil)) (mixenv (if (listp mix) (make-env :envelope mix :duration dur))) (mixscaler (if (listp mix) 0.0 mix)) (sine (make-oscil (if (numberp freqfunc) freqfunc 0.0) (centered-random pi))) ;; random phase on oscilator ;; ;; locsig stuff follows: ;; (update-rate 10) (degree-env (if (listp degree) (make-env :envelope degree :duration (/ dur update-rate)) nil)) (distance-env (if (listp distance) (make-env :envelope distance :duration (/ dur update-rate)))) (place (make-locsig :degree (if (numberp degree) degree 45.0) :distance (if (numberp distance) distance 1.0) :reverb (if (numberp reverb) reverb 0.0) :type mus-sinusoidal)) ) (run (loop for i fixnum from beg to end do (let (deg dist wave freqmod bwmod mixmod) #-just-lisp (declare (type :integer beg end update-rate) (type :mus-any ampenv noise bwenv freqenv mixenv sine degree-env distance-env place) (type :float mixscaler deg degree distance dist wave freqmod bwmod mixmod mixscaler)) (if (or degree-env distance-env) (if (= 0 (mod (- i beg) update-rate)) (setf deg (if degree-env (env degree-env) degree)) (setf dist (if distance-env (env distance-env) distance)) (move-locsig place deg dist))) (setf freqmod (if freqenv (env freqenv) 0.0)) (setf bwmod (if bwenv (env bwenv) 0.0)) ;; mix is not equal power (setf mixmod (if mixenv (env mixenv) mixscaler)) (setf wave (oscil sine freqmod)) (locsig place i (* (env ampenv) (+ (* mixmod wave (rand-interp noise bwmod)) (* (- 1.0 mixmod) wave))))) )))) From andersvi at extern.uio.no Tue Mar 29 23:51:14 2005 From: andersvi at extern.uio.no (andersvi at extern.uio.no) Date: Wed, 30 Mar 2005 09:51:14 +0200 Subject: [CM] clm-3 help In-Reply-To: (Michael Klingbeil's message of "Wed, 30 Mar 2005 01:04:24 -0500") References: Message-ID: It works here in clm-3 if you substitute all the checks for the various envelopes down in run with (env? envelope), ie. (if (or (env? degree-env) (env? distance-env)) instead of plain (if (or degree-env distance-env) etc. -anders From bil at ccrma.Stanford.EDU Thu Mar 31 03:38:34 2005 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Thu, 31 Mar 2005 03:38:34 -0800 Subject: [CM] clm-3 help In-Reply-To: References: Message-ID: <424BE13A.5050502@ccrma> Thanks for the bug report. It turns out to be a slightly tricky problem -- I'll probably have something worth testing in a couple days.