From ahcnz at orcon.net.nz Tue Mar 3 02:18:02 2020 From: ahcnz at orcon.net.nz (adam) Date: Tue, 03 Mar 2020 23:18:02 +1300 Subject: [CM] CM/Scheme without Grace? In-Reply-To: <20200228115215.GA32005@t480s-orm.localdomain> References: <20200228115215.GA32005@t480s-orm.localdomain> Message-ID: <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> Forgive me for asking, but how would I load and run the ../ormf/cm package? I have tried several approaches, including even /bin/cm.sh, with no success. Am on Linux with a fresh and working Emacs Slime sbcl setup. Step one may be to save a working image, to thereafter load as slime's lisp subprocess, as before. Through trial and error I find I can; (load "cm.asd) -> T and then (in-package :common-music-system) -> # however (cm) then returns an undefined function error. (load "./src/cm.lisp") -> error Component :FOMUS not found do I need Fomus loaded beforehand? Any help much appreciated. On Fri, 2020-02-28 at 12:52 +0100, Orm Finnendahl wrote: > Hello Neil, > > in case you're interested in the Common Lisp port of cm, I'd > recommend this repository, as it is more or less actively maintained > (including the loop code fixed and extensions for realtime integration > with incudine, svg im/export etc.): > > https://github.com/ormf/cm > > -- > Orm > > Am Donnerstag, den 27. Februar 2020 um 18:18:30 Uhr (+0000) schrieb Taube, Heinrich K: > > Hello Neil, that would be difficult as many of the scheme functions make calls to c++ > > code. > > A better solution would be to use the common-lisp version available on the source- > > forge website, but of course then its not in Scheme. > > > > ?Rick > > ________________________________ > > Rick Taube > > Chair, Composition/Theory > > School of Music > > University of Illinois Urbana-Champaign > > Email: taube at illinois.edu > > President, Illiac Software Inc. > > https://harmonia.illiacsoftware.com/ > > Email: taube at illiacsoftware.com > > > > > > On Feb 27, 2020, at 11:45 AM, Neil Baylis > neil.baylis at gmail.com>> wrote: > > > > Is it possible to run CM using scheme without the Grace application? For example, by > > just editing scheme files in an ordinary text editor? If so, can anyone point me at > > instructions for doing this? > > > > I see the Grace documentation lists a bunch of functions/macros related to algo music, > > but it's not clear to me whether Grace is required to get that functionality. > > > > My application is to algorithmically generate midi to be played by virtual > > instruments. (i.e., route the midi to a VST or AU host.) > > > > Neil Baylis > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From taube at illinois.edu Tue Mar 3 06:48:48 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Tue, 3 Mar 2020 14:48:48 +0000 Subject: [CM] CM/Scheme without Grace? In-Reply-To: <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> References: <20200228115215.GA32005@t480s-orm.localdomain> <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> Message-ID: <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> You should be able comment out the fomus loading, that was just an optional package. > On Mar 3, 2020, at 4:18 AM, adam wrote: > > > Forgive me for asking, but how would I load and run the ../ormf/cm package? > > I have tried several approaches, including even /bin/cm.sh, with no success. > Am on Linux with a fresh and working Emacs Slime sbcl setup. > > Step one may be to save a working image, to thereafter load as slime's > lisp subprocess, as before. > > Through trial and error I find I can; > (load "cm.asd) -> T > > and then > (in-package :common-music-system) -> # > > however (cm) then returns an undefined function error. > > (load "./src/cm.lisp") -> error Component :FOMUS not found > do I need Fomus loaded beforehand? > > Any help much appreciated. > > > > > On Fri, 2020-02-28 at 12:52 +0100, Orm Finnendahl wrote: >> Hello Neil, >> >> in case you're interested in the Common Lisp port of cm, I'd >> recommend this repository, as it is more or less actively maintained >> (including the loop code fixed and extensions for realtime integration >> with incudine, svg im/export etc.): >> >> https://github.com/ormf/cm >> >> -- >> Orm >> >> Am Donnerstag, den 27. Februar 2020 um 18:18:30 Uhr (+0000) schrieb Taube, Heinrich K: >>> Hello Neil, that would be difficult as many of the scheme functions make calls to c++ >>> code. >>> A better solution would be to use the common-lisp version available on the source- >>> forge website, but of course then its not in Scheme. >>> >>> ?Rick >>> ________________________________ >>> Rick Taube >>> Chair, Composition/Theory >>> School of Music >>> University of Illinois Urbana-Champaign >>> Email: taube at illinois.edu >>> President, Illiac Software Inc. >>> https://harmonia.illiacsoftware.com/ >>> Email: taube at illiacsoftware.com >>> >>> >>> On Feb 27, 2020, at 11:45 AM, Neil Baylis >> neil.baylis at gmail.com>> wrote: >>> >>> Is it possible to run CM using scheme without the Grace application? For example, by >>> just editing scheme files in an ordinary text editor? If so, can anyone point me at >>> instructions for doing this? >>> >>> I see the Grace documentation lists a bunch of functions/macros related to algo music, >>> but it's not clear to me whether Grace is required to get that functionality. >>> >>> My application is to algorithmically generate midi to be played by virtual >>> instruments. (i.e., route the midi to a VST or AU host.) >>> >>> Neil Baylis >>> _______________________________________________ >>> Cmdist mailing list >>> Cmdist at ccrma.stanford.edu >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>> >>> _______________________________________________ >>> Cmdist mailing list >>> Cmdist at ccrma.stanford.edu >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From taube at illinois.edu Tue Mar 3 09:21:29 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Tue, 3 Mar 2020 17:21:29 +0000 Subject: [CM] New home for Grace Message-ID: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> Ive moved the Grace repo to github where you can now download the sources. It seems to build fine on MacOS and Linux, but I haven?t done tons of testing yet so there are probably still some issues to fix. Windows doesn't work yet ? I can compile and link everything, the app boots but I dont seem to have s7 working yet. I?m sure it's something stupid that I?ve done, but don't know much about VisualStudio2019 so right now I'm still in the dark. Thank you Bill for all your help! This release is basically a major cleanup to get things building and running again in the very latest juce and sndlib/s7. Grace is a pretty old app so the next thing I will do is probably continue to simplify and modernize its code base. I will also add an internal midi synth (a juce fork of the sfzero sound font player) so that there is internal playback support on all OSes. here is how to download the sources, the grace/README.md will tell you what to do. $ git clone https://github.com/ricktaube/grace.git grace One thing I need to do asap is have documentation hosted by the github repo if at all possible. Iff anybody knows how to host a homepage for a github repo please let me know. ?Rick -------------- next part -------------- An HTML attachment was scrubbed... URL: From orm.finnendahl at selma.hfmdk-frankfurt.de Tue Mar 3 09:22:26 2020 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Tue, 3 Mar 2020 18:22:26 +0100 Subject: [CM] CM/Scheme without Grace? In-Reply-To: <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> References: <20200228115215.GA32005@t480s-orm.localdomain> <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> Message-ID: <20200303172226.GC57716@t480s-orm.localdomain> Hi Adam, sorry, I was unaware of the fomus dependency in cm. I will get rid of it as it is unneccessary. To get it running in the meantime, please just go ahead and also clone "fomus" and "cm-fomus" from the same github repo (they are fairly small): https://github.com/ormf/cm-fomus https://github.com/ormf/fomus To get it up and running (with slime/quicklisp installed): - Put the "cm", "cm-fomus" and "fomus" folders into the ~/quicklisp/local-projects/ folder - Optionally edit the attached .fomus file by filling in the paths to the executables (evince and lilypond) in case they are installed on your computer and copy the edited file to your home folder. - In the slime repl: CL-USER> (ql:quickload "cm") To load "cm": Load 1 ASDF system: cm ; Loading "cm" ;; FOMUS v0.2.28 ;; Lisp music notation formatter ;; Copyright (c) 2005, 2006, 2007 David Psenicka, All Rights Reserved ;; See file "COPYING" for terms of use and distribution. ;; Loading initialization file "/home/orm/.fomus"... ("cm") CL-USER> (cm) /\\\ ---\\\--------- ----\\\-------- ----/\\\------- Common Music 2.12.0 ---/--\\\------ --/----\\\----- / \\\/ CL-USER> Let me know if you run into problems. Best, Orm Am Dienstag, den 03. M?rz 2020 um 14:48:48 Uhr (+0000) schrieb Taube, Heinrich K: > You should be able comment out the fomus loading, that was just an optional package. > > > On Mar 3, 2020, at 4:18 AM, adam wrote: > > > > > > Forgive me for asking, but how would I load and run the ../ormf/cm package? > > > > I have tried several approaches, including even /bin/cm.sh, with no success. > > Am on Linux with a fresh and working Emacs Slime sbcl setup. > > > > Step one may be to save a working image, to thereafter load as slime's > > lisp subprocess, as before. > > > > Through trial and error I find I can; > > (load "cm.asd) -> T > > > > and then > > (in-package :common-music-system) -> # > > > > however (cm) then returns an undefined function error. > > > > (load "./src/cm.lisp") -> error Component :FOMUS not found > > do I need Fomus loaded beforehand? > > > > Any help much appreciated. > > > > > > > > > > On Fri, 2020-02-28 at 12:52 +0100, Orm Finnendahl wrote: > >> Hello Neil, > >> > >> in case you're interested in the Common Lisp port of cm, I'd > >> recommend this repository, as it is more or less actively maintained > >> (including the loop code fixed and extensions for realtime integration > >> with incudine, svg im/export etc.): > >> > >> https://github.com/ormf/cm > >> > >> -- > >> Orm > >> > >> Am Donnerstag, den 27. Februar 2020 um 18:18:30 Uhr (+0000) schrieb Taube, Heinrich K: > >>> Hello Neil, that would be difficult as many of the scheme functions make calls to c++ > >>> code. > >>> A better solution would be to use the common-lisp version available on the source- > >>> forge website, but of course then its not in Scheme. > >>> > >>> ?Rick > >>> ________________________________ > >>> Rick Taube > >>> Chair, Composition/Theory > >>> School of Music > >>> University of Illinois Urbana-Champaign > >>> Email: taube at illinois.edu > >>> President, Illiac Software Inc. > >>> https://harmonia.illiacsoftware.com/ > >>> Email: taube at illiacsoftware.com > >>> > >>> > >>> On Feb 27, 2020, at 11:45 AM, Neil Baylis >>> neil.baylis at gmail.com>> wrote: > >>> > >>> Is it possible to run CM using scheme without the Grace application? For example, by > >>> just editing scheme files in an ordinary text editor? If so, can anyone point me at > >>> instructions for doing this? > >>> > >>> I see the Grace documentation lists a bunch of functions/macros related to algo music, > >>> but it's not clear to me whether Grace is required to get that functionality. > >>> > >>> My application is to algorithmically generate midi to be played by virtual > >>> instruments. (i.e., route the midi to a VST or AU host.) > >>> > >>> Neil Baylis > >>> _______________________________________________ > >>> Cmdist mailing list > >>> Cmdist at ccrma.stanford.edu > >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > >>> > >>> _______________________________________________ > >>> Cmdist mailing list > >>> Cmdist at ccrma.stanford.edu > >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > >> > >> > >> _______________________________________________ > >> Cmdist mailing list > >> Cmdist at ccrma.stanford.edu > >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- :output '((:data) (:lilypond :process t :view nil)) :lilypond-exe "/home/orm/bin/lilypond" :lilypond-opts '("--pdf") :lilypond-out-ext "pdf" :lilypond-view-exe "/usr/bin/evince" :cmn-view-exe "/usr/bin/evince" :verbose 1 :min-tuplet-dur 1 :max-tuplet '(13) :caut-acc-ottavas t From orm.finnendahl at selma.hfmdk-frankfurt.de Tue Mar 3 09:40:47 2020 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Tue, 3 Mar 2020 18:40:47 +0100 Subject: [CM] CM/Scheme without Grace? In-Reply-To: <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> References: <20200228115215.GA32005@t480s-orm.localdomain> <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> Message-ID: <20200303174047.GA43139@t480s-orm.localdomain> Hi Adam, I removed the fomus dependency from cm. Download cm from the github repository, put the folder into ~/quicklisp/local-projects and issue (ql:quickload "cm") followed by (cm) That should get you into the vanilla cm package. Best, Orm Am Dienstag, den 03. M?rz 2020 um 14:48:48 Uhr (+0000) schrieb Taube, Heinrich K: > You should be able comment out the fomus loading, that was just an optional package. > > > On Mar 3, 2020, at 4:18 AM, adam wrote: > > > > > > Forgive me for asking, but how would I load and run the ../ormf/cm package? > > > > I have tried several approaches, including even /bin/cm.sh, with no success. > > Am on Linux with a fresh and working Emacs Slime sbcl setup. > > > > Step one may be to save a working image, to thereafter load as slime's > > lisp subprocess, as before. > > > > Through trial and error I find I can; > > (load "cm.asd) -> T > > > > and then > > (in-package :common-music-system) -> # > > > > however (cm) then returns an undefined function error. > > > > (load "./src/cm.lisp") -> error Component :FOMUS not found > > do I need Fomus loaded beforehand? > > > > Any help much appreciated. > > > > > > > > > > On Fri, 2020-02-28 at 12:52 +0100, Orm Finnendahl wrote: > >> Hello Neil, > >> > >> in case you're interested in the Common Lisp port of cm, I'd > >> recommend this repository, as it is more or less actively maintained > >> (including the loop code fixed and extensions for realtime integration > >> with incudine, svg im/export etc.): > >> > >> https://github.com/ormf/cm > >> > >> -- > >> Orm > >> > >> Am Donnerstag, den 27. Februar 2020 um 18:18:30 Uhr (+0000) schrieb Taube, Heinrich K: > >>> Hello Neil, that would be difficult as many of the scheme functions make calls to c++ > >>> code. > >>> A better solution would be to use the common-lisp version available on the source- > >>> forge website, but of course then its not in Scheme. > >>> > >>> ?Rick > >>> ________________________________ > >>> Rick Taube > >>> Chair, Composition/Theory > >>> School of Music > >>> University of Illinois Urbana-Champaign > >>> Email: taube at illinois.edu > >>> President, Illiac Software Inc. > >>> https://harmonia.illiacsoftware.com/ > >>> Email: taube at illiacsoftware.com > >>> > >>> > >>> On Feb 27, 2020, at 11:45 AM, Neil Baylis >>> neil.baylis at gmail.com>> wrote: > >>> > >>> Is it possible to run CM using scheme without the Grace application? For example, by > >>> just editing scheme files in an ordinary text editor? If so, can anyone point me at > >>> instructions for doing this? > >>> > >>> I see the Grace documentation lists a bunch of functions/macros related to algo music, > >>> but it's not clear to me whether Grace is required to get that functionality. > >>> > >>> My application is to algorithmically generate midi to be played by virtual > >>> instruments. (i.e., route the midi to a VST or AU host.) > >>> > >>> Neil Baylis > >>> _______________________________________________ > >>> Cmdist mailing list > >>> Cmdist at ccrma.stanford.edu > >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > >>> > >>> _______________________________________________ > >>> Cmdist mailing list > >>> Cmdist at ccrma.stanford.edu > >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > >> > >> > >> _______________________________________________ > >> Cmdist mailing list > >> Cmdist at ccrma.stanford.edu > >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From ahcnz at orcon.net.nz Tue Mar 3 14:19:04 2020 From: ahcnz at orcon.net.nz (adam) Date: Wed, 04 Mar 2020 11:19:04 +1300 Subject: [CM] CM/Scheme without Grace? In-Reply-To: <20200303172226.GC57716@t480s-orm.localdomain> References: <20200228115215.GA32005@t480s-orm.localdomain> <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> <20200303172226.GC57716@t480s-orm.localdomain> Message-ID: <93b3fe46abcee8c8204ca1a43beb8946537c2d4d.camel@orcon.net.nz> Thank you Orm and Ric. I'm sure I'll have success with that tonight, as that all makes great sense. Fomus is good to have around. On Tue, 2020-03-03 at 18:22 +0100, Orm Finnendahl wrote: > Hi Adam, > > sorry, I was unaware of the fomus dependency in cm. I will get rid of > it as it is unneccessary. To get it running in the meantime, please > just go ahead and also clone "fomus" and "cm-fomus" from the same > github repo (they are fairly small): > > https://github.com/ormf/cm-fomus > https://github.com/ormf/fomus > > To get it up and running (with slime/quicklisp installed): > > - Put the "cm", "cm-fomus" and "fomus" folders into the > ~/quicklisp/local-projects/ folder > > - Optionally edit the attached .fomus file by filling in the paths to > the executables (evince and lilypond) in case they are installed on > your computer and copy the edited file to your home folder. > > - In the slime repl: > > CL-USER> (ql:quickload "cm") > > To load "cm": > Load 1 ASDF system: > cm > ; Loading "cm" > > ;; FOMUS v0.2.28 > ;; Lisp music notation formatter > ;; Copyright (c) 2005, 2006, 2007 David Psenicka, All Rights Reserved > ;; See file "COPYING" for terms of use and distribution. > > ;; Loading initialization file "/home/orm/.fomus"... > > ("cm") > CL-USER> (cm) > > /\\\ > ---\\\--------- > ----\\\-------- > ----/\\\------- Common Music 2.12.0 > ---/--\\\------ > --/----\\\----- > / \\\/ > > CL-USER> > > Let me know if you run into problems. > > Best, > Orm > > > Am Dienstag, den 03. M?rz 2020 um 14:48:48 Uhr (+0000) schrieb Taube, Heinrich K: > > You should be able comment out the fomus loading, that was just an optional package. > > > > > On Mar 3, 2020, at 4:18 AM, adam wrote: > > > > > > > > > Forgive me for asking, but how would I load and run the ../ormf/cm package? > > > > > > I have tried several approaches, including even /bin/cm.sh, with no success. > > > Am on Linux with a fresh and working Emacs Slime sbcl setup. > > > > > > Step one may be to save a working image, to thereafter load as slime's > > > lisp subprocess, as before. > > > > > > Through trial and error I find I can; > > > (load "cm.asd) -> T > > > > > > and then > > > (in-package :common-music-system) -> # > > > > > > however (cm) then returns an undefined function error. > > > > > > (load "./src/cm.lisp") -> error Component :FOMUS not found > > > do I need Fomus loaded beforehand? > > > > > > Any help much appreciated. > > > > > > > > > > > > > > > On Fri, 2020-02-28 at 12:52 +0100, Orm Finnendahl wrote: > > > > Hello Neil, > > > > > > > > in case you're interested in the Common Lisp port of cm, I'd > > > > recommend this repository, as it is more or less actively maintained > > > > (including the loop code fixed and extensions for realtime integration > > > > with incudine, svg im/export etc.): > > > > > > > > https://github.com/ormf/cm > > > > > > > > -- > > > > Orm > > > > > > > > Am Donnerstag, den 27. Februar 2020 um 18:18:30 Uhr (+0000) schrieb Taube, > > > > Heinrich K: > > > > > Hello Neil, that would be difficult as many of the scheme functions make calls > > > > > to c++ > > > > > code. > > > > > A better solution would be to use the common-lisp version available on the > > > > > source- > > > > > forge website, but of course then its not in Scheme. > > > > > > > > > > ?Rick > > > > > ________________________________ > > > > > Rick Taube > > > > > Chair, Composition/Theory > > > > > School of Music > > > > > University of Illinois Urbana-Champaign > > > > > Email: taube at illinois.edu > > > > > President, Illiac Software Inc. > > > > > https://harmonia.illiacsoftware.com/ > > > > > Email: taube at illiacsoftware.com > > > > > > > > > > > > > > > On Feb 27, 2020, at 11:45 AM, Neil Baylis > > > > neil.baylis at gmail.com>> wrote: > > > > > > > > > > Is it possible to run CM using scheme without the Grace application? For > > > > > example, by > > > > > just editing scheme files in an ordinary text editor? If so, can anyone point me > > > > > at > > > > > instructions for doing this? > > > > > > > > > > I see the Grace documentation lists a bunch of functions/macros related to algo > > > > > music, > > > > > but it's not clear to me whether Grace is required to get that functionality. > > > > > > > > > > My application is to algorithmically generate midi to be played by virtual > > > > > instruments. (i.e., route the midi to a VST or AU host.) > > > > > > > > > > Neil Baylis > > > > > _______________________________________________ > > > > > Cmdist mailing list > > > > > Cmdist at ccrma.stanford.edu > > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > > > _______________________________________________ > > > > > Cmdist mailing list > > > > > Cmdist at ccrma.stanford.edu > > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > > > > > _______________________________________________ > > > > Cmdist mailing list > > > > Cmdist at ccrma.stanford.edu > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > _______________________________________________ > > > Cmdist mailing list > > > Cmdist at ccrma.stanford.edu > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From neil.baylis at gmail.com Tue Mar 3 15:37:08 2020 From: neil.baylis at gmail.com (Neil Baylis) Date: Tue, 3 Mar 2020 15:37:08 -0800 Subject: [CM] Using many MIDI outs with CM Message-ID: I have a project that needs to send midi to more than 40 instruments at the same time. Is there a way to specify more than one midi bus for output in CM/Grace? The dialog for selecting midi bus seems to only allow one at a time. I've been able to make this work with Pure Data, but was hoping to switch the project to CM because I prefer that programming model. I've used CM in previous projects, but never with more than 16 instruments. Neil Baylis -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Tue Mar 3 16:46:36 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Tue, 3 Mar 2020 16:46:36 -0800 Subject: [CM] New home for Grace In-Reply-To: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> Message-ID: How to proceed? Building this on Ubuntu 19.10, I end with: premake4 --with-g++ /home/forrest/parent/sndlib/premake4.lua:95: attempt to call field 'is64bit' (a nil value) "lua" in this case seems to be lua 5.3.3 (?) Forrest Curo San Diego On Tue, Mar 3, 2020 at 9:21 AM Taube, Heinrich K wrote: > Ive moved the Grace repo to github where you can now download the > sources. It seems to build fine on MacOS and Linux, but I haven?t done > tons of testing yet so there are probably still some issues to fix. > Windows doesn't work yet ? I can compile and link everything, the app boots > but I dont seem to have s7 working yet. I?m sure it's something stupid > that I?ve done, but don't know much about VisualStudio2019 so right now I'm > still in the dark. Thank you Bill for all your help! > > This release is basically a major cleanup to get things building and > running again in the very latest juce and sndlib/s7. Grace is a pretty old > app so the next thing I will do is probably continue to simplify and > modernize its code base. I will also add an internal midi synth (a juce > fork of the sfzero sound font player) so that there is internal playback > support on all OSes. > > here is how to download the sources, the grace/README.md will tell you > what to do. > > $ git clone https://github.com/ricktaube/grace.git grace > > One thing I need to do asap is have documentation hosted by the github > repo if at all possible. Iff anybody knows how to host a homepage for a > github repo please let me know. > > ?Rick > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Tue Mar 3 17:25:05 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Wed, 4 Mar 2020 01:25:05 +0000 Subject: [CM] Using many MIDI outs with CM In-Reply-To: References: Message-ID: im working on midi in/out right now. im going to replace the old ports with the standard juce audio device manager, wichc lets you set multiple midi inputs (and outputs i assume) > On Mar 3, 2020, at 5:37 PM, Neil Baylis wrote: > > I have a project that needs to send midi to more than 40 instruments at the same time. Is there a way to specify more than one midi bus for output in CM/Grace? The dialog for selecting midi bus seems to only allow one at a time. > > I've been able to make this work with Pure Data, but was hoping to switch the project to CM because I prefer that programming model. I've used CM in previous projects, but never with more than 16 instruments. > > Neil Baylis > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From taube at illinois.edu Tue Mar 3 17:35:48 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Wed, 4 Mar 2020 01:35:48 +0000 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> Message-ID: <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> yes i hit that too, i thought i sent the edited file to bil but i see i forgot. you can edit the premake.lua file replace that call with either true or false for your machine type. there might be some lua call that will return that value. im not sure why its not in premake. On Mar 3, 2020, at 6:46 PM, Forrest Curo > wrote: How to proceed? Building this on Ubuntu 19.10, I end with: premake4 --with-g++ /home/forrest/parent/sndlib/premake4.lua:95: attempt to call field 'is64bit' (a nil value) "lua" in this case seems to be lua 5.3.3 (?) Forrest Curo San Diego On Tue, Mar 3, 2020 at 9:21 AM Taube, Heinrich K > wrote: Ive moved the Grace repo to github where you can now download the sources. It seems to build fine on MacOS and Linux, but I haven?t done tons of testing yet so there are probably still some issues to fix. Windows doesn't work yet ? I can compile and link everything, the app boots but I dont seem to have s7 working yet. I?m sure it's something stupid that I?ve done, but don't know much about VisualStudio2019 so right now I'm still in the dark. Thank you Bill for all your help! This release is basically a major cleanup to get things building and running again in the very latest juce and sndlib/s7. Grace is a pretty old app so the next thing I will do is probably continue to simplify and modernize its code base. I will also add an internal midi synth (a juce fork of the sfzero sound font player) so that there is internal playback support on all OSes. here is how to download the sources, the grace/README.md will tell you what to do. $ git clone https://github.com/ricktaube/grace.git grace One thing I need to do asap is have documentation hosted by the github repo if at all possible. Iff anybody knows how to host a homepage for a github repo please let me know. ?Rick _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Tue Mar 3 17:57:59 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Tue, 3 Mar 2020 17:57:59 -0800 Subject: [CM] New home for Grace In-Reply-To: <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> Message-ID: Thanks, that worked! (Now to go wrestle with juce...) On Tue, Mar 3, 2020 at 5:35 PM Taube, Heinrich K wrote: > yes i hit that too, i thought i sent the edited file to bil but i see i > forgot. > you can edit the premake.lua file replace that call with either true or > false for your machine type. there might be some lua call that will return > that value. im not sure why its not in premake. > > > > On Mar 3, 2020, at 6:46 PM, Forrest Curo wrote: > > How to proceed? > > Building this on Ubuntu 19.10, I end with: > premake4 --with-g++ > /home/forrest/parent/sndlib/premake4.lua:95: attempt to call field > 'is64bit' (a nil value) > > "lua" in this case seems to be lua 5.3.3 > > (?) > Forrest Curo > San Diego > > > > On Tue, Mar 3, 2020 at 9:21 AM Taube, Heinrich K > wrote: > >> Ive moved the Grace repo to github where you can now download the >> sources. It seems to build fine on MacOS and Linux, but I haven?t done >> tons of testing yet so there are probably still some issues to fix. >> Windows doesn't work yet ? I can compile and link everything, the app boots >> but I dont seem to have s7 working yet. I?m sure it's something stupid >> that I?ve done, but don't know much about VisualStudio2019 so right now I'm >> still in the dark. Thank you Bill for all your help! >> >> This release is basically a major cleanup to get things building and >> running again in the very latest juce and sndlib/s7. Grace is a pretty old >> app so the next thing I will do is probably continue to simplify and >> modernize its code base. I will also add an internal midi synth (a juce >> fork of the sfzero sound font player) so that there is internal playback >> support on all OSes. >> >> here is how to download the sources, the grace/README.md will tell you >> what to do. >> >> $ git clone https://github.com/ricktaube/grace.git grace >> >> One thing I need to do asap is have documentation hosted by the github >> repo if at all possible. Iff anybody knows how to host a homepage for a >> github repo please let me know. >> >> ?Rick >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Tue Mar 3 18:15:50 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Wed, 4 Mar 2020 02:15:50 +0000 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> Message-ID: <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> it should be straightforward just clone it and then use the linux build script in grace/Builds/ directory. here is the list of juce dependencies for linux: https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33 I did not have any problems building either sndlib or grace on my stock ubuntu pc once i had the dependencies for sndlib and juce installed. But if you need to do something special on your linux you will want to build the juce/extras/Projucer app in gpl mode and then regenerate grace's linux build script. On Mar 3, 2020, at 7:57 PM, Forrest Curo > wrote: (Now to go wrestle with juce...) -------------- next part -------------- An HTML attachment was scrubbed... URL: From orm.finnendahl at selma.hfmdk-frankfurt.de Wed Mar 4 00:29:34 2020 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Wed, 4 Mar 2020 09:29:34 +0100 Subject: [CM] Using many MIDI outs with CM In-Reply-To: References: Message-ID: <20200304082934.GA104739@t480s-orm.localdomain> Hi Neil, a couple of years back I did this using 40 mictrotonal softsynths (occupying 4 Midi Channels each) in realtime. But that was using the Common Lisp version of cm (with incudine as the real time engine) and therefore might not be what you're looking for. Otherwise drop me a note and I'll help to get you going. -- Orm Am Dienstag, den 03. M?rz 2020 um 15:37:08 Uhr (-0800) schrieb Neil Baylis: > I have a project that needs to send midi to more than 40 instruments at the > same time. Is there a way to specify more than one midi bus for output in > CM/Grace? The dialog for selecting midi bus seems to only allow one at a > time. > > I've been able to make this work with Pure Data, but was hoping to switch > the project to CM because I prefer that programming model. I've used CM in > previous projects, but never with more than 16 instruments. > > Neil Baylis > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From orm.finnendahl at selma.hfmdk-frankfurt.de Wed Mar 4 01:02:11 2020 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Wed, 4 Mar 2020 10:02:11 +0100 Subject: [CM] CM/Scheme without Grace? In-Reply-To: <93b3fe46abcee8c8204ca1a43beb8946537c2d4d.camel@orcon.net.nz> References: <20200228115215.GA32005@t480s-orm.localdomain> <81b061512decab4e53f87ef7865eb92d26d2d204.camel@orcon.net.nz> <01CD68AD-F76F-46F6-9288-EC2E35FEC4D9@illinois.edu> <20200303172226.GC57716@t480s-orm.localdomain> <93b3fe46abcee8c8204ca1a43beb8946537c2d4d.camel@orcon.net.nz> Message-ID: <20200304090211.GB104739@t480s-orm.localdomain> Hi Adam, out of respect for the original cm I didn't change Rick's README, but since you're using the slime port and emacs: In the quicklisp "cm" folder is the file "etc/extras/emacs/cm.el". You can include that by putting the following lines into the emacs init file (normally located at "~/.emacs.d/init.el"): (add-to-list 'load-path "~/quicklisp/local-projects/cm/etc/emacs/") (require 'cm) (defvar *common-music-doc-root* (concat "file://" (expand-file-name "~/quicklisp/local-projects/cm/doc/")) "The root url for visiting CM documentation.") This will bring custom cm menus to your emacs, but more importantly will give you online help for cm by moving the cursor after a cm symbol and pressing "C-c C-d c". This was all part of cm back in 2007. I just updated the html to work on current browsers. I guess I should put that and other installation info into the README of the github page as this isn't something people will easily find. -- Orm Am Mittwoch, den 04. M?rz 2020 um 11:19:04 Uhr (+1300) schrieb adam: > > Thank you Orm and Ric. > > I'm sure I'll have success with that tonight, as that all makes great sense. > > Fomus is good to have around. > > > > > On Tue, 2020-03-03 at 18:22 +0100, Orm Finnendahl wrote: > > Hi Adam, > > > > sorry, I was unaware of the fomus dependency in cm. I will get rid of > > it as it is unneccessary. To get it running in the meantime, please > > just go ahead and also clone "fomus" and "cm-fomus" from the same > > github repo (they are fairly small): > > > > https://github.com/ormf/cm-fomus > > https://github.com/ormf/fomus > > > > To get it up and running (with slime/quicklisp installed): > > > > - Put the "cm", "cm-fomus" and "fomus" folders into the > > ~/quicklisp/local-projects/ folder > > > > - Optionally edit the attached .fomus file by filling in the paths to > > the executables (evince and lilypond) in case they are installed on > > your computer and copy the edited file to your home folder. > > > > - In the slime repl: > > > > CL-USER> (ql:quickload "cm") > > > > To load "cm": > > Load 1 ASDF system: > > cm > > ; Loading "cm" > > > > ;; FOMUS v0.2.28 > > ;; Lisp music notation formatter > > ;; Copyright (c) 2005, 2006, 2007 David Psenicka, All Rights Reserved > > ;; See file "COPYING" for terms of use and distribution. > > > > ;; Loading initialization file "/home/orm/.fomus"... > > > > ("cm") > > CL-USER> (cm) > > > > /\\\ > > ---\\\--------- > > ----\\\-------- > > ----/\\\------- Common Music 2.12.0 > > ---/--\\\------ > > --/----\\\----- > > / \\\/ > > > > CL-USER> > > > > Let me know if you run into problems. > > > > Best, > > Orm > > > > > > Am Dienstag, den 03. M?rz 2020 um 14:48:48 Uhr (+0000) schrieb Taube, Heinrich K: > > > You should be able comment out the fomus loading, that was just an optional package. > > > > > > > On Mar 3, 2020, at 4:18 AM, adam wrote: > > > > > > > > > > > > Forgive me for asking, but how would I load and run the ../ormf/cm package? > > > > > > > > I have tried several approaches, including even /bin/cm.sh, with no success. > > > > Am on Linux with a fresh and working Emacs Slime sbcl setup. > > > > > > > > Step one may be to save a working image, to thereafter load as slime's > > > > lisp subprocess, as before. > > > > > > > > Through trial and error I find I can; > > > > (load "cm.asd) -> T > > > > > > > > and then > > > > (in-package :common-music-system) -> # > > > > > > > > however (cm) then returns an undefined function error. > > > > > > > > (load "./src/cm.lisp") -> error Component :FOMUS not found > > > > do I need Fomus loaded beforehand? > > > > > > > > Any help much appreciated. > > > > > > > > > > > > > > > > > > > > On Fri, 2020-02-28 at 12:52 +0100, Orm Finnendahl wrote: > > > > > Hello Neil, > > > > > > > > > > in case you're interested in the Common Lisp port of cm, I'd > > > > > recommend this repository, as it is more or less actively maintained > > > > > (including the loop code fixed and extensions for realtime integration > > > > > with incudine, svg im/export etc.): > > > > > > > > > > https://github.com/ormf/cm > > > > > > > > > > -- > > > > > Orm > > > > > > > > > > Am Donnerstag, den 27. Februar 2020 um 18:18:30 Uhr (+0000) schrieb Taube, > > > > > Heinrich K: > > > > > > Hello Neil, that would be difficult as many of the scheme functions make calls > > > > > > to c++ > > > > > > code. > > > > > > A better solution would be to use the common-lisp version available on the > > > > > > source- > > > > > > forge website, but of course then its not in Scheme. > > > > > > > > > > > > ?Rick > > > > > > ________________________________ > > > > > > Rick Taube > > > > > > Chair, Composition/Theory > > > > > > School of Music > > > > > > University of Illinois Urbana-Champaign > > > > > > Email: taube at illinois.edu > > > > > > President, Illiac Software Inc. > > > > > > https://harmonia.illiacsoftware.com/ > > > > > > Email: taube at illiacsoftware.com > > > > > > > > > > > > > > > > > > On Feb 27, 2020, at 11:45 AM, Neil Baylis > > > > > neil.baylis at gmail.com>> wrote: > > > > > > > > > > > > Is it possible to run CM using scheme without the Grace application? For > > > > > > example, by > > > > > > just editing scheme files in an ordinary text editor? If so, can anyone point me > > > > > > at > > > > > > instructions for doing this? > > > > > > > > > > > > I see the Grace documentation lists a bunch of functions/macros related to algo > > > > > > music, > > > > > > but it's not clear to me whether Grace is required to get that functionality. > > > > > > > > > > > > My application is to algorithmically generate midi to be played by virtual > > > > > > instruments. (i.e., route the midi to a VST or AU host.) > > > > > > > > > > > > Neil Baylis > > > > > > _______________________________________________ > > > > > > Cmdist mailing list > > > > > > Cmdist at ccrma.stanford.edu > > > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > > > > > _______________________________________________ > > > > > > Cmdist mailing list > > > > > > Cmdist at ccrma.stanford.edu > > > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > > > > > > > > _______________________________________________ > > > > > Cmdist mailing list > > > > > Cmdist at ccrma.stanford.edu > > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > _______________________________________________ > > > > Cmdist mailing list > > > > Cmdist at ccrma.stanford.edu > > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > > > > > > > _______________________________________________ > > > Cmdist mailing list > > > Cmdist at ccrma.stanford.edu > > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > From iainduncanlists at gmail.com Wed Mar 4 07:54:48 2020 From: iainduncanlists at gmail.com (Iain Duncan) Date: Wed, 4 Mar 2020 07:54:48 -0800 Subject: [CM] New home for Grace In-Reply-To: <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> Message-ID: This is awesome news! I'm looking forward to working with CM and S7 in both Juce and Max myself. Thanks for putting it on Github Rick. iain On Tue, Mar 3, 2020 at 6:16 PM Taube, Heinrich K wrote: > it should be straightforward just clone it and then use the linux build > script in grace/Builds/ directory. here is the list of juce dependencies > for linux: > https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33 > I did not have any problems building either sndlib or grace on my stock > ubuntu pc once i had the dependencies for sndlib and juce installed. But > if you need to do something special on your linux you will want to build > the juce/extras/Projucer app in gpl mode and then regenerate grace's linux > build script. > > > > > On Mar 3, 2020, at 7:57 PM, Forrest Curo wrote: > > (Now to go wrestle with juce...) > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Wed Mar 4 12:05:50 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Wed, 4 Mar 2020 12:05:50 -0800 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> Message-ID: Not familiar with juce, but it compiled without error. It's in compiling grace that I continue to find befnurglement: " ~/parent/grace/Builds/LinuxMakefile$ make Compiling Audio.cpp In file included from ../../Source/Libraries.h:8, from ../../Source/Enumerations.h:17, from ../../Source/Audio.cpp:15: ../../Source/../JuceLibraryCode/JuceHeader.h:17:10: fatal error: juce_audio_basics/juce_audio_basics.h: No such file or directory 17 | #include | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:128: build/intermediate/Debug/Audio_a9638c37.o] Error 1 " -- -- -- -- - -- - -- - -- -- Should I try to use juce to chug out a new makefile...? Or move juce_audio_basics_/juce_audio_basics.h from ~/parent/juce/modules/ to wherever the Linux makefile expects to find it? Forrest Curo San Diego On Wed, Mar 4, 2020 at 7:54 AM Iain Duncan wrote: > This is awesome news! I'm looking forward to working with CM and S7 in > both Juce and Max myself. Thanks for putting it on Github Rick. > > iain > > On Tue, Mar 3, 2020 at 6:16 PM Taube, Heinrich K > wrote: > >> it should be straightforward just clone it and then use the linux build >> script in grace/Builds/ directory. here is the list of juce dependencies >> for linux: >> https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33 >> I did not have any problems building either sndlib or grace on my stock >> ubuntu pc once i had the dependencies for sndlib and juce installed. But >> if you need to do something special on your linux you will want to build >> the juce/extras/Projucer app in gpl mode and then regenerate grace's linux >> build script. >> >> >> >> >> On Mar 3, 2020, at 7:57 PM, Forrest Curo wrote: >> >> (Now to go wrestle with juce...) >> >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Wed Mar 4 14:35:56 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Wed, 4 Mar 2020 22:35:56 +0000 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> Message-ID: <3DEEA3E9-5149-4554-929C-2936BD115F9F@illinois.edu> looks like it can find the path to juce, not sure why yet (im traveiing). when i get to my hotel ill look at my Grace.projucer and make sure the path to juce is relative. On Mar 4, 2020, at 2:05 PM, Forrest Curo > wrote: Not familiar with juce, but it compiled without error. It's in compiling grace that I continue to find befnurglement: " ~/parent/grace/Builds/LinuxMakefile$ make Compiling Audio.cpp In file included from ../../Source/Libraries.h:8, from ../../Source/Enumerations.h:17, from ../../Source/Audio.cpp:15: ../../Source/../JuceLibraryCode/JuceHeader.h:17:10: fatal error: juce_audio_basics/juce_audio_basics.h: No such file or directory 17 | #include | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:128: build/intermediate/Debug/Audio_a9638c37.o] Error 1 " -- -- -- -- - -- - -- - -- -- Should I try to use juce to chug out a new makefile...? Or move juce_audio_basics_/juce_audio_basics.h from ~/parent/juce/modules/ to wherever the Linux makefile expects to find it? Forrest Curo San Diego On Wed, Mar 4, 2020 at 7:54 AM Iain Duncan > wrote: This is awesome news! I'm looking forward to working with CM and S7 in both Juce and Max myself. Thanks for putting it on Github Rick. iain On Tue, Mar 3, 2020 at 6:16 PM Taube, Heinrich K > wrote: it should be straightforward just clone it and then use the linux build script in grace/Builds/ directory. here is the list of juce dependencies for linux: https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33 I did not have any problems building either sndlib or grace on my stock ubuntu pc once i had the dependencies for sndlib and juce installed. But if you need to do something special on your linux you will want to build the juce/extras/Projucer app in gpl mode and then regenerate grace's linux build script. On Mar 3, 2020, at 7:57 PM, Forrest Curo > wrote: (Now to go wrestle with juce...) _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Wed Mar 4 14:42:36 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Wed, 4 Mar 2020 14:42:36 -0800 Subject: [CM] New home for Grace In-Reply-To: <3DEEA3E9-5149-4554-929C-2936BD115F9F@illinois.edu> References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> <3DEEA3E9-5149-4554-929C-2936BD115F9F@illinois.edu> Message-ID: Yeah. Trying to manually reset paths in JuceHeader.h has been *^@%*!&@#!!! Again, thanks! On Wed, Mar 4, 2020 at 2:36 PM Taube, Heinrich K wrote: > looks like it can find the path to juce, not sure why yet (im traveiing). > when i get to my hotel ill look at my Grace.projucer and make sure the > path to juce is relative. > > On Mar 4, 2020, at 2:05 PM, Forrest Curo wrote: > > Not familiar with juce, but it compiled without error. > > It's in compiling grace that I continue to find befnurglement: > > " > ~/parent/grace/Builds/LinuxMakefile$ make > Compiling Audio.cpp > In file included from ../../Source/Libraries.h:8, > from ../../Source/Enumerations.h:17, > from ../../Source/Audio.cpp:15: > ../../Source/../JuceLibraryCode/JuceHeader.h:17:10: fatal error: > juce_audio_basics/juce_audio_basics.h: No such file or directory > 17 | #include > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > compilation terminated. > make: *** [Makefile:128: build/intermediate/Debug/Audio_a9638c37.o] Error > 1 > " > -- -- -- -- - -- - -- - -- -- > Should I try to use juce to chug out a new makefile...? Or move > juce_audio_basics_/juce_audio_basics.h > from ~/parent/juce/modules/ to wherever the Linux makefile expects to > find it? > > Forrest Curo > San Diego > > > On Wed, Mar 4, 2020 at 7:54 AM Iain Duncan > wrote: > >> This is awesome news! I'm looking forward to working with CM and S7 in >> both Juce and Max myself. Thanks for putting it on Github Rick. >> >> iain >> >> On Tue, Mar 3, 2020 at 6:16 PM Taube, Heinrich K >> wrote: >> >>> it should be straightforward just clone it and then use the linux build >>> script in grace/Builds/ directory. here is the list of juce dependencies >>> for linux: >>> https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33 >>> I did not have any problems building either sndlib or grace on my stock >>> ubuntu pc once i had the dependencies for sndlib and juce installed. But >>> if you need to do something special on your linux you will want to build >>> the juce/extras/Projucer app in gpl mode and then regenerate grace's linux >>> build script. >>> >>> >>> >>> >>> On Mar 3, 2020, at 7:57 PM, Forrest Curo wrote: >>> >>> (Now to go wrestle with juce...) >>> >>> >>> _______________________________________________ >>> Cmdist mailing list >>> Cmdist at ccrma.stanford.edu >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Wed Mar 4 14:53:30 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Wed, 4 Mar 2020 22:53:30 +0000 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> <3DEEA3E9-5149-4554-929C-2936BD115F9F@illinois.edu> Message-ID: <8B55B9CF-C247-4A0D-93C3-0B03619DD71F@illinois.edu> I would not advise doing it that way ? you should only every have to edit the projucer file and it will take care of regenerating the projects with the changes. ill get to it sometime tonight or early tomorrow morning. On Mar 4, 2020, at 4:42 PM, Forrest Curo > wrote: Yeah. Trying to manually reset paths in JuceHeader.h has been *^@%*!&@#!!! Again, thanks! On Wed, Mar 4, 2020 at 2:36 PM Taube, Heinrich K > wrote: looks like it can find the path to juce, not sure why yet (im traveiing). when i get to my hotel ill look at my Grace.projucer and make sure the path to juce is relative. On Mar 4, 2020, at 2:05 PM, Forrest Curo > wrote: Not familiar with juce, but it compiled without error. It's in compiling grace that I continue to find befnurglement: " ~/parent/grace/Builds/LinuxMakefile$ make Compiling Audio.cpp In file included from ../../Source/Libraries.h:8, from ../../Source/Enumerations.h:17, from ../../Source/Audio.cpp:15: ../../Source/../JuceLibraryCode/JuceHeader.h:17:10: fatal error: juce_audio_basics/juce_audio_basics.h: No such file or directory 17 | #include | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:128: build/intermediate/Debug/Audio_a9638c37.o] Error 1 " -- -- -- -- - -- - -- - -- -- Should I try to use juce to chug out a new makefile...? Or move juce_audio_basics_/juce_audio_basics.h from ~/parent/juce/modules/ to wherever the Linux makefile expects to find it? Forrest Curo San Diego On Wed, Mar 4, 2020 at 7:54 AM Iain Duncan > wrote: This is awesome news! I'm looking forward to working with CM and S7 in both Juce and Max myself. Thanks for putting it on Github Rick. iain On Tue, Mar 3, 2020 at 6:16 PM Taube, Heinrich K > wrote: it should be straightforward just clone it and then use the linux build script in grace/Builds/ directory. here is the list of juce dependencies for linux: https://forum.juce.com/t/list-of-juce-dependencies-under-linux/15121/33 I did not have any problems building either sndlib or grace on my stock ubuntu pc once i had the dependencies for sndlib and juce installed. But if you need to do something special on your linux you will want to build the juce/extras/Projucer app in gpl mode and then regenerate grace's linux build script. On Mar 3, 2020, at 7:57 PM, Forrest Curo > wrote: (Now to go wrestle with juce...) _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Thu Mar 5 04:40:54 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Thu, 5 Mar 2020 12:40:54 +0000 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> Message-ID: <5788B4BE-CE4B-45FD-A629-D197D1C2588F@illinois.edu> I?ve changed Grace.jucer to use realtive pathnames so if you do a git pull you should get new build systems that you can try out (I wont have access to linux or windows until sunday to test.). As it stands the grace project expects a parent directory that contains juce, sndlb and grace as described in the readme. But if you don't like that you can change Grace.jucer in the Projucer to fit your needs, that's why its included. From taube at illinois.edu Thu Mar 5 07:28:42 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Thu, 5 Mar 2020 15:28:42 +0000 Subject: [CM] New home for Grace In-Reply-To: References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> <5788B4BE-CE4B-45FD-A629-D197D1C2588F@illinois.edu> Message-ID: <99D75258-FA65-42C7-B16C-7314741EC070@illinois.edu> once you do 'git clone https://github.com/WeAreROLI/JUCE.git juce? you shouldn't need to interact with the juce website at all. If you need to change Grace's build process you will edit Grace.jucer, make your changes, and regenerate the builds. For this you can build the juce/extras/Projucer app in GPL mode using one of their premade projects. On Mar 5, 2020, at 8:48 AM, Forrest Curo > wrote: Thanks much for humoring my impatience. (The delay gave me time to start a batch of sauerkraut before my cabbage rotted the wrong way in the fridge.) So, Projucer is in the package... If I don't have to mess with the JUCE website, that should save considerable annoyance. Onward, whee! On Thu, Mar 5, 2020 at 4:52 AM Taube, Heinrich K > wrote: I?ve changed Grace.jucer to use realtive pathnames so if you do a git pull you should get new build systems that you can try out (I wont have access to linux or windows until sunday to test.). As it stands the grace project expects a parent directory that contains juce, sndlb and grace as described in the readme. But if you don't like that you can change Grace.jucer in the Projucer to fit your needs, that's why its included. -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 10:32:46 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 10:32:46 -0800 Subject: [CM] New home for Grace In-Reply-To: <99D75258-FA65-42C7-B16C-7314741EC070@illinois.edu> References: <4E97ED84-EA83-4DDE-A618-1A1B9ED8B723@illinois.edu> <99787784-F549-4D73-B80E-097FBA893D00@illinois.edu> <5A1C6552-3112-4C3E-AED0-1501D086186D@illinois.edu> <5788B4BE-CE4B-45FD-A629-D197D1C2588F@illinois.edu> <99D75258-FA65-42C7-B16C-7314741EC070@illinois.edu> Message-ID: Yes. On alternate computer (Ubuntu 18.04) I initially run into: #error "This project was last saved using an outdated version of the Projucer! Re-save this project with the latest version to fix this error." which is fixable by editing: parent/juce/extras/Projucer/JuceLibraryCode/AppConfig.h to read (line 35): #define JUCER_ENABLE_GPL_MODE 1 Then to make Projucer then execute from terminal and open ~/parent/grace/Grace.jucer then save. and Grace (compilation) goes abounding along, whee! Hope this helps! On Thu, Mar 5, 2020 at 7:28 AM Taube, Heinrich K wrote: > once you do 'git clone https://github.com/WeAreROLI/JUCE.git juce? you > shouldn't need to interact with the juce website at all. > > If you need to change Grace's build process you will edit Grace.jucer, > make your changes, and regenerate the builds. For this you can build the > juce/extras/Projucer app in GPL mode using one of their premade projects. > > On Mar 5, 2020, at 8:48 AM, Forrest Curo wrote: > > Thanks much for humoring my impatience. (The delay gave me time to start a > batch of sauerkraut before my cabbage rotted the wrong way in the fridge.) > > So, Projucer is in the package... If I don't have to mess with the JUCE > website, that should save considerable annoyance. > > Onward, whee! > > On Thu, Mar 5, 2020 at 4:52 AM Taube, Heinrich K > wrote: > >> I?ve changed Grace.jucer to use realtive pathnames so if you do a git >> pull you should get new build systems that you can try out (I wont have >> access to linux or windows until sunday to test.). As it stands the grace >> project expects a parent directory that contains juce, sndlb and grace as >> described in the readme. But if you don't like that you can change >> Grace.jucer in the Projucer to fit your needs, that's why its included. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 14:18:58 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 14:18:58 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? Message-ID: I have csound running & set to receive udp (i.e. --port=4567 ) ( https://csound.com/docs/manual/udpserver.html ) I can send lines it lines for immediate output from pure data: [send scoreline_i "i 2 0 3 440 .5" ( | [netsend -u ] likewise channel values: [send @valu 330 ( | [netsend -u ] but in Grace the OSC examples are based on sending to an established TCP connection to Supercollider. What to do? -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Thu Mar 5 14:27:05 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Thu, 5 Mar 2020 22:27:05 +0000 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: Message-ID: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> You should be able to send OSC to any port you want, look in the Audio menu for the OSC Connections? command. I haven?t tested OSC yet on this release... On Mar 5, 2020, at 4:18 PM, Forrest Curo > wrote: I have csound running & set to receive udp (i.e. --port=4567 ) ( https://csound.com/docs/manual/udpserver.html ) I can send lines it lines for immediate output from pure data: [send scoreline_i "i 2 0 3 440 .5" ( | [netsend -u ] likewise channel values: [send @valu 330 ( | [netsend -u ] but in Grace the OSC examples are based on sending to an established TCP connection to Supercollider. What to do? _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 15:17:59 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 15:17:59 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: syntax for sending a string to a port? On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K wrote: > You should be able to send OSC to any port you want, look in the Audio > menu for the OSC Connections? command. > I haven?t tested OSC yet on this release... > > On Mar 5, 2020, at 4:18 PM, Forrest Curo wrote: > > I have csound running & set to receive udp (i.e. --port=4567 ) > > ( https://csound.com/docs/manual/udpserver.html ) > > I can send lines it lines for immediate output from pure data: > [send scoreline_i "i 2 0 3 440 .5" ( > | > [netsend -u ] > > likewise channel values: > > [send @valu 330 ( > | > [netsend -u ] > > but in Grace the OSC examples are based on sending to an established TCP > connection to Supercollider. > > What to do? > > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 15:24:20 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 15:24:20 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: cm says "OSC send test succeeded" & csound says: error: syntax error, unexpected '/' (token "/") line 7: >>>/ <<< Parsing failed due to invalid input! Stopping on parser failure On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo wrote: > syntax for sending a string to a port? > > On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K > wrote: > >> You should be able to send OSC to any port you want, look in the Audio >> menu for the OSC Connections? command. >> I haven?t tested OSC yet on this release... >> >> On Mar 5, 2020, at 4:18 PM, Forrest Curo wrote: >> >> I have csound running & set to receive udp (i.e. --port=4567 ) >> >> ( https://csound.com/docs/manual/udpserver.html ) >> >> I can send lines it lines for immediate output from pure data: >> [send scoreline_i "i 2 0 3 440 .5" ( >> | >> [netsend -u ] >> >> likewise channel values: >> >> [send @valu 330 ( >> | >> [netsend -u ] >> >> but in Grace the OSC examples are based on sending to an established TCP >> connection to Supercollider. >> >> What to do? >> >> >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 15:53:48 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 15:53:48 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: Supercollider is set up to accept udp formatted as OSC messages. Csound 'expects' score events instead. I'd know how to format these if I knew how to specify a string and send it from, Grace. On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo wrote: > cm says "OSC send test succeeded" > & csound says: > error: syntax error, unexpected '/' (token "/") line 7: > >>>/ <<< > Parsing failed due to invalid input! > Stopping on parser failure > > > > On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo wrote: > >> syntax for sending a string to a port? >> >> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K >> wrote: >> >>> You should be able to send OSC to any port you want, look in the Audio >>> menu for the OSC Connections? command. >>> I haven?t tested OSC yet on this release... >>> >>> On Mar 5, 2020, at 4:18 PM, Forrest Curo wrote: >>> >>> I have csound running & set to receive udp (i.e. --port=4567 ) >>> >>> ( https://csound.com/docs/manual/udpserver.html ) >>> >>> I can send lines it lines for immediate output from pure data: >>> [send scoreline_i "i 2 0 3 440 .5" ( >>> | >>> [netsend -u ] >>> >>> likewise channel values: >>> >>> [send @valu 330 ( >>> | >>> [netsend -u ] >>> >>> but in Grace the OSC examples are based on sending to an established TCP >>> connection to Supercollider. >>> >>> What to do? >>> >>> >>> >>> _______________________________________________ >>> Cmdist mailing list >>> Cmdist at ccrma.stanford.edu >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>> >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 16:14:44 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 16:14:44 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: Put in a header; csound objects. Leave it out; Grace calls an error. On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo wrote: > Supercollider is set up to accept udp formatted as OSC messages. > > Csound 'expects' score events instead. I'd know how to format these if I > knew how to specify a string and send it from, Grace. > > On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo wrote: > >> cm says "OSC send test succeeded" >> & csound says: >> error: syntax error, unexpected '/' (token "/") line 7: >> >>>/ <<< >> Parsing failed due to invalid input! >> Stopping on parser failure >> >> >> >> On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo >> wrote: >> >>> syntax for sending a string to a port? >>> >>> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K >>> wrote: >>> >>>> You should be able to send OSC to any port you want, look in the Audio >>>> menu for the OSC Connections? command. >>>> I haven?t tested OSC yet on this release... >>>> >>>> On Mar 5, 2020, at 4:18 PM, Forrest Curo wrote: >>>> >>>> I have csound running & set to receive udp (i.e. --port=4567 ) >>>> >>>> ( https://csound.com/docs/manual/udpserver.html ) >>>> >>>> I can send lines it lines for immediate output from pure data: >>>> [send scoreline_i "i 2 0 3 440 .5" ( >>>> | >>>> [netsend -u ] >>>> >>>> likewise channel values: >>>> >>>> [send @valu 330 ( >>>> | >>>> [netsend -u ] >>>> >>>> but in Grace the OSC examples are based on sending to an established >>>> TCP connection to Supercollider. >>>> >>>> What to do? >>>> >>>> >>>> >>>> _______________________________________________ >>>> Cmdist mailing list >>>> Cmdist at ccrma.stanford.edu >>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>>> >>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From taube at illinois.edu Thu Mar 5 16:36:46 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Fri, 6 Mar 2020 00:36:46 +0000 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: im pretty sure grace is sending valid osc messages, i cant tell what going on from the information you are giving me On Mar 5, 2020, at 6:14 PM, Forrest Curo > wrote: Put in a header; csound objects. Leave it out; Grace calls an error. On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo > wrote: Supercollider is set up to accept udp formatted as OSC messages. Csound 'expects' score events instead. I'd know how to format these if I knew how to specify a string and send it from, Grace. On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo > wrote: cm says "OSC send test succeeded" & csound says: error: syntax error, unexpected '/' (token "/") line 7: >>>/ <<< Parsing failed due to invalid input! Stopping on parser failure On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo > wrote: syntax for sending a string to a port? On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K > wrote: You should be able to send OSC to any port you want, look in the Audio menu for the OSC Connections? command. I haven?t tested OSC yet on this release... On Mar 5, 2020, at 4:18 PM, Forrest Curo > wrote: I have csound running & set to receive udp (i.e. --port=4567 ) ( https://csound.com/docs/manual/udpserver.html ) I can send lines it lines for immediate output from pure data: [send scoreline_i "i 2 0 3 440 .5" ( | [netsend -u ] likewise channel values: [send @valu 330 ( | [netsend -u ] but in Grace the OSC examples are based on sending to an established TCP connection to Supercollider. What to do? _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 18:05:04 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 18:05:04 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: Grace is sending valid osc messages. If these were going to Supercollider, that's how they'd be handled. Received by the csound udp server, valid osc is not valid realtime score events. Since JUCE is largely a C++ compiler... I should be able to #include and add code to either write csound score lines to a fifo, or call bash's 'nc' to udp them to another computer. (?) Those approaches wouldn't be graceful, but they are ways I could (eventually) do it for myself. On Thu, Mar 5, 2020 at 5:12 PM Taube, Heinrich K wrote: > im pretty sure grace is sending valid osc messages, i cant tell what going > on from the information you are giving me > > On Mar 5, 2020, at 6:14 PM, Forrest Curo wrote: > > Put in a header; csound objects. > Leave it out; Grace calls an error. > > On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo wrote: > >> Supercollider is set up to accept udp formatted as OSC messages. >> >> Csound 'expects' score events instead. I'd know how to format these if I >> knew how to specify a string and send it from, Grace. >> >> On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo >> wrote: >> >>> cm says "OSC send test succeeded" >>> & csound says: >>> error: syntax error, unexpected '/' (token "/") line 7: >>> >>>/ <<< >>> Parsing failed due to invalid input! >>> Stopping on parser failure >>> >>> >>> >>> On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo >>> wrote: >>> >>>> syntax for sending a string to a port? >>>> >>>> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K >>>> wrote: >>>> >>>>> You should be able to send OSC to any port you want, look in the >>>>> Audio menu for the OSC Connections? command. >>>>> I haven?t tested OSC yet on this release... >>>>> >>>>> On Mar 5, 2020, at 4:18 PM, Forrest Curo >>>>> wrote: >>>>> >>>>> I have csound running & set to receive udp (i.e. --port=4567 ) >>>>> >>>>> ( https://csound.com/docs/manual/udpserver.html ) >>>>> >>>>> I can send lines it lines for immediate output from pure data: >>>>> [send scoreline_i "i 2 0 3 440 .5" ( >>>>> | >>>>> [netsend -u ] >>>>> >>>>> likewise channel values: >>>>> >>>>> [send @valu 330 ( >>>>> | >>>>> [netsend -u ] >>>>> >>>>> but in Grace the OSC examples are based on sending to an established >>>>> TCP connection to Supercollider. >>>>> >>>>> What to do? >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Cmdist mailing list >>>>> Cmdist at ccrma.stanford.edu >>>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>>>> >>>>> >>>>> _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Thu Mar 5 18:16:48 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Thu, 5 Mar 2020 18:16:48 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: Um, a more graceful possibility: Adapt the c++ code from the Csound Api examples. Simply run instances of csound within Grace. (?) On Thu, Mar 5, 2020 at 6:05 PM Forrest Curo wrote: > Grace is sending valid osc messages. > > If these were going to Supercollider, that's how they'd be handled. > > Received by the csound udp server, valid osc is not valid realtime score > events. > > Since JUCE is largely a C++ compiler... I should be able to > #include and add code to either write csound score lines to a > fifo, or call bash's 'nc' to udp them to another computer. (?) > > Those approaches wouldn't be graceful, but they are ways I could > (eventually) do it for myself. > > > > > > On Thu, Mar 5, 2020 at 5:12 PM Taube, Heinrich K > wrote: > >> im pretty sure grace is sending valid osc messages, i cant tell what >> going on from the information you are giving me >> >> On Mar 5, 2020, at 6:14 PM, Forrest Curo wrote: >> >> Put in a header; csound objects. >> Leave it out; Grace calls an error. >> >> On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo >> wrote: >> >>> Supercollider is set up to accept udp formatted as OSC messages. >>> >>> Csound 'expects' score events instead. I'd know how to format these if I >>> knew how to specify a string and send it from, Grace. >>> >>> On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo >>> wrote: >>> >>>> cm says "OSC send test succeeded" >>>> & csound says: >>>> error: syntax error, unexpected '/' (token "/") line 7: >>>> >>>/ <<< >>>> Parsing failed due to invalid input! >>>> Stopping on parser failure >>>> >>>> >>>> >>>> On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo >>>> wrote: >>>> >>>>> syntax for sending a string to a port? >>>>> >>>>> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K >>>>> wrote: >>>>> >>>>>> You should be able to send OSC to any port you want, look in the >>>>>> Audio menu for the OSC Connections? command. >>>>>> I haven?t tested OSC yet on this release... >>>>>> >>>>>> On Mar 5, 2020, at 4:18 PM, Forrest Curo >>>>>> wrote: >>>>>> >>>>>> I have csound running & set to receive udp (i.e. --port=4567 ) >>>>>> >>>>>> ( https://csound.com/docs/manual/udpserver.html ) >>>>>> >>>>>> I can send lines it lines for immediate output from pure data: >>>>>> [send scoreline_i "i 2 0 3 440 .5" ( >>>>>> | >>>>>> [netsend -u ] >>>>>> >>>>>> likewise channel values: >>>>>> >>>>>> [send @valu 330 ( >>>>>> | >>>>>> [netsend -u ] >>>>>> >>>>>> but in Grace the OSC examples are based on sending to an established >>>>>> TCP connection to Supercollider. >>>>>> >>>>>> What to do? >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Cmdist mailing list >>>>>> Cmdist at ccrma.stanford.edu >>>>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>>>>> >>>>>> >>>>>> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tito.01beta at gmail.com Fri Mar 6 03:09:44 2020 From: tito.01beta at gmail.com (Tito Latini) Date: Fri, 6 Mar 2020 12:09:44 +0100 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: <20200306110944.GA3543@vis.roboris> On Thu, Mar 05, 2020 at 06:05:04PM -0800, Forrest Curo wrote: > Grace is sending valid osc messages. > > If these were going to Supercollider, that's how they'd be handled. > > Received by the csound udp server, valid osc is not valid realtime score > events. > > Since JUCE is largely a C++ compiler... I should be able to > #include and add code to either write csound score lines to a > fifo, or call bash's 'nc' to udp them to another computer. (?) > > Those approaches wouldn't be graceful, but they are ways I could > (eventually) do it for myself. You could use the csound command line option `-L' with a named pipe. The following example works with s7: Csound orchestra test.orc: instr 1 print p1, p2, p3, p4, p5 endin >From shell: mkfifo score csound -L score -odac -+rtaudio=null --orc test.orc >From s7: (define score (open-output-file "/path/to/score")) (define* (csound-test (instr 1) (dur 1.0) (freq 440) (amp 0) (port score)) (format port "i ~D 0 ~F ~F ~F~%" instr dur freq amp) (flush-output-port port)) (csound-test 1 1.5 1234 -6) (csound-test :dur 3.2) (csound-test :amp -3 :freq 660) ;; Remember to close the port. (close-output-port score) From taube at illinois.edu Fri Mar 6 04:54:15 2020 From: taube at illinois.edu (Taube, Heinrich K) Date: Fri, 6 Mar 2020 12:54:15 +0000 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> Message-ID: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> many years ago i had a connection to realtime csound using the juce InterprocessConnection class https://docs.juce.com/master/classInterprocessConnection.html. Its not in the code base anymore (no one ever used it) but thats the way i would do it. On Mar 5, 2020, at 8:16 PM, Forrest Curo > wrote: Um, a more graceful possibility: Adapt the c++ code from the Csound Api examples. Simply run instances of csound within Grace. (?) On Thu, Mar 5, 2020 at 6:05 PM Forrest Curo > wrote: Grace is sending valid osc messages. If these were going to Supercollider, that's how they'd be handled. Received by the csound udp server, valid osc is not valid realtime score events. Since JUCE is largely a C++ compiler... I should be able to #include and add code to either write csound score lines to a fifo, or call bash's 'nc' to udp them to another computer. (?) Those approaches wouldn't be graceful, but they are ways I could (eventually) do it for myself. On Thu, Mar 5, 2020 at 5:12 PM Taube, Heinrich K > wrote: im pretty sure grace is sending valid osc messages, i cant tell what going on from the information you are giving me On Mar 5, 2020, at 6:14 PM, Forrest Curo > wrote: Put in a header; csound objects. Leave it out; Grace calls an error. On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo > wrote: Supercollider is set up to accept udp formatted as OSC messages. Csound 'expects' score events instead. I'd know how to format these if I knew how to specify a string and send it from, Grace. On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo > wrote: cm says "OSC send test succeeded" & csound says: error: syntax error, unexpected '/' (token "/") line 7: >>>/ <<< Parsing failed due to invalid input! Stopping on parser failure On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo > wrote: syntax for sending a string to a port? On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K > wrote: You should be able to send OSC to any port you want, look in the Audio menu for the OSC Connections? command. I haven?t tested OSC yet on this release... On Mar 5, 2020, at 4:18 PM, Forrest Curo > wrote: I have csound running & set to receive udp (i.e. --port=4567 ) ( https://csound.com/docs/manual/udpserver.html ) I can send lines it lines for immediate output from pure data: [send scoreline_i "i 2 0 3 440 .5" ( | [netsend -u ] likewise channel values: [send @valu 330 ( | [netsend -u ] but in Grace the OSC examples are based on sending to an established TCP connection to Supercollider. What to do? _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist _______________________________________________ Cmdist mailing list Cmdist at ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Fri Mar 6 07:36:16 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Fri, 6 Mar 2020 07:36:16 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> Message-ID: I've used (and know of others using) -L; it's a good fast way to control csound. Tthanks for the code example re accessing it from Grace. Haven't really worked with juce (or c++) so far; but next time I need to network to csound I can [probably] put in & recompile with that InterprocessConnection class. Thanks all! On Fri, Mar 6, 2020 at 4:54 AM Taube, Heinrich K wrote: > many years ago i had a connection to realtime csound using the juce > InterprocessConnection class > https://docs.juce.com/master/classInterprocessConnection.html. Its not > in the code base anymore (no one ever used it) but thats the way i would do > it. > > > On Mar 5, 2020, at 8:16 PM, Forrest Curo wrote: > > Um, a more graceful possibility: > > Adapt the c++ code from the Csound Api examples. Simply run instances of > csound within Grace. > > (?) > > On Thu, Mar 5, 2020 at 6:05 PM Forrest Curo wrote: > >> Grace is sending valid osc messages. >> >> If these were going to Supercollider, that's how they'd be handled. >> >> Received by the csound udp server, valid osc is not valid realtime score >> events. >> >> Since JUCE is largely a C++ compiler... I should be able to >> #include and add code to either write csound score lines to a >> fifo, or call bash's 'nc' to udp them to another computer. (?) >> >> Those approaches wouldn't be graceful, but they are ways I could >> (eventually) do it for myself. >> >> >> >> >> >> On Thu, Mar 5, 2020 at 5:12 PM Taube, Heinrich K >> wrote: >> >>> im pretty sure grace is sending valid osc messages, i cant tell what >>> going on from the information you are giving me >>> >>> On Mar 5, 2020, at 6:14 PM, Forrest Curo wrote: >>> >>> Put in a header; csound objects. >>> Leave it out; Grace calls an error. >>> >>> On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo >>> wrote: >>> >>>> Supercollider is set up to accept udp formatted as OSC messages. >>>> >>>> Csound 'expects' score events instead. I'd know how to format these if >>>> I knew how to specify a string and send it from, Grace. >>>> >>>> On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo >>>> wrote: >>>> >>>>> cm says "OSC send test succeeded" >>>>> & csound says: >>>>> error: syntax error, unexpected '/' (token "/") line 7: >>>>> >>>/ <<< >>>>> Parsing failed due to invalid input! >>>>> Stopping on parser failure >>>>> >>>>> >>>>> >>>>> On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo >>>>> wrote: >>>>> >>>>>> syntax for sending a string to a port? >>>>>> >>>>>> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K >>>>>> wrote: >>>>>> >>>>>>> You should be able to send OSC to any port you want, look in the >>>>>>> Audio menu for the OSC Connections? command. >>>>>>> I haven?t tested OSC yet on this release... >>>>>>> >>>>>>> On Mar 5, 2020, at 4:18 PM, Forrest Curo >>>>>>> wrote: >>>>>>> >>>>>>> I have csound running & set to receive udp (i.e. --port=4567 ) >>>>>>> >>>>>>> ( https://csound.com/docs/manual/udpserver.html ) >>>>>>> >>>>>>> I can send lines it lines for immediate output from pure data: >>>>>>> [send scoreline_i "i 2 0 3 440 .5" ( >>>>>>> | >>>>>>> [netsend -u ] >>>>>>> >>>>>>> likewise channel values: >>>>>>> >>>>>>> [send @valu 330 ( >>>>>>> | >>>>>>> [netsend -u ] >>>>>>> >>>>>>> but in Grace the OSC examples are based on sending to an established >>>>>>> TCP connection to Supercollider. >>>>>>> >>>>>>> What to do? >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Cmdist mailing list >>>>>>> Cmdist at ccrma.stanford.edu >>>>>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>> Cmdist mailing list >>> Cmdist at ccrma.stanford.edu >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>> >>> >>> _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Fri Mar 6 14:31:25 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Fri, 6 Mar 2020 14:31:25 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <01C91057-CF0A-4069-BF8E-0284F670602E@illinois.edu> <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> Message-ID: Tito: Csound simply runs & ends from your command line. Just runs out of score events & stops. It prefers: csound -odac -+rtaudio=null *--daemon* -L "score" --orc test.orc I know that -L is supposed to imply running in '--daemon' mode but maybe not when using an .orc file? No problem, thanks! On Fri, Mar 6, 2020 at 7:36 AM Forrest Curo wrote: > I've used (and know of others using) -L; it's a good fast way to control > csound. Tthanks for the code example re accessing it from Grace. > > Haven't really worked with juce (or c++) so far; but next time I need to > network to csound I can [probably] put in & recompile with that > InterprocessConnection class. > > Thanks all! > > On Fri, Mar 6, 2020 at 4:54 AM Taube, Heinrich K > wrote: > >> many years ago i had a connection to realtime csound using the juce >> InterprocessConnection class >> https://docs.juce.com/master/classInterprocessConnection.html. Its not >> in the code base anymore (no one ever used it) but thats the way i would do >> it. >> >> >> On Mar 5, 2020, at 8:16 PM, Forrest Curo wrote: >> >> Um, a more graceful possibility: >> >> Adapt the c++ code from the Csound Api examples. Simply run instances of >> csound within Grace. >> >> (?) >> >> On Thu, Mar 5, 2020 at 6:05 PM Forrest Curo >> wrote: >> >>> Grace is sending valid osc messages. >>> >>> If these were going to Supercollider, that's how they'd be handled. >>> >>> Received by the csound udp server, valid osc is not valid realtime score >>> events. >>> >>> Since JUCE is largely a C++ compiler... I should be able to >>> #include and add code to either write csound score lines to a >>> fifo, or call bash's 'nc' to udp them to another computer. (?) >>> >>> Those approaches wouldn't be graceful, but they are ways I could >>> (eventually) do it for myself. >>> >>> >>> >>> >>> >>> On Thu, Mar 5, 2020 at 5:12 PM Taube, Heinrich K >>> wrote: >>> >>>> im pretty sure grace is sending valid osc messages, i cant tell what >>>> going on from the information you are giving me >>>> >>>> On Mar 5, 2020, at 6:14 PM, Forrest Curo wrote: >>>> >>>> Put in a header; csound objects. >>>> Leave it out; Grace calls an error. >>>> >>>> On Thu, Mar 5, 2020 at 3:53 PM Forrest Curo >>>> wrote: >>>> >>>>> Supercollider is set up to accept udp formatted as OSC messages. >>>>> >>>>> Csound 'expects' score events instead. I'd know how to format these if >>>>> I knew how to specify a string and send it from, Grace. >>>>> >>>>> On Thu, Mar 5, 2020 at 3:24 PM Forrest Curo >>>>> wrote: >>>>> >>>>>> cm says "OSC send test succeeded" >>>>>> & csound says: >>>>>> error: syntax error, unexpected '/' (token "/") line 7: >>>>>> >>>/ <<< >>>>>> Parsing failed due to invalid input! >>>>>> Stopping on parser failure >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Mar 5, 2020 at 3:17 PM Forrest Curo >>>>>> wrote: >>>>>> >>>>>>> syntax for sending a string to a port? >>>>>>> >>>>>>> On Thu, Mar 5, 2020 at 2:27 PM Taube, Heinrich K >>>>>>> wrote: >>>>>>> >>>>>>>> You should be able to send OSC to any port you want, look in the >>>>>>>> Audio menu for the OSC Connections? command. >>>>>>>> I haven?t tested OSC yet on this release... >>>>>>>> >>>>>>>> On Mar 5, 2020, at 4:18 PM, Forrest Curo >>>>>>>> wrote: >>>>>>>> >>>>>>>> I have csound running & set to receive udp (i.e. --port=4567 ) >>>>>>>> >>>>>>>> ( https://csound.com/docs/manual/udpserver.html ) >>>>>>>> >>>>>>>> I can send lines it lines for immediate output from pure data: >>>>>>>> [send scoreline_i "i 2 0 3 440 .5" ( >>>>>>>> | >>>>>>>> [netsend -u ] >>>>>>>> >>>>>>>> likewise channel values: >>>>>>>> >>>>>>>> [send @valu 330 ( >>>>>>>> | >>>>>>>> [netsend -u ] >>>>>>>> >>>>>>>> but in Grace the OSC examples are based on sending to an >>>>>>>> established TCP connection to Supercollider. >>>>>>>> >>>>>>>> What to do? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Cmdist mailing list >>>>>>>> Cmdist at ccrma.stanford.edu >>>>>>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>> Cmdist mailing list >>>> Cmdist at ccrma.stanford.edu >>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>>> >>>> >>>> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From tito.01beta at gmail.com Fri Mar 6 23:18:02 2020 From: tito.01beta at gmail.com (Tito Latini) Date: Sat, 7 Mar 2020 08:18:02 +0100 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> Message-ID: <20200307071802.GA1730@vis.roboris> On Fri, Mar 06, 2020 at 02:31:25PM -0800, Forrest Curo wrote: > Tito: > Csound simply runs & ends from your command line. Just runs out of score > events & stops. > > It prefers: > csound -odac -+rtaudio=null *--daemon* -L "score" --orc test.orc > > I know that -L is supposed to imply running in '--daemon' mode but maybe > not when using an .orc file? > > No problem, thanks! I have never used that flag but canonic-mode works: nohup csound -odac -+rtaudio=null -L score --orc test.orc & jobs [1]+ Running nohup csound -odac -+rtaudio=null -L score --orc test.orc & # game over kill % From tito.01beta at gmail.com Fri Mar 6 23:23:37 2020 From: tito.01beta at gmail.com (Tito Latini) Date: Sat, 7 Mar 2020 08:23:37 +0100 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> Message-ID: <20200307072337.GA1753@vis.roboris> I forgot... it works with or without daemon-mode here. Tested with a recent version. From treegestalt at gmail.com Sat Mar 7 10:59:39 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Sat, 7 Mar 2020 10:59:39 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: <20200307072337.GA1753@vis.roboris> References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> <20200307072337.GA1753@vis.roboris> Message-ID: Interestingly, Grace can receive udp from Pure Data -- but again, Pure Data won't receive from Grace except via the console menu: Audio, Osc out: port 8888, Test Output -- This works! When I attempt to format an osc message in Sal I either get an error (even using Grace's example messages) or the message goes but is not received by Pure Data. How is the 'Test Output' message formatted? ? ================ from pd: |connect localhost 7779( | [sendtyped / iii 4 5 6 ( | / | [osc/packOSC] | / [iemnet/udpsend] receiving (but only from 'Test Output'): > [udpreceive 8888] | [print incoming] On Fri, Mar 6, 2020 at 11:21 PM Tito Latini wrote: > I forgot... it works with or without daemon-mode here. > Tested with a recent version. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Sat Mar 7 11:16:40 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Sat, 7 Mar 2020 11:16:40 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> <20200307072337.GA1753@vis.roboris> Message-ID: In Bash: nc -l -u 8888 gives me: /Grace,fB(7? but only when I use 'Test Output' On Sat, Mar 7, 2020 at 10:59 AM Forrest Curo wrote: > Interestingly, Grace can receive udp from Pure Data -- but again, Pure > Data won't receive from Grace > > except via the console menu: Audio, Osc out: port 8888, Test Output -- > This works! > > When I attempt to format an osc message in Sal > I either get an error (even using Grace's example messages) > or the message goes but is not received by Pure Data. > How is the 'Test Output' message formatted? > ? > ================ > from pd: > |connect localhost 7779( > | [sendtyped / iii 4 5 6 ( > | / > | [osc/packOSC] > | / > [iemnet/udpsend] > > receiving (but only from 'Test Output'): >> > > [udpreceive 8888] > | > [print incoming] > > > > > > > > > On Fri, Mar 6, 2020 at 11:21 PM Tito Latini wrote: > >> I forgot... it works with or without daemon-mode here. >> Tested with a recent version. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From orm.finnendahl at selma.hfmdk-frankfurt.de Sat Mar 7 11:21:37 2020 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Sat, 7 Mar 2020 20:21:37 +0100 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> <20200307072337.GA1753@vis.roboris> Message-ID: <20200307192137.GB284088@t480s-orm.localdomain> Hi, for pd I would strongly advise not to use these old third party externals, as pd has builtin support for osc since version 0.46. Especially for testing it probably is much easier to understand what is going on by just plugging directly into the netsend/netreceive objects. For receiving: netreceive -b -u 8888 | | oscparse | | print or even connect a print object directly to the netreceive output. For sending from pd: |disconnect, connect localhost 7779( | | netsend -b -u And then use oscformat for formatting osc messages (check the help docs for examples, it's pretty straightforward). -- Orm Am Samstag, den 07. M?rz 2020 um 10:59:39 Uhr (-0800) schrieb Forrest Curo: > Interestingly, Grace can receive udp from Pure Data -- but again, Pure Data > won't receive from Grace > > except via the console menu: Audio, Osc out: port 8888, Test Output -- This > works! > > When I attempt to format an osc message in Sal > I either get an error (even using Grace's example messages) > or the message goes but is not received by Pure Data. > How is the 'Test Output' message formatted? > ? > ================ > from pd: > |connect localhost 7779( > | [sendtyped / iii 4 5 6 ( > | / > | [osc/packOSC] > | / > [iemnet/udpsend] > > receiving (but only from 'Test Output'): > > > > [udpreceive 8888] > | > [print incoming] > > > > > > > > > On Fri, Mar 6, 2020 at 11:21 PM Tito Latini wrote: > > > I forgot... it works with or without daemon-mode here. > > Tested with a recent version. > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From treegestalt at gmail.com Sat Mar 7 17:34:27 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Sat, 7 Mar 2020 17:34:27 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: <20200307192137.GB284088@t480s-orm.localdomain> References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> <20200307072337.GA1753@vis.roboris> <20200307192137.GB284088@t480s-orm.localdomain> Message-ID: Clarifications... Pure Data -> Grace works fine. Grace -> operating system, also Grace -> Pure Data work <==> sending Grace's "Test Output". If I try: osc:message("/Grace", :b, {0 2 4 6 8}) or osc:message( {"/Grace" 123 456.789 } ) there are no error messages, but neither Pure Data nor Bash nc receive anything. On Sat, Mar 7, 2020 at 11:23 AM Orm Finnendahl < orm.finnendahl at selma.hfmdk-frankfurt.de> wrote: > Hi, > > for pd I would strongly advise not to use these old third party > externals, as pd has builtin support for osc since version 0.46. > > Especially for testing it probably is much easier to understand what > is going on by just plugging directly into the netsend/netreceive > objects. > > For receiving: > > netreceive -b -u 8888 > | > | > oscparse > | > | > print > > or even connect a print object directly to the netreceive output. > > For sending from pd: > > |disconnect, connect localhost 7779( > | > | > netsend -b -u > > And then use oscformat for formatting osc messages (check the help > docs for examples, it's pretty straightforward). > > -- > Orm > > Am Samstag, den 07. M?rz 2020 um 10:59:39 Uhr (-0800) schrieb Forrest > Curo: > > Interestingly, Grace can receive udp from Pure Data -- but again, Pure > Data > > won't receive from Grace > > > > except via the console menu: Audio, Osc out: port 8888, Test Output -- > This > > works! > > > > When I attempt to format an osc message in Sal > > I either get an error (even using Grace's example messages) > > or the message goes but is not received by Pure Data. > > How is the 'Test Output' message formatted? > > ? > > ================ > > from pd: > > |connect localhost 7779( > > | [sendtyped / iii 4 5 6 ( > > | / > > | [osc/packOSC] > > | / > > [iemnet/udpsend] > > > > receiving (but only from 'Test Output'): > > > > > > > [udpreceive 8888] > > | > > [print incoming] > > > > > > > > > > > > > > > > > > On Fri, Mar 6, 2020 at 11:21 PM Tito Latini > wrote: > > > > > I forgot... it works with or without daemon-mode here. > > > Tested with a recent version. > > > > > > _______________________________________________ > > Cmdist mailing list > > Cmdist at ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Sat Mar 7 20:41:06 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Sat, 7 Mar 2020 20:41:06 -0800 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> <20200307072337.GA1753@vis.roboris> <20200307192137.GB284088@t480s-orm.localdomain> Message-ID: In the source file OpenSoundControl.cpp "sender.send" appears three times. *In this function, it's working:* void OpenSoundControl::testOutput() { if (!getOutputPort()) return; juce::String test = "OSC output test " ; float f = (juce::Random::getSystemRandom().nextFloat() * 100.0); if (sender.send ("/Grace", (float) f)) std::cout << "OSC send test succeeded!\n"; else std::cout << "OSC send test failed!\n"; } *In these other two instances, it isn't working:* // This should only be called by scheme thread. bool OpenSoundControl::sendMessage(juce::String path, s7_pointer schemeMessage) { juce::ScopedLock lock (oscLock); if (outputPort == 0) return false; if (juce::OSCMessage* message = parseMessage(schemeMessage, path)) { bool success = sender.send(*message); delete message; return success; } else return false; } // This should only be called by scheme thread. bool OpenSoundControl::sendBundle(double time, s7_pointer schemeBundle) { juce::ScopedLock lock (oscLock); if (outputPort == 0) return false; if (juce::OSCBundle* bundle = parseBundle(schemeBundle, time)) { bool success = sender.send(*bundle); delete bundle; return success; } else return false; } ========= What's the difference? Are ' *message' and ' *bundle' missing their payloads while '(float) f' here directly sends a random float. ? On Sat, Mar 7, 2020 at 5:34 PM Forrest Curo wrote: > Clarifications... > > Pure Data -> Grace works fine. > Grace -> operating system, also Grace -> Pure Data work <==> sending > Grace's "Test Output". > > If I try: > > osc:message("/Grace", :b, {0 2 4 6 8}) > > or > osc:message( {"/Grace" 123 456.789 } ) > > > there are no error messages, but neither Pure Data nor Bash nc receive anything. > > > On Sat, Mar 7, 2020 at 11:23 AM Orm Finnendahl < > orm.finnendahl at selma.hfmdk-frankfurt.de> wrote: > >> Hi, >> >> for pd I would strongly advise not to use these old third party >> externals, as pd has builtin support for osc since version 0.46. >> >> Especially for testing it probably is much easier to understand what >> is going on by just plugging directly into the netsend/netreceive >> objects. >> >> For receiving: >> >> netreceive -b -u 8888 >> | >> | >> oscparse >> | >> | >> print >> >> or even connect a print object directly to the netreceive output. >> >> For sending from pd: >> >> |disconnect, connect localhost 7779( >> | >> | >> netsend -b -u >> >> And then use oscformat for formatting osc messages (check the help >> docs for examples, it's pretty straightforward). >> >> -- >> Orm >> >> Am Samstag, den 07. M?rz 2020 um 10:59:39 Uhr (-0800) schrieb Forrest >> Curo: >> > Interestingly, Grace can receive udp from Pure Data -- but again, Pure >> Data >> > won't receive from Grace >> > >> > except via the console menu: Audio, Osc out: port 8888, Test Output -- >> This >> > works! >> > >> > When I attempt to format an osc message in Sal >> > I either get an error (even using Grace's example messages) >> > or the message goes but is not received by Pure Data. >> > How is the 'Test Output' message formatted? >> > ? >> > ================ >> > from pd: >> > |connect localhost 7779( >> > | [sendtyped / iii 4 5 6 ( >> > | / >> > | [osc/packOSC] >> > | / >> > [iemnet/udpsend] >> > >> > receiving (but only from 'Test Output'): >> > > >> > >> > [udpreceive 8888] >> > | >> > [print incoming] >> > >> > >> > >> > >> > >> > >> > >> > >> > On Fri, Mar 6, 2020 at 11:21 PM Tito Latini >> wrote: >> > >> > > I forgot... it works with or without daemon-mode here. >> > > Tested with a recent version. >> > > >> >> > _______________________________________________ >> > Cmdist mailing list >> > Cmdist at ccrma.stanford.edu >> > https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> >> >> _______________________________________________ >> Cmdist mailing list >> Cmdist at ccrma.stanford.edu >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From treegestalt at gmail.com Sun Mar 8 07:35:04 2020 From: treegestalt at gmail.com (Forrest Curo) Date: Sun, 8 Mar 2020 07:35:04 -0700 Subject: [CM] How to send udp bundles from Grace on Linux? In-Reply-To: References: <62144C98-2C35-49B6-A91C-6C2DBDE56FC4@illinois.edu> <20200307072337.GA1753@vis.roboris> <20200307192137.GB284088@t480s-orm.localdomain> Message-ID: It's working today... oh well, minor error on my part. On Sat, Mar 7, 2020 at 8:41 PM Forrest Curo wrote: > In the source file OpenSoundControl.cpp > "sender.send" appears three times. > *In this function, it's working:* > > void OpenSoundControl::testOutput() { > if (!getOutputPort()) return; > juce::String test = "OSC output test " ; > float f = (juce::Random::getSystemRandom().nextFloat() * 100.0); > if (sender.send ("/Grace", (float) f)) > std::cout << "OSC send test succeeded!\n"; > else > std::cout << "OSC send test failed!\n"; > } > *In these other two instances, it isn't working:* > // This should only be called by scheme thread. > bool OpenSoundControl::sendMessage(juce::String path, s7_pointer > schemeMessage) > { > juce::ScopedLock lock (oscLock); > if (outputPort == 0) > return false; > if (juce::OSCMessage* message = parseMessage(schemeMessage, path)) > { > bool success = sender.send(*message); > delete message; > return success; > } > else > return false; > } > > // This should only be called by scheme thread. > bool OpenSoundControl::sendBundle(double time, s7_pointer schemeBundle) > { > juce::ScopedLock lock (oscLock); > if (outputPort == 0) > return false; > if (juce::OSCBundle* bundle = parseBundle(schemeBundle, time)) > { > bool success = sender.send(*bundle); > delete bundle; > return success; > } > else > return false; > } > ========= > What's the difference? Are ' *message' and ' *bundle' missing their > payloads while '(float) f' here directly sends a random float. > > ? > > On Sat, Mar 7, 2020 at 5:34 PM Forrest Curo wrote: > >> Clarifications... >> >> Pure Data -> Grace works fine. >> Grace -> operating system, also Grace -> Pure Data work <==> sending >> Grace's "Test Output". >> >> If I try: >> >> osc:message("/Grace", :b, {0 2 4 6 8}) >> >> or >> osc:message( {"/Grace" 123 456.789 } ) >> >> >> there are no error messages, but neither Pure Data nor Bash nc receive anything. >> >> >> On Sat, Mar 7, 2020 at 11:23 AM Orm Finnendahl < >> orm.finnendahl at selma.hfmdk-frankfurt.de> wrote: >> >>> Hi, >>> >>> for pd I would strongly advise not to use these old third party >>> externals, as pd has builtin support for osc since version 0.46. >>> >>> Especially for testing it probably is much easier to understand what >>> is going on by just plugging directly into the netsend/netreceive >>> objects. >>> >>> For receiving: >>> >>> netreceive -b -u 8888 >>> | >>> | >>> oscparse >>> | >>> | >>> print >>> >>> or even connect a print object directly to the netreceive output. >>> >>> For sending from pd: >>> >>> |disconnect, connect localhost 7779( >>> | >>> | >>> netsend -b -u >>> >>> And then use oscformat for formatting osc messages (check the help >>> docs for examples, it's pretty straightforward). >>> >>> -- >>> Orm >>> >>> Am Samstag, den 07. M?rz 2020 um 10:59:39 Uhr (-0800) schrieb Forrest >>> Curo: >>> > Interestingly, Grace can receive udp from Pure Data -- but again, Pure >>> Data >>> > won't receive from Grace >>> > >>> > except via the console menu: Audio, Osc out: port 8888, Test Output -- >>> This >>> > works! >>> > >>> > When I attempt to format an osc message in Sal >>> > I either get an error (even using Grace's example messages) >>> > or the message goes but is not received by Pure Data. >>> > How is the 'Test Output' message formatted? >>> > ? >>> > ================ >>> > from pd: >>> > |connect localhost 7779( >>> > | [sendtyped / iii 4 5 6 ( >>> > | / >>> > | [osc/packOSC] >>> > | / >>> > [iemnet/udpsend] >>> > >>> > receiving (but only from 'Test Output'): >>> > > >>> > >>> > [udpreceive 8888] >>> > | >>> > [print incoming] >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Fri, Mar 6, 2020 at 11:21 PM Tito Latini >>> wrote: >>> > >>> > > I forgot... it works with or without daemon-mode here. >>> > > Tested with a recent version. >>> > > >>> >>> > _______________________________________________ >>> > Cmdist mailing list >>> > Cmdist at ccrma.stanford.edu >>> > https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>> >>> >>> _______________________________________________ >>> Cmdist mailing list >>> Cmdist at ccrma.stanford.edu >>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From bil at ccrma.Stanford.EDU Thu Mar 12 11:32:54 2020 From: bil at ccrma.Stanford.EDU (bil at ccrma.Stanford.EDU) Date: Thu, 12 Mar 2020 11:32:54 -0700 Subject: [CM] Snd 20.2 Message-ID: Snd 20.2: s7: profile.scm revised, (*s7* 'profile) s7_let_field_ref|set (for *s7* access from C) deprecated current s7_print_length|float_format_precision|gc_stats *function* (a function), replaces deprecated __func__ openlets moved to (*s7* 'openlets), s7-version to (*s7* 'version) checked: sbcl 2.0.2 Thanks!: Rick Taube, Kjetil Matheussen