<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> First off, I am by no means an expert. I've been using cm-incudine for about 4-5 months, so I am still learning a good portion of it. I haven't used much of Supercollider either. I have more of a background in Pure-data and pd-l2ork. I mainly use cm-incudine to do realtime composition with systems. Like, I make some code to output midi. <a moz-do-not-send="true" href="https://www.youtube.com/watch?v=INg7lqMifXY&t=234s">I have recently done a livestream working through a track I made in two hours using cm-incudine.</a> Maybe you can get an idea of the kinds of work I've been making with cm-incudine by watching some of that. What makes cm-incudine special, is it integrates cm 2.0 with incudine, which is a <a moz-do-not-send="true" href="http://incudine.sourceforge.net/">powerful synthesis engine in common lisp</a>. This allows you to use code from cm, to then output midi with incudine, giving you a robust realtime output, while still giving you the ability to output midi and .ly files. I've also used it to output OSC messages with lisp, allowing me to connect lisp programming with OSC. You could then send out values of a .csv file through OSC with just a simple (defun) and some (nth)s, for instance. Another note is that cm-incudine is not the current version of cm. The current version of cm uses a type of scheme to do the programming and looks like it has its own integrated development environment using juce, I think. I'm not exactly sure, as I don't use it, but it is quite different from cm-incudine, which uses and older version of cm that still used common lisp. I'd honestly be interested in hearing the history of common music and as to why everything changed so drastically if anybody on here knows. Based on the documentation of cm 2.0 and Notes from the Metalevel, it seems Heinrich Taube liked some of scheme's language more. This is just me guessing though, I don't actually know why cm 3.0 switched away from common lisp. The cool part of cm-incudine for me is being able to integrate other common lisp packages on top of it and having a rich access to the common lisp language, which I'm still learning. Orm Finnendahl, the person who introduced me to it (also the person who combined cm with incudine) showed me an <a moz-do-not-send="true" href="https://youtu.be/VCO1uSf5jE4">awesome live piece</a> he created using cm-incudine where everything was being handled with sbcl, including a qt gui the players are using (isn't that insane!?). Being able to use cl-collider with incudine is also appealing. Lastly, cm-incudine lets me stay in emacs to make music, and slime is fantastic. Hopefully this wasn't too long of a read and I hope this helps, Brandon Hale <div class="moz-cite-prefix">On 5/4/21 8:51 AM, Mario Lang wrote: </div> <blockquote type="cite" cite="mid:87r1imy845.fsf@blind.guru"> <pre class="moz-quote-pre" wrap="">Hi. This sparked my interest, as I have missed that CM has gained RT capabilities. As a non-GUI person, I played with Csound (early 90s), CM (around 2000) and SC (from 2003 onwards). Would you mind giving a short comparison of cm-incudine compared to SC? Or, if you have no SC experience, could you highlight what you particularily like about cm-incudine? I ask because I speak Lisp fluently, so CM is still an interesting option for me. I just left it behind since SC offered a much more interesting RT experience, and the custom language feels pretty concise. The last point is probably a strength and a weakness. sclang is a nice language, but it is also unique, which means almost no library reuse from other coders not involved in sound synthesis. BTW, there is also cl-collider, which I recently discovered any played with a little. I guess that is the main reason why I find it interesting to re-evaluate CM. Brandon Hale <a class="moz-txt-link-rfc2396E" href="mailto:bthaleproductions@gmail.com"><bthaleproductions@gmail.com></a> writes: </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Hello all, Have you ever wanted to use cm-incudine, but felt like it was too hard or too much work to install on your Arch Linux-based distro? Now you can install it with <a class="moz-txt-link-freetext" href="https://github.com/brandflake11/install-cm-incudine">https://github.com/brandflake11/install-cm-incudine</a> <a class="moz-txt-link-rfc2396E" href="https://github.com/brandflake11/install-cm-incudine"><https://github.com/brandflake11/install-cm-incudine></a>. This script will take you from zero to hero, installing emacs, slime, quicklisp, and all of the dependencies needed for cm-incudine. Hopefully this helps you install cm-incudine if you've ever been interested, but couldn't figure out all of the smaller bits. Feedback is welcome! Thank you very much for your time, Brandon Hale _______________________________________________ Linux-audio-user mailing list <a class="moz-txt-link-abbreviated" href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a> <a class="moz-txt-link-freetext" href="https://lists.linuxaudio.org/listinfo/linux-audio-user">https://lists.linuxaudio.org/listinfo/linux-audio-user</a> </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> </pre> </blockquote> </body> </html>