[CM] Fwd: CM's loop macro, issues/incompleteness of implementation?

Iain Duncan iainduncanlists at gmail.com
Sun Apr 19 08:30:23 PDT 2020

Thanks for the clarification Rick. My main goal is to make Scheme For Max
have an optional load layer that includes everything someone might want for
getting existing lisp computer music code working on S4M with minimal
adjustment. The way I have things working, it will be easy to turn that off
and run plain S7 if desired.  I had plans already for something quite
similar to CM's processes for Max, so I'm hoping I can make it client code
compatible (or nearly so) with CM eventually too. Ideally a user could take
CM code and run it with minimal adjustment in a Max host or on Max for
Live. We'll see how feasible that turns out to be! I'd also really like to
point people at Notes from the Metalevel as the best intro resource, it's
perfect for a someone who knows music but is new to lisp. Really well
written BTW, I love the book! :-)  So I'm planning on page in the docs with
details on what you can or can't do from the book direct in Scheme for Max,
and taking examples from Notes to make regression tests so I know which

With regard to sprouting processes, Max has a way for SDK functions to hook
into the global transport, so I'll try to rustle something up with that.
Great to hear it was added to Chicken too, which is on my learning list for
working with in a non-embedded context.

On Sun, Apr 19, 2020 at 8:20 AM Taube, Heinrich K <taube at illinois.edu>

> Begin forwarded message:
> *From: *Rick Taube <taube at illinois.edu>
> *Subject: **Re: [CM] CM's loop macro, issues/incompleteness of
> implementation?*
> *Date: *April 19, 2020 at 10:18:13 AM CDT
> *To: *Iain Duncan <iainduncanlists at gmail.com>
> Iain, the (loop …) macro that I implemented in grace’s s7  is a large
> subset of the full-blown common lisp loop facility.  (and I believe some
> years ago it was added to chicken scheme as some sort of add on package)
> im not exactly sure what you are trying to do by I doubt you are
> interested in cm’s processes or composition stuff because that would
> require juce/c++ support.
> but you should be able to take the version of loop i have in grace’s
> scheme files and drop it in "as is” in your s7/max environment.
> On Apr 19, 2020, at 9:58 AM, Iain Duncan <iainduncanlists at gmail.com>
> wrote:
> Thanks Rick. I'm a bit confused, because I see you quoting a message from
> Orm, but for some reason I don't see that message anywhere, so i'm not able
> to make sense of the thread properly. Are you saying that the loop macro is
> a complete implementation of Common Lisp's loop macro then, but a CM
> process is not?  I've gone through the loop chapter of Notes from the
> Metalevel, but don't know the CL implementation well enough to know if
> there is more that is missing.
> _______________________________________________
> 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/mailman/private/cmdist/attachments/20200419/750ed444/attachment.html>

More information about the Cmdist mailing list