From bil at ccrma.Stanford.EDU Sun Jul 1 03:55:43 2018 From: bil at ccrma.Stanford.EDU (bil at ccrma.Stanford.EDU) Date: Sun, 01 Jul 2018 03:55:43 -0700 Subject: [CM] Snd 18.5 Message-ID: <222243a25743df413b6fbd7591013b04@ccrma.stanford.edu> Snd 18.5: s7 to version 7 (many internal changes). checked: sbcl 1.4.8|9, gtk 3.94.0 Thanks!: Kjetil Matheussen From orm.finnendahl at selma.hfmdk-frankfurt.de Sun Jul 22 08:18:26 2018 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Sun, 22 Jul 2018 17:18:26 +0200 Subject: [CM] cm2: svg backend, permutation pattern Message-ID: <20180722151826.GA23292@T460s-orm> Hi List, Rick, as you might now, I'm using cm2 and try to somewhat maintain the code base on my github account (partly to keep "Notes on the Metalevel" alive), made it work in realtime with incudine and sc-collider and even programmed some extensions I use for my compositional work. I don't know if it makes any sense to announce it here, as I guess hardly anybody is using it. Therefore my question: Is *anybody* using cm2 and interested in these posts? Otherwise it might make more sense not to make any noise at all here... For those interested: Recently I made a svg backend for cm2: https://github.com/ormf/cm-svg you'll also need this package doing the heavy lifting: https://github.com/ormf/svg-import-export With the code loaded it is now possible to write (events (...) "/tmp/test.svg") and it'll save the data into an svg file in some sort of a "piano-roll" representation including a piano-roll background pattern, cent-aligned staff systems and barlines in different layers. The svg can be opened and edited in inkscape and reimported into cm using #'import-events. The major advantage to a midi piano-roll editor is that the y-axis isn't restricted to halfsteps and scaling/stretching/skewing operations will be imported correctly, which makes it quite nice for microtonal/spectral work. This is a preliminary port as I'm intending to extend this into arbitrary data sets available for non-midi purposes (interfacing with incudine, etc.). In addition I made a recursion pattern class. Although this could also be modeled with the existing rewrite pattern, the specialized class is a little more straightforward to use. I attach the file to this mail as it is fairly small. @Rick: I found some bugs in the cm dictionary and am a little unsure how to go about extending the documentation. I really like the symbol-lookup from the editor and wrote some javascript to make the frames version work with modern browsers. I'd love to extend your dict but there are some issues: 1. I would like to annotate the extensions in the documentation to distinguish it from the "original" common music (although this is difficult anyway, as the original code already was a moving target), keeping the code as much backward compatible, as possible. How would you recommend to do it? 2. You probably used some sort of documentation system. Would it be possible to hook into that and extend it from there and you send me the sources or is that copyrighted/protected code? 3. I would prefer to keep all additional cm code which isn't related to bugfixes in its own repository and don't know how I should handle extentions to the documentation of this additional code. It might be possible to just host the differences to the dict in the new repository rather than forking the complete dict, but I fear this is asking for trouble. Maybe you can give me some advice although I'm aware cm2 is not very high on your priority list... -------------- next part -------------- ;;; patterns.lisp ;;; ;;; Copyright (c) 2018 Orm Finnendahl ;;; ;;; This program is free software; you can redistribute it and/or modify ;;; it under the terms of the GNU General Public License as published by ;;; the Free Software Foundation; either version 2 of the License, or ;;; (at your option) any later version. ;;; ;;; This program is distributed in the hope that it will be useful, ;;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;;; GNU General Public License for more details. ;;; ;;; You should have received a copy of the GNU General Public License ;;; along with this program; if not, write to the Free Software ;;; Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA ;;; ;;; more pattern classes not existent in original cm2 ;;; (in-package #:cm) ;;; permutation pattern class ;;; ;;; repeatedly apply a permutation to a given list of items. ;;; ;;; :of keyword specifies the items to permutate. ;;; ;;; :idxs keyword is a list of permutation indexes. Make sure it has ;;; the same length as the item list and contains all indexes from 0 ;;; to length-1. ;;; ;;; :immediately specifies whether the permutation is immediately ;;; applied to the item list before accessing the first element of the ;;; pattern. If set to nil, next first returns one period of the ;;; original item list before applying the permutation. Default is t. ;;; ;;; ;;; #| Examples: (let ((seq (new permutation :of '(a b c d e) :idxs '(4 3 0 2 1) :immediately nil))) (loop for x below 6 collect (next seq t))) -> ((A B C D E) (E D A C B) (B C E A D) (D A B E C) (C E D B A) (A B C D E)) (let ((seq (new permutation :of '(a b c d e) :idxs '(4 3 0 2 1) :immediately t))) (loop for x below 6 collect (next seq t))) -> ((E D A C B) (B C E A D) (D A B E C) (C E D B A) (A B C D E) (E D A C B)) |# (progn (defclass permutation (cycle) ((idxs :initform 0 :initarg :idxs :accessor idxs) (immediately :initform t :initarg :immediately :accessor immediately))) (defparameter (find-class 'permutation)) (finalize-class ) (values)) (defmethod pattern-external-inits ((obj permutation)) (let ((inits (call-next-method))) (append inits (if (equal (permutations obj) 0) (list) (list ':idxs (expand-pattern-value (idxs obj)) ':immediately (immediately obj)))))) (defmethod initialize-instance :after ((obj permutation) &rest args) args (let ((cyc (pattern-data obj))) (cycl-data-set! cyc (copy-list (cycl-data cyc))) (unless (immediately obj) (cycl-tail-set! cyc (copy-list (cycl-data cyc)))) (values))) (defmethod next-in-pattern ((obj permutation)) (flet ((perm-in-place (lis len perm) (block main (loop for i = 0 then (incf i) while (< i len) do (progn (loop while (< (elt perm i) 0) ;;; is elem lready done/accessed? do (progn (incf i) (if (= i len) (return-from main)))) (loop ;;; do a full cycle of replacements starting with the ith element of perm for from = i then to for to = (elt perm from) until (= to i) for tmp = (elt lis to) do (setf (elt lis to) (elt lis from) ;;; swap list elements (elt lis from) tmp (elt perm from) (+ -1 (* -1 (elt perm from)))) ;;; tag elem of perm as accessed/done. finally (setf (elt perm from) (+ -1 (* -1 (elt perm from)))))))) ;;; tag starting element of permutation cycle as accessed/done. (loop for i below len do (setf (elt perm i) (* -1 (+ 1 (elt perm i))))) ;;; restore all elements of permutation. lis)) (let ((cyc (pattern-data obj))) (if (null (cycl-tail cyc)) (cycl-tail-set! cyc (perm-in-place (cycl-data cyc) (pattern-length obj) (idxs obj)))) (pop-cycl cyc)))) (export 'permutation 'cm) From mr.danielross at gmail.com Sun Jul 22 10:06:26 2018 From: mr.danielross at gmail.com (Daniel James Ross) Date: Sun, 22 Jul 2018 19:06:26 +0200 Subject: [CM] cm2: svg backend, permutation pattern In-Reply-To: <20180722151826.GA23292@T460s-orm> References: <20180722151826.GA23292@T460s-orm> Message-ID: I am certainly interested in this! I use Michael Edwards' *slippery chicken *regularly and, coincidentally, have recently been looking into combining CM output with cl-svg. I shall dive into your code and take a look! Thanks for sharing! Best, Dan *Daniel James Ross* vitruviandan.wordpress.com On 22 July 2018 at 17:18, Orm Finnendahl < orm.finnendahl at selma.hfmdk-frankfurt.de> wrote: > Hi List, Rick, > > as you might now, I'm using cm2 and try to somewhat maintain the code > base on my github account (partly to keep "Notes on the Metalevel" > alive), made it work in realtime with incudine and sc-collider and > even programmed some extensions I use for my compositional work. > > I don't know if it makes any sense to announce it here, as I guess > hardly anybody is using it. Therefore my question: Is *anybody* using > cm2 and interested in these posts? Otherwise it might make more sense > not to make any noise at all here... > > For those interested: Recently I made a svg backend for cm2: > > https://github.com/ormf/cm-svg > > you'll also need this package doing the heavy lifting: > > https://github.com/ormf/svg-import-export > > With the code loaded it is now possible to write > > (events (...) "/tmp/test.svg") > > and it'll save the data into an svg file in some sort of a > "piano-roll" representation including a piano-roll background pattern, > cent-aligned staff systems and barlines in different layers. The svg > can be opened and edited in inkscape and reimported into cm using > #'import-events. The major advantage to a midi piano-roll editor is > that the y-axis isn't restricted to halfsteps and > scaling/stretching/skewing operations will be imported correctly, > which makes it quite nice for microtonal/spectral work. This is a > preliminary port as I'm intending to extend this into arbitrary data > sets available for non-midi purposes (interfacing with incudine, > etc.). > > In addition I made a recursion pattern class. Although this could also > be modeled with the existing rewrite pattern, the specialized class is > a little more straightforward to use. I attach the file to this mail > as it is fairly small. > > @Rick: I found some bugs in the cm dictionary and am a little unsure > how to go about extending the documentation. I really like the > symbol-lookup from the editor and wrote some javascript to make the > frames version work with modern browsers. I'd love to extend your dict > but there are some issues: > > 1. I would like to annotate the extensions in the documentation to > distinguish it from the "original" common music (although this is > difficult anyway, as the original code already was a moving > target), keeping the code as much backward compatible, as possible. > How would you recommend to do it? > > 2. You probably used some sort of documentation system. Would it be > possible to hook into that and extend it from there and you send me > the sources or is that copyrighted/protected code? > > 3. I would prefer to keep all additional cm code which isn't related > to bugfixes in its own repository and don't know how I should > handle extentions to the documentation of this additional code. It > might be possible to just host the differences to the dict in the > new repository rather than forking the complete dict, but I fear > this is asking for trouble. > > Maybe you can give me some advice although I'm aware cm2 is not very > high on your priority list... > > _______________________________________________ > 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 ahcnz at orcon.net.nz Mon Jul 23 01:15:38 2018 From: ahcnz at orcon.net.nz (adam) Date: Mon, 23 Jul 2018 20:15:38 +1200 Subject: [CM] cm2: svg backend, permutation pattern In-Reply-To: <20180722151826.GA23292@T460s-orm> References: <20180722151826.GA23292@T460s-orm> Message-ID: <1532333738.8641.3.camel@orcon.net.nz> Yes, some of us still use CM2. +1 to keep posting Orm.? Although it refused to build the last time I tried it.? I must try again, I'm presently using an older image. ? I see that CM3 or Grace requires a make or cmake process these days.? It was nice when there was a Ubuntu executable. But that's OK.? Thank you.? On Sun, 2018-07-22 at 17:18 +0200, Orm Finnendahl wrote: > Hi List, Rick, > > ?as you might now, I'm using cm2 and try to somewhat maintain the code > base on my github account (partly to keep "Notes on the Metalevel" > alive), made it work in realtime with incudine and sc-collider and > even programmed some extensions I use for my compositional work. > > I don't know if it makes any sense to announce it here, as I guess > hardly anybody is using it. Therefore my question: Is *anybody* using > cm2 and interested in these posts? Otherwise it might make more sense > not to make any noise at all here... > > For those interested: Recently I made a svg backend for cm2: > > https://github.com/ormf/cm-svg > > you'll also need this package doing the heavy lifting: > > https://github.com/ormf/svg-import-export > > With the code loaded it is now possible to write > > ???(events (...) "/tmp/test.svg") > > and it'll save the data into an svg file in some sort of a > "piano-roll" representation including a piano-roll background pattern, > cent-aligned staff systems and barlines in different layers. The svg > can be opened and edited in inkscape and reimported into cm using > #'import-events. The major advantage to a midi piano-roll editor is > that the y-axis isn't restricted to halfsteps and > scaling/stretching/skewing operations will be imported correctly, > which makes it quite nice for microtonal/spectral work. This is a > preliminary port as I'm intending to extend this into arbitrary data > sets available for non-midi purposes (interfacing with incudine, > etc.). > > In addition I made a recursion pattern class. Although this could also > be modeled with the existing rewrite pattern, the specialized class is > a little more straightforward to use. I attach the file to this mail > as it is fairly small. > > @Rick: I found some bugs in the cm dictionary and am a little unsure > how to go about extending the documentation. I really like the > symbol-lookup from the editor and wrote some javascript to make the > frames version work with modern browsers. I'd love to extend your dict > but there are some issues: > > 1. I would like to annotate the extensions in the documentation to > ???distinguish it from the "original" common music (although this is > ???difficult anyway, as the original code already was a moving > ???target), keeping the code as much backward compatible, as possible. > ???How would you recommend to do it? > > 2. You probably used some sort of documentation system. Would it be > ???possible to hook into that and extend it from there and you send me > ???the sources or is that copyrighted/protected code? > > 3. I would prefer to keep all additional cm code which isn't related > ???to bugfixes in its own repository and don't know how I should > ???handle extentions to the documentation of this additional code. It > ???might be possible to just host the differences to the dict in the > ???new repository rather than forking the complete dict, but I fear > ???this is asking for trouble. > > Maybe you can give me some advice although I'm aware cm2 is not very > high on your priority list... > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From orm.finnendahl at selma.hfmdk-frankfurt.de Mon Jul 23 05:00:30 2018 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Mon, 23 Jul 2018 14:00:30 +0200 Subject: [CM] cm2: svg backend, permutation pattern In-Reply-To: <1532333738.8641.3.camel@orcon.net.nz> References: <20180722151826.GA23292@T460s-orm> <1532333738.8641.3.camel@orcon.net.nz> Message-ID: <20180723120030.GC30600@T460s-orm> Am Montag, den 23. Juli 2018 um 20:15:38 Uhr (+1200) schrieb adam: > > Yes, some of us still use CM2. +1 to keep posting Orm.? > > Although it refused to build the last time I tried it.? > I must try again, I'm presently using an older image. ? Let me know if you run into problems. As the svg code depends on xml libs from quicklisp, I'd suggest to use a recent lisp with quicklisp support. If you use sbcl (and jack) it gives you the opportunity to also use the realtime extensions. -- Orm From juanigrp at gmail.com Mon Jul 23 10:02:25 2018 From: juanigrp at gmail.com (Juan Reyes) Date: Mon, 23 Jul 2018 10:02:25 -0700 Subject: [CM] cm2: svg backend, perichmutation pattern In-Reply-To: <20180723120030.GC30600@T460s-orm> References: <20180722151826.GA23292@T460s-orm> <1532333738.8641.3.camel@orcon.net.nz> <20180723120030.GC30600@T460s-orm> Message-ID: <7c31350b-13cb-a567-04f0-97606262f667@ccrma.stanford.edu> Hi Orm, Same here I use CM-2.12 for the same reasons you are mentioning so (1+) also. Permutation pattern looks good and very useful. Hope it makes it to 'patterns.lisp'. However, any pointers on building on SBCL 1.4 Fedora-27 ?. Just tried to load it and ASDF is complaining about the Alexandria package after: (require :sb-posix) (load "cm.asd") (asdf:load-system :cm) Previous cm2.asd file was giving several warnings in regards to updating API: WARNING: DEPRECATED-FUNCTION-WARNING: Using deprecated function (ASDF/ACTION::BACKWARD-COMPATIBLE-DEPENDS-ON :FOR-OPERATION #) -- please update your code to use a newer API. Thanks a lot!, -- Juan Reyes >> >> Yes, some of us still use CM2. +1 to keep posting Orm.? >> >> Although it refused to build the last time I tried it.? >> I must try again, I'm presently using an older image. ? > > Let me know if you run into problems. As the svg code depends on xml > libs from quicklisp, I'd suggest to use a recent lisp with quicklisp > support. If you use sbcl (and jack) it gives you the opportunity to > also use the realtime extensions. > > > From orm.finnendahl at selma.hfmdk-frankfurt.de Mon Jul 23 10:52:47 2018 From: orm.finnendahl at selma.hfmdk-frankfurt.de (Orm Finnendahl) Date: Mon, 23 Jul 2018 19:52:47 +0200 Subject: [CM] cm2: svg backend, perichmutation pattern In-Reply-To: <7c31350b-13cb-a567-04f0-97606262f667@ccrma.stanford.edu> References: <20180722151826.GA23292@T460s-orm> <1532333738.8641.3.camel@orcon.net.nz> <20180723120030.GC30600@T460s-orm> <7c31350b-13cb-a567-04f0-97606262f667@ccrma.stanford.edu> Message-ID: <20180723175247.GA26900@T460s-orm> Hi Juan, Am Montag, den 23. Juli 2018 um 10:02:25 Uhr (-0700) schrieb Juan Reyes: > > However, any pointers on building on SBCL 1.4 Fedora-27 ?. I strongly advise to use quicklisp as their packages and dependencies are all kept up-to-date and you don't have to download and install their current versions manually: https://www.quicklisp.org/beta/ It uses asdf under the hood but takes care of downloading and updating dependencies. For nowaday's Common Lisp use it is a must-have and makes life really easy compared to all the hassle 10 years ago... I'm on sbcl 1.4.8 and arch linux and everything works fine here. Once installed, put the directories with asdf files of non quicklisp stuff (like cm, cm-svg, svg-import-export, cm-foums, etc.) into ~/quicklisp/local-projects/ get rid of any previously installed asdf stuff and simply issue (ql:quickload "cm-svg") and it should take care of everything... > Permutation pattern looks good and very useful. Hope it makes it to > 'patterns.lisp'. I will put the permutation pattern in a new repo in the near future but I first need to sort out how to handle the doc issues mentioned in the previous post. -- Orm yourself Montag, den 23. Juli 2018 um 10:02:25 Uhr (-0700) schrieb Juan Reyes: > Hi Orm, > > > Same here I use CM-2.12 for the same reasons you are mentioning so (1+) > also. > > Permutation pattern looks good and very useful. Hope it makes it to > 'patterns.lisp'. > > However, any pointers on building on SBCL 1.4 Fedora-27 ?. > > Just tried to load it and ASDF is complaining about the Alexandria > package after: > > (require :sb-posix) > (load "cm.asd") > (asdf:load-system :cm) > > Previous cm2.asd file was giving several warnings in regards to updating > API: > > WARNING: > DEPRECATED-FUNCTION-WARNING: Using deprecated function > (ASDF/ACTION::BACKWARD-COMPATIBLE-DEPENDS-ON > :FOR-OPERATION > > #) -- please update your code to use a newer API. > > Thanks a lot!, > > -- Juan Reyes > > > >> > >> Yes, some of us still use CM2. +1 to keep posting Orm.? > >> > >> Although it refused to build the last time I tried it.? > >> I must try again, I'm presently using an older image. ? > > > > Let me know if you run into problems. As the svg code depends on xml > > libs from quicklisp, I'd suggest to use a recent lisp with quicklisp > > support. If you use sbcl (and jack) it gives you the opportunity to > > also use the realtime extensions. > > > > > > > > _______________________________________________ > Cmdist mailing list > Cmdist at ccrma.stanford.edu > https://cm-mail.stanford.edu/mailman/listinfo/cmdist From juanigrp at gmail.com Tue Jul 24 14:19:04 2018 From: juanigrp at gmail.com (Juan Reyes) Date: Tue, 24 Jul 2018 14:19:04 -0700 Subject: [CM] cm2: svg backend, perichmutation pattern In-Reply-To: <20180723175247.GA26900@T460s-orm> References: <20180722151826.GA23292@T460s-orm> <1532333738.8641.3.camel@orcon.net.nz> <20180723120030.GC30600@T460s-orm> <7c31350b-13cb-a567-04f0-97606262f667@ccrma.stanford.edu> <20180723175247.GA26900@T460s-orm> Message-ID: Thanks a lot Orm!. Got CM2 with CM-SVG working with your instructions, great work!. Need to get my hands on with quicklisp but with minor testing, looks to be working on Fedora 27 and SBCl 1.4.2-1. Count on me. CM2 still very useful. Best of all, -- Juan >> >> However, any pointers on building on SBCL 1.4 Fedora-27 ?. > > I strongly advise to use quicklisp as their packages and dependencies > are all kept up-to-date and you don't have to download and install > their current versions manually: > > https://www.quicklisp.org/beta/ > > It uses asdf under the hood but takes care of downloading and updating > dependencies. For nowaday's Common Lisp use it is a must-have and > makes life really easy compared to all the hassle 10 years ago... I'm > on sbcl 1.4.8 and arch linux and everything works fine here. > > Once installed, put the directories with asdf files of non quicklisp > stuff (like cm, cm-svg, svg-import-export, cm-foums, etc.) into > ~/quicklisp/local-projects/ > > get rid of any previously installed asdf stuff and simply issue > (ql:quickload "cm-svg") and it should take care of everything... > From Torsten.Anders at beds.ac.uk Wed Jul 25 02:26:46 2018 From: Torsten.Anders at beds.ac.uk (Torsten Anders) Date: Wed, 25 Jul 2018 09:26:46 +0000 Subject: [CM] cm2: svg backend, permutation pattern In-Reply-To: <20180722151826.GA23292@T460s-orm> References: <20180722151826.GA23292@T460s-orm> Message-ID: On 22 Jul 2018, at 16:18, Orm Finnendahl > wrote: I don't know if it makes any sense to announce it here, as I guess hardly anybody is using it. FYI, Common Music code without the full Common Music actually is also under other composition systems. A core part of Common Music 2, namely its pattern definitions, have been ported to OpenMusic by Anders Vinjar (http://repmus.ircam.fr/openmusic/libraries, https://forge.ircam.fr/p/omlibraries/downloads/639/). I took that OpenMusic library, stripped off all visual programming code again, and made sure it can be loaded with ASDF in a strait forward way, so that it can be used in other composition environments based on Common Lisp (https://github.com/tanders/cm-patterns). Specifically, I am using it in Opusmodus. It has been tested with Clozure CL (under Opusmodus), LispWorks (for PWGL) and SBCL. However, the code is still not as portable as the original Common Music source. Note that I tried some time ago to get the full Common Music 2 code base loaded with ASDF, but ran into various difficulties, and for use in other composition systems I only need the Common Music patterns anyway, so this seems to be a good compromise to me. Best, Torsten This email message uses productivity features of Mailbutler. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Torsten.Anders at beds.ac.uk Wed Jul 25 02:26:59 2018 From: Torsten.Anders at beds.ac.uk (Torsten Anders) Date: Wed, 25 Jul 2018 09:26:59 +0000 Subject: [CM] cm2: svg backend, permutation pattern In-Reply-To: <20180722151826.GA23292@T460s-orm> References: <20180722151826.GA23292@T460s-orm> Message-ID: <0DDBB056-9647-407E-ABFF-C0997D2A277A@beds.ac.uk> A non-text attachment was scrubbed... Name: PGPMIME Versions Identification Type: application/pgp-encrypted Size: 13 bytes Desc: PGP/MIME Versions Identification URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: encrypted.asc Type: application/octet-stream Size: 4337 bytes Desc: OpenPGP encrypted message.asc URL: From anders.vinjar at bek.no Fri Jul 27 11:39:54 2018 From: anders.vinjar at bek.no (anders.vinjar at bek.no) Date: Fri, 27 Jul 2018 20:39:54 +0200 Subject: [CM] cm2: svg backend, permutation pattern References: <20180722151826.GA23292@T460s-orm> Message-ID: <877elg4j5x.fsf@bek.no> Hi. T> https://forge.ircam.fr/p/omlibraries/downloads/639/). If you want to check this, please use the most recent upload: https://forge.ircam.fr/p/omlibraries/downloads/703/ (some bugfixes and leftovers from the previous versions). Fwiw, i use cm2 a lot (in recent version of lispworks and sbcl), using the asd includeded with the sources at sf.net: https://svn.code.sf.net/p/commonmusic/code/branches/cm2 sbcl version is "1.4.2-1" -anders From bil at ccrma.Stanford.EDU Tue Jul 31 04:19:44 2018 From: bil at ccrma.Stanford.EDU (bil at ccrma.Stanford.EDU) Date: Tue, 31 Jul 2018 04:19:44 -0700 Subject: [CM] Snd 18.6 Message-ID: Snd 18.6. clm: Kjetil added a method to the granulate generator to set the jitter amount. s7: changed make-shared-vector to make-subvector (Matlab terminology) added subvector?, subvector-position, subvector-vector added make-weak-hash-table, weak-hash-table? s7 is now thread-safe, I think. symbol-setter has been folded into setter. c-pointer-info|type|weak1|weak2 (the latter are "weak" values) reactive.scm (the old stuff.scm code rewritten). checked: sbcl 1.4.10 Thanks!: Kjetil Matheussen