From j_hearon at hotmail.com  Thu Jun 15 11:14:06 2017
From: j_hearon at hotmail.com (James Hearon)
Date: Thu, 15 Jun 2017 18:14:06 +0000
Subject: [CM] float-vectors
In-Reply-To: <mailman.11.1495825202.17552.cmdist@ccrma.stanford.edu>
References: <mailman.11.1495825202.17552.cmdist@ccrma.stanford.edu>
Message-ID: <MWHPR1001MB208048E7C7F9845634A50734E5C00@MWHPR1001MB2080.namprd10.prod.outlook.com>


Hi,

I'm still struggling with this a bit.

I'm trying to understand more about float-vectors and output to be able to debug them.


How would you go about putting float-vector values on the output, or do they always need a generator of some sort?


   ex. (I'm imagining) something like...

    (map-channel (lambda (y) (myfloatvector)))

   or

   if snd object is already open

    (testme (channel->float-vector 0 fsize snd 0))

   then

    (map-channel (lambda (y) (testme)))

   or open from a file...

    (im (make-float-vector mysize))

    (mus-sound-read "test.wav"  0 mysize 2 im)

   then

    (do ((i 0 (+ i 1)))
        ((= i 22050))
      (outa i (im)))

I can't seem to find what I'm looking for in the documentation to work with just the numbers for freq, amp, and phase for testing as audio.  I know that's a bit spartan, so seems I need to work thru a generator such as maybe use table lookup, for ex. then apply the vocoder.


Thank You,

Jim





________________________________
From: cmdist-bounces at ccrma.Stanford.EDU <cmdist-bounces at ccrma.Stanford.EDU> on behalf of cmdist-request at ccrma.Stanford.EDU <cmdist-request at ccrma.Stanford.EDU>
Sent: Friday, May 26, 2017 7:00 PM
To: cmdist at ccrma.Stanford.EDU
Subject: Cmdist Digest, Vol 109, Issue 4

Send Cmdist mailing list submissions to
        cmdist at ccrma.stanford.edu

To subscribe or unsubscribe via the World Wide Web, visit
        https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Cmdist Info Page - Center for Computer Research in Music ...<https://cm-mail.stanford.edu/mailman/listinfo/cmdist>
cm-mail.stanford.edu
Common Music, Common Lisp Music, Common Music Notation and Snd mailing list. To see the collection of prior postings to the list, visit the Cmdist Archives.


or, via email, send a message with subject or body 'help' to
        cmdist-request at ccrma.stanford.edu

You can reach the person managing the list at
        cmdist-owner at ccrma.stanford.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Cmdist digest..."


Today's Topics:

   1. make-pvocoder (James Hearon)
   2. Re: make-pvocoder (bil at ccrma.Stanford.EDU)


----------------------------------------------------------------------

Message: 1
Date: Thu, 25 May 2017 19:00:15 +0000
From: James Hearon <j_hearon at hotmail.com>
To: "cmdist at ccrma.Stanford.EDU" <cmdist at ccrma.Stanford.EDU>
Subject: [CM] make-pvocoder
Message-ID:
        <BN6PR1001MB206736A3CF55B6980475A01CE5FF0 at BN6PR1001MB2067.namprd10.prod.outlook.com>

Content-Type: text/plain; charset="iso-8859-1"

Hi,

I'm working thru snd make-pvocoder, clm make-phase-vocoder trying to find more info on the analyze, edit, and synthesize methods, such as the one below the manual which shows a lambda func for the synthesis or resynthesis method.  Most of what I've been able to find is based on a gen from readin of a file or input samples to access spectral data.   I know this is a bit odd, but I was trying to create designer spectra, by filling empty vectors with various numbers etc, as opposed to getting the data from a readin generator.  So far mine just sounds like noise, so I don't have it quite right.  I'm wondering if I'm on the right track by using original vectors in the analyze, edit, and synthesize methods.  Or maybe I should just be creating sound files using something like infinite sums, for example, and sticking with the readin generator to analyze those sounds?  I've looked at at the moving-spectrum and pins insts too.


Thank you,

Jim

(with-sound (:srate 22050 :statistics #t)
  (let ((pv (make-phase-vocoder
             (make-readin "oboe.snd")
             512 4 128 1.0
             #f ; no change to analysis method
             #f ; no change to spectrum
             (lambda (gen) ; resynthesis function
               (float-vector-add! (phase-vocoder-amps gen) (phase-vocoder-amp-increments gen))
               (float-vector-add! (phase-vocoder-phase-increments gen) (phase-vocoder-freqs gen))
               (float-vector-add! (phase-vocoder-phases gen) (phase-vocoder-phase-increments gen))
               (let ((sum 0.0)
                     (n (length (phase-vocoder-amps gen))))
                 (do ((k 0 (+ k 1)))
                     ((= k n))
                   (set! sum (+ sum (* (float-vector-ref (phase-vocoder-amps gen) k)
                                       (sin (* 0.5 (float-vector-ref (phase-vocoder-phases gen) k)))))))
                 sum)))))
    (do ((i 0 (+ i 1)))
        ((= i 44100))
      (outa i (phase-vocoder pv)))))

--------------------


(with-sound (:reverb nrev :srate 48000 :channels 2 :header-type  mus-riff :statistics #t :output "/myTest.wav" :play #t )
  (let* ((samps (* 2 (mus-sound-framples "/Sample1.wav")))
         (hop 512)
         (jsampvec (make-float-vector hop))  ;create empty vectors
         (jsampincvec (make-float-vector hop))
         (jsfreqvec (make-float-vector hop))
         (jsphasevec (make-float-vector hop))
         (jsphaseincvec (make-float-vector hop))
             (pv (make-phase-vocoder
         (make-readin "/Sample1.wav")
             512 4  128  1.75    ;fft-size, overlap, interp, pitch
              #f ; no change to analysis
             #f ; no change to edit
             (lambda (gen) ; *attempt resynthesis function*
                  (do ((i 0 (+ i 1)))
              ((= i hop))
                  (set! (jsampvec i) (mus-random .02) ) ;fill vectors with numbers
                  (set! (jsampincvec i) (mus-random .05) )
                  (set! (jsfreqvec i) (mus-random 500) )
                  (set! (jsphasevec i) (mus-random 360) )
                  (set! (jsphaseincvec i) (mus-random .02) )
                  ) ;end do

           (float-vector-add! jsampvec jsampincvec)  ;add the vectors
           (float-vector-add! jsphaseincvec  jsfreqvec)
           (float-vector-add! jsphasevec  jsphaseincvec)

           (let ((sum 0.0)
                     (n hop))
         (do ((k 0 (+ k 1)))
             ((= k n))
   (set! sum (+ sum (* (jsampvec k)(sin (* 0.5 (jsphasevec k)))))) ;create waveform
                   )
         sum)
             )))
    (do ((i 0 (+ i 1)))
       ((= i samps))
      (outa i (* 4 (phase-vocoder pv)))
      (outb i (* 4 (phase-vocoder pv)))
      )))

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/mailman/private/cmdist/attachments/20170525/8c447611/attachment-0001.html>

------------------------------

Message: 2
Date: Thu, 25 May 2017 14:40:33 -0700
From: bil at ccrma.Stanford.EDU
To: James Hearon <j_hearon at hotmail.com>
Cc: "cmdist at ccrma.Stanford.EDU" <cmdist at ccrma.Stanford.EDU>
Subject: Re: [CM] make-pvocoder
Message-ID: <6940b572444d077c52c1342ced6d1baf at ccrma.stanford.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed

Your instrument fills all the vocoder arrays
with noise, so you get noise as the output.
Are you trying to do additive synthesis?



------------------------------

_______________________________________________
Cmdist mailing list
Cmdist at ccrma.stanford.edu
https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Cmdist Info Page - Center for Computer Research in Music ...<https://cm-mail.stanford.edu/mailman/listinfo/cmdist>
cm-mail.stanford.edu
Common Music, Common Lisp Music, Common Music Notation and Snd mailing list. To see the collection of prior postings to the list, visit the Cmdist Archives.




End of Cmdist Digest, Vol 109, Issue 4
**************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170615/e213487f/attachment.html>

From bil at ccrma.Stanford.EDU  Thu Jun 15 12:54:58 2017
From: bil at ccrma.Stanford.EDU (bil at ccrma.Stanford.EDU)
Date: Thu, 15 Jun 2017 12:54:58 -0700
Subject: [CM] float-vectors
In-Reply-To: <MWHPR1001MB208048E7C7F9845634A50734E5C00@MWHPR1001MB2080.namprd10.prod.outlook.com>
References: <mailman.11.1495825202.17552.cmdist@ccrma.stanford.edu>
	<MWHPR1001MB208048E7C7F9845634A50734E5C00@MWHPR1001MB2080.namprd10.prod.outlook.com>
Message-ID: <a900fe2df1a185d436c8be3b43dfe9f8@ccrma.stanford.edu>

float-vector->channel will write a float-vector's contents to
a Snd channel.  For element-at-a-time access, use float-vector-ref
which can be implicit: (do ((i 0 (+ i 1))) ((= i 22050)) (outa i (vect 
i)))
where (vect i) is shorthand for (float-vector-ref vect i).
If you want a generator, perhaps use make-iterator and iterate.



From nikoltoll at gmail.com  Fri Jun 16 02:58:15 2017
From: nikoltoll at gmail.com (Nikolaj Tollenaar)
Date: Fri, 16 Jun 2017 11:58:15 +0200
Subject: [CM] problem with list construction for rhythms
Message-ID: <CAM4zxbXpu=e5brMrN8f1-mj2NpAbAHT8YShFhMUSYDssP+L2BQ@mail.gmail.com>

Dear all,

I'm trying to construct a rhythm value list through this function:

(define (make-rhy-list length)
   ;; chooses random groupings of values
        (loop with rhy = (list) repeat length
               do
               (set! rhy (concat rhy (pick '((1/4 1/4)
                                   (1/3 1/3 1/3)
                                   (1/8 1/8 1/8 1/8)
                                   (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
                                   1/2 1/2))))
               finally (return rhy)))

But, when I use these in a sprout, all notes are played simultaneously.

(define rhy-lst1 (make-rhy-list 20))
(sprout (play-pattern (make-cycle '(70 72 80 88)) (make-cycle rhy-lst1) 160
115 0.9))

Why is this and what can I do about it?

If I use the single element construction, sprout works as expected.

Like so:

(define (make-rhy-list length)
   ;; chooses random single values
   (loop for key from 1 to length
         collect (pick '(1/4 1/4 1/4 1/8 1/8 1/16 1/2 1/2))))

Greetings,

Nikolaj

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virusvrij.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170616/9b55656d/attachment.html>

From aykut_caglayan at yahoo.com  Fri Jun 16 13:09:43 2017
From: aykut_caglayan at yahoo.com (Aykut Caglayan)
Date: Fri, 16 Jun 2017 22:09:43 +0200
Subject: [CM] problem with list construction for rhythms
In-Reply-To: <mailman.1.1497639602.28222.cmdist@ccrma.stanford.edu>
References: <mailman.1.1497639602.28222.cmdist@ccrma.stanford.edu>
Message-ID: <C76C693E-FAD7-4698-919E-33391E21E06C@yahoo.com>

'sprout' is sprouting a 'process'.
My suggestion:

(define (make-rhy-list length)
  ;; first create your rhythm list and assign it to a variable
  (let ((rhy-list (loop with rhy = (list) repeat length
              do
              (set! rhy (concat rhy (pick '((1/4 1/4)
                                  (1/3 1/3 1/3)
                                  (1/8 1/8 1/8 1/8)
                                  (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
                                  1/2 1/2))))
              finally (return rhy))))
    ;;use the rhythm list within a process
    (process for i in rhy-list
             do
             ;;you might want to send it through midi
             (send "mp:midi" :dur i)
             (wait i))))

(sprout (make-rhy-list 2))

> Message: 2
> Date: Fri, 16 Jun 2017 11:58:15 +0200
> From: Nikolaj Tollenaar <nikoltoll at gmail.com>
> To: cmdist at ccrma.Stanford.EDU
> Subject: [CM] problem with list construction for rhythms
> Message-ID:
> 	<CAM4zxbXpu=e5brMrN8f1-mj2NpAbAHT8YShFhMUSYDssP+L2BQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Dear all,
> 
> I'm trying to construct a rhythm value list through this function:
> 
> (define (make-rhy-list length)
>   ;; chooses random groupings of values
>        (loop with rhy = (list) repeat length
>               do
>               (set! rhy (concat rhy (pick '((1/4 1/4)
>                                   (1/3 1/3 1/3)
>                                   (1/8 1/8 1/8 1/8)
>                                   (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
>                                   1/2 1/2))))
>               finally (return rhy)))
> 
> But, when I use these in a sprout, all notes are played simultaneously.
> 
> (define rhy-lst1 (make-rhy-list 20))
> (sprout (play-pattern (make-cycle '(70 72 80 88)) (make-cycle rhy-lst1) 160
> 115 0.9))
> 
> Why is this and what can I do about it?
> 
> If I use the single element construction, sprout works as expected.
> 
> Like so:
> 
> (define (make-rhy-list length)
>   ;; chooses random single values
>   (loop for key from 1 to length
>         collect (pick '(1/4 1/4 1/4 1/8 1/8 1/16 1/2 1/2))))
> 
> Greetings,
> 
> Nikolaj
> 
> 



From nikoltoll at gmail.com  Fri Jun 16 22:47:07 2017
From: nikoltoll at gmail.com (Nikolaj Tollenaar)
Date: Sat, 17 Jun 2017 07:47:07 +0200
Subject: [CM] problem with list construction for rhythms
In-Reply-To: <C76C693E-FAD7-4698-919E-33391E21E06C@yahoo.com>
References: <mailman.1.1497639602.28222.cmdist@ccrma.stanford.edu>
	<C76C693E-FAD7-4698-919E-33391E21E06C@yahoo.com>
Message-ID: <CAM4zxbWcghAROqxnBhLfch7N1JGK9CuECW8uYjBH56A1Xf9ppg@mail.gmail.com>

Thank you for your response, but this is not the problem. I see I forgot to
include my play-pattern function that includes the process (sorry for that):

(define (play-pattern pat rhy times tmpo ampl)
  ;; plays pattern times times, with tempo tmpo and amplitude ampl:
  (let* ((dur (in-tempo 1/4 tmpo)))
    (process repeat times
             for x = (next pat)
             for y = (next rhy)
             do
             (if (number? x)
                 (mp:midi :key x :dur dur :amp (* ampl (pick .9 .95 1
.85))))
             (wait (in-tempo y tmpo))
             )))

The problem arises when I want to use this pattern based composition.
make-cycle on the rhythm list made through concat doesn't work (all notes
played simultaneously), whereas the rhythm list made through collect *does*
work (music plays).

I am using Grace 3.9.0 on Windows.

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virusvrij.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2017-06-16 22:09 GMT+02:00 Aykut Caglayan <aykut_caglayan at yahoo.com>:

> 'sprout' is sprouting a 'process'.
> My suggestion:
>
> (define (make-rhy-list length)
>   ;; first create your rhythm list and assign it to a variable
>   (let ((rhy-list (loop with rhy = (list) repeat length
>               do
>               (set! rhy (concat rhy (pick '((1/4 1/4)
>                                   (1/3 1/3 1/3)
>                                   (1/8 1/8 1/8 1/8)
>                                   (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
>                                   1/2 1/2))))
>               finally (return rhy))))
>     ;;use the rhythm list within a process
>     (process for i in rhy-list
>              do
>              ;;you might want to send it through midi
>              (send "mp:midi" :dur i)
>              (wait i))))
>
> (sprout (make-rhy-list 2))
>
> > Message: 2
> > Date: Fri, 16 Jun 2017 11:58:15 +0200
> > From: Nikolaj Tollenaar <nikoltoll at gmail.com>
> > To: cmdist at ccrma.Stanford.EDU
> > Subject: [CM] problem with list construction for rhythms
> > Message-ID:
> >       <CAM4zxbXpu=e5brMrN8f1-mj2NpAbAHT8YShFhMUSYDssP+L2BQ@
> mail.gmail.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Dear all,
> >
> > I'm trying to construct a rhythm value list through this function:
> >
> > (define (make-rhy-list length)
> >   ;; chooses random groupings of values
> >        (loop with rhy = (list) repeat length
> >               do
> >               (set! rhy (concat rhy (pick '((1/4 1/4)
> >                                   (1/3 1/3 1/3)
> >                                   (1/8 1/8 1/8 1/8)
> >                                   (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
> >                                   1/2 1/2))))
> >               finally (return rhy)))
> >
> > But, when I use these in a sprout, all notes are played simultaneously.
> >
> > (define rhy-lst1 (make-rhy-list 20))
> > (sprout (play-pattern (make-cycle '(70 72 80 88)) (make-cycle rhy-lst1)
> 160
> > 115 0.9))
> >
> > Why is this and what can I do about it?
> >
> > If I use the single element construction, sprout works as expected.
> >
> > Like so:
> >
> > (define (make-rhy-list length)
> >   ;; chooses random single values
> >   (loop for key from 1 to length
> >         collect (pick '(1/4 1/4 1/4 1/8 1/8 1/16 1/2 1/2))))
> >
> > Greetings,
> >
> > Nikolaj
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170617/82b140c3/attachment.html>

From taube at illinois.edu  Sat Jun 17 06:22:07 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Sat, 17 Jun 2017 13:22:07 +0000
Subject: [CM] problem with list construction for rhythms
In-Reply-To: <CAM4zxbWcghAROqxnBhLfch7N1JGK9CuECW8uYjBH56A1Xf9ppg@mail.gmail.com>
References: <mailman.1.1497639602.28222.cmdist@ccrma.stanford.edu>
	<C76C693E-FAD7-4698-919E-33391E21E06C@yahoo.com>
	<CAM4zxbWcghAROqxnBhLfch7N1JGK9CuECW8uYjBH56A1Xf9ppg@mail.gmail.com>
Message-ID: <924E0583-FB5D-4D36-BC5E-D1A8AB416533@illinois.edu>

Hi Nikolaj, ive run your example and it works for me, so offhand I?m not sure what the issue might be.  Im on a mac and you are on windows, but i can?t see what difference that would make.  Since you think it has something to do with concat, as a test Ive rewritten your make-rhy-list function to avoid ?concat? . Try this version and tell me if it works.  On my mac both your version and my version of 'make-rhy-list ? work fine so lets see what happens on your machine.

best, Rick


(define (play-pattern pat rhy times tmpo ampl)
  ;; plays pattern times times, with tempo tmpo and amplitude ampl:
  (let* ((dur (in-tempo 1/4 tmpo)))
    (process repeat times
             for x = (next pat)
             for y = (next rhy)
             do
             (if (number? x)
                 (mp:midi :key x :dur dur :amp (* ampl (pick .9 .95 1 .85))))
             (wait (in-tempo y tmpo))
             )))

;; NEW VERSION of make-rhy-list avoids concat

(define (make-rhy-list length)
  ;; chooses random groupings of values
  (loop repeat length
        append (pick '((1/4 1/4) 
                       (1/3 1/3 1/3) 
                       (1/8 1/8 1/8 1/8) 
                       (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
                       (1/2 1/2)))))

(define rhy-lst1 (make-rhy-list 20))

(sprout (play-pattern (make-cycle '(70 72 80 88)) (make-cycle rhy-lst1) 160 115 0.9))





From nikoltoll at gmail.com  Sat Jun 17 11:48:12 2017
From: nikoltoll at gmail.com (Nikolaj Tollenaar)
Date: Sat, 17 Jun 2017 20:48:12 +0200
Subject: [CM] problem with list construction for rhythms
In-Reply-To: <924E0583-FB5D-4D36-BC5E-D1A8AB416533@illinois.edu>
References: <mailman.1.1497639602.28222.cmdist@ccrma.stanford.edu>
	<C76C693E-FAD7-4698-919E-33391E21E06C@yahoo.com>
	<CAM4zxbWcghAROqxnBhLfch7N1JGK9CuECW8uYjBH56A1Xf9ppg@mail.gmail.com>
	<924E0583-FB5D-4D36-BC5E-D1A8AB416533@illinois.edu>
Message-ID: <CAM4zxbVkigpmoNkzFfriVpd=pdfrFbS9VTSRwXD5v8EdWPXeXQ@mail.gmail.com>

Hello Heinrich,

This is really puzzling! After running your version, it also works with me,
and all my other versions of make-rhy-list work too. After some time, the
behaviour returns and I get the sound as attached.

That is really bizarre, because this afternoon I already tried the
following function, to no avail:

(define (make-rhy-list length)
   ;; chooses random groupings of values (more general)
        (loop with rhy = (list) repeat length
               do
               (set! rhy (append rhy (pick '((1/4 1/4)
                                   (1/3 1/3 1/3)
                                   (1/8 1/8 1/8 1/8)
                                   (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
                                   (1/2 1/2)))))
               finally (return rhy)))

I also tried different midi outputs, and that does not seem to inluence the
outcome.

This is really hard to test, so I will stick with your version of
make-rhy-list.

Thank you for your help,

Nikolaj

2017-06-17 15:22 GMT+02:00 Taube, Heinrich K <taube at illinois.edu>:

> Hi Nikolaj, ive run your example and it works for me, so offhand I?m not
> sure what the issue might be.  Im on a mac and you are on windows, but i
> can?t see what difference that would make.  Since you think it has
> something to do with concat, as a test Ive rewritten your make-rhy-list
> function to avoid ?concat? . Try this version and tell me if it works.  On
> my mac both your version and my version of 'make-rhy-list ? work fine so
> lets see what happens on your machine.
>
> best, Rick
>
>
> (define (play-pattern pat rhy times tmpo ampl)
>   ;; plays pattern times times, with tempo tmpo and amplitude ampl:
>   (let* ((dur (in-tempo 1/4 tmpo)))
>     (process repeat times
>              for x = (next pat)
>              for y = (next rhy)
>              do
>              (if (number? x)
>                  (mp:midi :key x :dur dur :amp (* ampl (pick .9 .95 1
> .85))))
>              (wait (in-tempo y tmpo))
>              )))
>
> ;; NEW VERSION of make-rhy-list avoids concat
>
> ??
> (define (make-rhy-list length)
>   ;; chooses random groupings of values
>   (loop repeat length
>         append (pick '((1/4 1/4)
>                        (1/3 1/3 1/3)
>                        (1/8 1/8 1/8 1/8)
>                        (1/16 1/16 1/8 1/16 1/8 1/16 1/8)
>                        (1/2 1/2)))))
>
> (define rhy-lst1 (make-rhy-list 20))
>
> (sprout (play-pattern (make-cycle '(70 72 80 88)) (make-cycle rhy-lst1)
> 160 115 0.9))
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170617/82ff0e33/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rhy-list make-cycle.wav
Type: audio/x-wav
Size: 233420 bytes
Desc: not available
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170617/82ff0e33/attachment.wav>

From taube at illinois.edu  Mon Jun 19 19:12:21 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Tue, 20 Jun 2017 02:12:21 +0000
Subject: [CM] Grace 3.10.0 is available
Message-ID: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>

Grace 3.10.0 is available for download at https://sourceforge.net/projects/commonmusic/

The primary focus of this release was to update the code base to the latest versions of JUCE (v5.0.1), S7 (5.1), and Sndlib (24).  The main new feature I?ve added is a complete reimplemention of OSC support using new JUCE 5 features so that sending and receiving OSC will now work in all ports of CM without any external dependancies.  See the changeling for a full list of additions and fixes.

Ive built and uploaded the Mac version of Grace, its on source forge in the file Grace-3.10.0-osx.zip.  Moving forward I intend to be more active with CM development again but I am going to rely on other people to build a windows executable and make sure the app compiles and runs on linux.  ill reintegerate whatever changes are needed back into the repository to support those platforms.





From tito.01beta at gmail.com  Tue Jun 20 01:20:53 2017
From: tito.01beta at gmail.com (Tito Latini)
Date: Tue, 20 Jun 2017 10:20:53 +0200
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
Message-ID: <20170620082053.GA1677@rhk.Home>

Thanks.

I can compile Grace with success on linux with the attached patch.

# tested with gcc-5.3.0 (x86_64)
unzip cm-3.10.0.zip
cd cm-3.10.0
patch -p1 < cm-3.10.0-linux-build.diff
premake4
make
-------------- next part --------------
diff -ur cm-3.10.0~/premake4.lua cm-3.10.0/premake4.lua
--- cm-3.10.0~/premake4.lua	2017-06-19 06:00:32.000000000 +0200
+++ cm-3.10.0/premake4.lua	2017-06-20 10:05:11.604594830 +0200
@@ -56,7 +56,7 @@
                "JUCE_USE_MP3AUDIOFORMAT=1",
                "JUCE_USE_WINDOWS_MEDIA_FORMAT=1",
                "JUCE_USE_CDBURNER=0", "JUCE_USE_CDREADER=0",
-               "JUCE_WEBBROWSER=0", "JUCE_CHECK_MEMORY_LEAKS=0",
+               "JUCE_WEB_BROWSER=0", "JUCE_CHECK_MEMORY_LEAKS=0",
 	       "JUCE_SUPPORT_CARBON=0",  "JUCE_STRING_UTF_TYPE=8",
 	       "JUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1",
 	       -- temporary workaround to JUCE 5 'undefined' bug in juce_JUCESplashScreen.h/cpp	       
@@ -139,7 +139,7 @@
 
 -- Linux
 configuration("linux")
-buildoptions({"`pkg-config --cflags freetype2`"})
+buildoptions({"-std=gnu++11 `pkg-config --cflags freetype2 gtk+-3.0`"})
 table.insert(JUCEDefines, "JUCE_ALSA=1")
 if (_OPTIONS["with-jack"]) then table.insert(JUCEDefines, "JUCE_JACK=1") end
 defines(JUCEDefines)
Solo in cm-3.10.0/sndlib: Makefile
Solo in cm-3.10.0/sndlib: lib
Solo in cm-3.10.0/sndlib: obj
Solo in cm-3.10.0/sndlib: sndlib.make
diff -ur cm-3.10.0~/src/Libraries.h cm-3.10.0/src/Libraries.h
--- cm-3.10.0~/src/Libraries.h	2017-05-08 09:25:58.000000000 +0200
+++ cm-3.10.0/src/Libraries.h	2017-06-20 09:52:20.571636248 +0200
@@ -24,6 +24,8 @@
 #include "modules/juce_osc/juce_osc.h"
 #include "modules/juce_video/juce_video.h"
 
+#include <limits.h>
+
 //-----------//
 // S7 Scheme //
 //-----------//

From taube at illinois.edu  Tue Jun 20 04:24:47 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Tue, 20 Jun 2017 11:24:47 +0000
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <20170620082053.GA1677@rhk.Home>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
Message-ID: <30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>

Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:

svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm


> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
> 
> Thanks.
> 
> I can compile Grace with success on linux with the attached patch.
> 
> # tested with gcc-5.3.0 (x86_64)
> unzip cm-3.10.0.zip
> cd cm-3.10.0
> patch -p1 < cm-3.10.0-linux-build.diff
> premake4
> make
> <cm-3.10.0-linux-build.diff>




From dlphillips at woh.rr.com  Wed Jun 21 09:03:24 2017
From: dlphillips at woh.rr.com (Dave Phillips)
Date: Wed, 21 Jun 2017 12:03:24 -0400
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
Message-ID: <594A98CC.3040100@woh.rr.com>

Hi Rick, hi Tito !

On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
>
> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm

Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF 
support. :)

Thank you !

Best,

dp


>
>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
>>
>> Thanks.
>>
>> I can compile Grace with success on linux with the attached patch.
>>
>> # tested with gcc-5.3.0 (x86_64)
>> unzip cm-3.10.0.zip
>> cd cm-3.10.0
>> patch -p1 < cm-3.10.0-linux-build.diff
>> premake4
>> make
>> <cm-3.10.0-linux-build.diff>
>
> _______________________________________________
> Cmdist mailing list
> Cmdist at ccrma.stanford.edu
> https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>
>



From taube at illinois.edu  Wed Jun 21 09:55:51 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Wed, 21 Jun 2017 16:55:51 +0000
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <594A98CC.3040100@woh.rr.com>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
	<594A98CC.3040100@woh.rr.com>
Message-ID: <35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>

Thank you Dave!

If there is someone out there on windows that knows a bit about compiling in VS please let me know!

> On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com> wrote:
> 
> Hi Rick, hi Tito !
> 
> On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
>> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
>> 
>> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
> 
> Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF support. :)
> 
> Thank you !
> 
> Best,
> 
> dp
> 
> 
>> 
>>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
>>> 
>>> Thanks.
>>> 
>>> I can compile Grace with success on linux with the attached patch.
>>> 
>>> # tested with gcc-5.3.0 (x86_64)
>>> unzip cm-3.10.0.zip
>>> cd cm-3.10.0
>>> patch -p1 < cm-3.10.0-linux-build.diff
>>> premake4
>>> make
>>> <cm-3.10.0-linux-build.diff>
>> 
>> _______________________________________________
>> 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 treegestalt at gmail.com  Wed Jun 21 12:58:59 2017
From: treegestalt at gmail.com (Forrest Curo)
Date: Wed, 21 Jun 2017 12:58:59 -0700
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
	<594A98CC.3040100@woh.rr.com>
	<35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>
Message-ID: <CAAn-EcwzFLS4aAG4X0fQ00O8fTa7G3v+uotXd2QQhasvgnJqxA@mail.gmail.com>

Um, works on ubuntu 16.10.

Readme file still calls for
"premake4 --with-oscpack"

(but that is neither accepted nor needed; osc seems to be built in
automatically now.)

On Wed, Jun 21, 2017 at 9:55 AM, Taube, Heinrich K <taube at illinois.edu>
wrote:

> Thank you Dave!
>
> If there is someone out there on windows that knows a bit about compiling
> in VS please let me know!
>
> > On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com>
> wrote:
> >
> > Hi Rick, hi Tito !
> >
> > On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
> >> Thank you Tito, you sure made that easy!  I've committed your changes
> (rev 21776 ).  ill wait a day or two an then update the source zip.  in the
> meantime patched sources for building on linux can be downloaded by doing:
> >>
> >> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
> >
> > Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF
> support. :)
> >
> > Thank you !
> >
> > Best,
> >
> > dp
> >
> >
> >>
> >>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com>
> wrote:
> >>>
> >>> Thanks.
> >>>
> >>> I can compile Grace with success on linux with the attached patch.
> >>>
> >>> # tested with gcc-5.3.0 (x86_64)
> >>> unzip cm-3.10.0.zip
> >>> cd cm-3.10.0
> >>> patch -p1 < cm-3.10.0-linux-build.diff
> >>> premake4
> >>> make
> >>> <cm-3.10.0-linux-build.diff>
> >>
> >> _______________________________________________
> >> 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: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170621/6749925d/attachment.html>

From danielhensel at icloud.com  Wed Jun 21 13:02:10 2017
From: danielhensel at icloud.com (Daniel Hensel)
Date: Wed, 21 Jun 2017 22:02:10 +0200
Subject: [CM] CLM in Grace 3.10.0 not working and CLM/CM-score-request
In-Reply-To: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>
References: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>
Message-ID: <9DC006E6-3DE6-4452-A3FE-2487ACC5A8B2@icloud.com>

Hi,

I hope I do not make a fool out of myself, but I tried some CLM-code in the new Grace-Version on macOS sierra 10.5. and it is not working:

when I evaluate the built-in CLM Code-examples:

(define (simpwav n r d lb ub)
  (process repeat n
           for k = (between lb ub)
           do
           (wave (elapsed #t) d (hertz k) .1)
           (wait r)
           ))

(sprout (simpwav 10 .2 .1 60 80) "test.wav?)

The compiler complains:

simpwav
>>> Error: *clm-data-format*: unbound variable
snd:open-output-file: (list-prop args :data-fo... ; args: (:data-format 10 :header-t...
snd:open-output-file: (mus-sample-type-name (l...
snd:open-output-file: (*wsdat*)open-file: ((set! mode *score-type-sndlib*))      ; mode: 0
open-file: ((ffi_sched_set_score_mode mode) mode)sprout: ((if *sprout-hook* (*sprout-hook* file... ; file: "test.wav", start: 0
                                                   ; id: 0
                                                   ; startBeat: 0

The same is with the other Examples:


(define (gongalong num rate dur freqenv)
  (process for i below num
           do
           (sprout (gong (pick 2 3) dur (interp (/ i num) freqenv)
                         .05 45 0 0))
           (wait rate)
           ))


gongalong
>>> Error: *clm-data-format*: unbound variable
snd:open-output-file: (list-prop args :data-fo... ; args: (:data-format 10 :header-t...
snd:open-output-file: (mus-sample-type-name (l...
snd:open-output-file: (*wsdat*)open-file: ((set! mode *score-type-sndlib*))      ; mode: 0
open-file: ((ffi_sched_set_score_mode mode) mode)sprout: ((if *sprout-hook* (*sprout-hook* file... ; file: "gongalong.wav"
                                                   ; start: 0, id: 0
                                                   ; startBeat: 0

By the way: does anyone have a piece composed with CLM and CM and would be so kind to share his or her score for the purposes of private studies? I?d be very interested in it.

All the best,
Daniel Hensel


> Am 21.06.2017 um 21:00 schrieb cmdist-request at ccrma.Stanford.EDU:
> 
> Send Cmdist mailing list submissions to
> 	cmdist at ccrma.stanford.edu
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://cm-mail.stanford.edu/mailman/listinfo/cmdist
> or, via email, send a message with subject or body 'help' to
> 	cmdist-request at ccrma.stanford.edu
> 
> You can reach the person managing the list at
> 	cmdist-owner at ccrma.stanford.edu
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Cmdist digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Grace 3.10.0 is available (Dave Phillips)
>   2. Re: Grace 3.10.0 is available (Taube, Heinrich K)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 21 Jun 2017 12:03:24 -0400
> From: Dave Phillips <dlphillips at woh.rr.com>
> To: cmdist at ccrma.Stanford.EDU
> Subject: Re: [CM] Grace 3.10.0 is available
> Message-ID: <594A98CC.3040100 at woh.rr.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> Hi Rick, hi Tito !
> 
> On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
>> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
>> 
>> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
> 
> Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF 
> support. :)
> 
> Thank you !
> 
> Best,
> 
> dp
> 
> 
>> 
>>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
>>> 
>>> Thanks.
>>> 
>>> I can compile Grace with success on linux with the attached patch.
>>> 
>>> # tested with gcc-5.3.0 (x86_64)
>>> unzip cm-3.10.0.zip
>>> cd cm-3.10.0
>>> patch -p1 < cm-3.10.0-linux-build.diff
>>> premake4
>>> make
>>> <cm-3.10.0-linux-build.diff>
>> 
>> _______________________________________________
>> Cmdist mailing list
>> Cmdist at ccrma.stanford.edu
>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>> 
>> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 21 Jun 2017 16:55:51 +0000
> From: "Taube, Heinrich K" <taube at illinois.edu>
> To: Dave Phillips <dlphillips at woh.rr.com>
> Cc: commonmusic-Mailing-List List <cmdist at ccrma.Stanford.EDU>
> Subject: Re: [CM] Grace 3.10.0 is available
> Message-ID: <35635A62-40E0-4E1A-AACF-BB327F93A9EC at illinois.edu>
> Content-Type: text/plain; charset="us-ascii"
> 
> Thank you Dave!
> 
> If there is someone out there on windows that knows a bit about compiling in VS please let me know!
> 
>> On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com> wrote:
>> 
>> Hi Rick, hi Tito !
>> 
>> On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
>>> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
>>> 
>>> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
>> 
>> Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF support. :)
>> 
>> Thank you !
>> 
>> Best,
>> 
>> dp
>> 
>> 
>>> 
>>>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
>>>> 
>>>> Thanks.
>>>> 
>>>> I can compile Grace with success on linux with the attached patch.
>>>> 
>>>> # tested with gcc-5.3.0 (x86_64)
>>>> unzip cm-3.10.0.zip
>>>> cd cm-3.10.0
>>>> patch -p1 < cm-3.10.0-linux-build.diff
>>>> premake4
>>>> make
>>>> <cm-3.10.0-linux-build.diff>
>>> 
>>> _______________________________________________
>>> 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
> 
> 
> End of Cmdist Digest, Vol 110, Issue 6
> **************************************
> 

 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170621/5d38cb18/attachment.html>

From taube at illinois.edu  Wed Jun 21 13:10:26 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Wed, 21 Jun 2017 20:10:26 +0000
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <CAAn-EcwzFLS4aAG4X0fQ00O8fTa7G3v+uotXd2QQhasvgnJqxA@mail.gmail.com>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
	<594A98CC.3040100@woh.rr.com>
	<35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>
	<CAAn-EcwzFLS4aAG4X0fQ00O8fTa7G3v+uotXd2QQhasvgnJqxA@mail.gmail.com>
Message-ID: <F2B81E3D-BBA2-4FFD-9713-6CAB1078AFBC@illinois.edu>

Forrest thanks, Ill take care of that nit.  yes osc is built in now so it should even run on windows... assuming someone can actually compile it there!

> On Jun 21, 2017, at 2:58 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> 
> Um, works on ubuntu 16.10. 
> 
> Readme file still calls for 
> "premake4 --with-oscpack"
> 
> (but that is neither accepted nor needed; osc seems to be built in automatically now.)
> 
> On Wed, Jun 21, 2017 at 9:55 AM, Taube, Heinrich K <taube at illinois.edu> wrote:
> Thank you Dave!
> 
> If there is someone out there on windows that knows a bit about compiling in VS please let me know!
> 
> > On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com> wrote:
> >
> > Hi Rick, hi Tito !
> >
> > On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
> >> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
> >>
> >> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
> >
> > Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF support. :)
> >
> > Thank you !
> >
> > Best,
> >
> > dp
> >
> >
> >>
> >>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
> >>>
> >>> Thanks.
> >>>
> >>> I can compile Grace with success on linux with the attached patch.
> >>>
> >>> # tested with gcc-5.3.0 (x86_64)
> >>> unzip cm-3.10.0.zip
> >>> cd cm-3.10.0
> >>> patch -p1 < cm-3.10.0-linux-build.diff
> >>> premake4
> >>> make
> >>> <cm-3.10.0-linux-build.diff>
> >>
> >> _______________________________________________
> >> 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  Wed Jun 21 13:38:44 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Wed, 21 Jun 2017 20:38:44 +0000
Subject: [CM] CLM in Grace 3.10.0 not working and CLM/CM-score-request
In-Reply-To: <9DC006E6-3DE6-4452-A3FE-2487ACC5A8B2@icloud.com>
References: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>
	<9DC006E6-3DE6-4452-A3FE-2487ACC5A8B2@icloud.com>
Message-ID: <4F01B7E3-D3EF-4439-A8AB-82A6780E44F2@illinois.edu>

arrg,  if anyone is a fool its me, *clm-data-format* has been renamed *clm-sample-type* and i thought i caught all those in the refactoring.
straight clm calls should still work now, eg   (make-bird) -- ill get the cm side fixed tomorrow morning and make a new tarball/app

> On Jun 21, 2017, at 3:02 PM, Daniel Hensel <danielhensel at icloud.com> wrote:
> 
> Hi,
> 
> I hope I do not make a fool out of myself, but I tried some CLM-code in the new Grace-Version on macOS sierra 10.5. and it is not working:
> 
> when I evaluate the built-in CLM Code-examples:
> 
> (define (simpwav n r d lb ub)
>   (process repeat n
>            for k = (between lb ub)
>            do
>            (wave (elapsed #t) d (hertz k) .1)
>            (wait r)
>            ))
> 
> (sprout (simpwav 10 .2 .1 60 80) "test.wav?)
> 
> The compiler complains:
> 
> simpwav
> >>> Error: *clm-data-format*: unbound variable
> snd:open-output-file: (list-prop args :data-fo... ; args: (:data-format 10 :header-t...
> snd:open-output-file: (mus-sample-type-name (l...
> snd:open-output-file: (*wsdat*)open-file: ((set! mode *score-type-sndlib*))      ; mode: 0
> open-file: ((ffi_sched_set_score_mode mode) mode)sprout: ((if *sprout-hook* (*sprout-hook* file... ; file: "test.wav", start: 0
>                                                    ; id: 0
>                                                    ; startBeat: 0
> 
> The same is with the other Examples:
> 
> 
> (define (gongalong num rate dur freqenv)
>   (process for i below num
>            do
>            (sprout (gong (pick 2 3) dur (interp (/ i num) freqenv)
>                          .05 45 0 0))
>            (wait rate)
>            ))
> 
> 
> gongalong
> >>> Error: *clm-data-format*: unbound variable
> snd:open-output-file: (list-prop args :data-fo... ; args: (:data-format 10 :header-t...
> snd:open-output-file: (mus-sample-type-name (l...
> snd:open-output-file: (*wsdat*)open-file: ((set! mode *score-type-sndlib*))      ; mode: 0
> open-file: ((ffi_sched_set_score_mode mode) mode)sprout: ((if *sprout-hook* (*sprout-hook* file... ; file: "gongalong.wav"
>                                                    ; start: 0, id: 0
>                                                    ; startBeat: 0
> 
> By the way: does anyone have a piece composed with CLM and CM and would be so kind to share his or her score for the purposes of private studies? I?d be very interested in it.
> 
> All the best,
> Daniel Hensel
> 
> 
>> Am 21.06.2017 um 21:00 schrieb cmdist-request at ccrma.Stanford.EDU:
>> 
>> Send Cmdist mailing list submissions to
>> 	cmdist at ccrma.stanford.edu
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>> or, via email, send a message with subject or body 'help' to
>> 	cmdist-request at ccrma.stanford.edu
>> 
>> You can reach the person managing the list at
>> 	cmdist-owner at ccrma.stanford.edu
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Cmdist digest..."
>> 
>> 
>> Today's Topics:
>> 
>>   1. Re: Grace 3.10.0 is available (Dave Phillips)
>>   2. Re: Grace 3.10.0 is available (Taube, Heinrich K)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Wed, 21 Jun 2017 12:03:24 -0400
>> From: Dave Phillips <dlphillips at woh.rr.com>
>> To: cmdist at ccrma.Stanford.EDU
>> Subject: Re: [CM] Grace 3.10.0 is available
>> Message-ID: <594A98CC.3040100 at woh.rr.com>
>> Content-Type: text/plain; charset=windows-1252; format=flowed
>> 
>> Hi Rick, hi Tito !
>> 
>> On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
>>> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
>>> 
>>> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
>> 
>> Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF 
>> support. :)
>> 
>> Thank you !
>> 
>> Best,
>> 
>> dp
>> 
>> 
>>> 
>>>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
>>>> 
>>>> Thanks.
>>>> 
>>>> I can compile Grace with success on linux with the attached patch.
>>>> 
>>>> # tested with gcc-5.3.0 (x86_64)
>>>> unzip cm-3.10.0.zip
>>>> cd cm-3.10.0
>>>> patch -p1 < cm-3.10.0-linux-build.diff
>>>> premake4
>>>> make
>>>> <cm-3.10.0-linux-build.diff>
>>> 
>>> _______________________________________________
>>> Cmdist mailing list
>>> Cmdist at ccrma.stanford.edu
>>> https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>>> 
>>> 
>> 
>> 
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Wed, 21 Jun 2017 16:55:51 +0000
>> From: "Taube, Heinrich K" <taube at illinois.edu>
>> To: Dave Phillips <dlphillips at woh.rr.com>
>> Cc: commonmusic-Mailing-List List <cmdist at ccrma.Stanford.EDU>
>> Subject: Re: [CM] Grace 3.10.0 is available
>> Message-ID: <35635A62-40E0-4E1A-AACF-BB327F93A9EC at illinois.edu>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> Thank you Dave!
>> 
>> If there is someone out there on windows that knows a bit about compiling in VS please let me know!
>> 
>>> On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com> wrote:
>>> 
>>> Hi Rick, hi Tito !
>>> 
>>> On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
>>>> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
>>>> 
>>>> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
>>> 
>>> Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF support. :)
>>> 
>>> Thank you !
>>> 
>>> Best,
>>> 
>>> dp
>>> 
>>> 
>>>> 
>>>>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
>>>>> 
>>>>> Thanks.
>>>>> 
>>>>> I can compile Grace with success on linux with the attached patch.
>>>>> 
>>>>> # tested with gcc-5.3.0 (x86_64)
>>>>> unzip cm-3.10.0.zip
>>>>> cd cm-3.10.0
>>>>> patch -p1 < cm-3.10.0-linux-build.diff
>>>>> premake4
>>>>> make
>>>>> <cm-3.10.0-linux-build.diff>
>>>> 
>>>> _______________________________________________
>>>> 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
>> 
>> 
>> End of Cmdist Digest, Vol 110, Issue 6
>> **************************************
>> 
> 
>  
> 
> 
> _______________________________________________
> Cmdist mailing list
> Cmdist at ccrma.stanford.edu
> https://cm-mail.stanford.edu/mailman/listinfo/cmdist




From treegestalt at gmail.com  Wed Jun 21 20:39:28 2017
From: treegestalt at gmail.com (Forrest Curo)
Date: Wed, 21 Jun 2017 20:39:28 -0700
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <F2B81E3D-BBA2-4FFD-9713-6CAB1078AFBC@illinois.edu>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
	<594A98CC.3040100@woh.rr.com>
	<35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>
	<CAAn-EcwzFLS4aAG4X0fQ00O8fTa7G3v+uotXd2QQhasvgnJqxA@mail.gmail.com>
	<F2B81E3D-BBA2-4FFD-9713-6CAB1078AFBC@illinois.edu>
Message-ID: <CAAn-EcwLPthZfVegvJ6H3gper=epxpWyVa5ZBfVy4dW+Sd=u7g@mail.gmail.com>

What I'm not finding is the documentation.

I built the program in ~/Grace/cm, where I find a directory named

/home/forrest/Grace/doc/Common Music 3.10.0

but it's empty.

On Wed, Jun 21, 2017 at 1:10 PM, Taube, Heinrich K <taube at illinois.edu>
wrote:

> Forrest thanks, Ill take care of that nit.  yes osc is built in now so it
> should even run on windows... assuming someone can actually compile it
> there!
>
> > On Jun 21, 2017, at 2:58 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> >
> > Um, works on ubuntu 16.10.
> >
> > Readme file still calls for
> > "premake4 --with-oscpack"
> >
> > (but that is neither accepted nor needed; osc seems to be built in
> automatically now.)
> >
> > On Wed, Jun 21, 2017 at 9:55 AM, Taube, Heinrich K <taube at illinois.edu>
> wrote:
> > Thank you Dave!
> >
> > If there is someone out there on windows that knows a bit about
> compiling in VS please let me know!
> >
> > > On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com>
> wrote:
> > >
> > > Hi Rick, hi Tito !
> > >
> > > On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
> > >> Thank you Tito, you sure made that easy!  I've committed your changes
> (rev 21776 ).  ill wait a day or two an then update the source zip.  in the
> meantime patched sources for building on linux can be downloaded by doing:
> > >>
> > >> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
> > >
> > > Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF
> support. :)
> > >
> > > Thank you !
> > >
> > > Best,
> > >
> > > dp
> > >
> > >
> > >>
> > >>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com>
> wrote:
> > >>>
> > >>> Thanks.
> > >>>
> > >>> I can compile Grace with success on linux with the attached patch.
> > >>>
> > >>> # tested with gcc-5.3.0 (x86_64)
> > >>> unzip cm-3.10.0.zip
> > >>> cd cm-3.10.0
> > >>> patch -p1 < cm-3.10.0-linux-build.diff
> > >>> premake4
> > >>> make
> > >>> <cm-3.10.0-linux-build.diff>
> > >>
> > >> _______________________________________________
> > >> 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: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170621/2975799a/attachment.html>

From treegestalt at gmail.com  Thu Jun 22 07:44:17 2017
From: treegestalt at gmail.com (Forrest Curo)
Date: Thu, 22 Jun 2017 07:44:17 -0700
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <CAAn-EcwLPthZfVegvJ6H3gper=epxpWyVa5ZBfVy4dW+Sd=u7g@mail.gmail.com>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
	<594A98CC.3040100@woh.rr.com>
	<35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>
	<CAAn-EcwzFLS4aAG4X0fQ00O8fTa7G3v+uotXd2QQhasvgnJqxA@mail.gmail.com>
	<F2B81E3D-BBA2-4FFD-9713-6CAB1078AFBC@illinois.edu>
	<CAAn-EcwLPthZfVegvJ6H3gper=epxpWyVa5ZBfVy4dW+Sd=u7g@mail.gmail.com>
Message-ID: <CAAn-Ecy07OGk=0MW71+UKSfPDp6GWTbObonr_9G+FcLUeNuP-Q@mail.gmail.com>

Okay, the documentation came out in
~/Grace/cm/res/doc/cm.html#introduction

On Wed, Jun 21, 2017 at 8:39 PM, Forrest Curo <treegestalt at gmail.com> wrote:

> What I'm not finding is the documentation.
>
> I built the program in ~/Grace/cm, where I find a directory named
>
> /home/forrest/Grace/doc/Common Music 3.10.0
>
> but it's empty.
>
> On Wed, Jun 21, 2017 at 1:10 PM, Taube, Heinrich K <taube at illinois.edu>
> wrote:
>
>> Forrest thanks, Ill take care of that nit.  yes osc is built in now so it
>> should even run on windows... assuming someone can actually compile it
>> there!
>>
>> > On Jun 21, 2017, at 2:58 PM, Forrest Curo <treegestalt at gmail.com>
>> wrote:
>> >
>> > Um, works on ubuntu 16.10.
>> >
>> > Readme file still calls for
>> > "premake4 --with-oscpack"
>> >
>> > (but that is neither accepted nor needed; osc seems to be built in
>> automatically now.)
>> >
>> > On Wed, Jun 21, 2017 at 9:55 AM, Taube, Heinrich K <taube at illinois.edu>
>> wrote:
>> > Thank you Dave!
>> >
>> > If there is someone out there on windows that knows a bit about
>> compiling in VS please let me know!
>> >
>> > > On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com>
>> wrote:
>> > >
>> > > Hi Rick, hi Tito !
>> > >
>> > > On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
>> > >> Thank you Tito, you sure made that easy!  I've committed your
>> changes (rev 21776 ).  ill wait a day or two an then update the source
>> zip.  in the meantime patched sources for building on linux can be
>> downloaded by doing:
>> > >>
>> > >> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
>> > >
>> > > Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF
>> support. :)
>> > >
>> > > Thank you !
>> > >
>> > > Best,
>> > >
>> > > dp
>> > >
>> > >
>> > >>
>> > >>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com>
>> wrote:
>> > >>>
>> > >>> Thanks.
>> > >>>
>> > >>> I can compile Grace with success on linux with the attached patch.
>> > >>>
>> > >>> # tested with gcc-5.3.0 (x86_64)
>> > >>> unzip cm-3.10.0.zip
>> > >>> cd cm-3.10.0
>> > >>> patch -p1 < cm-3.10.0-linux-build.diff
>> > >>> premake4
>> > >>> make
>> > >>> <cm-3.10.0-linux-build.diff>
>> > >>
>> > >> _______________________________________________
>> > >> 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: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170622/f0715bae/attachment.html>

From taube at illinois.edu  Thu Jun 22 07:49:07 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Thu, 22 Jun 2017 14:49:07 +0000
Subject: [CM] Grace 3.10.0 is available
In-Reply-To: <CAAn-Ecy07OGk=0MW71+UKSfPDp6GWTbObonr_9G+FcLUeNuP-Q@mail.gmail.com>
References: <EA7E4350-6CAE-4320-88B8-B87D84C37BDF@illinois.edu>
	<20170620082053.GA1677@rhk.Home>
	<30CE685A-9CA2-415C-9976-5C421FAB822E@illinois.edu>
	<594A98CC.3040100@woh.rr.com>
	<35635A62-40E0-4E1A-AACF-BB327F93A9EC@illinois.edu>
	<CAAn-EcwzFLS4aAG4X0fQ00O8fTa7G3v+uotXd2QQhasvgnJqxA@mail.gmail.com>
	<F2B81E3D-BBA2-4FFD-9713-6CAB1078AFBC@illinois.edu>
	<CAAn-EcwLPthZfVegvJ6H3gper=epxpWyVa5ZBfVy4dW+Sd=u7g@mail.gmail.com>
	<CAAn-Ecy07OGk=0MW71+UKSfPDp6GWTbObonr_9G+FcLUeNuP-Q@mail.gmail.com>
Message-ID: <F8B719B3-FB18-4025-81F4-1389C0149469@illinois.edu>

In Grace?s Help menu you should be able to simply select  Common Music (in the Documentation & Reference menu section)

that should open the documentation in your browser.

alternately, if you are in the editor, you can look up the documentation for a function or reserverd word by clicking on it and then pressing Command-D 


> On Jun 22, 2017, at 9:44 AM, Forrest Curo <treegestalt at gmail.com> wrote:
> 
> Okay, the documentation came out in
> ~/Grace/cm/res/doc/cm.html#introduction
> 
> On Wed, Jun 21, 2017 at 8:39 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> What I'm not finding is the documentation.
> 
> I built the program in ~/Grace/cm, where I find a directory named 
> 
> /home/forrest/Grace/doc/Common Music 3.10.0
> 
> but it's empty.
> 
> On Wed, Jun 21, 2017 at 1:10 PM, Taube, Heinrich K <taube at illinois.edu> wrote:
> Forrest thanks, Ill take care of that nit.  yes osc is built in now so it should even run on windows... assuming someone can actually compile it there!
> 
> > On Jun 21, 2017, at 2:58 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> >
> > Um, works on ubuntu 16.10.
> >
> > Readme file still calls for
> > "premake4 --with-oscpack"
> >
> > (but that is neither accepted nor needed; osc seems to be built in automatically now.)
> >
> > On Wed, Jun 21, 2017 at 9:55 AM, Taube, Heinrich K <taube at illinois.edu> wrote:
> > Thank you Dave!
> >
> > If there is someone out there on windows that knows a bit about compiling in VS please let me know!
> >
> > > On Jun 21, 2017, at 11:03 AM, Dave Phillips <dlphillips at woh.rr.com> wrote:
> > >
> > > Hi Rick, hi Tito !
> > >
> > > On 06/20/2017 07:24 AM, Taube, Heinrich K wrote:
> > >> Thank you Tito, you sure made that easy!  I've committed your changes (rev 21776 ).  ill wait a day or two an then update the source zip.  in the meantime patched sources for building on linux can be downloaded by doing:
> > >>
> > >> svn checkout  https://svn.code.sf.net/p/commonmusic/code/trunk cm
> > >
> > > Successfully built & tested on Fedora 21 x86_64, with FOMUS and SDIF support. :)
> > >
> > > Thank you !
> > >
> > > Best,
> > >
> > > dp
> > >
> > >
> > >>
> > >>> On Jun 20, 2017, at 3:20 AM, Tito Latini <tito.01beta at gmail.com> wrote:
> > >>>
> > >>> Thanks.
> > >>>
> > >>> I can compile Grace with success on linux with the attached patch.
> > >>>
> > >>> # tested with gcc-5.3.0 (x86_64)
> > >>> unzip cm-3.10.0.zip
> > >>> cd cm-3.10.0
> > >>> patch -p1 < cm-3.10.0-linux-build.diff
> > >>> premake4
> > >>> make
> > >>> <cm-3.10.0-linux-build.diff>
> > >>
> > >> _______________________________________________
> > >> 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 danielhensel at icloud.com  Fri Jun 23 12:53:24 2017
From: danielhensel at icloud.com (Daniel Hensel)
Date: Fri, 23 Jun 2017 21:53:24 +0200
Subject: [CM] CLM/CM-score request
In-Reply-To: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>
References: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>
Message-ID: <AF56C04E-87A3-44A3-9266-F1787C0B2112@icloud.com>

Hi,

does anyone wanna share an interesting score composed with CLM and CM  for the purposes of private studies?  I want to see the two ?beasts? in action  :) 

Thanks!

All the best,
Daniel




From treegestalt at gmail.com  Fri Jun 23 13:59:37 2017
From: treegestalt at gmail.com (Forrest Curo)
Date: Fri, 23 Jun 2017 13:59:37 -0700
Subject: [CM] real time csound and Grace
Message-ID: <CAAn-Ecy-uOQ2hXottfpapmG6T8+2DHWRySEuksL2tNGHAkrLgg@mail.gmail.com>

I'm a little confused re real time interactions between Grace and csound,
guessing that the possiblities (especially with OSC but probably also using
simply "cs:i ...") have probably outrun the documentation.

What is the actual situation? Lots of ways to run the two programs
independently... but with one cm process running a real-time csound
instance & sending it various forms of data?

Wouldn't work well? Cumbersome? Redundant?

Or should the best way be pretty self-explanatory by now?

Forrest Curo
San Diego
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170623/a0f4b62e/attachment.html>

From taube at illinois.edu  Fri Jun 23 17:23:16 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Sat, 24 Jun 2017 00:23:16 +0000
Subject: [CM] CLM/CM-score request
In-Reply-To: <AF56C04E-87A3-44A3-9266-F1787C0B2112@icloud.com>
References: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>
	<AF56C04E-87A3-44A3-9266-F1787C0B2112@icloud.com>
Message-ID: <C820B924-9CE6-49E4-A27D-F81B071DF232@illinois.edu>

if you go to http://commonmusic.sourceforge.net/  then down the page you can find some music and scores


> On Jun 23, 2017, at 2:53 PM, Daniel Hensel <danielhensel at icloud.com> wrote:
> 
> Hi,
> 
> does anyone wanna share an interesting score composed with CLM and CM  for the purposes of private studies?  I want to see the two ?beasts? in action  :) 
> 
> Thanks!
> 
> All the best,
> Daniel
> 
> 
> _______________________________________________
> Cmdist mailing list
> Cmdist at ccrma.stanford.edu
> https://cm-mail.stanford.edu/mailman/listinfo/cmdist




From taube at illinois.edu  Fri Jun 23 17:22:02 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Sat, 24 Jun 2017 00:22:02 +0000
Subject: [CM] real time csound and Grace
In-Reply-To: <CAAn-Ecy-uOQ2hXottfpapmG6T8+2DHWRySEuksL2tNGHAkrLgg@mail.gmail.com>
References: <CAAn-Ecy-uOQ2hXottfpapmG6T8+2DHWRySEuksL2tNGHAkrLgg@mail.gmail.com>
Message-ID: <0A6DB069-690E-4932-9DCB-C5391FCF219E@illinois.edu>

at one point i had a real-time connection to libcsound, but back then it was very hard to maintain and also to build the csound lib on the different platforms. So i went back to basic writing files and calling csound from the shell


> On Jun 23, 2017, at 3:59 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> 
> I'm a little confused re real time interactions between Grace and csound, guessing that the possiblities (especially with OSC but probably also using simply "cs:i ...") have probably outrun the documentation. 
> 
> What is the actual situation? Lots of ways to run the two programs independently... but with one cm process running a real-time csound instance & sending it various forms of data? 
> 
> Wouldn't work well? Cumbersome? Redundant? 
> 
> Or should the best way be pretty self-explanatory by now?
> 
> Forrest Curo
> San Diego
> _______________________________________________
> Cmdist mailing list
> Cmdist at ccrma.stanford.edu
> https://cm-mail.stanford.edu/mailman/listinfo/cmdist




From treegestalt at gmail.com  Fri Jun 23 18:00:48 2017
From: treegestalt at gmail.com (Forrest Curo)
Date: Fri, 23 Jun 2017 18:00:48 -0700
Subject: [CM] real time csound and Grace
In-Reply-To: <0A6DB069-690E-4932-9DCB-C5391FCF219E@illinois.edu>
References: <CAAn-Ecy-uOQ2hXottfpapmG6T8+2DHWRySEuksL2tNGHAkrLgg@mail.gmail.com>
	<0A6DB069-690E-4932-9DCB-C5391FCF219E@illinois.edu>
Message-ID: <CAAn-Ecx1oa8dJMyUG28VpcZqXmJxaPDFtnSc3_1w5gd4qqAEaw@mail.gmail.com>

It _looks_ like one could save and play a score file that basically said,
say : "f0 600" for ten minutes of communicating with it by other means...

Instead I'll just start csound rendering away on one computer while another
sends it messages over a network cable. Would then use cm basically for
timing, scheduling, midi interface.

I can barely imagine the hassles of writing something for multiple
platforms.

On Fri, Jun 23, 2017 at 5:22 PM, Taube, Heinrich K <taube at illinois.edu>
wrote:

> at one point i had a real-time connection to libcsound, but back then it
> was very hard to maintain and also to build the csound lib on the different
> platforms. So i went back to basic writing files and calling csound from
> the shell
>
>
> > On Jun 23, 2017, at 3:59 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> >
> > I'm a little confused re real time interactions between Grace and
> csound, guessing that the possiblities (especially with OSC but probably
> also using simply "cs:i ...") have probably outrun the documentation.
> >
> > What is the actual situation? Lots of ways to run the two programs
> independently... but with one cm process running a real-time csound
> instance & sending it various forms of data?
> >
> > Wouldn't work well? Cumbersome? Redundant?
> >
> > Or should the best way be pretty self-explanatory by now?
> >
> > Forrest Curo
> > San Diego
> > _______________________________________________
> > Cmdist mailing list
> > Cmdist at ccrma.stanford.edu
> > https://cm-mail.stanford.edu/mailman/listinfo/cmdist
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170623/35deeaaa/attachment.html>

From taube at illinois.edu  Fri Jun 23 19:27:54 2017
From: taube at illinois.edu (Taube, Heinrich K)
Date: Sat, 24 Jun 2017 02:27:54 +0000
Subject: [CM] real time csound and Grace
In-Reply-To: <CAAn-Ecx1oa8dJMyUG28VpcZqXmJxaPDFtnSc3_1w5gd4qqAEaw@mail.gmail.com>
References: <CAAn-Ecy-uOQ2hXottfpapmG6T8+2DHWRySEuksL2tNGHAkrLgg@mail.gmail.com>
	<0A6DB069-690E-4932-9DCB-C5391FCF219E@illinois.edu>
	<CAAn-Ecx1oa8dJMyUG28VpcZqXmJxaPDFtnSc3_1w5gd4qqAEaw@mail.gmail.com>
Message-ID: <03D82CCC-0448-44C6-8862-BA57C9B4D481@illinois.edu>

if CSound takes OSC messages you could send your data that way in real time.

> On Jun 23, 2017, at 8:00 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> 
> It _looks_ like one could save and play a score file that basically said, say : "f0 600" for ten minutes of communicating with it by other means...
> 
> Instead I'll just start csound rendering away on one computer while another sends it messages over a network cable. Would then use cm basically for timing, scheduling, midi interface.
> 
> I can barely imagine the hassles of writing something for multiple platforms.
> 
> On Fri, Jun 23, 2017 at 5:22 PM, Taube, Heinrich K <taube at illinois.edu> wrote:
> at one point i had a real-time connection to libcsound, but back then it was very hard to maintain and also to build the csound lib on the different platforms. So i went back to basic writing files and calling csound from the shell
> 
> 
> > On Jun 23, 2017, at 3:59 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> >
> > I'm a little confused re real time interactions between Grace and csound, guessing that the possiblities (especially with OSC but probably also using simply "cs:i ...") have probably outrun the documentation.
> >
> > What is the actual situation? Lots of ways to run the two programs independently... but with one cm process running a real-time csound instance & sending it various forms of data?
> >
> > Wouldn't work well? Cumbersome? Redundant?
> >
> > Or should the best way be pretty self-explanatory by now?
> >
> > Forrest Curo
> > San Diego
> > _______________________________________________
> > Cmdist mailing list
> > Cmdist at ccrma.stanford.edu
> > https://cm-mail.stanford.edu/mailman/listinfo/cmdist
> 
> 




From treegestalt at gmail.com  Sat Jun 24 11:18:29 2017
From: treegestalt at gmail.com (Forrest Curo)
Date: Sat, 24 Jun 2017 11:18:29 -0700
Subject: [CM] real time csound and Grace
In-Reply-To: <03D82CCC-0448-44C6-8862-BA57C9B4D481@illinois.edu>
References: <CAAn-Ecy-uOQ2hXottfpapmG6T8+2DHWRySEuksL2tNGHAkrLgg@mail.gmail.com>
	<0A6DB069-690E-4932-9DCB-C5391FCF219E@illinois.edu>
	<CAAn-Ecx1oa8dJMyUG28VpcZqXmJxaPDFtnSc3_1w5gd4qqAEaw@mail.gmail.com>
	<03D82CCC-0448-44C6-8862-BA57C9B4D481@illinois.edu>
Message-ID: <CAAn-EczxotZrMQfe0qQc4LpCKfaTsrSwsAwyY7HSqnsvYvE7uQ@mail.gmail.com>

You used to be able to run cm from emacs; that would likewise be suitable
for various kinds of messages...

(?)

On Fri, Jun 23, 2017 at 7:27 PM, Taube, Heinrich K <taube at illinois.edu>
wrote:

> if CSound takes OSC messages you could send your data that way in real
> time.
>
> > On Jun 23, 2017, at 8:00 PM, Forrest Curo <treegestalt at gmail.com> wrote:
> >
> > It _looks_ like one could save and play a score file that basically
> said, say : "f0 600" for ten minutes of communicating with it by other
> means...
> >
> > Instead I'll just start csound rendering away on one computer while
> another sends it messages over a network cable. Would then use cm basically
> for timing, scheduling, midi interface.
> >
> > I can barely imagine the hassles of writing something for multiple
> platforms.
> >
> > On Fri, Jun 23, 2017 at 5:22 PM, Taube, Heinrich K <taube at illinois.edu>
> wrote:
> > at one point i had a real-time connection to libcsound, but back then it
> was very hard to maintain and also to build the csound lib on the different
> platforms. So i went back to basic writing files and calling csound from
> the shell
> >
> >
> > > On Jun 23, 2017, at 3:59 PM, Forrest Curo <treegestalt at gmail.com>
> wrote:
> > >
> > > I'm a little confused re real time interactions between Grace and
> csound, guessing that the possiblities (especially with OSC but probably
> also using simply "cs:i ...") have probably outrun the documentation.
> > >
> > > What is the actual situation? Lots of ways to run the two programs
> independently... but with one cm process running a real-time csound
> instance & sending it various forms of data?
> > >
> > > Wouldn't work well? Cumbersome? Redundant?
> > >
> > > Or should the best way be pretty self-explanatory by now?
> > >
> > > Forrest Curo
> > > San Diego
> > > _______________________________________________
> > > Cmdist mailing list
> > > Cmdist at ccrma.stanford.edu
> > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170624/72fb9863/attachment.html>

From bil at ccrma.Stanford.EDU  Mon Jun 26 15:13:14 2017
From: bil at ccrma.Stanford.EDU (bil at ccrma.Stanford.EDU)
Date: Mon, 26 Jun 2017 15:13:14 -0700
Subject: [CM] Snd 17.5
Message-ID: <5ad64381988643cf518e1b72846525cf@ccrma.stanford.edu>

Snd 17.5:

s7: s7_history and s7_add_to_history (Kjetil's suggestion).
     (*s7* 'history) for non-error scheme-side access to the history info
     lambda* keyword argument handling changed slightly.
     multithread sanity-checks thanks to Kjetil.
     Kjetil also ported s7 to mingw.

checked: gtk 3.91.0, sbcl 1.3.18, FC 26 (gcc 7.1.1)

Thanks!: Kjetil Matheussen, Rick Taube



From Michael.Rogulla at SIZ.DE  Tue Jun 27 00:28:19 2017
From: Michael.Rogulla at SIZ.DE (Michael.Rogulla at SIZ.DE)
Date: Tue, 27 Jun 2017 09:28:19 +0200
Subject: [CM] Antwort: Re:  CLM/CM-score request
In-Reply-To: <C820B924-9CE6-49E4-A27D-F81B071DF232@illinois.edu>
References: <mailman.3.1498071602.2710.cmdist@ccrma.stanford.edu>	<AF56C04E-87A3-44A3-9266-F1787C0B2112@icloud.com>
	<C820B924-9CE6-49E4-A27D-F81B071DF232@illinois.edu>
Message-ID: <OF5FC3D77E.91C3F574-ONC125814C.0028B873-C125814C.00290BC3@SIZ>

Hi,

I am also interested in seeing CLM / CM at work, but I could not find any 
sourcecode on the mentioned pages, only music and scores (notes). Is there 
anybody out there willing to share some code? I mean, a real piece of 
music, not just short examples?

Greetings,
Michael




Von:    "Taube, Heinrich K" <taube at illinois.edu>
An:     Daniel Hensel <danielhensel at icloud.com>
Kopie:  commonmusic-Mailing-List List <cmdist at ccrma.Stanford.EDU>
Datum:  24.06.2017 02:27
Betreff:        Re: [CM] CLM/CM-score request
Gesendet von:   cmdist-bounces at ccrma.Stanford.EDU



if you go to http://commonmusic.sourceforge.net/  then down the page you 
can find some music and scores


> On Jun 23, 2017, at 2:53 PM, Daniel Hensel <danielhensel at icloud.com> 
wrote:
> 
> Hi,
> 
> does anyone wanna share an interesting score composed with CLM and CM 
for the purposes of private studies?  I want to see the two ?beasts? in 
action  :) 
> 
> Thanks!
> 
> All the best,
> Daniel
> 
> 
> _______________________________________________
> 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: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170627/bb46c222/attachment.html>

From k.s.matheussen at gmail.com  Tue Jun 27 07:35:38 2017
From: k.s.matheussen at gmail.com (Kjetil Matheussen)
Date: Tue, 27 Jun 2017 16:35:38 +0200
Subject: [CM] Snd 17.5
In-Reply-To: <5ad64381988643cf518e1b72846525cf@ccrma.stanford.edu>
References: <5ad64381988643cf518e1b72846525cf@ccrma.stanford.edu>
Message-ID: <CAC6niE+TYutNEGtu5ym_Rp02k2PigPqvOiUVhukCj0OgzX19Uw@mail.gmail.com>

On Tue, Jun 27, 2017 at 12:13 AM, <bil at ccrma.stanford.edu> wrote:

> Snd 17.5:
>
> s7: s7_history and s7_add_to_history (Kjetil's suggestion).
>     (*s7* 'history) for non-error scheme-side access to the history info
>     lambda* keyword argument handling changed slightly.
>     multithread sanity-checks thanks to Kjetil.
>     Kjetil also ported s7 to mingw.
>
>
FTR, I just fixed some printf formatting and removed some compiler
warnings. s7 worked with mingw before this release too.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20170627/4ea95ccb/attachment.html>