From lievenmoors at gmail.com Thu Mar 5 13:14:25 2009 From: lievenmoors at gmail.com (lieven moors) Date: Thu, 05 Mar 2009 22:14:25 +0100 Subject: [CM] building sndlib with jack support (for CM3) Message-ID: <49B040B1.5010303@gmail.com> Hi everybody, I tried to build cm today on my 64bit machine, and I noticed a problem. When I build sndlib with jack support (and CC=G++), the static library is not built. And when I look at the makefile, I can see that the A_LD variable is not set. When I build without jack support, this variable is set to ar. So I tried to put "A_LD = ar" in the makefile. But then ar gives an error because it is passed an -L option (which I believe is meant for gcc?) to link with the jack libraries. I was wondering if the static library is intentionally not built when compiled with jack support, or if it is a bug which can be fixed. thanks for your help, greetings Lieven Moors From bil at ccrma.Stanford.EDU Fri Mar 6 04:19:50 2009 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Fri, 6 Mar 2009 04:19:50 -0800 Subject: [CM] building sndlib with jack support (for CM3) In-Reply-To: <49B040B1.5010303@gmail.com> References: <49B040B1.5010303@gmail.com> Message-ID: <20090306121438.M30278@ccrma.Stanford.EDU> > I was wondering if the static library is intentionally not built when > compiled with jack support, or if it is a bug which can be fixed. yes and probably yes, but jack is not in my bailiwick. The configure script uses jack's pkgconfig script, I think, so it is Jack that inserts the -L business. You can get libsndlib.a with Jack by making these changes: JACK_LIBS = /usr/local/lib/libjack.so /usr/lib/libpthread.a /usr/lib/librt.a A_LD = ar (you might have to fix the directories above). From yuri at voivod.net Fri Mar 6 10:52:58 2009 From: yuri at voivod.net (Yuri Jossa) Date: Fri, 06 Mar 2009 13:52:58 -0500 Subject: [CM] CM version that works with the examples in the book? References: Message-ID: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> Thank you Achim. The link below has only the source code for the Windows download for CM 2.10.0. Does anyone have the binary for this? or can someone let me know what Windows compiler i can use to compile the source code? thanks > > Try this one, and watch that the following line is not wrapped, > > http://sourceforge.net/project/showfiles.php?group_id=9766&package_id=106649 > > > > From ahcnz at ihug.co.nz Fri Mar 6 23:05:12 2009 From: ahcnz at ihug.co.nz (Adam) Date: Sat, 7 Mar 2009 20:05:12 +1300 Subject: [CM] CM version that works with the examples in the book? In-Reply-To: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> References: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> Message-ID: <200903072005.14075.ahcnz@ihug.co.nz> That 'source code' should work with CLisp, and Emacs & Slime, on WinXP. The installation instructions are in /cm2/doc/install.html and for setting up in Emacs and Slime, in /cm2/doc/emacs.html However CM2 does not seem to be working right on WinXP under CLisp, Emacs & Slime. And this is a great pity. Rick has suggested that CM2 is no longer being developed. Thats OK. Its great as is. Perhaps CM2 works fine on the Mac and in Linux. I will try in Linux next. It would be great if it could be left as is, but working on XP too. This is where I was downloading from; svn co https://commonmusic.svn.sf.net/svnroot/commonmusic/branches/cm2 On Saturday 07 March 2009 07:52 am, Yuri Jossa wrote: > Thank you Achim. > The link below has only the source code for the Windows download for CM > 2.10.0. > Does anyone have the binary for this? or can someone let me know what > Windows compiler i can use to compile the source code? > > thanks > > > Try this one, and watch that the following line is not wrapped, > > > > http://sourceforge.net/project/showfiles.php?group_id=9766&package_id=106 > >649 > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From lievenmoors at hotmail.com Tue Mar 10 12:31:48 2009 From: lievenmoors at hotmail.com (Lieven Moors) Date: Tue, 10 Mar 2009 20:31:48 +0100 Subject: [CM] cm3 with emacs Message-ID: Hi, I'm wondering how to register alsa midi ports when using cm3 from within emacs. When I sprout a process from within Grace, I can see a Juce port in the alsa sequencer (I still have to make connections manually, even if I select a port from within Grace). But when I start cm from within emacs, I cannot see any Juce ports being registered... thanks for your help, Lieven Moors -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at uiuc.edu Wed Mar 11 11:17:39 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 11 Mar 2009 13:17:39 -0500 Subject: [CM] cm3 with emacs In-Reply-To: References: Message-ID: <918E1F68-74C3-4904-AC5E-82D8149872EF@uiuc.edu> Hi im sorry for the delay in this reply, its been a very busy two weeks! Are you using the function mp:open to open the port? first use (ports) list the avaiable ports: cm> (ports) (("midi.port" (0 -> "IAC Driver Bus 1" #f) (0 <- "IAC Driver Bus 1" #f))) then use (mp:open out . in) to open a device. the -> means in the device listing means that device is an output. so this would open the output device 0 (mp:open 0) cm> (mp:open 0) CoreMidi - opening out: Bus 1 0 cm> > Hi, > > I'm wondering how to register alsa midi ports > when using cm3 from within emacs. When I sprout > a process from within Grace, I can see a Juce port > in the alsa sequencer (I still have to make connections > manually, even if I select a port from within Grace). > But when I start cm from within emacs, I cannot see > any Juce ports being registered... > > thanks for your help, > > Lieven Moors > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Wed Mar 11 11:18:54 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 11 Mar 2009 13:18:54 -0500 Subject: [CM] CM version that works with the examples in the book? In-Reply-To: <200903072005.14075.ahcnz@ihug.co.nz> References: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> <200903072005.14075.ahcnz@ihug.co.nz> Message-ID: <1BB173F8-05D9-42B4-AB58-BE1BCF5F8133@uiuc.edu> hello, im sorry for the delay in this reply, On Mar 7, 2009, at 1:05 AM, Adam wrote: > That 'source code' should work with CLisp, and Emacs & Slime, > on WinXP. > > The installation instructions are in /cm2/doc/install.html > and for setting up in Emacs and Slime, in /cm2/doc/emacs.html > > However CM2 does not seem to be working right on WinXP > under CLisp, Emacs & Slime. And this is a great pity. > > Rick has suggested that CM2 is no longer being developed. > Thats OK. Its great as is. > > Perhaps CM2 works fine on the Mac and in Linux. I will try in Linux > next. > > It would be great if it could be left as is, but working on XP too. > > This is where I was downloading from; > svn co https://commonmusic.svn.sf.net/svnroot/commonmusic/branches/cm2 > > > > > On Saturday 07 March 2009 07:52 am, Yuri Jossa wrote: >> Thank you Achim. >> The link below has only the source code for the Windows download >> for CM >> 2.10.0. >> Does anyone have the binary for this? or can someone let me know what >> Windows compiler i can use to compile the source code? >> >> thanks >> >>> Try this one, and watch that the following line is not wrapped, >>> >>> http://sourceforge.net/project/showfiles.php?group_id=9766&package_id=106 >>> 649 >> >> _______________________________________________ >> 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 From taube at uiuc.edu Wed Mar 11 11:22:01 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 11 Mar 2009 13:22:01 -0500 Subject: [CM] CM version that works with the examples in the book? In-Reply-To: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> References: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> Message-ID: <0DBFE3DF-8E70-4A38-8E82-D6466BEFD74F@uiuc.edu> Arrrrg! let me try again... did you get this issue resolved? > However CM2 does not seem to be working right on WinXP > under CLisp, Emacs & Slime. And this is a great pity. what specifically is the issue? I cant fix it with this information -- it was certainly working at one point and should continue to > Rick has suggested that CM2 is no longer being developed. > Thats OK. Its great as is. i will continue to support cm2 fix bugs etc but not add new features (use cm3 line for this) From ahcnz at ihug.co.nz Wed Mar 11 14:10:35 2009 From: ahcnz at ihug.co.nz (Adam) Date: Thu, 12 Mar 2009 10:10:35 +1300 Subject: [CM] CM version that works with the examples in the book? In-Reply-To: <0DBFE3DF-8E70-4A38-8E82-D6466BEFD74F@uiuc.edu> References: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> <0DBFE3DF-8E70-4A38-8E82-D6466BEFD74F@uiuc.edu> Message-ID: <200903121010.36132.ahcnz@ihug.co.nz> Thanks for the reply, Rick. I'll chat with Yuri, and get back with details. Adam. From yuri at voivod.net Fri Mar 13 11:22:30 2009 From: yuri at voivod.net (Yuri Jossa) Date: Fri, 13 Mar 2009 14:22:30 -0400 Subject: [CM] CM version that works with the examples in the book? References: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> <0DBFE3DF-8E70-4A38-8E82-D6466BEFD74F@uiuc.edu> Message-ID: <003c01c9a408$abb26a60$6700a8c0@ncore1> I have CM 2.42 (the version that came with the CD included with the book) running fine on Win XP.. however a good quantity of the programs on the book do not work with that version. I cannot find a compiled version of the CM 2.0 version that the programs on the book are supposed to work with.. a link to the source code was provided but i haven't tried to compile it.. i was hoping someone would have a binary distribution somewhere.. Thanks ----- Original Message ----- From: "Heinrich Taube" To: "Yuri Jossa" Cc: "cm list" ; "Adam" Sent: Wednesday, March 11, 2009 2:22 PM Subject: Re: [CM] CM version that works with the examples in the book? > Arrrrg! let me try again... > > did you get this issue resolved? > > >> However CM2 does not seem to be working right on WinXP >> under CLisp, Emacs & Slime. And this is a great pity. > > what specifically is the issue? I cant fix it with this information -- it > was certainly working at one point and should continue to > >> Rick has suggested that CM2 is no longer being developed. >> Thats OK. Its great as is. > > i will continue to support cm2 fix bugs etc but not add new features > (use cm3 line for this) From taube at uiuc.edu Fri Mar 13 13:05:17 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 13 Mar 2009 15:05:17 -0500 Subject: [CM] CM version that works with the examples in the book? In-Reply-To: <003c01c9a408$abb26a60$6700a8c0@ncore1> References: <001d01c99e8c$c48e25f0$6700a8c0@ncore1> <0DBFE3DF-8E70-4A38-8E82-D6466BEFD74F@uiuc.edu> <003c01c9a408$abb26a60$6700a8c0@ncore1> Message-ID: If you have a running 2.42 that works well then probably the easiest thing is for me to get the examples working in that, there wont be much difference. If you can send me information about what examples or chapters are not working I can probably fix it for you and post in on the website for the future. probably best you just send this info to me, dont bother the list with this; ill post the fixes once we have it resolved. On Mar 13, 2009, at 1:22 PM, Yuri Jossa wrote: > I have CM 2.42 (the version that came with the CD included with the > book) > running fine on Win XP.. however a good quantity of the programs on > the book > do not work with that version. > > I cannot find a compiled version of the CM 2.0 version that the > programs > on the book are supposed to work with.. a link to the source code was > provided but i haven't tried to compile it.. > > i was hoping someone would have a binary distribution somewhere.. > > Thanks > > > ----- Original Message ----- > From: "Heinrich Taube" > To: "Yuri Jossa" > Cc: "cm list" ; "Adam" > Sent: Wednesday, March 11, 2009 2:22 PM > Subject: Re: [CM] CM version that works with the examples in the book? > > >> Arrrrg! let me try again... >> >> did you get this issue resolved? >> >> >>> However CM2 does not seem to be working right on WinXP >>> under CLisp, Emacs & Slime. And this is a great pity. >> >> what specifically is the issue? I cant fix it with this information >> -- it >> was certainly working at one point and should continue to >> >>> Rick has suggested that CM2 is no longer being developed. >>> Thats OK. Its great as is. >> >> i will continue to support cm2 fix bugs etc but not add new features >> (use cm3 line for this) > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From o.finnendahl at mh-freiburg.de Sat Mar 14 01:34:47 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Sat, 14 Mar 2009 09:34:47 +0100 Subject: [CM] linux version on sf broken? Message-ID: <20090314083447.GA7562@varese> Hi, I'm experiencing problems uncompressing the cm-3.2.4-linux.tgz file downloaded today from sourceforge. The archive seems to be incomplete: gzip: stdin: unexpected end of file tar: Unerwartetes Dateiende im Archiv. tar: Unerwartetes Dateiende im Archiv. tar: Nicht behebbarer Fehler: Programmabbruch. If the file on sf really is corrupted and it got fixed, please let me know. -- Orm From c.mcclelland at qub.ac.uk Sat Mar 14 11:02:20 2009 From: c.mcclelland at qub.ac.uk (Christopher McClelland) Date: Sat, 14 Mar 2009 18:02:20 +0000 Subject: [CM] [ANN] Sound and Music Computing Conference Message-ID: [Sorry for cross-postings] [Please circulate] Call for Participation Sound and Music Computing Conference, 23-25 July 2009 Casa da M?sica, Porto, Portugal http://smc2009.smcnetwork.org/ SMC is a privileged forum in Europe for the promotion of international exchanges around Sound and Music Computing topics. SMC 2009 will feature papers, posters, music works, tutorials and special sessions. = Important dates: . Paper, Music and Tutorials submission deadline: Friday 17 April 2009 . [LATE DEADLINE] Deadline for participation to special sessions: Monday 8 June 2009 Sound and Music Computing is an interdisciplinary field that approaches the whole sound and music communication chain from a multidisciplinary point of view. By combining scientific, technological and artistic methodologies it aims at understanding, modeling and generating sound and music through computational approaches. Its core academic subjects relate to musicology, physics (acoustics), engineering (including computer science, signal processing and electronics), psychology (including psychoacoustics, experimental psychology and neurosciences) and music composition. Topics will include: . Automatic music generation/accompaniment systems . Computer environments for sound/music processing/composition . Networked music generation . Physical modeling for sound generation . Sound/music signal processing algorithms . Digital Audio Effects . Musical sound source separation and recognition . Automatic music transcription . Music information retrieval . Musical pattern recognition/modeling . Music and robotics . Computational musicology . Sonic interaction design . 3D sound/music . Data sonification . Visualization of sound/music data . Interfaces for music creation and fruition . Interactive performance systems . Musical performance modeling . Gesture controlled audio systems . Sound/music perception and cognition . Sound/music and Neuroscience . Music and emotions . Multimodality in sound and music computing . Web 2.0 and music . Mobile music . Technologies for the preservation, access and modelling of musical heritage All accepted papers and posters will be published in the conference Proceedings, which will account for an ISBN. Furthermore, a special issue of the Computer Music Journal will be devoted to articles based on selected items from the conference. Not only will the best conference papers be considered for publication in extended form in the Journal, but also posters, tutorials, and reports of special sessions. = Note on Special Sessions: http://smc2009.smcnetwork.org/call-for-participation/special-sessions.html SMC 2009 will feature special sessions on "hot" topics relevant to Sound and Music Computing research, where a special focus will be put on interaction between participants and the audience (members of the scientific and music communities, and the general public at large). There are, for now, 2 special sessions, on "Sonic Interaction Design" and "Music Visualization". http://smc2009.smcnetwork.org/programme/special-sessions/sid.html http://smc2009.smcnetwork.org/programme/special-sessions/visualization.html (Stay tuned for announces of more special sessions in the upcoming weeks...) = Note on Tutorials: The day prior to the conference (22 July 2009) will consist of tutorials, focusing on a single topic presented either at an introductory level or in depth, lasting about 3 hours (including a break). You are welcome to propose tutorial along the guidelines detailed on http://smc2009.smcnetwork.org/call-for-participation/call-for-tutorials.html = Stay tuned: . RSS feed: http://smc2009.smcnetwork.org/news/news/RSS . Facebook group: http://www.new.facebook.com/group.php?gid=42958077160 . Twitter: http://twitter.com/smc2009 = Want to help us promote SMC 2009? . Follow and promote SMC 2009 on facebook and twitter . Have a quick look here: http://smc2009.smcnetwork.org/promote-us ........................................................................... Chris McClelland Sonic Arts Research Centre Queens University Belfast BT7 1NN Tel: 02890974445 Email: c.mcclelland at qub.ac.uk -------------- next part -------------- An HTML attachment was scrubbed... URL: From o.finnendahl at mh-freiburg.de Sun Mar 15 06:54:40 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Sun, 15 Mar 2009 14:54:40 +0100 Subject: [CM] linux version needed Message-ID: <20090315135440.GB6589@varese> Hi all, I posted to the list that the linux version of common music seems broken on sf. Does anybody have a working version (also, even preferably cm-2) he could send me off-list? I need the midi import functions quite urgently and hesitate rolling my own at the moment. -- Orm From taube at uiuc.edu Sun Mar 15 10:13:18 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Sun, 15 Mar 2009 12:13:18 -0500 Subject: [CM] linux version needed In-Reply-To: <20090315135440.GB6589@varese> References: <20090315135440.GB6589@varese> Message-ID: for importing midifiles in cm2 you dont need anyhing other than svn, here is what you do assuming you have sbcl installed on your path (BTW midifile import is in the next cm3 release, along with fomus...) [all one line] $ svn co https://commonmusic.svn.sourceforge.net/svnroot/commonmusic/branches/cm2 cm $ cd cm $ bin/cm.sh -l sbcl zippy-2:cm hkt$ bin/cm.sh -l sbcl ;; loading #P"/usr/local/lib/sbcl/sb-posix/sb-posix.asd" ; loading system definition from /usr/local/lib/sbcl/sb-grovel/sb- grovel.asd ; into # ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/sb-grovel.asd" ; registering # as SB-GROVEL ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/defpackage.fasl" ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/def-to-lisp.fasl" ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/foreign-glue.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-posix/defpackage.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-posix/designator.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-posix/macros.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-posix/constants.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-posix/interface.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/defpackage.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/split.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/constants.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sockets.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sockopt.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/inet.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/local.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/name-service.fasl" ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/misc.fasl" ; CM install directory: /Users/hkt/cm/ ; Compiling pkg.lisp ; Loading pkg.fasl ; Generating iter.lisp ; Generating utils.lisp ; Generating mop.lisp ; Generating objects.lisp ; Generating data.lisp ; Generating scales.lisp ; Generating spectral.lisp ; Generating patterns.lisp ; Generating io.lisp ; Generating scheduler.lisp ; Generating gnuplot.lisp ; Generating plt.lisp ; Generating sco.lisp ; Generating clm.lisp ; Generating midi1.lisp ; Generating midi2.lisp ; Generating midi3.lisp ; Generating cmn.lisp ; Generating fomus.lisp ; Generating midishare.lisp ; Generating player.lisp ; Generating sc.lisp ; Generating pm.lisp ; Generating rt.lisp ; Compiling sbcl.lisp ; Compiling iter.lisp ; Loading sbcl.fasl ; Loading iter.fasl ; Compiling level1.lisp ; Loading level1.fasl ; Compiling clos.lisp ; Compiling scheme.lisp ; Compiling utils.lisp ; Loading clos.fasl ; Loading utils.fasl ; Compiling mop.lisp ; Loading mop.fasl ; Compiling objects.lisp ; Compiling data.lisp ; Loading data.fasl ; Loading objects.fasl ; Compiling scales.lisp ; Compiling spectral.lisp ; Loading scales.fasl ; Compiling patterns.lisp ; Compiling io.lisp ; Loading io.fasl ; Compiling scheduler.lisp ; Compiling gnuplot.lisp ; Loading gnuplot.fasl ; Compiling plt.lisp ; Compiling sco.lisp ; Compiling clm.lisp ; Compiling midi1.lisp ; Loading midi1.fasl ; Loading scheduler.fasl ; Compiling midi2.lisp ; Loading midi2.fasl ; Compiling midi3.lisp ; Loading midi3.fasl ; Compiling cmn.lisp ; Compiling fomus.lisp ; Compiling midishare.lisp ; Loading midishare.fasl ; Compiling player.lisp ; Compiling sc.lisp ; Compiling pm.lisp ; Compiling rt.lisp ; Compiling parse.lisp ; Loading parse.fasl ; Compiling sal.lisp ; Loading scheme.fasl ; Loading spectral.fasl ; Loading patterns.fasl ; Loading plt.fasl ; Loading sco.fasl ; Loading clm.fasl ; Loading cmn.fasl ; Loading fomus.fasl ; Loading player.fasl ; Loading sc.fasl ; Loading pm.fasl ; Loading rt.fasl ; Loading sal.fasl /\\\ ---\\\--------- ----\\\-------- ----/\\\------- Common Music 2.11.3 ---/--\\\------ --/----\\\----- / \\\/ * From o.finnendahl at mh-freiburg.de Sun Mar 15 12:19:02 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Sun, 15 Mar 2009 20:19:02 +0100 Subject: [CM] linux version needed In-Reply-To: References: <20090315135440.GB6589@varese> Message-ID: <20090315191902.GC6589@varese> Hi Rick, great thanks! I didn't know how to obtain cm2 with svn. That helped a lot and saves my day! Yours, Orm Am Sonntag, den 15. M?rz 2009 um 12:13:18 Uhr (-0500) schrieb Rick Taube: > for importing midifiles in cm2 you dont need anyhing other than svn, > here is what you do assuming you have sbcl installed on your path > (BTW midifile import is in the next cm3 release, along with fomus...) > > [all one line] > > $ svn co > https://commonmusic.svn.sourceforge.net/svnroot/commonmusic/branches/cm2 > cm > $ cd cm > $ bin/cm.sh -l sbcl > zippy-2:cm hkt$ bin/cm.sh -l sbcl > ;; loading #P"/usr/local/lib/sbcl/sb-posix/sb-posix.asd" > ; loading system definition from /usr/local/lib/sbcl/sb-grovel/sb- > grovel.asd > ; into # > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/sb-grovel.asd" > ; registering # as SB-GROVEL > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/defpackage.fasl" > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/def-to-lisp.fasl" > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/foreign-glue.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/defpackage.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/designator.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/macros.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/constants.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/interface.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/defpackage.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/split.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/constants.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sockets.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sockopt.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/inet.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/local.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/name-service.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/misc.fasl" > ; CM install directory: /Users/hkt/cm/ > ; Compiling pkg.lisp > ; Loading pkg.fasl > ; Generating iter.lisp > ; Generating utils.lisp > ; Generating mop.lisp > ; Generating objects.lisp > ; Generating data.lisp > ; Generating scales.lisp > ; Generating spectral.lisp > ; Generating patterns.lisp > ; Generating io.lisp > ; Generating scheduler.lisp > ; Generating gnuplot.lisp > ; Generating plt.lisp > ; Generating sco.lisp > ; Generating clm.lisp > ; Generating midi1.lisp > ; Generating midi2.lisp > ; Generating midi3.lisp > ; Generating cmn.lisp > ; Generating fomus.lisp > ; Generating midishare.lisp > ; Generating player.lisp > ; Generating sc.lisp > ; Generating pm.lisp > ; Generating rt.lisp > ; Compiling sbcl.lisp > ; Compiling iter.lisp > ; Loading sbcl.fasl > ; Loading iter.fasl > ; Compiling level1.lisp > ; Loading level1.fasl > ; Compiling clos.lisp > ; Compiling scheme.lisp > ; Compiling utils.lisp > ; Loading clos.fasl > ; Loading utils.fasl > ; Compiling mop.lisp > ; Loading mop.fasl > ; Compiling objects.lisp > ; Compiling data.lisp > ; Loading data.fasl > ; Loading objects.fasl > ; Compiling scales.lisp > ; Compiling spectral.lisp > ; Loading scales.fasl > ; Compiling patterns.lisp > ; Compiling io.lisp > ; Loading io.fasl > ; Compiling scheduler.lisp > ; Compiling gnuplot.lisp > ; Loading gnuplot.fasl > ; Compiling plt.lisp > ; Compiling sco.lisp > ; Compiling clm.lisp > ; Compiling midi1.lisp > ; Loading midi1.fasl > ; Loading scheduler.fasl > ; Compiling midi2.lisp > ; Loading midi2.fasl > ; Compiling midi3.lisp > ; Loading midi3.fasl > ; Compiling cmn.lisp > ; Compiling fomus.lisp > ; Compiling midishare.lisp > ; Loading midishare.fasl > ; Compiling player.lisp > ; Compiling sc.lisp > ; Compiling pm.lisp > ; Compiling rt.lisp > ; Compiling parse.lisp > ; Loading parse.fasl > ; Compiling sal.lisp > ; Loading scheme.fasl > ; Loading spectral.fasl > ; Loading patterns.fasl > ; Loading plt.fasl > ; Loading sco.fasl > ; Loading clm.fasl > ; Loading cmn.fasl > ; Loading fomus.fasl > ; Loading player.fasl > ; Loading sc.fasl > ; Loading pm.fasl > ; Loading rt.fasl > ; Loading sal.fasl > > /\\\ > ---\\\--------- > ----\\\-------- > ----/\\\------- Common Music 2.11.3 > ---/--\\\------ > --/----\\\----- > / \\\/ > > * > > > From njcross at sbcglobal.net Sun Mar 15 14:25:13 2009 From: njcross at sbcglobal.net (njcross) Date: Sun, 15 Mar 2009 14:25:13 -0700 Subject: [CM] linux version needed In-Reply-To: References: Message-ID: <200903151425.14353.njcross@sbcglobal.net> Also the midishare interface files appear to have disappeared. Does midishare interface build with cm2? On Sunday 15 March 2009 12:00:01 pm cmdist-request at ccrma.stanford.edu wrote: > Message: 2 > Date: Sun, 15 Mar 2009 12:13:18 -0500 > From: Heinrich Taube > Subject: Re: [CM] linux version needed > To: Orm Finnendahl > Cc: cm list > Message-ID: > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > for importing midifiles in cm2 you dont need anyhing other than svn, ? > here is what you do assuming you have sbcl installed on your path > (BTW midifile import is in the next cm3 release, along with fomus...) > > [all one line] > > $ svn co > https://commonmusic.svn.sourceforge.net/svnroot/commonmusic/branches/cm2 cm > $ cd cm > $ bin/cm.sh -l sbcl > zippy-2:cm hkt$ bin/cm.sh -l sbcl > ;; loading #P"/usr/local/lib/sbcl/sb-posix/sb-posix.asd" > ; loading system definition from /usr/local/lib/sbcl/sb-grovel/sb- > grovel.asd > ; into # > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/sb-grovel.asd" > ; registering # as SB-GROVEL > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/defpackage.fasl" > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/def-to-lisp.fasl" > ;;; loading #P"/usr/local/lib/sbcl/sb-grovel/foreign-glue.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/defpackage.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/designator.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/macros.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/constants.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-posix/interface.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/defpackage.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/split.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/constants.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sockets.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/sockopt.fasl" > ;; loading #P"/usr/local/lib/sbcl/sb-bsd-sockets/inet.fasl" > ;; lo From taube at uiuc.edu Mon Mar 16 09:29:49 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Mon, 16 Mar 2009 11:29:49 -0500 Subject: [CM] cm2 setup on WinXP In-Reply-To: <200903161017.32926.ahcnz@ihug.co.nz> References: <200903161017.32926.ahcnz@ihug.co.nz> Message-ID: <57F11596-F7B0-4396-A250-E98CF989A67A@uiuc.edu> > I'd like to keep on with Emacs, Common Lisp, and I'm quite > happy with CM 2.10 if that was the last version. > I'll certainly be using Grace in the future, but separately. > > It seems a simple error in my install. I can't seem to get > a working result by following Install.html and Emacs.html. > > As you know, Emacs *with Slime* is the only way to go. > Maybe CM 2.10 or CM 2.4 works OK under just CLisp alone, > but its hard for me to tell. I can persist and check that if > you wish. It seems something about the Emacs config. Hi there were some changes in recent slimes that caused things to not work but ive made fixes to cm/etc/emacs/cm.el and checked them into svn. I just reinstalled cm2 + clisp + emacs + slime from scratch on my windows box and I dont have any problems now. So rather than try to fix you problem Ill just tell you what I did. its basically a two step proccess; (1) installing lisp and (2) configureing emacs Install clisp and cm on my local machine ( c: /Software/cm2 and c:/ Sofware/clisp-2.47) 1 svn'ed the lastest cm2 from today ( REV 1688 / cm 2.11.3) into my C:/Software folder: svn co https://commonmusic.svn.sf.net/svnroot/commonmusic/branches/cm2 2 dowloaded and installed the latest clisp (clisp-2.47-win32-mingw- big.zip) into c:/Software/clisp-2.47 3 double-clicked C:/Software/clisp-2.47/install.bat to install clisp and typed 'y' to add a GNU-CLISP desktop icon to start clisp 4 double-clicked the GNU-CLISP icon on my desktop to start clisp 5 Loaded cm.lisp to build the system and to save cm2/bin/cm-clisp.bat : (load "/Software/cm2/src/cm.lisp") 6 Quit Clisp At this point CM is compiled and it saved a CM startup script in cm2/ bin: C:/Software/cm2/bin/cm-clisp.bat Configuring Emacs 1. downloaded the latest cvs snapshot of Slime into c:/Software/ slime-2009-03-16 2. Started Emacs and edited my Emacs init file: ~/.emacs 3. Added the following to the top of my .emacs file. you have to change the directories for your machine: (add-to-list 'load-path "/Software/slime-2009-03-16/") (require 'slime) (slime-setup '(slime-repl)) (setq cm-program "/Software/cm2/bin/cm-clisp.bat") (add-to-list 'load-path "/Software/cm2/") (load "etc/emacs/cm.el") (enable-cm-commands) 4. saved .emacs file, the quit and restarted Emacs to make the changes to .emacs take effect. 3. Started CM by typeing M-x: cm Cm starts up in a slime repl window. I can eval stuff from a .lisp buffer without problems. On Mar 15, 2009, at 5:17 PM, Adam wrote: -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at uiuc.edu Mon Mar 16 09:41:13 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Mon, 16 Mar 2009 11:41:13 -0500 Subject: [CM] cm2 setup on WinXP In-Reply-To: <57F11596-F7B0-4396-A250-E98CF989A67A@uiuc.edu> References: <200903161017.32926.ahcnz@ihug.co.nz> <57F11596-F7B0-4396-A250-E98CF989A67A@uiuc.edu> Message-ID: > 1 svn'ed the lastest cm2 from today ( REV 1688 / cm 2.11.3) into my > C:/Software folder: just fixed a comment nit, make that REV 1689 ;) From alrefi at ibest.com.br Tue Mar 17 05:01:57 2009 From: alrefi at ibest.com.br (Alexandre Ficagna) Date: Tue, 17 Mar 2009 09:01:57 -0300 Subject: [CM] trying to compile grace Message-ID: <3d37741d0903170501t737092fcg905ca33eb82f0021@mail.gmail.com> Hi, I'm trying to build GraceCL under Ubuntu 8.04, but I'm getting trouble trying to do JUCE. Here's what I've got (I've already edited juce_Config.h turning xinerama, unicode and opengl off): bageh at bageh-laptop:/usr/local/lisp/juce/build/linux$ sudo make ==== Building JUCE ==== juce_Time.cpp juce_Logger.cpp juce_SystemStats.cpp make[1]: *** [../../bin/intermediate_linux/Debug/juce_SystemStats.o] Interromper make: *** [JUCE] Interromper bageh at bageh-laptop:/usr/local/lisp/juce/build/linux$ make CONFIG=Release ==== Building JUCE ==== juce_Time.cpp ../../src/juce_core/basics/juce_Time.cpp:525: erro fatal: opening dependency file ../../bin/intermediate_linux/Release/juce_Time.d: Permiss?o negada Compila??o conclu?da. make[1]: ** [../../bin/intermediate_linux/Release/juce_Time.o] Erro 1 make: ** [JUCE] Erro 2 bageh at bageh-laptop:/usr/local/lisp/juce/build/linux$ sudo make CONFIG=Release ==== Building JUCE ==== juce_Time.cpp juce_Logger.cpp juce_SystemStats.cpp juce_FileLogger.cpp juce_RelativeTime.cpp juce_Random.cpp juce_MD5.cpp juce_BlowFish.cpp juce_Primes.cpp juce_RSAKey.cpp juce_MemoryBlock.cpp juce_PropertySet.cpp juce_BitArray.cpp juce_OutputStream.cpp juce_InputStream.cpp juce_NamedPipe.cpp juce_File.cpp juce_FileInputStream.cpp juce_FileOutputStream.cpp juce_FileSearchPath.cpp juce_DirectoryIterator.cpp juce_URL.cpp juce_Socket.cpp juce_MemoryInputStream.cpp juce_GZIPCompressorOutputStream.cpp juce_FileInputSource.cpp juce_MemoryOutputStream.cpp juce_SubregionStream.cpp juce_GZIPDecompressorInputStream.cpp juce_BufferedInputStream.cpp juce_Uuid.cpp juce_ZipFile.cpp juce_PerformanceCounter.cpp juce_XmlElement.cpp juce_String.cpp juce_LocalisedStrings.cpp juce_XmlDocument.cpp ../../src/juce_core/text/juce_XmlDocument.cpp: In member function ?int juce::XmlDocument::findNextTokenLength()?: ../../src/juce_core/text/juce_XmlDocument.cpp:193: aviso: comparison is always true due to limited range of data type ../../src/juce_core/text/juce_XmlDocument.cpp: In member function ?juce::XmlElement* juce::XmlDocument::readNextElement(bool)?: ../../src/juce_core/text/juce_XmlDocument.cpp:400: aviso: comparison is always true due to limited range of data type juce_StringPairArray.cpp juce_CharacterFunctions.cpp juce_StringArray.cpp juce_ReadWriteLock.cpp juce_TimeSliceThread.cpp juce_ThreadPool.cpp juce_InterProcessLock.cpp juce_Thread.cpp juce_ApplicationCommandManager.cpp juce_DeletedAtShutdown.cpp juce_ApplicationCommandInfo.cpp juce_ApplicationCommandTarget.cpp juce_PropertiesFile.cpp juce_ApplicationProperties.cpp juce_Application.cpp juce_AudioDataConverters.cpp juce_IIRFilter.cpp juce_AudioSampleBuffer.cpp juce_MidiFile.cpp juce_MidiKeyboardState.cpp juce_MidiBuffer.cpp juce_MidiMessage.cpp juce_MidiMessageCollector.cpp juce_MidiMessageSequence.cpp juce_GenericAudioProcessorEditor.cpp juce_AudioProcessorGraph.cpp juce_AudioProcessor.cpp juce_AudioProcessorPlayer.cpp juce_AudioProcessorEditor.cpp juce_AudioPluginFormat.cpp juce_PluginDescription.cpp juce_PluginDirectoryScanner.cpp juce_KnownPluginList.cpp juce_AudioPluginFormatManager.cpp juce_AudioPluginInstance.cpp juce_PluginListComponent.cpp juce_VSTPluginFormat.cpp juce_AudioUnitPluginFormat.cpp juce_FlacAudioFormat.cpp ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:79: aviso: ?void* FlacNamespace::safe_malloc_add_3op_(size_t, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:90: aviso: ?void* FlacNamespace::safe_malloc_add_4op_(size_t, size_t, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:126: aviso: ?void* FlacNamespace::safe_malloc_mul_3op_(size_t, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:139: aviso: ?void* FlacNamespace::safe_malloc_mul2add_(size_t, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:159: aviso: ?void* FlacNamespace::safe_realloc_add_2op_(void*, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:167: aviso: ?void* FlacNamespace::safe_realloc_add_3op_(void*, size_t, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:178: aviso: ?void* FlacNamespace::safe_realloc_add_4op_(void*, size_t, size_t, size_t, size_t)? defined but not used ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:202: aviso: ?void* FlacNamespace::safe_realloc_muladd2_(void*, size_t, size_t, size_t)? defined but not used juce_AudioThumbnail.cpp juce_AudioSubsectionReader.cpp juce_AudioFormat.cpp juce_AiffAudioFormat.cpp juce_AudioCDReader.cpp juce_OggVorbisAudioFormat.cpp In file included from ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp:58: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c: In function ?int OggVorbisNamespace::_vorbis_pack_info(OggVorbisNamespace::oggpack_buffer*, OggVorbisNamespace::vorbis_info*)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c:393: aviso: deprecated conversion from string constant to ?char*? ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c: In function ?int OggVorbisNamespace::_vorbis_pack_comment(OggVorbisNamespace::oggpack_buffer*, OggVorbisNamespace::vorbis_comment*)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c:417: aviso: deprecated conversion from string constant to ?char*? ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c: In function ?int OggVorbisNamespace::_vorbis_pack_books(OggVorbisNamespace::oggpack_buffer*, OggVorbisNamespace::vorbis_info*)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c:448: aviso: deprecated conversion from string constant to ?char*? In file included from ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp:70: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c: In function ?int OggVorbisNamespace::ov_crosslap(OggVorbisNamespace::OggVorbis_File*, OggVorbisNamespace::OggVorbis_File*)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c:1859: aviso: deprecated conversion from string constant to ?char*? ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c:1860: aviso: deprecated conversion from string constant to ?char*? ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp: In constructor ?juce::OggWriter::OggWriter(juce::OutputStream*, double, int, int, int)?: ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp:266: aviso: deprecated conversion from string constant to ?char*? ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c: In function ?void OggVorbisNamespace::bark_noise_hybridmp(int, const long int*, const float*, float*, float, int)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c:559: aviso: ?D? may be used uninitialized in this function ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c:559: aviso: ?B? may be used uninitialized in this function ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c:559: aviso: ?A? may be used uninitialized in this function ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c: In function ?int OggVorbisNamespace::ov_raw_seek(OggVorbisNamespace::OggVorbis_File*, OggVorbisNamespace::ogg_int64_t)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c:993: aviso: ?eosflag? may be used uninitialized in this function ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/mapping0.c: In function ?int OggVorbisNamespace::mapping0_forward(OggVorbisNamespace::vorbis_block*)?: ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/mapping0.c:593: aviso: ?mag_sort? may be used uninitialized in this function ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/mapping0.c:592: aviso: ?mag_memo? may be used uninitialized in this function juce_QuickTimeAudioFormat.cpp juce_AudioThumbnailCache.cpp juce_WavAudioFormat.cpp juce_AudioFormatManager.cpp juce_MixerAudioSource.cpp juce_BufferingAudioSource.cpp juce_IIRFilterAudioSource.cpp juce_AudioFormatReaderSource.cpp juce_ResamplingAudioSource.cpp juce_ToneGeneratorAudioSource.cpp juce_AudioSourcePlayer.cpp juce_AudioTransportSource.cpp juce_ChannelRemappingAudioSource.cpp juce_AudioIODevice.cpp juce_AudioDeviceManager.cpp juce_MidiOutput.cpp juce_AudioIODeviceType.cpp juce_Sampler.cpp juce_Synthesiser.cpp juce_UndoManager.cpp juce_FileBasedDocument.cpp juce_RecentlyOpenedFilesList.cpp juce_AsyncUpdater.cpp juce_MessageListener.cpp juce_ActionListenerList.cpp juce_Message.cpp juce_Timer.cpp juce_ActionBroadcaster.cpp juce_MultiTimer.cpp juce_MessageManager.cpp juce_ChangeBroadcaster.cpp juce_InterprocessConnection.cpp juce_InterprocessConnectionServer.cpp juce_ChangeListenerList.cpp juce_GradientBrush.cpp juce_ImageBrush.cpp juce_SolidColourBrush.cpp juce_Brush.cpp juce_Colour.cpp juce_Colours.cpp juce_ColourGradient.cpp juce_RectanglePlacement.cpp juce_LowLevelGraphicsSoftwareRenderer.cpp ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp: In member function ?void juce::LowLevelGraphicsSoftwareRenderer::clippedFillPathWithGradient(int, int, int, int, const juce::Path&, const juce::AffineTransform&, const juce::ColourGradient&, juce::EdgeTable::OversamplingLevel)?: ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1310: aviso: ?renderer.juce::GradientEdgeTableRenderer::.juce::LinearGradientPixelGenerator::start? may be used uninitialized in this function ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1310: aviso: ?renderer.juce::GradientEdgeTableRenderer::.juce::LinearGradientPixelGenerator::grad? may be used uninitialized in this function ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1310: aviso: ?renderer.juce::GradientEdgeTableRenderer::.juce::LinearGradientPixelGenerator::yTerm? may be used uninitialized in this function ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1333: aviso: ?renderer.juce::GradientEdgeTableRenderer::.juce::LinearGradientPixelGenerator::start? may be used uninitialized in this function ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1333: aviso: ?renderer.juce::GradientEdgeTableRenderer::.juce::LinearGradientPixelGenerator::grad? may be used uninitialized in this function ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1333: aviso: ?renderer.juce::GradientEdgeTableRenderer::.juce::LinearGradientPixelGenerator::yTerm? may be used uninitialized in this function juce_LowLevelGraphicsPostScriptRenderer.cpp juce_Justification.cpp juce_Graphics.cpp juce_EdgeTable.cpp juce_SVGParser.cpp juce_Drawable.cpp juce_DrawableText.cpp juce_DrawablePath.cpp juce_DrawableComposite.cpp juce_DrawableImage.cpp juce_DropShadowEffect.cpp juce_GlowEffect.cpp juce_ReduceOpacityEffect.cpp juce_GlyphArrangement.cpp juce_TextLayout.cpp juce_Font.cpp juce_Typeface.cpp juce_Rectangle.cpp juce_Point.cpp juce_RectangleList.cpp juce_BorderSize.cpp juce_AffineTransform.cpp juce_Path.cpp juce_PathIterator.cpp juce_PositionedRectangle.cpp juce_Line.cpp juce_PathStrokeType.cpp juce_Image.cpp juce_ImageConvolutionKernel.cpp juce_ImageFileFormat.cpp juce_ImageCache.cpp juce_GIFLoader.cpp juce_PNGLoader.cpp juce_JPEGLoader.cpp juce_Component.cpp juce_Desktop.cpp juce_ComponentListener.cpp juce_ImageButton.cpp juce_ArrowButton.cpp juce_Button.cpp juce_HyperlinkButton.cpp juce_ShapeButton.cpp juce_DrawableButton.cpp juce_ToggleButton.cpp juce_ToolbarButton.cpp juce_TextButton.cpp juce_ProgressBar.cpp juce_TableHeaderComponent.cpp juce_ListBox.cpp juce_Toolbar.cpp juce_ToolbarItemPalette.cpp juce_Slider.cpp juce_ToolbarItemComponent.cpp juce_TreeView.cpp juce_TableListBox.cpp juce_TextEditor.cpp juce_Label.cpp juce_ComboBox.cpp juce_FileChooserDialogBox.cpp juce_FileSearchPathListComponent.cpp juce_FileBrowserComponent.cpp juce_FilenameComponent.cpp juce_WildcardFileFilter.cpp juce_FileTreeComponent.cpp juce_DirectoryContentsList.cpp juce_ImagePreviewComponent.cpp juce_DirectoryContentsDisplayComponent.cpp juce_FileChooser.cpp juce_FileListComponent.cpp juce_FileFilter.cpp juce_KeyMappingEditorComponent.cpp juce_KeyPressMappingSet.cpp juce_KeyboardFocusTraverser.cpp juce_KeyPress.cpp juce_ModifierKeys.cpp juce_KeyListener.cpp juce_ResizableCornerComponent.cpp juce_GroupComponent.cpp juce_ComponentMovementWatcher.cpp juce_ResizableBorderComponent.cpp juce_MultiDocumentPanel.cpp juce_TabbedComponent.cpp juce_ScrollBar.cpp juce_ComponentAnimator.cpp juce_TabbedButtonBar.cpp juce_ComponentBoundsConstrainer.cpp juce_StretchableLayoutResizerBar.cpp juce_StretchableLayoutManager.cpp juce_StretchableObjectResizer.cpp juce_Viewport.cpp juce_OldSchoolLookAndFeel.cpp juce_LookAndFeel.cpp juce_PopupMenu.cpp juce_MenuBarComponent.cpp juce_MenuBarModel.cpp juce_ComponentDragger.cpp juce_MouseHoverDetector.cpp juce_MouseEvent.cpp juce_MouseListener.cpp juce_DragAndDropContainer.cpp juce_MouseCursor.cpp juce_ButtonPropertyComponent.cpp juce_TextPropertyComponent.cpp juce_ChoicePropertyComponent.cpp juce_SliderPropertyComponent.cpp juce_PropertyPanel.cpp juce_PropertyComponent.cpp juce_BooleanPropertyComponent.cpp juce_PreferencesPanel.cpp juce_AudioDeviceSelectorComponent.cpp juce_QuickTimeMovieComponent.cpp juce_BubbleComponent.cpp juce_OpenGLComponent.cpp juce_MidiKeyboardComponent.cpp juce_ColourSelector.cpp juce_DropShadower.cpp juce_MagnifierComponent.cpp juce_BubbleMessageComponent.cpp juce_SystemTrayIconComponent.cpp juce_AlertWindow.cpp juce_TooltipWindow.cpp juce_ComponentPeer.cpp juce_DocumentWindow.cpp juce_ThreadWithProgressWindow.cpp juce_ResizableWindow.cpp juce_DialogWindow.cpp juce_SplashScreen.cpp juce_TopLevelWindow.cpp juce_linux_AudioCDReader.cpp juce_linux_Windowing.cpp platform_specific_code/juce_linux_Windowing.cpp:52:34: aviso: X11/extensions/XShm.h: Arquivo ou diret?rio inexistente platform_specific_code/juce_linux_Windowing.cpp: In function ?bool juce::isShmAvailable()?: platform_specific_code/juce_linux_Windowing.cpp:409: erro: ?XShmQueryVersion? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:413: erro: ?XShmSegmentInfo? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:413: erro: expected `;' before ?segmentInfo? platform_specific_code/juce_linux_Windowing.cpp:414: erro: ?segmentInfo? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:416: erro: ?XShmCreateImage? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:430: erro: ?XShmAttach? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:433: erro: ?XShmDetach? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp: At global scope: platform_specific_code/juce_linux_Windowing.cpp:649: erro: ?XShmSegmentInfo? does not name a type platform_specific_code/juce_linux_Windowing.cpp: In constructor ?juce::XBitmapImage::XBitmapImage(juce::Image::PixelFormat, int, int, bool, bool)?: platform_specific_code/juce_linux_Windowing.cpp:477: erro: ?segmentInfo? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:479: erro: ?XShmCreateImage? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:498: erro: ?XShmAttach? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp: In destructor ?virtual juce::XBitmapImage::~XBitmapImage()?: platform_specific_code/juce_linux_Windowing.cpp:569: erro: ?segmentInfo? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:569: erro: ?XShmDetach? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp: In member function ?void juce::XBitmapImage::blitToWindow(Window, int, int, int, int, int, int)?: platform_specific_code/juce_linux_Windowing.cpp:635: erro: ?XShmPutImage? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp: In constructor ?juce::LinuxComponentPeer::LinuxRepaintManager::LinuxRepaintManager(juce::LinuxComponentPeer*)?: platform_specific_code/juce_linux_Windowing.cpp:1688: erro: ?XShmSegmentInfo? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:1688: erro: expected `;' before ?segmentinfo? platform_specific_code/juce_linux_Windowing.cpp:1692: erro: ?segmentinfo? was not declared in this scope platform_specific_code/juce_linux_Windowing.cpp:1692: erro: ?XShmCreateImage? was not declared in this scope make[1]: ** [../../bin/intermediate_linux/Release/juce_linux_Windowing.o] Erro 1 make: ** [JUCE] Erro 2 Thanks, Alexandre Ficagna -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.s.matheussen at notam02.no Tue Mar 17 06:18:01 2009 From: k.s.matheussen at notam02.no (Kjetil S. Matheussen) Date: Tue, 17 Mar 2009 14:18:01 +0100 (CET) Subject: [CM] trying to compile grace In-Reply-To: <3d37741d0903170501t737092fcg905ca33eb82f0021@mail.gmail.com> References: <3d37741d0903170501t737092fcg905ca33eb82f0021@mail.gmail.com> Message-ID: You seem to be missing Xshm.h. It's probably in an X development package. I don't know how to find out the correct package to install in Ubuntu though. Could be xorg-devel or x11-devel. On Tue, 17 Mar 2009, Alexandre Ficagna wrote: > Hi, > > I'm trying to build GraceCL under Ubuntu 8.04, but I'm getting trouble > trying to do JUCE. Here's what I've got (I've already edited juce_Config.h > turning xinerama, unicode and opengl off): > > bageh at bageh-laptop:/usr/local/lisp/juce/build/linux$ sudo make > ==== Building JUCE ==== > juce_Time.cpp > juce_Logger.cpp > juce_SystemStats.cpp > make[1]: *** [../../bin/intermediate_linux/Debug/juce_SystemStats.o] > Interromper > make: *** [JUCE] Interromper > > bageh at bageh-laptop:/usr/local/lisp/juce/build/linux$ make CONFIG=Release > ==== Building JUCE ==== > juce_Time.cpp > ../../src/juce_core/basics/juce_Time.cpp:525: erro fatal: opening dependency > file ../../bin/intermediate_linux/Release/juce_Time.d: Permiss?o negada > Compila??o conclu?da. > make[1]: ** [../../bin/intermediate_linux/Release/juce_Time.o] Erro 1 > make: ** [JUCE] Erro 2 > bageh at bageh-laptop:/usr/local/lisp/juce/build/linux$ sudo make > CONFIG=Release > ==== Building JUCE ==== > juce_Time.cpp > juce_Logger.cpp > juce_SystemStats.cpp > juce_FileLogger.cpp > juce_RelativeTime.cpp > juce_Random.cpp > juce_MD5.cpp > juce_BlowFish.cpp > juce_Primes.cpp > juce_RSAKey.cpp > juce_MemoryBlock.cpp > juce_PropertySet.cpp > juce_BitArray.cpp > juce_OutputStream.cpp > juce_InputStream.cpp > juce_NamedPipe.cpp > juce_File.cpp > juce_FileInputStream.cpp > juce_FileOutputStream.cpp > juce_FileSearchPath.cpp > juce_DirectoryIterator.cpp > juce_URL.cpp > juce_Socket.cpp > juce_MemoryInputStream.cpp > juce_GZIPCompressorOutputStream.cpp > juce_FileInputSource.cpp > juce_MemoryOutputStream.cpp > juce_SubregionStream.cpp > juce_GZIPDecompressorInputStream.cpp > juce_BufferedInputStream.cpp > juce_Uuid.cpp > juce_ZipFile.cpp > juce_PerformanceCounter.cpp > juce_XmlElement.cpp > juce_String.cpp > juce_LocalisedStrings.cpp > juce_XmlDocument.cpp > ../../src/juce_core/text/juce_XmlDocument.cpp: In member function ?int > juce::XmlDocument::findNextTokenLength()?: > ../../src/juce_core/text/juce_XmlDocument.cpp:193: aviso: comparison is > always true due to limited range of data type > ../../src/juce_core/text/juce_XmlDocument.cpp: In member function > ?juce::XmlElement* juce::XmlDocument::readNextElement(bool)?: > ../../src/juce_core/text/juce_XmlDocument.cpp:400: aviso: comparison is > always true due to limited range of data type > juce_StringPairArray.cpp > juce_CharacterFunctions.cpp > juce_StringArray.cpp > juce_ReadWriteLock.cpp > juce_TimeSliceThread.cpp > juce_ThreadPool.cpp > juce_InterProcessLock.cpp > juce_Thread.cpp > juce_ApplicationCommandManager.cpp > juce_DeletedAtShutdown.cpp > juce_ApplicationCommandInfo.cpp > juce_ApplicationCommandTarget.cpp > juce_PropertiesFile.cpp > juce_ApplicationProperties.cpp > juce_Application.cpp > juce_AudioDataConverters.cpp > juce_IIRFilter.cpp > juce_AudioSampleBuffer.cpp > juce_MidiFile.cpp > juce_MidiKeyboardState.cpp > juce_MidiBuffer.cpp > juce_MidiMessage.cpp > juce_MidiMessageCollector.cpp > juce_MidiMessageSequence.cpp > juce_GenericAudioProcessorEditor.cpp > juce_AudioProcessorGraph.cpp > juce_AudioProcessor.cpp > juce_AudioProcessorPlayer.cpp > juce_AudioProcessorEditor.cpp > juce_AudioPluginFormat.cpp > juce_PluginDescription.cpp > juce_PluginDirectoryScanner.cpp > juce_KnownPluginList.cpp > juce_AudioPluginFormatManager.cpp > juce_AudioPluginInstance.cpp > juce_PluginListComponent.cpp > juce_VSTPluginFormat.cpp > juce_AudioUnitPluginFormat.cpp > juce_FlacAudioFormat.cpp > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:79: > aviso: ?void* FlacNamespace::safe_malloc_add_3op_(size_t, size_t, size_t)? > defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:90: > aviso: ?void* FlacNamespace::safe_malloc_add_4op_(size_t, size_t, size_t, > size_t)? defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:126: > aviso: ?void* FlacNamespace::safe_malloc_mul_3op_(size_t, size_t, size_t)? > defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:139: > aviso: ?void* FlacNamespace::safe_malloc_mul2add_(size_t, size_t, size_t)? > defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:159: > aviso: ?void* FlacNamespace::safe_realloc_add_2op_(void*, size_t, size_t)? > defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:167: > aviso: ?void* FlacNamespace::safe_realloc_add_3op_(void*, size_t, size_t, > size_t)? defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:178: > aviso: ?void* FlacNamespace::safe_realloc_add_4op_(void*, size_t, size_t, > size_t, size_t)? defined but not used > ../../src/juce_appframework/audio/audio_file_formats/flac/libFLAC/../alloc.h:202: > aviso: ?void* FlacNamespace::safe_realloc_muladd2_(void*, size_t, size_t, > size_t)? defined but not used > juce_AudioThumbnail.cpp > juce_AudioSubsectionReader.cpp > juce_AudioFormat.cpp > juce_AiffAudioFormat.cpp > juce_AudioCDReader.cpp > juce_OggVorbisAudioFormat.cpp > In file included from > ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp:58: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c: > In function ?int > OggVorbisNamespace::_vorbis_pack_info(OggVorbisNamespace::oggpack_buffer*, > OggVorbisNamespace::vorbis_info*)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c:393: > aviso: deprecated conversion from string constant to ?char*? > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c: > In function ?int > OggVorbisNamespace::_vorbis_pack_comment(OggVorbisNamespace::oggpack_buffer*, > OggVorbisNamespace::vorbis_comment*)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c:417: > aviso: deprecated conversion from string constant to ?char*? > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c: > In function ?int > OggVorbisNamespace::_vorbis_pack_books(OggVorbisNamespace::oggpack_buffer*, > OggVorbisNamespace::vorbis_info*)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/info.c:448: > aviso: deprecated conversion from string constant to ?char*? > In file included from > ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp:70: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c: > In function ?int > OggVorbisNamespace::ov_crosslap(OggVorbisNamespace::OggVorbis_File*, > OggVorbisNamespace::OggVorbis_File*)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c:1859: > aviso: deprecated conversion from string constant to ?char*? > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c:1860: > aviso: deprecated conversion from string constant to ?char*? > ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp: > In constructor ?juce::OggWriter::OggWriter(juce::OutputStream*, double, int, > int, int)?: > ../../src/juce_appframework/audio/audio_file_formats/juce_OggVorbisAudioFormat.cpp:266: > aviso: deprecated conversion from string constant to ?char*? > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c: > In function ?void OggVorbisNamespace::bark_noise_hybridmp(int, const long > int*, const float*, float*, float, int)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c:559: > aviso: ?D? may be used uninitialized in this function > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c:559: > aviso: ?B? may be used uninitialized in this function > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/psy.c:559: > aviso: ?A? may be used uninitialized in this function > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c: > In function ?int > OggVorbisNamespace::ov_raw_seek(OggVorbisNamespace::OggVorbis_File*, > OggVorbisNamespace::ogg_int64_t)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/vorbisfile.c:993: > aviso: ?eosflag? may be used uninitialized in this function > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/mapping0.c: > In function ?int > OggVorbisNamespace::mapping0_forward(OggVorbisNamespace::vorbis_block*)?: > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/mapping0.c:593: > aviso: ?mag_sort? may be used uninitialized in this function > ../../src/juce_appframework/audio/audio_file_formats/oggvorbis/libvorbis-1.1.2/lib/mapping0.c:592: > aviso: ?mag_memo? may be used uninitialized in this function > juce_QuickTimeAudioFormat.cpp > juce_AudioThumbnailCache.cpp > juce_WavAudioFormat.cpp > juce_AudioFormatManager.cpp > juce_MixerAudioSource.cpp > juce_BufferingAudioSource.cpp > juce_IIRFilterAudioSource.cpp > juce_AudioFormatReaderSource.cpp > juce_ResamplingAudioSource.cpp > juce_ToneGeneratorAudioSource.cpp > juce_AudioSourcePlayer.cpp > juce_AudioTransportSource.cpp > juce_ChannelRemappingAudioSource.cpp > juce_AudioIODevice.cpp > juce_AudioDeviceManager.cpp > juce_MidiOutput.cpp > juce_AudioIODeviceType.cpp > juce_Sampler.cpp > juce_Synthesiser.cpp > juce_UndoManager.cpp > juce_FileBasedDocument.cpp > juce_RecentlyOpenedFilesList.cpp > juce_AsyncUpdater.cpp > juce_MessageListener.cpp > juce_ActionListenerList.cpp > juce_Message.cpp > juce_Timer.cpp > juce_ActionBroadcaster.cpp > juce_MultiTimer.cpp > juce_MessageManager.cpp > juce_ChangeBroadcaster.cpp > juce_InterprocessConnection.cpp > juce_InterprocessConnectionServer.cpp > juce_ChangeListenerList.cpp > juce_GradientBrush.cpp > juce_ImageBrush.cpp > juce_SolidColourBrush.cpp > juce_Brush.cpp > juce_Colour.cpp > juce_Colours.cpp > juce_ColourGradient.cpp > juce_RectanglePlacement.cpp > juce_LowLevelGraphicsSoftwareRenderer.cpp > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp: > In member function ?void > juce::LowLevelGraphicsSoftwareRenderer::clippedFillPathWithGradient(int, > int, int, int, const juce::Path&, const juce::AffineTransform&, const > juce::ColourGradient&, juce::EdgeTable::OversamplingLevel)?: > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1310: > aviso: ?renderer.juce::GradientEdgeTableRenderer juce::LinearGradientPixelGenerator>::.juce::LinearGradientPixelGenerator::start? > may be used uninitialized in this function > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1310: > aviso: ?renderer.juce::GradientEdgeTableRenderer juce::LinearGradientPixelGenerator>::.juce::LinearGradientPixelGenerator::grad? > may be used uninitialized in this function > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1310: > aviso: ?renderer.juce::GradientEdgeTableRenderer juce::LinearGradientPixelGenerator>::.juce::LinearGradientPixelGenerator::yTerm? > may be used uninitialized in this function > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1333: > aviso: ?renderer.juce::GradientEdgeTableRenderer juce::LinearGradientPixelGenerator>::.juce::LinearGradientPixelGenerator::start? > may be used uninitialized in this function > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1333: > aviso: ?renderer.juce::GradientEdgeTableRenderer juce::LinearGradientPixelGenerator>::.juce::LinearGradientPixelGenerator::grad? > may be used uninitialized in this function > ../../src/juce_appframework/gui/graphics/contexts/juce_LowLevelGraphicsSoftwareRenderer.cpp:1333: > aviso: ?renderer.juce::GradientEdgeTableRenderer juce::LinearGradientPixelGenerator>::.juce::LinearGradientPixelGenerator::yTerm? > may be used uninitialized in this function > juce_LowLevelGraphicsPostScriptRenderer.cpp > juce_Justification.cpp > juce_Graphics.cpp > juce_EdgeTable.cpp > juce_SVGParser.cpp > juce_Drawable.cpp > juce_DrawableText.cpp > juce_DrawablePath.cpp > juce_DrawableComposite.cpp > juce_DrawableImage.cpp > juce_DropShadowEffect.cpp > juce_GlowEffect.cpp > juce_ReduceOpacityEffect.cpp > juce_GlyphArrangement.cpp > juce_TextLayout.cpp > juce_Font.cpp > juce_Typeface.cpp > juce_Rectangle.cpp > juce_Point.cpp > juce_RectangleList.cpp > juce_BorderSize.cpp > juce_AffineTransform.cpp > juce_Path.cpp > juce_PathIterator.cpp > juce_PositionedRectangle.cpp > juce_Line.cpp > juce_PathStrokeType.cpp > juce_Image.cpp > juce_ImageConvolutionKernel.cpp > juce_ImageFileFormat.cpp > juce_ImageCache.cpp > juce_GIFLoader.cpp > juce_PNGLoader.cpp > juce_JPEGLoader.cpp > juce_Component.cpp > juce_Desktop.cpp > juce_ComponentListener.cpp > juce_ImageButton.cpp > juce_ArrowButton.cpp > juce_Button.cpp > juce_HyperlinkButton.cpp > juce_ShapeButton.cpp > juce_DrawableButton.cpp > juce_ToggleButton.cpp > juce_ToolbarButton.cpp > juce_TextButton.cpp > juce_ProgressBar.cpp > juce_TableHeaderComponent.cpp > juce_ListBox.cpp > juce_Toolbar.cpp > juce_ToolbarItemPalette.cpp > juce_Slider.cpp > juce_ToolbarItemComponent.cpp > juce_TreeView.cpp > juce_TableListBox.cpp > juce_TextEditor.cpp > juce_Label.cpp > juce_ComboBox.cpp > juce_FileChooserDialogBox.cpp > juce_FileSearchPathListComponent.cpp > juce_FileBrowserComponent.cpp > juce_FilenameComponent.cpp > juce_WildcardFileFilter.cpp > juce_FileTreeComponent.cpp > juce_DirectoryContentsList.cpp > juce_ImagePreviewComponent.cpp > juce_DirectoryContentsDisplayComponent.cpp > juce_FileChooser.cpp > juce_FileListComponent.cpp > juce_FileFilter.cpp > juce_KeyMappingEditorComponent.cpp > juce_KeyPressMappingSet.cpp > juce_KeyboardFocusTraverser.cpp > juce_KeyPress.cpp > juce_ModifierKeys.cpp > juce_KeyListener.cpp > juce_ResizableCornerComponent.cpp > juce_GroupComponent.cpp > juce_ComponentMovementWatcher.cpp > juce_ResizableBorderComponent.cpp > juce_MultiDocumentPanel.cpp > juce_TabbedComponent.cpp > juce_ScrollBar.cpp > juce_ComponentAnimator.cpp > juce_TabbedButtonBar.cpp > juce_ComponentBoundsConstrainer.cpp > juce_StretchableLayoutResizerBar.cpp > juce_StretchableLayoutManager.cpp > juce_StretchableObjectResizer.cpp > juce_Viewport.cpp > juce_OldSchoolLookAndFeel.cpp > juce_LookAndFeel.cpp > juce_PopupMenu.cpp > juce_MenuBarComponent.cpp > juce_MenuBarModel.cpp > juce_ComponentDragger.cpp > juce_MouseHoverDetector.cpp > juce_MouseEvent.cpp > juce_MouseListener.cpp > juce_DragAndDropContainer.cpp > juce_MouseCursor.cpp > juce_ButtonPropertyComponent.cpp > juce_TextPropertyComponent.cpp > juce_ChoicePropertyComponent.cpp > juce_SliderPropertyComponent.cpp > juce_PropertyPanel.cpp > juce_PropertyComponent.cpp > juce_BooleanPropertyComponent.cpp > juce_PreferencesPanel.cpp > juce_AudioDeviceSelectorComponent.cpp > juce_QuickTimeMovieComponent.cpp > juce_BubbleComponent.cpp > juce_OpenGLComponent.cpp > juce_MidiKeyboardComponent.cpp > juce_ColourSelector.cpp > juce_DropShadower.cpp > juce_MagnifierComponent.cpp > juce_BubbleMessageComponent.cpp > juce_SystemTrayIconComponent.cpp > juce_AlertWindow.cpp > juce_TooltipWindow.cpp > juce_ComponentPeer.cpp > juce_DocumentWindow.cpp > juce_ThreadWithProgressWindow.cpp > juce_ResizableWindow.cpp > juce_DialogWindow.cpp > juce_SplashScreen.cpp > juce_TopLevelWindow.cpp > juce_linux_AudioCDReader.cpp > juce_linux_Windowing.cpp > platform_specific_code/juce_linux_Windowing.cpp:52:34: aviso: > X11/extensions/XShm.h: Arquivo ou diret?rio inexistente > platform_specific_code/juce_linux_Windowing.cpp: In function ?bool > juce::isShmAvailable()?: > platform_specific_code/juce_linux_Windowing.cpp:409: erro: > ?XShmQueryVersion? was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:413: erro: ?XShmSegmentInfo? > was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:413: erro: expected `;' > before ?segmentInfo? > platform_specific_code/juce_linux_Windowing.cpp:414: erro: ?segmentInfo? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:416: erro: ?XShmCreateImage? > was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:430: erro: ?XShmAttach? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:433: erro: ?XShmDetach? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp: At global scope: > platform_specific_code/juce_linux_Windowing.cpp:649: erro: ?XShmSegmentInfo? > does not name a type > platform_specific_code/juce_linux_Windowing.cpp: In constructor > ?juce::XBitmapImage::XBitmapImage(juce::Image::PixelFormat, int, int, bool, > bool)?: > platform_specific_code/juce_linux_Windowing.cpp:477: erro: ?segmentInfo? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:479: erro: ?XShmCreateImage? > was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:498: erro: ?XShmAttach? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp: In destructor ?virtual > juce::XBitmapImage::~XBitmapImage()?: > platform_specific_code/juce_linux_Windowing.cpp:569: erro: ?segmentInfo? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:569: erro: ?XShmDetach? was > not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp: In member function ?void > juce::XBitmapImage::blitToWindow(Window, int, int, int, int, int, int)?: > platform_specific_code/juce_linux_Windowing.cpp:635: erro: ?XShmPutImage? > was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp: In constructor > ?juce::LinuxComponentPeer::LinuxRepaintManager::LinuxRepaintManager(juce::LinuxComponentPeer*)?: > platform_specific_code/juce_linux_Windowing.cpp:1688: erro: > ?XShmSegmentInfo? was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:1688: erro: expected `;' > before ?segmentinfo? > platform_specific_code/juce_linux_Windowing.cpp:1692: erro: ?segmentinfo? > was not declared in this scope > platform_specific_code/juce_linux_Windowing.cpp:1692: erro: > ?XShmCreateImage? was not declared in this scope > make[1]: ** [../../bin/intermediate_linux/Release/juce_linux_Windowing.o] > Erro 1 > make: ** [JUCE] Erro 2 > > Thanks, > Alexandre Ficagna > From njcross at sbcglobal.net Tue Mar 17 08:25:14 2009 From: njcross at sbcglobal.net (njcross) Date: Tue, 17 Mar 2009 08:25:14 -0700 Subject: [CM] cm2 and midishare Message-ID: <200903170825.14647.njcross@sbcglobal.net> I'll try this again. I would also like to build cm2 again, but when I went to download the MidiShare Interface from the cm site it had been removed: http://sourceforge.net/project/showfiles.php?group_id=9766&package_id=172112 I'd wish to build cm with midishare and use the gui. Is it possible now? From tejohnso at illinois.edu Tue Mar 17 13:55:48 2009 From: tejohnso at illinois.edu (Timothy Ernest Johnson) Date: Tue, 17 Mar 2009 15:55:48 -0500 (CDT) Subject: [CM] Windows softsynth Message-ID: <20090317155548.BVW60465@expms5.cites.uiuc.edu> Can anyone recommend a free standalone softsynth to use with GRACE in a Windows Vista environment? (analogous to SimpleSynth for OSX) Dr. Timothy Ernest Johnson Adjunct Faculty, Lewis University Adjunct Faculty, Columbia College Chicago From taube at uiuc.edu Tue Mar 17 14:57:37 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Tue, 17 Mar 2009 16:57:37 -0500 Subject: [CM] Windows softsynth In-Reply-To: <20090317155548.BVW60465@expms5.cites.uiuc.edu> References: <20090317155548.BVW60465@expms5.cites.uiuc.edu> Message-ID: <3A82F7BE-15B6-47A1-92D4-D363D91EF9E9@uiuc.edu> hi tim! the window's software synth should be available as a MidiOut device, look under Audio>Midiout for the device called "Microsoft GS Wavetable SW Synth" ive never seen it not listed before, its even available in my Parallels windows emulator on my mac! On Mar 17, 2009, at 3:55 PM, Timothy Ernest Johnson wrote: > Can anyone recommend a free standalone softsynth to use with GRACE > in a Windows Vista environment? (analogous to SimpleSynth for OSX) > > Dr. Timothy Ernest Johnson > Adjunct Faculty, Lewis University > Adjunct Faculty, Columbia College Chicago > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Wed Mar 18 04:16:44 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 06:16:44 -0500 Subject: [CM] cm2 setup on WinXP In-Reply-To: <200903181256.39206.ahcnz@ihug.co.nz> References: <200903161017.32926.ahcnz@ihug.co.nz> <57F11596-F7B0-4396-A250-E98CF989A67A@uiuc.edu> <200903181256.39206.ahcnz@ihug.co.nz> Message-ID: I have no idea, im using the same emacs and its working fine for me: This is GNU Emacs 22.3.1 (i386-mingw-nt5.1.2600) of 2008-09-06 on SOFT-MJASON when you get the spawning error, what is the value of your inferior- lisp-program variable? M-x: eval-expression inferior-lisp-program try setting it to the same value as cm-program ??? im just stabbing in the dark here, and wont be able to help you if this doesnt work. you can try googling Spawning child process: invalid argument From taube at uiuc.edu Wed Mar 18 04:28:47 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 06:28:47 -0500 Subject: [CM] cm2 setup on WinXP In-Reply-To: References: <200903161017.32926.ahcnz@ihug.co.nz> <57F11596-F7B0-4396-A250-E98CF989A67A@uiuc.edu> <200903181256.39206.ahcnz@ihug.co.nz> Message-ID: this sets both variables at the top before anything is loadd. make sure this is the complete contennts of your .emacs file, ie dont do anything else until you can get this to work (setq cm-program "C:/home/cm2/bin/cm-lisp.bat") (setq inferior-lisp-program cm-program) (add-to-list 'load-path "C:/home/slime/") (require 'slime) (slime-setup '(slime-repl)) (add-to-list 'load-path "C:/home/cm2/") (load "C:/home/cm2/etc/emacs/cm.el") (enable-cm-commands) From lievenmoors at hotmail.com Wed Mar 18 05:40:18 2009 From: lievenmoors at hotmail.com (Lieven Moors) Date: Wed, 18 Mar 2009 13:40:18 +0100 Subject: [CM] cm3 error Message-ID: Hi, I would like to report an error I get when starting cm3. This only happens on my 64bit computer, running Ubuntu Studio (it works on my i686 laptop with Ubuntu Studio), and only when I try to start it from a virtual terminal (with or without emacs). I have no problems when I start cm in emacs, from within an X session (not sure if it works without starting emacs first in X, I think it doesn't, but I can check later). The error I get is: "No protocol specified Failed to open the X display." I don't recall any errors while building cm. I could provide you with more details, but I'm not sure where to start. -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at uiuc.edu Wed Mar 18 06:09:48 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 08:09:48 -0500 Subject: [CM] cm2 setup on WinXP In-Reply-To: <200903190103.58503.ahcnz@ihug.co.nz> References: <200903161017.32926.ahcnz@ihug.co.nz> <200903190103.58503.ahcnz@ihug.co.nz> Message-ID: <7BE70C67-E48B-4BC7-810F-FCF853D0E8C7@uiuc.edu> sorry i have no other ideas. i dont have this behavior on my machine with the same components. From o.finnendahl at mh-freiburg.de Wed Mar 18 04:32:41 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Wed, 18 Mar 2009 12:32:41 +0100 Subject: [CM] midifile import Message-ID: <20090318113241.GC15841@varese> Hi, using the midifile functions of cm2 to import a file exported from the Muse Sequencer I ran into the following problems: 1. The time signature Meta event has length 2, which throws an error (bytes 3 and 4 are simply left out). 2. NoteOffs are coded as NoteOns with velocity 0. Rosegarden can deal with these things so I'm unsure whether Muse exports are valid or not (even if I couldn't find anything about 2 byte time signatures anywhere). As the changes are considerably small I wanted to let you know and would vote for being less strict about the time signature format and reinterpreting the NoteOn/Velocity 0 into NoteOff Messages (as this is common practice in communication between devices anyway). Below are the respective outputs of the MIDI Track Data (in Hex) of the same sequence in both forms to see the difference. Yours, Orm BTW: I also left a message on muse-devel (hope that doesn't start flames ;-) with NoteOff as NoteOn/Velocity0: ;dtime noteon pitch velo 00 90 1B 7F 83 00 1B 00 00 2B 7F 00 28 7F 83 00 2B 00 00 28 00 00 36 7F 00 34 7F 83 00 36 00 00 34 00 with NoteOff explicitely: ;dtime note-on/off pitch velo 00 90 1B 7F 83 00 80 1B 7F 00 90 2B 7F 00 28 7F 83 00 80 2B 7F 00 28 7F 00 90 36 7F 00 34 7F 83 00 80 36 7F 00 34 7F From dlphillips at woh.rr.com Wed Mar 18 06:31:55 2009 From: dlphillips at woh.rr.com (Dave Phillips) Date: Wed, 18 Mar 2009 09:31:55 -0400 Subject: [CM] midifile import In-Reply-To: <20090318113241.GC15841@varese> References: <20090318113241.GC15841@varese> Message-ID: <49C0F7CB.6000602@woh.rr.com> Orm Finnendahl wrote: > using the midifile functions of cm2 to import a file exported from > the Muse Sequencer I ran into the following problems: > [snip] > > 2. NoteOffs are coded as NoteOns with velocity 0. > > ... As the changes are considerably small > I wanted to let you know and would vote for being less strict about > the time signature format and reinterpreting the NoteOn/Velocity 0 > into NoteOff Messages (as this is common practice in communication > between devices anyway). > Hi Orm, I'm not sure what you mean by "devices" in this context. By far the greater number of (pre-21st century) hardware synthesizers employ the "note-on of 0 equals a note-off" method of silencing a MIDI note event. I've always felt a bit cheated by those manufacturers, since note-off velocity can be routed for some very interesting effects upon key release. Best, dp From taube at uiuc.edu Wed Mar 18 08:25:59 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 10:25:59 -0500 Subject: [CM] midifile import In-Reply-To: <20090318113241.GC15841@varese> References: <20090318113241.GC15841@varese> Message-ID: Hi are you saying you cant import a file because cm is doing something wrong? noteOn with zero velocity is valid midi and cm is explicity checking for so should parse it : [...] (or (= s +ml-note-off-opcode+) (and (= s +ml-note-on-opcode+) (= 0 (channel-message-data2 m)))) time signatures are four bytes and im pretty sure cm is writing and reading this correctly, ie it should signal an error if it doesnt read 4 bytes: [...] ((= byte +ml-file-time-signature-opcode+) (let ((len (read-variable-quantity fp))) (unless (= len 4) (err "unexpected time signature length: ~s" len)) if you cant import the file and the file is valid send it to me along with your import statement. if its not valid then whatever app wrote it should be fixed, if its Cm then send me the code so i can see whats going wrong btw there is a cm function (midi-file-print ...) that will print exactly what is in a valid file, you can pass it a :track value for level 1 files. > Hi, > > using the midifile functions of cm2 to import a file exported from > the Muse Sequencer I ran into the following problems: > > 1. The time signature Meta event has length 2, which throws an error > (bytes 3 and 4 are simply left out). > > 2. NoteOffs are coded as NoteOns with velocity 0. > > Rosegarden can deal with these things so I'm unsure whether Muse > exports are valid or not (even if I couldn't find anything about 2 > byte time signatures anywhere). As the changes are considerably small > I wanted to let you know and would vote for being less strict about > the time signature format and reinterpreting the NoteOn/Velocity 0 > into NoteOff Messages (as this is common practice in communication > between devices anyway). > > Below are the respective outputs of the MIDI Track Data (in Hex) of > the same sequence in both forms to see the difference. > > Yours, > Orm > > BTW: I also left a message on muse-devel (hope that doesn't start > flames ;-) > > with NoteOff as NoteOn/Velocity0: > > ;dtime noteon pitch velo > 00 90 1B 7F > 83 00 1B 00 > 00 2B 7F > 00 28 7F > 83 00 2B 00 > 00 28 00 > 00 36 7F > 00 34 7F > 83 00 36 00 > 00 34 00 > > with NoteOff explicitely: > > ;dtime note-on/off pitch velo > 00 90 1B 7F > 83 00 80 1B 7F > 00 90 2B 7F > 00 28 7F > 83 00 80 2B 7F > 00 28 7F > 00 90 36 7F > 00 34 7F > 83 00 80 36 7F > 00 34 7F > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Wed Mar 18 08:31:44 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 10:31:44 -0500 Subject: [CM] cm3 error In-Reply-To: References: Message-ID: Hi, i have no idea about this. i dont have a studio64 machine to test on, sorry. --rick On Mar 18, 2009, at 7:40 AM, Lieven Moors wrote: > Hi, I would like to report an error I get when > starting cm3. This only happens on my 64bit computer, > running Ubuntu Studio (it works on my i686 laptop with Ubuntu > Studio), and only when I try to start it from a virtual terminal (with > or without emacs). I have no problems when I start cm in emacs, > from within an X session (not sure if it works without starting emacs > first in X, > I think it doesn't, but I can check later). > > The error I get is: > > "No protocol specified > Failed to open the X display." > > I don't recall any errors while building cm. I could provide you > with more details, but I'm not sure where to start. > > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Wed Mar 18 10:34:48 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 12:34:48 -0500 Subject: [CM] cm3 error In-Reply-To: References: Message-ID: take a look at cm3's scale function, it does bascially what cm2's modes and tunings did only much simpler (ie no objects its just a list ). the word 'tuning' is not stated explicily in the doc but the steps you pass to scale can be floating point key numbers, which are equivalent to hertz, which would make it a 'tuning' in cm2 speak http://commonmusic.sourceforge.net/cm/res/doc/cm.html#scale On Mar 18, 2009, at 12:01 PM, Lieven Moors wrote: > That's ok, I can use cm without it as well, which > makes me very happy, by the way... Maybe I'll try > to do a little debugging myself, as an exercise :-) > > > I really like the way cm3 is going, a function like 'fit' f.e. really > makes my day... > Because I didn't find the old modes and tunings funtions in the new > dictionary, > and because I wanted to see if I could do it myself, I wrote some code > to replace it. > > Basically what it does is this: > > You can make a new mode like this (define *mode* (make-mode 60 0 2)) > where 60 is the base note, 0 is the starting index, and 2 is the > number > of flats or sharps > (a negative int would be flats). *mode* is a closure which you can > transpose with > (transpose-mode *mode* 2), where 2 is number of flarps again. And you > can get a note > within the mode with (next-note *mode* 4), where 4 is a step within > the > mode (which can > be negative). For example if you are in mode C on index 0, a step of > four would take you > 2+2+1+2 = 7 halfnotes up. I do all of this with one vector #(2 2 1 2 > 2 2 > 1), without hash tables. > I only did it very roughly, but things seem to work as expected so > far. > > I was curious if you would be interested to have a look at it, I'm > going > to license all of > my work under GPL or LGPL (don't know the difference yet) anyway... > > Well, thanks again for all your help, > > Greetings, > > Lieven Moors > > > > > > > Heinrich Taube wrote: > > Hi, i have no idea about this. i dont have a studio64 machine to > test > > on, sorry. > > --rick > > > > On Mar 18, 2009, at 7:40 AM, Lieven Moors wrote: > > > >> Hi, I would like to report an error I get when > >> starting cm3. This only happens on my 64bit computer, > >> running Ubuntu Studio (it works on my i686 laptop with Ubuntu > >> Studio), and only when I try to start it from a virtual terminal > (with > >> or without emacs). I have no problems when I start cm in emacs, > >> from within an X session (not sure if it works without starting > emacs > >> first in X, > >> I think it doesn't, but I can check later). > >> > >> The error I get is: > >> > >> "No protocol specified > >> Failed to open the X display." > >> > >> I don't recall any errors while building cm. I could provide you > >> with more details, but I'm not sure where to start. > >> > >> > >> > >> _______________________________________________ > >> Cmdist mailing list > >> Cmdist at ccrma.stanford.edu > >> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > From taube at uiuc.edu Wed Mar 18 12:13:05 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 14:13:05 -0500 Subject: [CM] cm3 error In-Reply-To: References: Message-ID: first...its great that your implementing your own code! for transposing in cm3 you could just use the 'plus' function -- its overloaded to handle common list procssing like this. so you just pass it the scale as the first arg and the distance you want to transpose it as the second: (plus '(60 62 64} 7) => (67 69 71) so the only bit of code you need (i guess...) is a function that converts two keysigs to the semitone interval distance between them. if you encode signatures using signed ints where 0=C -7= seven flats and 7=seven sharps something like this might work i think (define (sigdiff sig1 sig2) (modulo (* 7 (- sig2 sig1)) 12)) (sigdiff -3 3) ; ef to a => 6 (sigdiff -3 2) ; ef to d => 11 (sigdiff 0 1) ; c to g => 7 (sigdiff 0 -1) ; c to f => 5 On Mar 18, 2009, at 1:36 PM, Lieven Moors wrote: > I see, I had a look at it already, but didn't realize that I could > pass > a list of steps. > (should have read the manual better...). But still that doesn't solve > the problem > of transposing the mode. I wanted to be able to say: transpose this > mode > up or > down with n flats or sharps, and always do the right thing... Do you > think there > is a simple way to do this? > > greets > From njcross at sbcglobal.net Wed Mar 18 13:24:27 2009 From: njcross at sbcglobal.net (njcross) Date: Wed, 18 Mar 2009 13:24:27 -0700 Subject: [CM] cm2 and midishare In-Reply-To: <200903170825.14647.njcross@sbcglobal.net> References: <200903170825.14647.njcross@sbcglobal.net> Message-ID: <200903181324.28242.njcross@sbcglobal.net> I'll try again. If anyone has file midishare-1.0.0.tar.gz, midishare-1.0.1.tar.gz, midishare-1.0.0.tar.gz or knows where I can still download these old files, they are no longer available from the cm sourceforge site, please let me know. Thank you. On Tuesday 17 March 2009 08:25:14 am njcross wrote: > I'll try this again. I would also like to build cm2 again, but when I went > to download the MidiShare Interface from the cm site it had been removed: > http://sourceforge.net/project/showfiles.php?group_id=9766&package_id=17211 >2 > > I'd wish to build cm with midishare and use the gui. Is it possible now? > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Wed Mar 18 13:13:28 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Wed, 18 Mar 2009 15:13:28 -0500 Subject: [CM] cm2 and midishare In-Reply-To: <200903181324.28242.njcross@sbcglobal.net> References: <200903170825.14647.njcross@sbcglobal.net> <200903181324.28242.njcross@sbcglobal.net> Message-ID: <0C5B5446-6BFB-4D47-9058-9F4FE3CED71E@uiuc.edu> sorry ill send you a tarball. i just have to dig it up, On Mar 18, 2009, at 3:24 PM, njcross wrote: > > I'll try again. If anyone has file midishare-1.0.0.tar.gz, > midishare-1.0.1.tar.gz, midishare-1.0.0.tar.gz or knows where I can > still > download these old files, they are no longer available from the cm > sourceforge site, please let me know. Thank you. > On Tuesday 17 March 2009 08:25:14 am njcross wrote: >> I'll try this again. I would also like to build cm2 again, but when >> I went >> to download the MidiShare Interface from the cm site it had been >> removed: >> http://sourceforge.net/project/showfiles.php?group_id=9766&package_id=17211 >> 2 >> >> I'd wish to build cm with midishare and use the gui. Is it possible >> now? >> >> _______________________________________________ >> 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 From andersvi at notam02.no Thu Mar 19 04:58:28 2009 From: andersvi at notam02.no (andersvi at notam02.no) Date: Thu, 19 Mar 2009 12:58:28 +0100 Subject: [CM] various snd-10 - motif and gtk troubles Message-ID: <871vstwwpn.fsf@notam02.no> Hi there. Ive built both gtk and motif versions of latest snd from the tarball at ccrma, and they both break on various places when trying to include the 'extra menus' stuff in the preferences. Ive tried running under gdb, but dont get any stack-trace or locals at all. Surely im doing something wrong here, but the snd is compiled with -g and (i think) im following the hints in README.snd. GTK: The gtk-version breaks when pushing the first one (the 'context-sensitive pop-up' menu: ERROR: Unbound variable: gtk_menu_new The motif-version breaks on 2 places, dependent on whether xm is linked statically or not. XM STATIC: In the static version it breaks when trying to include either the 'marks or the 'toolbar knob: ERROR: In procedure XLoadQueryFont: ERROR: Wrong type argument in position 2 (expecting char*): #f XM DYNAMIC: In the non-static case it breaks on the same place as the gtk-version (the 'context-sensitive...), with the error: ERROR: Unbound variable: XmNbackground This is on a ubuntu-dist, and im using libmotif-dev (2.2.3-2) for the motif-version. Any hints? -anders From andersvi at notam02.no Thu Mar 19 05:13:53 2009 From: andersvi at notam02.no (andersvi at notam02.no) Date: Thu, 19 Mar 2009 13:13:53 +0100 Subject: [CM] various snd-10 - motif and gtk troubles In-Reply-To: <871vstwwpn.fsf@notam02.no> (andersvi@notam02.no's message of "Thu, 19 Mar 2009 12:58:28 +0100") References: <871vstwwpn.fsf@notam02.no> Message-ID: <87wsalvhfi.fsf@notam02.no> motif-version now: the 'TAB-completion' feature has been one of the main reasons ive sticked with the motif-version of snd. Besides the menu-shortcuts (typing Alt-f to access file-menu etc.) used to work fine in the motif-version. None of these work anymore. It seems to work in gtk however. Hmm, maybe its time to switch... Whats missing in the gtk-version now is the menu-shortcuts and the bugs reported in the previous email. Any clues? -anders From taube at uiuc.edu Thu Mar 19 06:06:15 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Thu, 19 Mar 2009 08:06:15 -0500 Subject: [CM] midifile import In-Reply-To: <20090319122241.GA9368@varese> References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> Message-ID: orm i would not want to add anything that actually imports non- standard messages. however perhaps adding control over whether cm actually signals an error or just a warning for illegal messages would be useful? so to import a midifile with bogus messages dropped you would do (midi-file-import ... :strict nil) On Mar 19, 2009, at 7:22 AM, Orm Finnendahl wrote: > Hi Rick, > > I doublechecked the state of affairs and as far as I can see cm isn't > doing anything wrong. > > There are two things in the exported file, cm doesn't like (I > erroneously thought the 2nd was related to the NoteOffs as NoteOns > with velocity 0): > > 1. The time signature has a length of 2 > > 2. There is a midi meta event of unknown type (#x0F) From bil at ccrma.Stanford.EDU Thu Mar 19 07:05:09 2009 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Thu, 19 Mar 2009 07:05:09 -0700 Subject: [CM] various snd-10 - motif and gtk troubles In-Reply-To: <871vstwwpn.fsf@notam02.no> References: <871vstwwpn.fsf@notam02.no> Message-ID: <20090319140052.M83678@ccrma.Stanford.EDU> Except for the XLoadQueryFont problem, I think all of the problems are the same -- you don't have the xm.so module loaded, and the scheme code can't find xm.so (or xg.so) -- if you were running Snd from a terminal, you'd get an error message. Perhaps I should launch an error monolog, or (in the preferences dialog), post the error message in that dialog. The XLoadQueryFont bug is a side-effect of trying to get the xm module to work in 64-bit machines -- I forgot that #f = null in this case. On the menu accelerators and tab-completion in Motif 2.2.3, both work fine for me. Does Ubuntu mess with Motif in any way? I had menu "accelerators" in gtk originally, but removed them. Can't remember why -- I'll look at them again. From o.finnendahl at mh-freiburg.de Thu Mar 19 05:22:42 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Thu, 19 Mar 2009 13:22:42 +0100 Subject: [CM] midifile import In-Reply-To: References: <20090318113241.GC15841@varese> Message-ID: <20090319122241.GA9368@varese> Hi Rick, I doublechecked the state of affairs and as far as I can see cm isn't doing anything wrong. There are two things in the exported file, cm doesn't like (I erroneously thought the 2nd was related to the NoteOffs as NoteOns with velocity 0): 1. The time signature has a length of 2 2. There is a midi meta event of unknown type (#x0F) The meta event is displayed by Muse as a "comment" and is containing ascii characters. I couldn't find any information in the web about that meta event type. Neither could I find anything about the validity of time signatures of length 2 (the midi file format specs I have actually quite clearly state the opposite but that might be outdated). The fact that Rosegarden *can* import the file doesn't necessarily mean that the file is adhering to the standard. I will wait about comments from the Muse developers. In order to avoid trouble with those files in my work, I changed the respective functions to be less strict about 2 byte time signatures (using sensible defaults and issuing a warning) and adding a "comment" meta event type and the respective handler functions, params etc. If anybody is interested, let me know. Yours, Orm Am Mittwoch, den 18. M?rz 2009 um 10:25:59 Uhr (-0500) schrieb Rick Taube: > Hi are you saying you cant import a file because cm is doing something > wrong? > > noteOn with zero velocity is valid midi and cm is explicity checking > for so should parse it : > [...] > (or (= s +ml-note-off-opcode+) > (and (= s +ml-note-on-opcode+) > (= 0 (channel-message-data2 m)))) > > time signatures are four bytes and im pretty sure cm is writing and > reading this correctly, ie it should signal an error if it doesnt read > 4 bytes: > [...] > ((= byte +ml-file-time-signature-opcode+) > (let ((len (read-variable-quantity fp))) > (unless (= len 4) > (err "unexpected time signature length: ~s" len)) > > if you cant import the file and the file is valid send it to me along > with your import statement. > if its not valid then whatever app wrote it should be fixed, if its Cm > then send me the code so i can see whats going wrong > > btw there is a cm function > (midi-file-print ...) > > that will print exactly what is in a valid file, you can pass it > a :track value for level 1 files. > > > > > Hi, > > > > using the midifile functions of cm2 to import a file exported from > > the Muse Sequencer I ran into the following problems: > > > > 1. The time signature Meta event has length 2, which throws an error > > (bytes 3 and 4 are simply left out). > > > > 2. NoteOffs are coded as NoteOns with velocity 0. > > > > Rosegarden can deal with these things so I'm unsure whether Muse > > exports are valid or not (even if I couldn't find anything about 2 > > byte time signatures anywhere). As the changes are considerably small > > I wanted to let you know and would vote for being less strict about > > the time signature format and reinterpreting the NoteOn/Velocity 0 > > into NoteOff Messages (as this is common practice in communication > > between devices anyway). > > > > Below are the respective outputs of the MIDI Track Data (in Hex) of > > the same sequence in both forms to see the difference. > > > > Yours, > > Orm > > > > BTW: I also left a message on muse-devel (hope that doesn't start > > flames ;-) > > > > with NoteOff as NoteOn/Velocity0: > > > > ;dtime noteon pitch velo > > 00 90 1B 7F > > 83 00 1B 00 > > 00 2B 7F > > 00 28 7F > > 83 00 2B 00 > > 00 28 00 > > 00 36 7F > > 00 34 7F > > 83 00 36 00 > > 00 34 00 > > > > with NoteOff explicitely: > > > > ;dtime note-on/off pitch velo > > 00 90 1B 7F > > 83 00 80 1B 7F > > 00 90 2B 7F > > 00 28 7F > > 83 00 80 2B 7F > > 00 28 7F > > 00 90 36 7F > > 00 34 7F > > 83 00 80 36 7F > > 00 34 7F > > > > _______________________________________________ > > 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 From o.finnendahl at mh-freiburg.de Thu Mar 19 06:39:09 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Thu, 19 Mar 2009 14:39:09 +0100 Subject: [CM] midifile import In-Reply-To: References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> Message-ID: <20090319133909.GA28124@varese> Rick, Am Donnerstag, den 19. M?rz 2009 um 08:06:15 Uhr (-0500) schrieb Rick Taube: > orm i would not want to add anything that actually imports non-standard > messages. I certainly agree (and wouldn't do it either). > however perhaps adding control over whether cm actually signals an error > or just a warning for illegal messages would be useful? > so to import a midifile with bogus messages dropped you would do > (midi-file-import ... :strict nil) Sounds like an excellent idea to me! -- Orm From rm at seid-online.de Thu Mar 19 07:23:59 2009 From: rm at seid-online.de (Ralf Mattes) Date: Thu, 19 Mar 2009 15:23:59 +0100 Subject: [CM] midifile import In-Reply-To: <20090319133909.GA28124@varese> References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> <20090319133909.GA28124@varese> Message-ID: <1237472639.7511.14.camel@mhflaptop01> On Thu, 2009-03-19 at 14:39 +0100, Orm Finnendahl wrote: > Rick, Hi everyone, > > Am Donnerstag, den 19. M?rz 2009 um 08:06:15 Uhr (-0500) schrieb Rick Taube: > > orm i would not want to add anything that actually imports non-standard > > messages. > > I certainly agree (and wouldn't do it either). > > however perhaps adding control over whether cm actually signals an error > > or just a warning for illegal messages would be useful? > > so to import a midifile with bogus messages dropped you would do > > (midi-file-import ... :strict nil) > > Sounds like an excellent idea to me! Sorry, but why not use the wonderful features of Common Lisp? Recovering from parsing errors/problems seems like the perfect job for conditions and restarts. Just define a condition like: (define-condition midifile-error (error) ((message :initarg :message :accessor message-of :documentation "Some meaningful error message") (tick-time :initarg :tick-time :accessor tick-time-of :documentation "When in the stream did the parsing error happen) (part :initarg :part :accessor part-of :documentation "Waht part is messed up"))) (defun midifile-error (message &key tick-time part) (error midifile-error :message message :part part :tick-time tick-ime)) and then later on use (midifile-error "Parse time signature: expected 4 byte but only got 2" :ticks ticks) and add some useful restarts to the parsing code (like ignore-message, use-data, abort ...). Cheers, RalfD > -- > Orm > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From rm at seid-online.de Thu Mar 19 07:37:03 2009 From: rm at seid-online.de (Ralf Mattes) Date: Thu, 19 Mar 2009 15:37:03 +0100 Subject: [CM] midifile import In-Reply-To: <20090319122241.GA9368@varese> References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> Message-ID: <1237473423.7511.19.camel@mhflaptop01> On Thu, 2009-03-19 at 13:22 +0100, Orm Finnendahl wrote: > Hi Rick, > > I doublechecked the state of affairs and as far as I can see cm isn't > doing anything wrong. > > There are two things in the exported file, cm doesn't like (I > erroneously thought the 2nd was related to the NoteOffs as NoteOns > with velocity 0): > > 1. The time signature has a length of 2 > > 2. There is a midi meta event of unknown type (#x0F) > > The meta event is displayed by Muse as a "comment" and is containing > ascii characters. I couldn't find any information in the web about > that meta event type. Somehow i using comments in midi files, but that was on a distant Mac in a different life :-) I'd just ignore unknown messages. > Neither could I find anything about the validity > of time signatures of length 2 (the midi file format specs I have > actually quite clearly state the opposite but that might be outdated). > > The fact that Rosegarden *can* import the file doesn't necessarily > mean that the file is adhering to the standard. I will wait about > comments from the Muse developers. Hey, this _is_ Open Source. Just read it: case MIDI_TIME_SIGNATURE: numerator = (int) (*midiEvent)->getMetaMessage()[0]; denominator = 1 << ((int)(*midiEvent)->getMetaMessage()[1]); // NB. a MIDI time signature also has // metamessage[2] and [3], containing some timing data if (numerator == 0) numerator = 4; if (denominator == 0) denominator = 4; So the Rosegarden programmers just decided to always ignore part of the time signature message. Tsk. Cheers, RalfD From o.finnendahl at mh-freiburg.de Thu Mar 19 07:38:19 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Thu, 19 Mar 2009 15:38:19 +0100 Subject: [CM] midifile import In-Reply-To: <1237472639.7511.14.camel@mhflaptop01> References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> <20090319133909.GA28124@varese> <1237472639.7511.14.camel@mhflaptop01> Message-ID: <20090319143819.GC28124@varese> Ralf, I had similar ideas (expecially after reading the Seibel book), but I abandoned it realising that the lisp code actually seems to get autogenerated from scheme code. And I guess that can become quite tricky... -- Orm Am Donnerstag, den 19. M?rz 2009 um 15:23:59 Uhr (+0100) schrieb Ralf Mattes: > On Thu, 2009-03-19 at 14:39 +0100, Orm Finnendahl wrote: > > Rick, > > Hi everyone, > > > > > Am Donnerstag, den 19. M?rz 2009 um 08:06:15 Uhr (-0500) schrieb Rick Taube: > > > orm i would not want to add anything that actually imports non-standard > > > messages. > > > > I certainly agree (and wouldn't do it either). > > > > however perhaps adding control over whether cm actually signals an error > > > or just a warning for illegal messages would be useful? > > > so to import a midifile with bogus messages dropped you would do > > > (midi-file-import ... :strict nil) > > > > Sounds like an excellent idea to me! > > Sorry, but why not use the wonderful features of Common Lisp? Recovering > from parsing errors/problems seems like the perfect job for conditions > and restarts. Just define a condition like: > > (define-condition midifile-error (error) > ((message :initarg :message > :accessor message-of > :documentation "Some meaningful error message") > (tick-time :initarg :tick-time > :accessor tick-time-of > :documentation "When in the stream did the parsing error > happen) > (part :initarg :part > :accessor part-of > :documentation "Waht part is messed up"))) > > (defun midifile-error (message &key tick-time part) > (error midifile-error :message message :part part :tick-time > tick-ime)) > > and then later on use > > (midifile-error "Parse time signature: expected 4 byte but only got > 2" :ticks ticks) > > > and add some useful restarts to the parsing code (like ignore-message, > use-data, abort ...). > > Cheers, RalfD > > > > -- > > Orm > > > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From o.finnendahl at mh-freiburg.de Thu Mar 19 07:45:43 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Thu, 19 Mar 2009 15:45:43 +0100 Subject: [CM] midifile import In-Reply-To: <1237473423.7511.19.camel@mhflaptop01> References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> <1237473423.7511.19.camel@mhflaptop01> Message-ID: <20090319144543.GD28124@varese> Am Donnerstag, den 19. M?rz 2009 um 15:37:03 Uhr (+0100) schrieb Ralf Mattes: > > Somehow i using comments in midi files, but that was on a distant Mac in > a different life :-) I'd just ignore unknown messages. These "comments" in Muse are track specific: You can edit them by rightclicking on the track name. This also exists for DAWs like ardour so I guess that's where the idea stems from but apparently this is not standarized in the midi file format. -- Orm From taube at uiuc.edu Thu Mar 19 08:24:26 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Thu, 19 Mar 2009 10:24:26 -0500 Subject: [CM] midifile import In-Reply-To: <1237472639.7511.14.camel@mhflaptop01> References: <20090318113241.GC15841@varese> <20090319122241.GA9368@varese> <20090319133909.GA28124@varese> <1237472639.7511.14.camel@mhflaptop01> Message-ID: <667C21AF-9880-4EC0-AC6D-9D63927CB632@uiuc.edu> > > Sorry, but why not use the wonderful features of Common Lisp? > Recovering > cm2 is also meant to work in scheme -- there is a srfi condition system for scheme but i have to look into it. but it would not be hard to wrap the errors im currently triggering with something that checks o see if sould just print the warning and continue. On Mar 19, 2009, at 9:23 AM, Ralf Mattes wrote: From taube at uiuc.edu Thu Mar 19 10:32:21 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Thu, 19 Mar 2009 12:32:21 -0500 Subject: [CM] CM 3 / Emacs In-Reply-To: <1e6b7d810903190930y4224c59u4021ce1ffd0b9386@mail.gmail.com> References: <1e6b7d810903190930y4224c59u4021ce1ffd0b9386@mail.gmail.com> Message-ID: <1F0472F9-7E8D-4385-9700-37056995F38E@uiuc.edu> hi yes i forgot to add this to the docs, it'll be there in the next release. in the meantime this is what you do: 1. use the ports funciont to find out what is avaiable: (ports) (("midi.port" (0 -> "IAC Driver Bus 1" #f) (0 <- "IAC Driver Bus 1" #f))) note that the -> means output and <- means input. t 2. use the mp:open function to open the port you want. for example this will output the midi output device 0 and (mp:open 0) this will open the output device 0 and the input device 0: (mp:open 0 0) NB: the name (ports) is not a good name and will probably change when the upcoming release happens, maybe it'll become (describe-audio) or something. ill be certain to point that out in the changelog. On Mar 19, 2009, at 11:30 AM, Neil Baylis wrote: > Hi Rick, > > I'm attempting to use CM with Emacs, instead of via Grace. It seems > there might be some items that only work via Grace. For example, in > the REPL, how would I select the MIDI Out port? I've been searching > the documentation for this, but haven't found it ... it just says to > use the menu item. Do all the menu items have scheme equivalents? > > (I'm using the Leopard/Intel version of CM) > > Thanks, > > Neil Baylis > > -- > http://www.pixpopuli.com From sr at seanreed.ie Fri Mar 20 07:07:18 2009 From: sr at seanreed.ie (Sean Reed) Date: Fri, 20 Mar 2009 14:07:18 +0000 Subject: [CM] CM Clisp 2.46 Cygwin shell start and bat file Vista 32 Message-ID: Hi, I have a question concerning CM 2.10 on Vista32 with Cygwin and Clisp2.46. Would anyone have a hint on getting CM to load and start from cygwin- bash (and xemacs M-x prompt) by just typing "cm" on the above system? At the moment it loads all the fasls but exits back to the normal bash prompt for me. Background: I installed Clisp2.46 through the Cygwin.setup installer. I have created a symbolic link to cm.sh in the /bin directory. When I type cm at the cygwin-bash prompt, the .fasls are loaded and the CM logo appears, but then the shell returns to the normal bash prompt. I discovered from reading through the archives that the cm.bat file may be necessary for this to work. However, no cm.bat file is generated in /usr/local/lisp/cm/bin/ when I start clisp from the cygwin-bash and (load "/path/to/cm.lisp") This also means that setq-ing the cm-program to the cm.bat file in the .xemacs/init.el is not possible. When I start clisp from the cygwin-bash shell (or xemacs-slime), then (load "/usr/local/lisp/cm/src/cm.lisp") everything functions fine; however, when at the cygwin-bash prompt I type cm -l clisp or clisp -x "(load \"/usr/local/lisp/cm/src/cm.lisp\")" the same thing happens as I described above: all the .fasls are loaded, the logo appears, and the shell returns to the normal bash prompt. I am setting up CM for a teaching situation. Although I can get it to work by loading everything separately (either through xemacs-slime or bash-shell clisp then load cm.lisp), an environment where the students can just type "cm" would be much easier on their command-line-challenged brains. Thanks for any assistance, Sean ------------------------- Sean Reed Dublin sr at seanreed.ie www.seanreed.ie -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at uiuc.edu Fri Mar 20 07:54:40 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 09:54:40 -0500 Subject: [CM] CM Clisp 2.46 Cygwin shell start and bat file Vista 32 In-Reply-To: References: Message-ID: > When I type cm at the cygwin-bash prompt, the .fasls are loaded and > the CM logo appears, but then the shell returns to the normal bash > prompt. hi try starting clisp first, then loading cm2/src/cm.lisp into it. if that works write a script that does that. Im soory I cant help with the windows/emacs/cygwin shell stuff anymore. its very frustrating trying to deal with all the randomness, and its why ive attempted to move away from it and provide systems that I have a better chance of supporting. i do have Grace + cm3 that works on windows, it doesnt need installing, its scorefile and realtime schediing and ports and midi and clm and csound and it has an emacs editor with synax highlighting. i do have GraceCL + cm2 that works on windows, you should be able to start clisp in it if these systems dont work then tell me what the problem is and i have a reasonable chance of fixing it. if there is something that these systems lack tell me and ill add it. but i simply dont have the time or energy anymore to figure out all the weird things that happen in windows + common lisp environments, im sorry! On Mar 20, 2009, at 9:07 AM, Sean Reed wrote: > Hi, > > I have a question concerning CM 2.10 on Vista32 with Cygwin and > Clisp2.46. > > Would anyone have a hint on getting CM to load and start from cygwin- > bash (and xemacs M-x prompt) by just typing "cm" on the above system? > > At the moment it loads all the fasls but exits back to the normal > bash prompt for me. > > > Background: > I installed Clisp2.46 through the Cygwin.setup installer. > > I have created a symbolic link to cm.sh in the /bin directory. > When I type cm at the cygwin-bash prompt, the .fasls are loaded and > the CM logo appears, but then the shell returns to the normal bash > prompt. > > I discovered from reading through the archives that the cm.bat file > may be necessary for this to work. > However, no cm.bat file is generated in /usr/local/lisp/cm/bin/ when > I start clisp from the cygwin-bash and (load "/path/to/cm.lisp") > This also means that setq-ing the cm-program to the cm.bat file in > the .xemacs/init.el is not possible. > > When I start clisp from the cygwin-bash shell (or xemacs-slime), > then (load "/usr/local/lisp/cm/src/cm.lisp") everything functions > fine; however, when at the cygwin-bash prompt I type > > cm -l clisp > > or > > clisp -x "(load \"/usr/local/lisp/cm/src/cm.lisp\")" > > the same thing happens as I described above: all the .fasls are > loaded, the logo appears, and the shell returns to the normal bash > prompt. > > I am setting up CM for a teaching situation. > Although I can get it to work by loading everything separately > (either through xemacs-slime or bash-shell clisp then load cm.lisp), > an environment where the students can just type "cm" would be much > easier on their command-line-challenged brains. > > Thanks for any assistance, > Sean > > > ------------------------- > Sean Reed > Dublin > sr at seanreed.ie > www.seanreed.ie > > > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Fri Mar 20 08:01:05 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 10:01:05 -0500 Subject: [CM] CM Clisp 2.46 Cygwin shell start and bat file Vista 32 In-Reply-To: References: Message-ID: <079EFBBC-FD74-4DCB-9AFD-ABDD7DA6F710@uiuc.edu> did you see my post a few days ago on running cm in emacs? ive included it at the bottom of this message if you use that then your students just have to type m-x: cm it works witht he latest emacs and cm2 on my windwos box if you can get that to work, and it doestn work with cm 2.10 then I can fix that im sure. but i dont want to do that unless you get it working at all. On Mar 20, 2009, at 9:07 AM, Sean Reed wrote: > Although I can get it to work by loading everything separately > (either through xemacs-slime or bash-shell clisp then load cm.lisp), > an environment where the students can just type "cm" would be much > easier on their command-line-challenged brains. > Hi there were some changes in recent slimes that caused things to not work but ive made fixes to cm/etc/emacs/cm.el and checked them into svn. I just reinstalled cm2 + clisp + emacs + slime from scratch on my windows box and I dont have any problems now. So rather than try to fix you problem Ill just tell you what I did. its basically a two step proccess; (1) installing lisp and (2) configureing emacs Install clisp and cm on my local machine ( c: /Software/cm2 and c:/ Sofware/clisp-2.47) 1 svn'ed the lastest cm2 from today ( REV 1688 / cm 2.11.3) into my C:/Software folder: svn co https://commonmusic.svn.sf.net/svnroot/commonmusic/branches/cm2 2 dowloaded and installed the latest clisp (clisp-2.47-win32-mingw- big.zip) into c:/Software/clisp-2.47 3 double-clicked C:/Software/clisp-2.47/install.bat to install clisp and typed 'y' to add a GNU-CLISP desktop icon to start clisp 4 double-clicked the GNU-CLISP icon on my desktop to start clisp 5 Loaded cm.lisp to build the system and to save cm2/bin/cm-clisp.bat : (load "/Software/cm2/src/cm.lisp") 6 Quit Clisp At this point CM is compiled and it saved a CM startup script in cm2/ bin: C:/Software/cm2/bin/cm-clisp.bat Configuring Emacs 1. downloaded the latest cvs snapshot of Slime into c:/Software/ slime-2009-03-16 2. Started Emacs and edited my Emacs init file: ~/.emacs 3. Added the following to the top of my .emacs file. you have to change the directories for your machine: (add-to-list 'load-path "/Software/slime-2009-03-16/") (require 'slime) (slime-setup '(slime-repl)) (setq cm-program "/Software/cm2/bin/cm-clisp.bat") (add-to-list 'load-path "/Software/cm2/") (load "etc/emacs/cm.el") (enable-cm-commands) 4. saved .emacs file, the quit and restarted Emacs to make the changes to .emacs take effect. 3. Started CM by typeing M-x: cm Cm starts up in a slime repl window. I can eval stuff from a .lisp buffer without problems. On Mar 15, 2009, at 5:17 PM, Adam wrote: _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From o.finnendahl at mh-freiburg.de Fri Mar 20 08:31:46 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Fri, 20 Mar 2009 16:31:46 +0100 Subject: [CM] rts in cm-2 Message-ID: <20090320153146.GB29837@varese> Hi, what is the state of rtf in cm-2? I tried to load it and got this: (use-system :rts) ; Can't locate system file "rts.asd" in asdf:*central-registry* or under "/LISP/cm2/*/rts.asd". Specify location using :directory arg to use-system. Looks as if I'm missing the relevant files. I use cm2 with sbcl on linux (checkout a couple of days ago), so I guess it should be possible to get it up and running. Is there something on the server relating to rts and, if so, which command obtains it? Yours, Orm From o.finnendahl at mh-freiburg.de Fri Mar 20 08:41:28 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Fri, 20 Mar 2009 16:41:28 +0100 Subject: [CM] rts in cm-2 Message-ID: <20090320154128.GC29837@varese> Hi all, Sorry, my mail contained a typo. As you might have guessed, I'm curious to know about the state of "rts" in cm and not "rtf"... -- Orm From taube at uiuc.edu Fri Mar 20 09:39:14 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 11:39:14 -0500 Subject: [CM] rts in cm-2 In-Reply-To: <20090320153146.GB29837@varese> References: <20090320153146.GB29837@varese> Message-ID: <8AFBFA24-99C7-4966-8212-5EAA39FA6190@uiuc.edu> do you have the rts software installed? it should be in the same parent directory as cm2, eg /software/cm2 /software/rts if you dont have the software i can make it available again On Mar 20, 2009, at 10:31 AM, Orm Finnendahl wrote: > Hi, > > what is the state of rtf in cm-2? I tried to load it and got this: > > (use-system :rts) > ; Can't locate system file "rts.asd" in asdf:*central-registry* or > under "/LISP/cm2/*/rts.asd". Specify location using :directory arg > to use-system. > > Looks as if I'm missing the relevant files. I use cm2 with sbcl on > linux (checkout a couple of days ago), so I guess it should be > possible to get it up and running. Is there something on the server > relating to rts and, if so, which command obtains it? > > Yours, > Orm > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Fri Mar 20 09:50:27 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 11:50:27 -0500 Subject: [CM] midishare and rts and gracecl packages In-Reply-To: <20090320154128.GC29837@varese> References: <20090320154128.GC29837@varese> Message-ID: <2642B757-84D0-4CBC-8DE2-1125194462D2@uiuc.edu> ok ive activated the rts, midishare an gracecl packages on the cm project page, let me know if you have problems downloading https://sourceforge.net/project/showfiles.php?group_id=9766 From o.finnendahl at mh-freiburg.de Fri Mar 20 10:44:00 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Fri, 20 Mar 2009 18:44:00 +0100 Subject: [CM] midishare and rts and gracecl packages In-Reply-To: <2642B757-84D0-4CBC-8DE2-1125194462D2@uiuc.edu> References: <20090320154128.GC29837@varese> <2642B757-84D0-4CBC-8DE2-1125194462D2@uiuc.edu> Message-ID: <20090320174400.GF29837@varese> Hi Rick, had no problem downloading, thanks a lot! -- Orm Am Freitag, den 20. M?rz 2009 um 11:50:27 Uhr (-0500) schrieb Rick Taube: > ok ive activated the rts, midishare an gracecl packages on the cm > project page, let me know if you have problems downloading > > > https://sourceforge.net/project/showfiles.php?group_id=9766 > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From o.finnendahl at mh-freiburg.de Fri Mar 20 11:38:37 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Fri, 20 Mar 2009 19:38:37 +0100 Subject: [CM] rts install Message-ID: <20090320183837.GA20508@varese> Hi Rick, sorry to bug you again. I'm trying to install rts and might be doing it wrong, but couldn't find documentation. Is there anything available? Here is what I did: Asking cm to "(use-system :rts)" leads to the complaint that cffi isn't loaded. So I installed and loaded cffi (and its dependencies with "(use-system :cffi)" which works well. Now if I do "(use-system :rts)" it starts loading and stops with this error: Unknown CFFI type: RTS::QTIME_T. [Condition of type SIMPLE-ERROR] BTW: I also did ./configure && make in the rts directory and the shared library file gets generated without errors. Am I doing it wrong? -- Orm From taube at uiuc.edu Fri Mar 20 12:22:51 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 14:22:51 -0500 Subject: [CM] rts install In-Reply-To: <20090320183837.GA20508@varese> References: <20090320183837.GA20508@varese> Message-ID: <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> i guess something in cffi has changed: debugger invoked on a ASDF:MISSING-DEPENDENCY: component #:BABEL not found, required by # you could try to install a version that is from around the time of the rts release. sigh. i guess the fact that you can double-click a grace/cm3 app with a solid built in realtime scheduler wont help. regardless, i will have a much better chance of fixing/improving/maintinaing things there then i ever will in all the common-lisp spagetti systems. From o.finnendahl at mh-freiburg.de Fri Mar 20 12:58:51 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Fri, 20 Mar 2009 20:58:51 +0100 Subject: [CM] rts install In-Reply-To: <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> Message-ID: <20090320195851.GB20508@varese> Hi Rick, I perfectly understand your sentiments... I know that I had it working once but the harddrive with that is in Freiburg where I'll be after Easter. I will check it there. I don't really object to using cm3 as long as it is possible to use lisp syntax and having full access to a common lisp system. Is that the case (or at least possible)? I'm sorry to be so ignorant about recent developments but I basically use cm as some sort of library and an excellent object system for definition of musical structure and not as much as a stand-alone monolithic system, although I can definetely see the benefits from your point of view regarding the nightmare of cl systems and different platforms. nevertheless, thanks a lot! Orm Am Freitag, den 20. M?rz 2009 um 14:22:51 Uhr (-0500) schrieb Rick Taube: > i guess something in cffi has changed: > > debugger invoked on a ASDF:MISSING-DEPENDENCY: > component #:BABEL not found, required by # > > you could try to install a version that is from around the time of the > rts release. > > sigh. i guess the fact that you can double-click a grace/cm3 app with a > solid built in realtime scheduler wont help. regardless, i will have a > much better chance of fixing/improving/maintinaing things there then i > ever will in all the common-lisp spagetti systems. > > From o.finnendahl at mh-freiburg.de Fri Mar 20 13:04:35 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Fri, 20 Mar 2009 21:04:35 +0100 Subject: [CM] rts install In-Reply-To: <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> Message-ID: <20090320200435.GC20508@varese> Hi Rick, Am Freitag, den 20. M?rz 2009 um 14:22:51 Uhr (-0500) schrieb Rick Taube: > i guess something in cffi has changed: > > debugger invoked on a ASDF:MISSING-DEPENDENCY: > component #:BABEL not found, required by # I just saw your error, different from mine. That one is fairly simple: You have to get "babel" (which depends on "alexandria" which depends on "trivial-feature", all of them found as asdf packages at cliki). After that, cffi loads fine... -- Orm From bil at ccrma.Stanford.EDU Fri Mar 20 13:44:04 2009 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Fri, 20 Mar 2009 13:44:04 -0700 Subject: [CM] various snd-10 - motif and gtk troubles In-Reply-To: <87wsalvhfi.fsf@notam02.no> References: <871vstwwpn.fsf@notam02.no> <87wsalvhfi.fsf@notam02.no> Message-ID: <20090320204057.M78163@ccrma.Stanford.EDU> > Whats missing in the gtk-version now is the menu-shortcuts I think you can use Kjetil's kmenu.scm to get whatever shortcuts you want in gtk. It's working in s7 now (as well as guile) -- when I tried it, I suddenly remembered why I had discarded that "feature" (some things are so ugly, you feel like you're in that famous Mauch painting...). Also the XLoadQueryFont bug should be fixed. From bil at ccrma.Stanford.EDU Fri Mar 20 13:47:03 2009 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Fri, 20 Mar 2009 13:47:03 -0700 Subject: [CM] various snd-10 - motif and gtk troubles In-Reply-To: <87wsalvhfi.fsf@notam02.no> References: <871vstwwpn.fsf@notam02.no> <87wsalvhfi.fsf@notam02.no> Message-ID: <20090320204648.M72423@ccrma.Stanford.EDU> make that Munch -- my memory is fading fast... From k.s.matheussen at notam02.no Fri Mar 20 13:57:03 2009 From: k.s.matheussen at notam02.no (Kjetil S. Matheussen) Date: Fri, 20 Mar 2009 21:57:03 +0100 (CET) Subject: [CM] various snd-10 - motif and gtk troubles In-Reply-To: <20090320204057.M78163@ccrma.Stanford.EDU> References: <871vstwwpn.fsf@notam02.no> <87wsalvhfi.fsf@notam02.no> <20090320204057.M78163@ccrma.Stanford.EDU> Message-ID: On Fri, 20 Mar 2009, Bill Schottstaedt wrote: >> Whats missing in the gtk-version now is the menu-shortcuts > > I think you can use Kjetil's kmenu.scm to get whatever shortcuts I think so too, but kmenu.scm is not written by me. :-) From taube at uiuc.edu Fri Mar 20 13:57:24 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 15:57:24 -0500 Subject: [CM] rts install In-Reply-To: <20090320195851.GB20508@varese> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> <20090320195851.GB20508@varese> Message-ID: cm3 its written in lisp and has lisp syntax and lisp buffers. it uses s7 scheme, which has lots of cl features. you can also build it with chicken scheme, which is really good for realtime work since it compiles to c. but if you want common lisp then there is no substitute for cm2. but things like rts etc will never work as well in cl as they do in cm3 i think the thing to do is find the set of cl systems that works with cm2 and then i can put that info on the website. On Mar 20, 2009, at 2:58 PM, Orm Finnendahl wrote: > I don't really object to using cm3 as long as it is possible to use > lisp syntax and having full access to a common lisp system. Is that From taube at uiuc.edu Fri Mar 20 16:33:18 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Fri, 20 Mar 2009 18:33:18 -0500 Subject: [CM] rts install In-Reply-To: <20090320200435.GC20508@varese> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> <20090320200435.GC20508@varese> Message-ID: <52AE67F6-CF46-42E8-8754-66CC070B4385@uiuc.edu> rts seems to compile in this version cffi-060313.tar.gz From o.finnendahl at mh-freiburg.de Sat Mar 21 01:13:06 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Sat, 21 Mar 2009 09:13:06 +0100 Subject: [CM] rts install In-Reply-To: <52AE67F6-CF46-42E8-8754-66CC070B4385@uiuc.edu> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> <20090320200435.GC20508@varese> <52AE67F6-CF46-42E8-8754-66CC070B4385@uiuc.edu> Message-ID: <20090321081306.GA7059@varese> Hi Rick, that worked right away, thanks a lot! Thanks also for the cm3 infos. I will look into it. Maybe there are ways to link it with my other code. I couldn't find any information on s7 scheme. Is there something out there? Where can I get it? Yours, Orm Am Friday, den 20. March 2009 um 18:33:18 Uhr (-0500) schrieb Rick Taube: > rts seems to compile in this version > > cffi-060313.tar.gz > > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From bil at ccrma.Stanford.EDU Sat Mar 21 02:32:11 2009 From: bil at ccrma.Stanford.EDU (Bill Schottstaedt) Date: Sat, 21 Mar 2009 02:32:11 -0700 Subject: [CM] rts install In-Reply-To: <20090321081306.GA7059@varese> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> <20090320200435.GC20508@varese> <52AE67F6-CF46-42E8-8754-66CC070B4385@uiuc.edu> <20090321081306.GA7059@varese> Message-ID: <20090321093039.M21869@ccrma.Stanford.EDU> > I couldn't find any information on s7 scheme. Is there > something out there? Where can I get it? It's at ccrma-ftp:/pub/Lisp/s7.tar.gz, and also comes bundled with Snd and other fine music software. From o.finnendahl at mh-freiburg.de Sat Mar 21 04:57:55 2009 From: o.finnendahl at mh-freiburg.de (Orm Finnendahl) Date: Sat, 21 Mar 2009 12:57:55 +0100 Subject: [CM] rts install In-Reply-To: <20090321093039.M21869@ccrma.Stanford.EDU> References: <20090320183837.GA20508@varese> <73184E0F-319A-4DAC-91F8-961D0D0C8CA3@uiuc.edu> <20090320200435.GC20508@varese> <52AE67F6-CF46-42E8-8754-66CC070B4385@uiuc.edu> <20090321081306.GA7059@varese> <20090321093039.M21869@ccrma.Stanford.EDU> Message-ID: <20090321115755.GB7059@varese> Am Saturday, den 21. March 2009 um 02:32:11 Uhr (-0700) schrieb Bill Schottstaedt: > > I couldn't find any information on s7 scheme. Is there > > something out there? Where can I get it? > > It's at ccrma-ftp:/pub/Lisp/s7.tar.gz, and also comes bundled > with Snd and other fine music software. I got it and looked into it a bit. Very impressive! -- Orm From taube at uiuc.edu Sat Mar 21 07:24:34 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Sat, 21 Mar 2009 09:24:34 -0500 Subject: [CM] cm3 midifile importing Message-ID: svn trunk has midi importing working in cm3. the importing tool is in Audio>MidiIn>Import Midifile... menu. The tool gives you full controls over what tracks to import , what message types (notes, program changes etc) and channels to include, and where to import the events to (console window, editor buffer or clipboard). it also lets you import the midi events in different formats, eg as lists of parameter values or as actualy send messages. here is example imports from bach269.mid in both formats: (define bach269-track1-notes '( (1.364 0.500 67 96 0) ; time dur key chan (2.045 0.500 67 96 0) (3.409 0.500 74 96 0) (4.091 0.500 71 96 0) (5.114 0.500 69 96 0) (5.455 0.500 67 96 0) (6.136 0.500 67 96 0) (7.159 0.500 69 96 0) (7.500 0.500 71 96 0) (8.182 0.500 69 96 0) (9.545 0.500 71 96 0) (10.227 0.500 74 96 0) (11.591 0.500 72 96 0) (12.273 0.500 71 96 0) (12.955 0.500 69 96 0) (14.318 0.500 67 96 0) (15.682 0.500 67 96 0) (16.364 0.500 67 96 0) (17.727 0.500 74 96 0) (18.409 0.500 71 96 0) (19.432 0.500 69 96 0) (19.773 0.500 67 96 0) (20.455 0.500 67 96 0) (21.477 0.500 69 96 0) (21.818 0.500 71 96 0) (22.500 0.500 69 96 0) (23.864 0.500 71 96 0) (24.546 0.500 74 96 0) (25.909 0.500 72 96 0) (26.591 0.500 71 96 0) (27.273 0.500 69 96 0) (28.636 0.500 67 96 0) (30.000 0.500 71 96 0) (30.682 0.500 71 96 0) (31.364 0.500 72 96 0) (32.046 0.500 74 96 0) (32.727 0.500 74 96 0) (33.750 0.500 72 96 0) (34.091 0.500 71 96 0) (34.773 0.500 69 96 0) (36.136 0.500 67 96 0) (36.818 0.500 71 96 0) (38.182 0.500 72 96 0) (38.864 0.500 74 96 0) (40.227 0.500 72 96 0) (40.909 0.500 71 96 0) (42.955 0.500 67 96 0) (44.318 0.500 71 96 0) (45.000 0.500 74 96 0) (46.364 0.500 72 96 0) (47.046 0.500 71 96 0) (48.409 0.500 69 96 0) (49.091 0.500 67 96 0) (50.114 0.500 69 96 0) (50.455 0.500 71 96 0) (51.137 0.500 69 96 0) (52.500 0.500 71 96 0) (53.182 0.500 74 96 0) (54.546 0.500 72 96 0) (55.227 0.500 71 96 0) (55.909 0.500 69 96 0) (57.273 0.500 67 96 0) )) (define bach269-track1-ctrls '( (0.000 7 101 0) ; time controller value chan (0.000 10 64 0) )) (define bach269-track1-metas '( (0.000 #x9 "SmartMusic SoftSynth 1") (0.000 #x3 "Instrument 1") )) ;; imported send messages (begin (send "mp:meta" 0.000 #x9 "SmartMusic SoftSynth 1") (send "mp:meta" 0.000 #x3 "Instrument 1") (send "mp:ctrl" 0.000 7 101 0) (send "mp:ctrl" 0.000 10 64 0) (send "mp:note" 1.364 0.500 67 96 0) (send "mp:note" 2.045 0.500 67 96 0) (send "mp:note" 3.409 0.500 74 96 0) (send "mp:note" 4.091 0.500 71 96 0) (send "mp:note" 5.114 0.500 69 96 0) (send "mp:note" 5.455 0.500 67 96 0) (send "mp:note" 6.136 0.500 67 96 0) (send "mp:note" 7.159 0.500 69 96 0) (send "mp:note" 7.500 0.500 71 96 0) (send "mp:note" 8.182 0.500 69 96 0) (send "mp:note" 9.545 0.500 71 96 0) (send "mp:note" 10.227 0.500 74 96 0) (send "mp:note" 11.591 0.500 72 96 0) (send "mp:note" 12.273 0.500 71 96 0) (send "mp:note" 12.955 0.500 69 96 0) (send "mp:note" 14.318 0.500 67 96 0) (send "mp:note" 15.682 0.500 67 96 0) (send "mp:note" 16.364 0.500 67 96 0) (send "mp:note" 17.727 0.500 74 96 0) (send "mp:note" 18.409 0.500 71 96 0) (send "mp:note" 19.432 0.500 69 96 0) (send "mp:note" 19.773 0.500 67 96 0) (send "mp:note" 20.455 0.500 67 96 0) (send "mp:note" 21.477 0.500 69 96 0) (send "mp:note" 21.818 0.500 71 96 0) (send "mp:note" 22.500 0.500 69 96 0) (send "mp:note" 23.864 0.500 71 96 0) (send "mp:note" 24.546 0.500 74 96 0) (send "mp:note" 25.909 0.500 72 96 0) (send "mp:note" 26.591 0.500 71 96 0) (send "mp:note" 27.273 0.500 69 96 0) (send "mp:note" 28.636 0.500 67 96 0) (send "mp:note" 30.000 0.500 71 96 0) (send "mp:note" 30.682 0.500 71 96 0) (send "mp:note" 31.364 0.500 72 96 0) (send "mp:note" 32.046 0.500 74 96 0) (send "mp:note" 32.727 0.500 74 96 0) (send "mp:note" 33.750 0.500 72 96 0) (send "mp:note" 34.091 0.500 71 96 0) (send "mp:note" 34.773 0.500 69 96 0) (send "mp:note" 36.136 0.500 67 96 0) (send "mp:note" 36.818 0.500 71 96 0) (send "mp:note" 38.182 0.500 72 96 0) (send "mp:note" 38.864 0.500 74 96 0) (send "mp:note" 40.227 0.500 72 96 0) (send "mp:note" 40.909 0.500 71 96 0) (send "mp:note" 42.955 0.500 67 96 0) (send "mp:note" 44.318 0.500 71 96 0) (send "mp:note" 45.000 0.500 74 96 0) (send "mp:note" 46.364 0.500 72 96 0) (send "mp:note" 47.046 0.500 71 96 0) (send "mp:note" 48.409 0.500 69 96 0) (send "mp:note" 49.091 0.500 67 96 0) (send "mp:note" 50.114 0.500 69 96 0) (send "mp:note" 50.455 0.500 71 96 0) (send "mp:note" 51.137 0.500 69 96 0) (send "mp:note" 52.500 0.500 71 96 0) (send "mp:note" 53.182 0.500 74 96 0) (send "mp:note" 54.546 0.500 72 96 0) (send "mp:note" 55.227 0.500 71 96 0) (send "mp:note" 55.909 0.500 69 96 0) (send "mp:note" 57.273 0.500 67 96 0) ) ; From lievenmoors at gmail.com Thu Mar 26 07:19:05 2009 From: lievenmoors at gmail.com (lieven moors) Date: Thu, 26 Mar 2009 15:19:05 +0100 Subject: [CM] cm3 Message-ID: <49CB8ED9.7030304@gmail.com> Hi, I have reported a problem earlier about CM3 not being able to start without the X environment on my 64bit machine. I tried some debugging myself, to find out what the problem is. As I have no experience debugging c programs, I'm not sure this will be useful to you. I started CM (compiled with CONFIG=Debug) within gdb. I get this error: /No protocol specified //Failed to open the X display. / Then I did 'info stack': Because I didn't know how to write this output to a file from gdb (and I don't have my other computer here, I'll type this out (not so accurate) 0 doPlatformSpecificInitialisation() at platform_specific_code/juce_linux_Messaging.cpp (line 208) 1 juce::MessageManager::getInstance() at src/juce_appframework/events/juceMessageManager.cpp (line 84) 2 in main Main.cpp (line 194) which is MessageManager::getInstance(); The function doPlatformSpecificInitialisation seems to try to open the default X display, but fails. I hope this might help to fix this bug. If you need more help with this, you can always ask me to... P.S. I use the fglx module for my ATI graphics card, but I don't know if this has anything to do with it... From taube at uiuc.edu Sat Mar 28 07:01:09 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Sat, 28 Mar 2009 09:01:09 -0500 Subject: [CM] new GraceCL Message-ID: cm trunk now builds a newly implemented GraceCL app that supports the Common Music 2 branch. I will be able to maintain and improve it along with Grace and Cm3 because its really just an additional file and a -D compiler switch! obviously there is no Audio menu or realtime scheduler , its a replacement for working with CM2 in emacs/ slime. To try it out: (1) download a beta executable: mac: http://camil.music.uiuc.edu/Software/grace/downloads/GraceCL-3.2.4a-x86-leopard.zip windows: http://camil.music.uiuc.edu/Software/grace/downloads/GraceCL-3.2.4a-win32.zip linux: http://camil.music.uiuc.edu/Software/grace/downloads/GraceCL-3.2.4a-linux.zip (2) install the latest cm2 (required): svn co https://commonmusic.svn.sf.net/svnroot/commonmusic/branches/ cm2 cm2 (3) Start GraceCL, use File>Configure Lisp... to specify your lisp exe (either sbcl or clisp) and your cm2 installation directory, then File>Start Lisp to start it running. then open a lisp file and eval away. it seems to be working on windows linux and mac. From lievenmoors at gmail.com Sun Mar 29 08:18:34 2009 From: lievenmoors at gmail.com (lieven moors) Date: Sun, 29 Mar 2009 17:18:34 +0200 Subject: [CM] problems with cm3 Message-ID: <49CF914A.5010405@gmail.com> Hi, I'm still experiencing a number of problems after switching to cm3. The biggest one I have is that when I sprout a number of processes at the same ahead time, there seems to be a systematic drift between the different processes. The processes start out in sync, slowly drift apart. Once in a while, I can hear that the processes are in sync with each other, after which they drift apart again. I'm using ubuntu studio 8.04 on a dual core system with 4gigs of ram, so performance shouldn't be the problem. Although I wonder if realtime priorities might have an influence on his. Another problem I have is when i'm sprouting to a midi file. When I write a file which according to the scheduler is 120 seconds long (display (elapsed)), and when I open it in another sequencer (Rosegarden or Seq24), all the notes are compressed in one bar. And the distance between the original eight notes has become 8 ms. I saw a previous thread in which you mention the miliseconds vs divisions-per-quarter formats. I wonder if you are still using the miliseconds format, and if this is the problem I'm facing... I also have problems when I use Grace to save (scheme) files. When I try to commit my changes using git, git suddenly complains about lots of trailing whitespaces. When I open the file I saved in Grace in another text editor (vim or emacs), I cannot see any of the whitespaces git is complaining about, so I'm not even able to get rid of them. I even have this problem when I just save an emty file with Grace. Thanks for your help Lieven From taube at uiuc.edu Sun Mar 29 11:39:15 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Sun, 29 Mar 2009 13:39:15 -0500 Subject: [CM] problems with cm3 In-Reply-To: <49CF914A.5010405@gmail.com> References: <49CF914A.5010405@gmail.com> Message-ID: I cant debug without a way of duplicating your envronment. if you can please send me SIMPLE testing code I can try to see whats going on. for the first problem, will your processes stay in sync if you spout everting at 0, ie without specifying a start time? (sprout (list ....) ) what version are you using? the current svn? On Mar 29, 2009, at 10:18 AM, lieven moors wrote: > Hi, > > I'm still experiencing a number of problems after switching to cm3. > > The biggest one I have is that when I sprout a number of processes at > the same ahead time, there seems to be a systematic drift between the > different processes. The processes start out in sync, slowly drift > apart. Once in a while, I can hear that the processes are in sync with > each other, after which they drift apart again. I'm using ubuntu > studio > 8.04 on a dual core system with 4gigs of ram, so performance shouldn't > be the problem. Although I wonder if realtime priorities might have an > influence on his. > > Another problem I have is when i'm sprouting to a midi file. When I > write a file which according to the scheduler is 120 seconds long > (display (elapsed)), and when I open it > in another sequencer (Rosegarden or Seq24), all the notes are > compressed > in one bar. > And the distance between the original eight notes has become 8 ms. I > saw > a previous thread in which you mention the miliseconds vs > divisions-per-quarter formats. I wonder > if you are still using the miliseconds format, and if this is the > problem I'm facing... > > I also have problems when I use Grace to save (scheme) files. When I > try > to commit my changes using git, git suddenly complains about lots of > trailing whitespaces. When I open the file I saved in Grace in another > text editor (vim or emacs), I cannot see any of the whitespaces git is > complaining about, so I'm not even able to get rid of them. > I even have this problem when I just save an emty file with Grace. > > > Thanks for your help > > Lieven > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist From taube at uiuc.edu Sun Mar 29 11:40:01 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Sun, 29 Mar 2009 13:40:01 -0500 Subject: [CM] problems with cm3 In-Reply-To: <49CF914A.5010405@gmail.com> References: <49CF914A.5010405@gmail.com> Message-ID: <7113F817-3768-4BA0-BDA8-EB9E35B4FD00@uiuc.edu> use Audio>MidiOut>Midifle settings .... to see if its milliseconds or seconds. On Mar 29, 2009, at 10:18 AM, lieven moors wrote: > if you are still using the miliseconds format, and if this is the > problem I'm facing... > From taube at uiuc.edu Sun Mar 29 12:21:20 2009 From: taube at uiuc.edu (Heinrich Taube) Date: Sun, 29 Mar 2009 14:21:20 -0500 Subject: [CM] problems with cm3 In-Reply-To: <49CFC7EB.50604@gmail.com> References: <49CF914A.5010405@gmail.com> <7113F817-3768-4BA0-BDA8-EB9E35B4FD00@uiuc.edu> <49CFC7EB.50604@gmail.com> Message-ID: <24C55338-EC1E-455B-86E4-7C0D4DB3BB78@uiuc.edu> yes, i will take a look at your issues in the svn version to see whats going on. it will take me a day or two, ive got a lot on my plate till tuesday so please be patient On Mar 29, 2009, at 2:11 PM, lieven moors wrote: > I don't see this in Grace, maybe my version is too old? > > Heinrich Taube wrote: >> use Audio>MidiOut>Midifle settings .... to see if its >> milliseconds or seconds. >> >> >> On Mar 29, 2009, at 10:18 AM, lieven moors wrote: >> >>> if you are still using the miliseconds format, and if this is the >>> problem I'm facing... >>> >> >> > From lievenmoors at gmail.com Sun Mar 29 12:07:30 2009 From: lievenmoors at gmail.com (lieven moors) Date: Sun, 29 Mar 2009 21:07:30 +0200 Subject: [CM] problems with cm3 In-Reply-To: References: <49CF914A.5010405@gmail.com> Message-ID: <49CFC6F2.2030106@gmail.com> Heinrich Taube wrote: > I cant debug without a way of duplicating your envronment. > if you can please send me SIMPLE testing code I can try to see whats > going on. > for the first problem, will your processes stay in sync if you spout > everting at 0, ie without specifying a start time? > (sprout (list ....) ) I just tried with this code (took it from mailing list), on my laptop (my other computer is in my home studio), and the processes don't stay in sync (it's very noticeable). (define keyscale (scale 7 48 '(2 2 1 2 2 2 1))) (define (algo01 dur row beat amp chan) (process while (< (elapsed #f) dur) with range = (length row) for d = beat for k = (list-ref row chan) for a = (between 0.1 amp) for w = d do (send "mp:midi" :time (elapsed #f) :dur d :key k :amp a :chan chan) (wait w))) (sprout (list (algo01 16 keyscale .25 1.0 0) (algo01 14 keyscale .25 1.0 1) (algo01 12 keyscale .25 1.0 2) (algo01 10 keyscale .25 1.0 3))) > > what version are you using? the current svn? no, cm-3.2.4 > > On Mar 29, 2009, at 10:18 AM, lieven moors wrote: > >> Hi, >> >> I'm still experiencing a number of problems after switching to cm3. >> >> The biggest one I have is that when I sprout a number of processes at >> the same ahead time, there seems to be a systematic drift between the >> different processes. The processes start out in sync, slowly drift >> apart. Once in a while, I can hear that the processes are in sync with >> each other, after which they drift apart again. I'm using ubuntu studio >> 8.04 on a dual core system with 4gigs of ram, so performance shouldn't >> be the problem. Although I wonder if realtime priorities might have an >> influence on his. >> >> Another problem I have is when i'm sprouting to a midi file. When I >> write a file which according to the scheduler is 120 seconds long >> (display (elapsed)), and when I open it >> in another sequencer (Rosegarden or Seq24), all the notes are compressed >> in one bar. >> And the distance between the original eight notes has become 8 ms. I saw >> a previous thread in which you mention the miliseconds vs >> divisions-per-quarter formats. I wonder >> if you are still using the miliseconds format, and if this is the >> problem I'm facing... >> >> I also have problems when I use Grace to save (scheme) files. When I try >> to commit my changes using git, git suddenly complains about lots of >> trailing whitespaces. When I open the file I saved in Grace in another >> text editor (vim or emacs), I cannot see any of the whitespaces git is >> complaining about, so I'm not even able to get rid of them. >> I even have this problem when I just save an emty file with Grace. >> >> >> Thanks for your help >> >> Lieven >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist > > From lievenmoors at gmail.com Sun Mar 29 12:11:39 2009 From: lievenmoors at gmail.com (lieven moors) Date: Sun, 29 Mar 2009 21:11:39 +0200 Subject: [CM] problems with cm3 In-Reply-To: <7113F817-3768-4BA0-BDA8-EB9E35B4FD00@uiuc.edu> References: <49CF914A.5010405@gmail.com> <7113F817-3768-4BA0-BDA8-EB9E35B4FD00@uiuc.edu> Message-ID: <49CFC7EB.50604@gmail.com> I don't see this in Grace, maybe my version is too old? Heinrich Taube wrote: > use Audio>MidiOut>Midifle settings .... to see if its milliseconds > or seconds. > > > On Mar 29, 2009, at 10:18 AM, lieven moors wrote: > >> if you are still using the miliseconds format, and if this is the >> problem I'm facing... >> > > From lievenmoors at gmail.com Sun Mar 29 12:28:35 2009 From: lievenmoors at gmail.com (lieven moors) Date: Sun, 29 Mar 2009 21:28:35 +0200 Subject: [CM] problems with cm3 In-Reply-To: <24C55338-EC1E-455B-86E4-7C0D4DB3BB78@uiuc.edu> References: <49CF914A.5010405@gmail.com> <7113F817-3768-4BA0-BDA8-EB9E35B4FD00@uiuc.edu> <49CFC7EB.50604@gmail.com> <24C55338-EC1E-455B-86E4-7C0D4DB3BB78@uiuc.edu> Message-ID: <49CFCBE3.6010007@gmail.com> Hey, no problem, thanks for responding so quickly... If you can think of anything i could do myself, or something I can look into, just ask me, anytime. Heinrich Taube wrote: > yes, i will take a look at your issues in the svn version to see whats > going on. it will take me a day or two, ive got a lot on my plate till > tuesday so please be patient > > On Mar 29, 2009, at 2:11 PM, lieven moors wrote: > >> I don't see this in Grace, maybe my version is too old? >> >> Heinrich Taube wrote: >>> use Audio>MidiOut>Midifle settings .... to see if its >>> milliseconds or seconds. >>> >>> >>> On Mar 29, 2009, at 10:18 AM, lieven moors wrote: >>> >>>> if you are still using the miliseconds format, and if this is the >>>> problem I'm facing... >>>> >>> >>> >> > >