<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On 22 Jul 2018, at 16:18, Orm Finnendahl <<a href="mailto:orm.finnendahl@selma.hfmdk-frankfurt.de" class="">orm.finnendahl@selma.hfmdk-frankfurt.de</a>> wrote:<br class="">
<blockquote type="cite" class="">I don't know if it makes any sense to announce it here, as I guess hardly anybody is using it. </blockquote>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
</div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
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 (<a href="http://repmus.ircam.fr/openmusic/libraries" class="">http://repmus.ircam.fr/openmusic/libraries</a>,
<a href="https://forge.ircam.fr/p/omlibraries/downloads/639/" class="">https://forge.ircam.fr/p/omlibraries/downloads/639/</a>).</div>
<div class=""><br class="">
</div>
<div class="">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 (<a href="https://github.com/tanders/cm-patterns" class="">https://github.com/tanders/cm-patterns</a>).
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. </div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Torsten</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</div>
<img src="https://bowtie.mailbutler.io/tracking/hit/8983A8E0-B166-4453-9E92-0D1B1ECD5D1B/3FED3F95-0621-43E0-B2DF-4737B301A951/t.gif" align="left" width="0" height="0" style="width:0;height:0;border:0;" title="" alt="" id="MailbutlerTrackingPixel" class=""><!--How does Mailbutler’s Email Tracking Work?
We, Mailbutler GmbH, Belzigerstr. 69 , 10823 Berlin/Germany offer Mailbutler, a software extension (plugin) for the Apple Mail program, which, inter alia, enables mail senders to see when, where, how often and on which device the recipient has opened (read) an email. If the sender activates the email tracking for a specific email, Mailbutler includes a hidden image (also referred to as web-bug or 1-pixel image) with a unique mail-ID into the outgoing mail. Once the recipient views the email, the recipient’s mail client or web service sends a request to our server in order to load the hidden image. Our servers collect and store the mail-ID, IP address, email client information, device information and the date and time of such request. We pass on the date/time, IP address, email client information, device information and mail-ID to the Mailbutler software of the sender where it is linked to the specific email and enables the Mailbutler software to display the read date/time, IP address, email client information, device information and location based on the IP address.
What data is collected?
Through Mailbutler’s email tracking the sender obtains the information when the recipient has first opened the email. We, Mailbutler, only store the mail-ID together with the corresponding read date/time, device information and the recipient’s IP address. We do not collect further data. We are unable to link this information to an individual email address of the sender or recipient, since the mail-ID is linked to a specific email only locally at the device of the Mailbutler installation at the sender.
Who is responsible?
We do not collect information that can be attributed to an individual and therefore do not collect, process or use personal data. However, the sender of an email using Mailbutler’s email tracking functionality may collect, process and use personal data. It is the sender’s responsibility to ensure that the use of the email tracking functionality is in compliance with any laws applicable to the sender, in particular data protection laws. This may require the sender to inform the recipient about the tracking, to offer an opt-out or to obtain prior consent.
How can the Recipient avoid Email Tracking?
Recipients can configure their email client (e.g. Outlook) or web service (e.g. googlemail) so that by default images contained in emails are not loaded. Please see the configurations menu and manual of your email client or web service for details. Alternatively, you can contact the sender and object to any future email tracking. Please note that we, Mailbutler, can not deactivate email tracking for specific e-mail address since we have no access to information about the sender or recipient of tracked emails.
-->
<div id="MailbutlerSponsoredActions" class=""><br class="">
<span class="">This email message uses productivity features of <a style="color:#77a091;" href="https://www.mailbutler.io" class="">
<strong class="">Mailbutler</strong></a>.</span></div>
</body>
</html>